timb-machine / timb-machine/linux-malware

[Intel]: https://www.tarlogic.com/blog/how-to-attack-kerberos/

Open
#229 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

missing:tactics missing:tag:Non-persistentStorage missing:tag:T1005 missing:tag:T1021.002 missing:tag:T1027.002 missing:tag:T1048 missing:tag:T1057 missing:tag:T1059.006 missing:tag:T1070.004 missing:tag:T1071.001 missing:tag:T1083 missing:tag:T1491 missing:tag:T1546.004 missing:tag:T1558 missing:tag:T1560 missing:tag:T1567 missing:tag:T1573 missing:tag:T1590 new
Dominant language
HTML
Stars
1.2k
Forks
95
PR merge metrics
No merged PRs in 30d

Description

Area

Offensive techniques

Parent threat

No response

Finding

https://www.tarlogic.com/blog/how-to-attack-kerberos/

Industry reference

No response

Malware reference

No response

Actor reference

No response

Component

No response

Scenario

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Read the linked Tarlogic article first, then inspect how existing offensive-technique findings are represented in the repository. Determine the appropriate record and metadata for this Kerberos reference; done means the finding is documented consistently with comparable entries.

Written by the indexing model from the issue text.

Assessment

Domain
documentation, security
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.