Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ATT&CK ICS, D3FEND & ISTG #3

Open
scriptingxss opened this issue Oct 24, 2023 · 3 comments
Open

ATT&CK ICS, D3FEND & ISTG #3

scriptingxss opened this issue Oct 24, 2023 · 3 comments
Labels
question Further information is requested

Comments

@scriptingxss
Copy link
Collaborator

Folks have asked about relation to adjacent frameworks like ATT&CK ICS, D3FEND (links below) and overlap of them with ISTG.

https://attack.mitre.org/techniques/ics/
https://attack.mitre.org/matrices/ics/
https://d3fend.mitre.org/

Curious if the project has a perspective to share and if there are opportunities to partner or collaborate on mappings in the future?

@scriptingxss scriptingxss added the question Further information is requested label Oct 24, 2023
@scriptingxss
Copy link
Collaborator Author

Similar to MASTG, ATT&CK mobile provides an adversarial perspective with known tools, tactics, procedures, and detections from known events or malicious software. Although these are valuable to organizations, verification standards and testing guides offer assurance lifecycle practices incorporated into security programs producing high quality software from manufacturers of IoT.

Based off the mitigations for ICS, ATT&CK might focus on an enterprise adversary perspective with operational mitigations and detections. There are mitigations that allude to software security practices such as validate user input and code signing.

@scriptingxss
Copy link
Collaborator Author

@rockhoppersec, curious on your perspective :)

@rockhoppersec
Copy link
Collaborator

As @scriptingxss already mentioned, the frameworks above are very useful tools, but for slightly different subjects and audiences.

While these frameworks work very well when it comes to assessing attack vectors against, for example, enterprise networks, the ISTG is intended to provide a more hands-on approach to testing IoT devices. While there are definitely overlaps, the ISTG will focus more on technologies and attack vectors tailored to testing individual devices, thereby providing a different perspective.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants