Common Weakness Enumeration

CWE Glossary Definition

Name of Your Organization:

High-Tech Bridge SA

Web Site:

http://www.htbridge.com/

Compatible Capability:

ImmuniWeb

Capability home page:

https://www.htbridge.com/immuniweb/

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):

ImmuniWeb is publicly available on ImmuniWeb Portal, https://portal.htbridge.com, for any person who has a web browser and connection to the Internet.

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):

Upon ImmuniWeb security assessment completion customer receives assessment report in PDF format. In the report all the detected vulnerabilities are presented in a table format with various technical fields. All the vulnerabilities without exception have the following field:

Vulnerability CWE-ID: CWE-ID-HERE

This field is clickable and leads to the appropriate section of our CWE Vulnerability Glossary.

For example SQL injection vulnerability (CWE-89) will point here: https://www.htbridge.com/vulnerability/sql-injection.html

Cross-Site Scripting (XSS) vulnerability (CWE-79) will point here: https://www.htbridge.com/vulnerability/cross-site-scripting.html

These pages are also accessible by short aliases:
https://www.htbridge.com/CWE-89
https://www.htbridge.com/CWE-79

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):

ImmuniWeb security assessment process is managed by High-Tech Bridge security auditors and therefore each vulnerability is being manually verified and validated by human before being added to ImmuniWeb report.

Such QA procedure assures accuracy of the security assessment report and makes report update mechanism useless.

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):

Please refer to <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):

We believe that the best and the most appropriate resource with CWE documentation that can provide our customers with the most complete, accurate and latest information about CWE — is the official CWE website. Each ImmuniWeb security assessment report contains a hyperlink to it.

CWE-Compatibility will be described on ImmuniWeb web page, https://www.htbridge.com/immuniweb/, also providing links to the official CWE website.

Nevertheless, we develop, support and regularly update CWE Vulnerability Glossary, https://www.htbridge.com/vulnerability/, which contains detailed information about each CWE-ID that is detected by ImmuniWeb.

Each CWE Glossary entry generally includes the following sections:

• Description
• Potential impact
• Attack patterns
• Affected software
• Exploitation Examples
• Severity and CVSS Scoring
• Mitigations
• Vulnerability Remediation Techniques and Examples
• References
• Latest Related HTB Security Advisories

The last section contains numerous examples from High-Tech Bridge Security Research Lab, https://www.htbridge.com/advisory/, which is also CWE-Compatible since 2012.

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):

As already mentioned above, ImmuniWeb security assessment report in delivered in PDF format. ImmuniWeb customers can use default built-in Adobe Reader (or any other PDF document reading software) search function to search vulnerabilities in the report by CWE-ID. This feature is obvious and does not require specific documentation.

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):

Same answer as in <CR_5.2>.

Type-Specific Capability Questions

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):

Each vulnerability in ImmuniWeb security assessment report is presented in a table that has the following fields:

• CVE-ID
• CWE-ID
• CVSSv2 Base Score

These fields make obvious which security tests were performed by ImmuniWeb.

A complete list of detectable security vulnerabilities is available on ImmuniWeb webpage, https://www.htbridge.com/immuniweb/technical-specifications.html#detected_vulnerabilities, where they are classified by CWE-ID.

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):

In ImmuniWeb security assessment report for each detected security vulnerability there is field in the table named "Vulnerability CWE-ID" that contains CWE-ID. Please see <CR_6.1> for more details.

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):

All the CWE-IDs that ImmuniWeb SaaS detects are publicly available on ImmuniWeb web page: https://www.htbridge.com/immuniweb/technical-specifications.html#detected_vulnerabilities.

Please also see for more information about our CWE Vulnerability Glossary that contains detailed description of each CWE-ID that ImmuniWeb detects.

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):

ImmuniWeb security assessment report is provided in PDF format only.

Built-in search functions of PDF document reading software can be easily used to search vulnerabilities by specific CWE-ID.

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):

ImmuniWeb report is well structured, and each table with vulnerability description is located on a separate page of the PDF document. As already mentioned above, each vulnerability description is presented in a table format that always contain highly visible "Vulnerability CWE-ID" field that also contains a hyperlink to our CWE Vulnerability Glossary.

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):

It depends on the software that user uses to read ImmuniWeb security assessment report that is delivered in PDF format.

For Adobe Reader it’s enough just to press "CTRL+F" key combination to get a search input box, which can be used to search vulnerabilities by CWE-ID or any other search parameter.

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):

The question is answered in details in <CR_B.4.1>.

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: Ilia Kolochenko

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: Ilia Kolochenko

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: Ilia Kolochenko

Title: CEO