Weakness - Cisco XDR APIs

{"type":"model","meta":{"id":"/apps/pubhub/media/cisco-xdr-api-docs/fa9197522b1e6452b6dbfc472555dcc7ceeb71bd/2c61df32-bc97-34af-969d-a2ce06b8e459","info":{"title":"CTIA","description":"A Threat Intelligence API service\n\n This API provides a mechanism for making Judgements on the Disposition\n of Observables, which are then distilled into a final Verdict. A\n Disposition is a statement regarding the malicious, or otherwise,\n nature of an Observable.\n\n The Judgements can be grouped into Indicators, which can be associated\n with Campaigns, Actors and TTPs. Feedback can be given on specific\n Judgements, indicating agreement or disagreement, or clarification.\n\n When an Observable with a malicious Verdict is seen, it can be recorded as\n a Sighting, and the Relations that Observable had with other Observables can\n be recorded as well.\n\n We support a pre-defined set of Observable Types. Each Observable Type has a\n specific form of natural identifier, its ID, which is almost always\n the default way it is represented when observed in the wild.\n\n * Ipv4/IPv6 -- 192.168.1.1\n * Domain/Hostname -- foo.com, www.bar.com\n * SHA256 -- the sha256 checksum of a file, or other data blob\n * MD5 -- the md5 checksum of a file, or other data blob\n * SHA1 -- the sha1 checksum of a file, or other data blob\n * URL -- A minimal form of the URL\n\n The Verdict is derived from all of the Judgements on that Observable which\n have not yet expired. The highest priority Judgement becomes the\n active verdict. If there is more than one Judgement with that\n priority, than Clean disposition has priority over all others, then\n Malicious disposition, and so on down to Unknown.\n\n \u003ca href='/doc/README.md'\u003eCTIA Documentation\u003c/a\u003e","contact":{"name":"Cisco Security Business Group -- Advanced Threat ","url":"http://github.com/threatgrid/ctia","email":"cisco-intel-api-support@cisco.com"},"license":{"name":"All Rights Reserved","url":""},"version":"2.24.0"},"security":[{"oAuth2":["integration:read","private-intel:read","profile:read","inspect:read","users:read","invite:read","enrich:read","oauth:read","response:read","global-intel:read","ao:read","playbook:read"]}],"tags":[{"name":"Actor","description":"Actor operations"},{"name":"Asset","description":"Asset operations"},{"name":"Asset Mapping","description":"Asset Mapping operations"},{"name":"Asset Properties","description":"Asset Properties operations"},{"name":"Attack Pattern","description":"Attack Pattern operations"},{"name":"Campaign","description":"Campaign operations"},{"name":"Casebook","description":"Casebook operations"},{"name":"COA","description":"COA operations"},{"name":"Event","description":"Events operations"},{"name":"Feed","description":"Feed operations"},{"name":"Incident","description":"Incident operations"},{"name":"Indicator","description":"Indicator operations"},{"name":"Judgement","description":"Judgement operations"},{"name":"Malware","description":"Malware operations"},{"name":"Relationship","description":"Relationship operations"},{"name":"Sighting","description":"Sighting operations"},{"name":"Target Record","description":"Target Record operations"},{"name":"Tool","description":"Tool operations"}],"x-parser-conf":{"serverConfig":"select","overview":{"markdownPath":"reference/private-intel/overview.md","uri":"private-intel-ctia-api-guide"},"disableAuthEditing":true,"exampleAsDefault":true,"oAuth2":{"clientId":"client-546e34fc-c6bf-4951-ac69-f6d7987a7814","clientSecret":"MYw4_E_tBdFwUwrX6WFYKVD5LQrG2k7XrJ5J046wWE0s1gAKCxJ8VA","proxyEnabled":false},"meta":{"useProxy":true}},"openapi":"3.0.1","servers":[{"url":"https://private.intel.amp.cisco.com"}],"securitySchemes":{"oAuth2":{"type":"oauth2","flows":{"clientCredentials":{"tokenUrl":"https://visibility.amp.cisco.com/iroh/oauth2/token","scopes":{"telemetry":"Collect application data for analytics","integration:read":"Manage your modules","private-intel:read":"Access Private Intelligence","admin":"Provide admin privileges","cognitive":"Cognitive Integration","profile:read":"Get your profile information","inspect:read":"Extract Observables and data from text","asset":"Access and modify your assets","event":"Read IROH Events","feedback":"Submit Customer Feedback","sse":"SSE Integration. Manage your Devices.","registry":"Manage registry entries","users:read":"Manage users of your organization","investigation":"Perform threat analysis investigation","invite:read":"Invite users into your organization","casebook":"Access and modify your casebooks","playbook:read":"Access and modify your playbooks","orbital":"Orbital Integration.","enrich:read":"Query your configured modules for threat intelligence","oauth:read":"Manage OAuth2 Clients","vault":"Grants access to Module Vaults","response:read":"List and execute response actions using configured modules","notification":"Receive notifications from integrations","global-intel:read":"Access AMP Global Intelligence","webhook":"Manage your Webhooks","ao:read":"AO Integration."}}}}}},"spec":{"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"background_details":{"type":"string","description":"Information that is relevant but not related to the nature of the weakness itself.","example":"string"},"paradigms":{"type":"array","description":"Applicable paradigms.","example":[{"prevalence":"Often","name":"string"}],"items":{"type":"object","properties":{"prevalence":{"type":"string","description":"Defines the different regularities that guide the applicability of platforms.","example":"Often","enum":["Undetermined","Sometimes","Often","Rarely"]},"name":{"type":"string","description":"Paradigm name (Client Server, Mainframe)","example":"string"}},"additionalProperties":false,"example":{"prevalence":"Often","name":"string"},"$$ref":"#/components/schemas/Paradigm"}},"abstraction_level":{"type":"string","description":"Refers to the level of abstraction or granularity used to describe the weakness. It helps to categorize the vulnerability based on the level of detail provided.","example":"Base","enum":["Variant","Class","Base","Compound"]},"architectures":{"type":"array","description":"Applicable architectures.","example":[{"prevalence":"Often","name":"string","class":"Embedded"}],"items":{"type":"object","properties":{"prevalence":{"type":"string","description":"Defines the different regularities that guide the applicability of platforms.","example":"Often","enum":["Undetermined","Sometimes","Often","Rarely"]},"name":{"type":"string","description":"Architecture name (ARM, x86, ...)","example":"string"},"class":{"type":"string","description":"Class of architecture","example":"Embedded"}},"additionalProperties":false,"example":{"prevalence":"Often","name":"string","class":"Embedded"},"$$ref":"#/components/schemas/Architecture"}},"schema_version":{"type":"string"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"alternate_terms":{"type":"array","description":"Indicates one or more other names used to describe this weakness.","example":[{"term":"string","description":"string"}],"items":{"type":"object","properties":{"term":{"type":"string","description":"The actual alternate term.","example":"string"},"description":{"type":"string","description":"Provides context for the alternate term by which this weakness may be known.","example":"string"}},"additionalProperties":false,"example":{"term":"string","description":"string"},"$$ref":"#/components/schemas/AlternateTerm"}},"likelihood":{"type":"string","description":"Likelihood of exploit.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"type":{"type":"string","description":"The fixed value weakness","example":"weakness","enum":["weakness"]},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"functional_areas":{"type":"array","description":"Identifies the functional area of the software in which the weakness is most likely to occur.","example":["Authentication"],"items":{"type":"string"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"modes_of_introduction":{"type":"array","description":"Information about how and when a given weakness may be introduced.","example":[{"phase":"Architecture and Design","note":"string"}],"items":{"type":"object","properties":{"phase":{"type":"string","description":"Identifies the point in the software life cycle at which the weakness may be introduced.","example":"Architecture and Design"},"note":{"type":"string","description":"Provides a typical scenario related to introduction during the given phase.","example":"string"}},"additionalProperties":false,"example":{"phase":"Architecture and Design","note":"string"},"$$ref":"#/components/schemas/ModeOfIntroduction"}},"structure":{"type":"string","description":"Defines the structural nature of the weakness.","example":"Chain","enum":["Chain","Simple","Composite"]},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"notes":{"type":"array","description":"Provides any additional comments about the weakness.","example":[{"type":"Applicable Platform","note":"string"}],"items":{"type":"object","properties":{"schema_version":{"type":"string"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"content":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"note_class":{"type":"string","example":"keyword"},"type":{"type":"string","example":"note","enum":["note"]},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"author":{"type":"string","example":"string"},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"related_entities":{"type":"array","example":[{"entity_type":"string","entity_id":"string"}],"items":{"required":["entity_id","entity_type"],"type":"object","properties":{"entity_type":{"type":"string","example":"string"},"entity_id":{"type":"string","description":"A URI leading to an entity.","example":"string"}},"additionalProperties":false,"example":{"entity_type":"string","entity_id":"string"},"$$ref":"#/components/schemas/NoteRelatedEntity"}}},"additionalProperties":false,"description":"A Note is intended to convey informative text to provide further context and/or to provide additional analysis not contained in the Objects, assigning Text/content to the Object the Note relates to Notes can be created by anyone (not just the original object creator).\nFor example, an analyst may add a Note to a Campaign object created by another organization indicating that they've seen posts related to that Campaign on a hacker forum.","example":{"schema_version":"1.3.18","revision":10,"content":"string","note_class":"keyword","type":"note","source":"string","external_ids":["string"],"external_references":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"author":"string","source_uri":"string","language":"string","id":"string","tlp":"green","timestamp":"2016-01-01T01:01:01.000Z","related_entities":[{"entity_type":"string","entity_id":"string"}]},"$$ref":"#/components/schemas/Note"}},"common_consequences":{"type":"array","description":"Refers to the typical or expected negative effects that can result from exploiting the weakness. This could include anything from unauthorized access to data, denial of service, system crashes or other things.","example":[{"scopes":["Access Control"],"impacts":["Alter Execution Logic"],"likelihood":"High","note":"string"}],"items":{"type":"object","properties":{"scopes":{"type":"array","description":"Identifies the security property that is violated.","example":["Access Control"],"items":{"type":"string"}},"impacts":{"type":"array","description":"Describes the technical impact that arises if an adversary succeeds in exploiting this weakness.","example":["Alter Execution Logic"],"items":{"type":"string"}},"likelihood":{"type":"string","description":"How likely the specific consequence is expected to be seen relative to the other consequences.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"note":{"type":"string","description":"Additional commentary about a consequence.","example":"string"}},"additionalProperties":false,"example":{"scopes":["Access Control"],"impacts":["Alter Execution Logic"],"likelihood":"High","note":"string"},"$$ref":"#/components/schemas/Consequence"}},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"detection_methods":{"type":"array","description":"Identifies methods that may be employed to detect this weakness, including their strengths and limitations.","example":[{"method":"Architecture or Design Review","description":"string","effectiveness":"High","effectiveness_notes":"string"}],"items":{"type":"object","properties":{"method":{"type":"string","description":"Identifies the particular detection method being described.","example":"Architecture or Design Review"},"description":{"type":"string","description":"Provides some context of how this method can be applied to a specific weakness.","example":"string"},"effectiveness":{"type":"string","description":"How effective the detection method may be in detecting the associated weakness.","example":"High"},"effectiveness_notes":{"type":"string","description":"Provides additional discussion of the strengths and shortcomings of this detection method.","example":"string"}},"additionalProperties":false,"example":{"method":"Architecture or Design Review","description":"string","effectiveness":"High","effectiveness_notes":"string"},"$$ref":"#/components/schemas/DetectionMethod"}},"operating_systems":{"type":"array","description":"Applicable operating systems.","example":[{"prevalence":"Often","name":"string","version":"string","cpe_id":"string","class":"Android"}],"items":{"type":"object","properties":{"prevalence":{"type":"string","description":"Defines the different regularities that guide the applicability of platforms.","example":"Often","enum":["Undetermined","Sometimes","Often","Rarely"]},"name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"version":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"cpe_id":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"class":{"type":"string","description":"Class of Operating System.","example":"Android"}},"additionalProperties":false,"example":{"prevalence":"Often","name":"string","version":"string","cpe_id":"string","class":"Android"},"$$ref":"#/components/schemas/OperatingSystem"}},"affected_resources":{"type":"array","description":"Identifies system resources that can be affected by an exploit of this weakness.","example":["CPU"],"items":{"type":"string"}},"languages":{"type":"array","description":"Applicable Languages.","example":[{"prevalence":"Often","name":"string","class":"Assembly"}],"items":{"type":"object","properties":{"prevalence":{"type":"string","description":"Defines the different regularities that guide the applicability of platforms.","example":"Often","enum":["Undetermined","Sometimes","Often","Rarely"]},"name":{"type":"string","description":"Language name (Clojure, Java, ...)","example":"string"},"class":{"type":"string","description":"Class of language.","example":"Assembly"}},"additionalProperties":false,"example":{"prevalence":"Often","name":"string","class":"Assembly"},"$$ref":"#/components/schemas/Language"}},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"potential_mitigations":{"type":"array","description":"Describes potential mitigations associated with a weakness.","example":[{"description":"string","phases":["Architecture and Design"],"strategy":"Attack Surface Reduction","effectiveness":"Defense in Depth","effectiveness_notes":"string"}],"items":{"type":"object","properties":{"description":{"type":"string","description":"A description of this individual mitigation including any strengths and shortcomings of this mitigation for the weakness.","example":"string"},"phases":{"type":"array","description":"Indicates the development life cycle phase during which this particular mitigation may be applied.","example":["Architecture and Design"],"items":{"type":"string"}},"strategy":{"type":"string","description":"A general strategy for protecting a system to which this mitigation contributes.","example":"Attack Surface Reduction"},"effectiveness":{"type":"string","description":"Summarizes how effective the mitigation may be in preventing the weakness.","example":"Defense in Depth"},"effectiveness_notes":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"}},"additionalProperties":false,"example":{"description":"string","phases":["Architecture and Design"],"strategy":"Attack Surface Reduction","effectiveness":"Defense in Depth","effectiveness_notes":"string"},"$$ref":"#/components/schemas/Mitigation"}},"technologies":{"type":"array","description":"Applicable technologies.","example":[{"prevalence":"Often","name":"string"}],"items":{"type":"object","properties":{"prevalence":{"type":"string","description":"Defines the different regularities that guide the applicability of platforms.","example":"Often","enum":["Undetermined","Sometimes","Often","Rarely"]},"name":{"type":"string","description":"Technology name (Web Server, Web Client)","example":"string"}},"additionalProperties":false,"example":{"prevalence":"Often","name":"string"},"$$ref":"#/components/schemas/Technology"}}},"additionalProperties":false,"description":"A mistake or condition that, if left unaddressed, could under the proper conditions contribute to a cyber-enabled capability being vulnerable to attack, allowing an adversary to make items function in unintended ways.","example":{"description":"string","background_details":"string","paradigms":[{"prevalence":"Often","name":"string"}],"abstraction_level":"Base","architectures":[{"prevalence":"Often","name":"string","class":"Embedded"}],"schema_version":"1.3.18","revision":10,"alternate_terms":[{"term":"string","description":"string"}],"likelihood":"High","type":"weakness","source":"string","external_ids":["string"],"short_description":"string","title":"string","external_references":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"functional_areas":["Authentication"],"source_uri":"string","modes_of_introduction":[{"phase":"Architecture and Design","note":"string"}],"structure":"Chain","language":"string","id":"string","notes":[{"type":"Applicable Platform","note":"string"}],"common_consequences":[{"scopes":["Access Control"],"impacts":["Alter Execution Logic"],"likelihood":"High","note":"string"}],"tlp":"green","detection_methods":[{"method":"Architecture or Design Review","description":"string","effectiveness":"High","effectiveness_notes":"string"}],"operating_systems":[{"prevalence":"Often","name":"string","version":"string","cpe_id":"string","class":"Android"}],"affected_resources":["CPU"],"languages":[{"prevalence":"Often","name":"string","class":"Assembly"}],"timestamp":"2016-01-01T01:01:01.000Z","potential_mitigations":[{"description":"string","phases":["Architecture and Design"],"strategy":"Attack Surface Reduction","effectiveness":"Defense in Depth","effectiveness_notes":"string"}],"technologies":[{"prevalence":"Often","name":"string"}]},"$$ref":"#/components/schemas/Weakness","title":"Weakness"}}