mitre-attack / mitre-attack/attack-website
URLs are inconsistent
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 588
- Forks
- 174
- Avg merge
- 13d 4h
- Merged PRs (30d)
- 2
Description
- Problem
URLs to the same technique, software, mitigation, or group page are inconsistent.
- Detail
URLs to the same object are inconsistent. For example,
/techniques/T1595/(inhrefattributes inanchortags)/techniques/T1595/index.html(inindex.jsonused in ATT&CK object search)
Both URLs lead us to the same object (the same web content).
There are many incosistent URL expressions in ATT&CK, such as the example above.
If there is no reason, I would like to suggest unifying the them into a single URL format as shown in the solution section below.
- Solution
I would go for something like "/techniques/T1595/" with "/" and without "index.html" at the end.
That is what you get when you click the links in the ATT&CK pages.
As for 'without "index.html"', the ATT&CK pages are currently static,
but they might be generated dynamically in the future.
It would be safe not to specify "index.html", to be prepared for dynamic HTML generation.
- Additional improvement
Not in this repo, but ATT&CK STIX 2 JSON file has URLs like "/technique/T1595" in its external_references.
I believe that they should be consistent with URLs in this repo.
When the standard is set, I will raise an issue for the ATT&CK STIX 2 JSON file.
Contributor guide
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.
Research direction
Start by locating the anchor href attributes and index.json entries that reference ATT&CK objects. Normalize equivalent URLs to the trailing-slash form without index.html, then verify that links and object-search results still resolve to the same pages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- web-dev
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100