Common Weakness Enumeration

CWE Glossary Definition

Name of Your Organization:

Ambionics Security

Web Site:

www.ambionics.io

Compatible Capability:

Ambionics Security

Capability home page:

https://www.ambionics.io

Product Accessibility <CR_2.4>

Provide a short description of how and where your capability is made available to your customers and the public (required):

Ambionics Security provides an offensive and continuous web security assessment service delivered via a cloud-based platform publicly available for customers with a valid subscription.

Map Currency Indication <CR_6.1>

Describe how and where your capability indicates the most recent CWE content used to create or update its mappings (required):

During Ambionics Security assessment each detected vulnerability is reported in real time to the customer. Vulnerability details are available on Ambionics Security Portal. One of these details is the "Category" which is the CWE ID assigned to the vulnerability. This field is a link to the official CWE description.

For example, the "Category" for a SQL Injection vulnerability will be "CWE-89" directly linked to https://cwe.mitre.org/data/definitions/89.html

Map Currency Update Approach <CR_6.2>

Indicate how often you plan on updating the mappings to reflect the current CWE content and describe your approach to keeping reasonably current with the CWE content when mapping them to your repository (recommended):

All vulnerabilities are detected and managed by Ambionics Security team. Our experts will manually assign the right CWE to each vulnerability before publishing details and alerting the customer. This process insures the accuracy of information provided in the vulnerability description. So, there is no need for an update process.

MAP CURRENCY UPDATE TIME <CR_6.3>

Describe how and where you explain to your customers the timeframe they should expect an update of your capability’s mappings to reflect newly available CWE content (required):

See <CR_6.2>.

CWE AND COMPATIBILITY DOCUMENTATION <CR_5.1>

Provide a copy, or directions to its location, of where your documentation describes CWE and CWE compatibility for your customers (required):

The category of vulnerability is based on CWE (Common Weakness Enumeration): https://cwe.mitre.org/

Within Ambionics Security Portal, every vulnerability is directly linked to the CWE website for customers to obtain more details about the CWE category.

DOCUMENTATION OF FINDING ELEMENTS USING CWE IDENTIFIERS <CR_5.2>

Provide a copy, or directions to its location, of where your documentation describes the specific details of how your customers can use CWE identifiers to find the individual security elements within your capability’s repository (required):

Within Ambionics Security Portal, in the "Vulnerabilities" panel, customers can filter vulnerabilities by "Category" (CWE) with:

The CWE drop-down list which includes CWE ID of all detected vulnerabilities

The Search text box in which customers can enter a CWE ID as a search string

DOCUMENTATION OF FINDING CWE IDENTIFIERS USING ELEMENTS <CR_5.3>

Provide a copy, or directions to its location, of where your documentation describes the process a user would follow to find the CWE identifiers associated with individual security elements within your capability’s repository (required):

Within Ambionics Security Portal, in the "Vulnerabilities" panel, customers can view the list of detected vulnerabilities with the following columns: ID, Asset, Title, Severity, Discovered, Remediation, Status, Category and Type. The "Category" column is the CWE-ID of the vulnerability. Customers can also find the CWE-ID in the detailed description of the vulnerability.

FINDING TASKS USING CWE IDENTIFIERS <CR_A.3.1>

Give detailed examples and explanations of how a user can locate tasks in the tool by looking for their associated CWE identifier (required):

Our experts will manually assign the right CWE to each vulnerability they detected on customer’s assets before publishing details and alerting the customer. Within Ambionics Security Portal, in the "Vulnerabilities" panel, customers can filter vulnerabilities by "Category" (CWE) with the CWE drop-down list and the Search text box.

FINDING CWE IDENTIFIERS USING ELEMENTS IN REPORTS <CR_A.3.2>

Give detailed examples and explanations of how, for reports that identify individual security elements, the tool allows the user to determine the associated CWE identifier for the individual security elements in the report (required):

Within Ambionics Security Portal, in the "Vulnerabilities" panel, each vulnerability is directly linked to the CWE website for customers to obtain more details about the CWE category.

GETTING A LIST OF CLAIMED CWE IDENTIFIER COVERAGE <CR_A.3.3>

Give detailed examples and explanations of how a user can obtain a listing of all of the CWE identifiers that the owner claims the tool is effective at locating in software (required):

Vulnerabilities are detected and managed by Ambionics Security team. So, our experts could manually detect or validate all kinds of vulnerability.

ELECTRONIC DOCUMENT FORMAT INFO <B.3.1>

Provide details about the different electronic document formats that you provide and describe how they can be searched for specific CWE-related text (required):

Ambionics Security provides assessment results within a web portal. In the "Vulnerabilities" panel, each vulnerability description is directly linked to the CWE website. Customers can filter vulnerabilities by "Category" (CWE) with the CWE drop-down list and the Search text box.

Vulnerabilities can be exported in PDF or CSV format. The exported file includes the "Category" (CWE-ID). Programs typically used to view these formats have built-in search capabilities.

ELECTRONIC DOCUMENT LISTING OF CWE IDENTIFIERS <CR_B.3.2>

If one of the capability’s standard electronic documents only lists security elements by their short names or titles provide example documents that demonstrate how the associated CWE identifiers are listed for each individual security element (required):

Within Ambionics Security Portal, in the "Vulnerabilities" panel, customers can view the list of detected vulnerabilities with the following columns: ID, Asset, Title, Severity, Discovered, Remediation, Status, Category and Type. The "Category" column displays the CWE-ID of the vulnerability.

The CWE-ID is provided for each vulnerability in exported PDF and CSV file.

FINDING ELEMENTS USING CWE IDENTIFIERS THROUGH THE GUI <CR_B.4.1>

Give detailed examples and explanations of how the GUI provides a "find" or "search" function for the user to identify your capability’s elements by looking for their associated CWE identifier(s) (required):

Within Ambionics Security Portal, in the "Vulnerabilities" panel, vulnerability listing can be sorted and filtered by "Category" (CWE-ID). Customers can filter vulnerabilities with:

The CWE drop-down list which includes CWE ID of all detected vulnerabilities

The Search text box in which customers can enter a CWE ID as a search string

GUI ELEMENT TO CWE IDENTIFIER MAPPING <CR_B.4.2>

Briefly describe how the associated CWE identifiers are listed for the individual security elements or discuss how the user can use the mapping between CWE identifiers and the capability’s elements, also describe the format of the mapping (required):

Within Ambionics Security Portal, every vulnerability is associated with a "Category" (CWE-ID) in the GUI (web portal). The "Category" is directly linked to the CWE website.

GUI EXPORT ELECTRONIC DOCUMENT FORMAT INFO <CR_B.4.3>

Provide details about the different electronic document formats that you provide for exporting or accessing CWE-related data and describe how they can be searched for specific CWE-related text (recommended):

Vulnerabilities can be exported in PDF or CSV format. The exported file includes the "Category" (CWE-ID).

STATEMENT OF COMPATIBILITY <CR_2.11>

Have an authorized individual sign and date the following Compatibility Statement (required):

"As an authorized representative of my organization I agree that we will abide by all of the mandatory CWE Compatibility Requirements as well as all of the additional mandatory CWE Compatibility Requirements that are appropriate for our specific type of capability."

Name: Eric Detoisien

Title: CEO

STATEMENT OF ACCURACY <CR_3.4>

Have an authorized individual sign and date the following accuracy Statement (recommended):

"As an authorized representative of my organization I agree that we will abide by all of the mandatory CWE Compatibility Requirements as well as all of the additional mandatory CWE Compatibility Requirements that are appropriate for our specific type of capability."

Name: Eric Detoisien

Title: CEO

STATEMENT ON FALSE-POSITIVES AND FALSE-NEGATIVES <CR_B.2.10> and/or <CR_B.3.7>

FOR TOOLS AND SERVICES ONLY — Have an authorized individual sign and date the following statement about your tools efficiency in identification of security elements (required):

"As an authorized representative of my organization I agree that we will abide by all of the mandatory CWE Compatibility Requirements as well as all of the additional mandatory CWE Compatibility Requirements that are appropriate for our specific type of capability."

Name: Eric Detoisien

Title: CEO