Common Weakness Enumeration

CWE Glossary Definition

Name of Your Organization:

Oversecured Inc

Web Site:

https://oversecured.com/

Compatible Capability:

Oversecured

Capability home page:

https://oversecured.com/

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

The SaaS-based vulnerability scanner is located on https://oversecured.com/. Users must create an account in order to scan APK files they want. Oversecured provides five free scans to all new users.

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

The list of vulnerabilities is located on https://oversecured.com/vulnerabilities. The user should open a category in order to see the description and CWE identifiers.

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

The link will stay the same, but new vulnerabilities will be appended to the list. Usually it happens at least once a month.

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

https://oversecured.com/vulnerabilities, each vulnerability category contains a reference to a 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):

https://oversecured.com/vulnerabilities. The scanner analyses Android app source codes and outputs found vulnerabilities with Oversecured-provided categories, descriptions and appropriate CWE identifiers.

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

https://oversecured.com/vulnerabilities

DOCUMENTATION INDEXING OF CWE-RELATED MATERIAL <CR_5.4>

If your documentation includes an index, provide a copy of the items and resources that you have listed under "CWE" in your index. Alternately, provide directions to where these "CWE" items are posted on your web site (recommended):

https://oversecured.com/vulnerabilities

Type-Specific Capability Questions

FINDING TASKS USING CWE IDENTIFIERS <CR_A.2.1>

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

The service (tool) doesn't allow to scan for a specific category of vulnerabilities, or for a single task. It scans a mobile application to detect all known vulnerabilities. It gives to the user the scan report with the detected vulnerabilities and their CWE references. Example can be found in https://content.oversecured.com/oversecured_sample_report.pdf (it's a bit outdated, currently all vulnerabilities contain at least one reference to a CWE identifier), category `Theft of arbitrary files`

FINDING CWE IDENTIFIERS USING ELEMENTS IN REPORTS <CR_A.2.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):

See answer for the previous question. Those items are located under the found vulnerability when a scan report is exported to a PDF. When users learn a report using the service (example https://oversecured.com/scan/info/8fe0acaa-cb64-49df-ad5b-a5766222401e), they should click (i) button for a category in the statistics block to get CWE identifiers.

GETTING A LIST OF CLAIMED CWE IDENTIFIER COVERAGE <CR_A.2.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):

https://oversecured.com/vulnerabilities, the list is available only to a specific vulnerability category

GETTING A LIST OF CWE IDENTIFIERS ASSOCIATED WITH TASKS <CR_A.2.6>

Give detailed examples and explanations of how a user can obtain a listing of all of the CWE identifiers that are associated with the tool’s tasks (recommended):

https://oversecured.com/vulnerabilities

SELECTING TASKS WITH A LIST OF CWE IDENTIFIERS <CR_A.2.7>

Describe the steps and format that a user would use to select a set of tasks by providing a file with a list of CWE identifiers (recommended):

That's impossible for that tool. The user cannot define a specific task.

SELECTING TASKS USING INDIVIDUAL CWE IDENTIFIERS <CR_A.2.8>

Describe the steps that a user would follow to browse, select, and deselect a set of tasks for the tool by using individual CWE identifiers (recommended):

That's impossible for that tool. The user cannot define a specific task.

NON-SUPPORT NOTIFICATION FOR A REQUESTED CWE IDENTIFIER <CR_A.2.9>

Provide a description of how the tool notifies the user that a task associated with a selected CWE Identifier cannot be performed (recommended):

That's impossible for that tool. The user cannot define a specific task.

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

Scan reports are available only online and can be exported to PDFs.

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

They are never listed in a short way. Oversecured always shows the full description with references to CWE categories.

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

We don't have a GUI option for the service. It's available only online, the list is available on https://oversecured.com/vulnerabilities

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

CWE identifiers are provided in the scan report. In case if it's an online report, it will be shown for a detected vulnerability category by clicking on the (i) button. In PDFs descriptions with CWE identifiers are duplicated for each vulnerability and available under the trace of the vulnerable code.

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: Sergey Toshin

Title: Founder

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 and to the best of my knowledge, there are no errors in the mapping between our capability's Repository and the CWE identifiers our capability reports, and those CWE identifiers are as specific as possible within the available CWE repository."

Name: Sergey Toshin

Title: Founder

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 and to the best of my knowledge, normally when our capability reports a specific security element, it is generally correct and normally when an event occurs that is related to a specific security element our capability generally reports it."

Name: Sergey Toshin

Title: Founder