Add content for detection strategies
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- html
- Domain
- content
Research direction
Start with the unchecked checklist items for the website: remove Data Sources and add Detection Strategies to the Random Page list. Then review the LinkById stixtests entry point and the search and navigation changes already described. Done means the remaining website behavior works, while Excel and release-note support is coordinated with mitreattack-python issue 188.
Written by the indexing model from the issue text.
Description
Add relevant pages to the website to incorporate new detection strategies.
- Update the bottom of Technique pages to link to the new detection strategies (@adpare)
- Create overview pages for (@clemiller)
- Detection Strategies (url: /detectionstrategies/)
- Analytics (url: /analytics/)
- Data Components (url: /datacomponents/)
- Create individual pages for (@clemiller)
- Detection Strategies (url: /detectionstrategies/DET)
- Data Components (url: /datacomponents/DC)
- Update navbar (@clemiller)
- Remove Data Source pages
- Add Detections, with a submenu for Detection Strategies, Analytics, and Data Components
- Remove Data Sources from "Random Page" list
- Add Detection Strategies to "Random Page" list
- Update LinkById
stixteststo support DC/DS schema changes (@clemiller) - Make sure search functionality works for new objects
- Make sure the Excel files have the three new object types. This will need to be addressed in the mitreattack-python library (issue)
- Make sure the release notes are generated correctly with Detection Strategies, Analytics, and Data Components. This will need to be addressed in mitreattack-python as well.
This preview from the July 15, 2025 blog post could be incorporated into a Detection Strategy page.
- Dominant language
- HTML
- Stars
- 588
- Forks
- 174
- Avg merge
- 3d 11h
- Merged PRs (30d)
- 2
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mitre-attack/attack-website
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
mitre-attack/attack-website#628 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
mitre-attack/attack-website#626 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
mitre-attack/attack-website#596 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
mitre-attack/attack-website#571 · 2 comments · 1 reaction ·
-
[Accessibility] Navbar logo missing alt text causing WCAG violationMay be free again @jondricek claimed this 223 days ago, and no pull request is open. Open
mitre-attack/attack-website#563 · 1 assignee ·
All issues in mitre-attack/attack-website
Similar issues
-
3 star needs images needs review showcase
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
[Author] @roschinskyOpenauthor-page claim-verified
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
shanselman/TinyToolTown#823 · 5 comments ·
Maintainers usually reply within 7 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
521xueweihan/HelloGitHub#3790 ·
-
check:passed streams:add
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
e2b-dev/awesome-ai-agents#1646 ·
Maintainers usually reply within 1 day