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

[MITRE] Common Attack Pattern Enumeration and Classification (CAPEC™) 3.2 connector #344

Closed
2xyo opened this issue Apr 9, 2020 · 1 comment
Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@2xyo
Copy link
Contributor

2xyo commented Apr 9, 2020

Problem to Solve

I would like to map techniques employed by adversaries to exploit known weaknesses in cyber-enabled capabilities. (e.g., SQL Injection, XSS, Session Fixation, Clickjacking)

The Common Attack Pattern Enumeration and Classification (CAPEC™) is the de facto standard to meet this need.

Proposed Solution

Additional Information

  • https://capec.mitre.org/about/index.html
  • https://capec.mitre.org/about/attack_comparison.html
  • https://capec.mitre.org/about/use_cases.html
    • Application Testing
      • [UC-1] Security Test Case Identification and Construction: CAPEC assists testers to construct systematic and real-world attack scenarios.
      • [UC-2] Red Teaming Template Creation: Attack Patterns provide an excellent resource for defining penetration testing templates for red teams.
    • Analysis
      • [UC-3] Incident Response and Threat Analysis | Knowledge of the attack patterns enables responders to better align mitigation strategies.
      • [UC-4] Compliance Analysis | Support measuring compliance with industry standards and guidelines.
      • [UC-5] Malware Behavior Analysis | Relate the behavior of malicious code to attack patterns.
      • [UC-6] Threat Characterization and Attribution | Provide assistance in characterizing and eventually supporting attribution of threats from observed attack instances.
      • ...
    • Threat Modeling
      • [UC-12] Threat Modeling: Mapping relevant threats and likely actions against the specific attack surface of the software to place threat information in an objective and actionable context.
    • ...
@SamuelHassine SamuelHassine transferred this issue from OpenCTI-Platform/opencti Apr 22, 2021
@SamuelHassine SamuelHassine added the feature use for describing a new feature to develop label Jan 31, 2022
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label May 20, 2022
@SamuelHassine SamuelHassine added this to the Release 5.3.0 milestone May 20, 2022
@2xyo
Copy link
Contributor Author

2xyo commented May 21, 2022

Thanks @SamuelHassine :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

No branches or pull requests

2 participants