Name of Your Organization:

TrustSign Certificadora Digital Comércio & Serviços em Tecnologia e Segurança da Informação Ltda

Web Site:

http://www.trustsign.com.br

Compatible Capability:

Selos de Segurança

Capability home page:

http://www.trustsign.com.br/canais/solucoes/selosseguranca.asp

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

You can contact us through our www.trustsign.com.br website and the sales team will give you the access to the Security Dashboard.

Map Currency Indication <CR_5.1>

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

TrustSign verifies the updates and the news entered on the CVE newsletters and changelog available in https://cassandra.cerias.purdue.edu/CVE_changes/ so the updates are carried through as soon as they are available.

Map Currency Update Approach <CR_5.2>

Indicate how often you plan on updating the mappings to reflect new CVE versions and describe your approach to keeping reasonably current with CVE versions when mapping them to your repository (required):

TrustSign verifies the updates and the news entered on the CVE newsletters and changelog available in https://cassandra.cerias.purdue.edu/CVE_changes/. Of this form are carried through incremental updates always that they will be available.

Map Currency Update Time <CR_5.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 CVE content (required):

We use our newsletter to inform all customers about new CVE-IDs. If a client needs an update because of new CVE-ID(s), we will act in less than 24 hours to ensure the security of the network.

Map Content Selection Criteria <CR_5.4>

Describe the criteria used for determining the relevance of a given CVE Identifier to your Capability (required):

TrustSign’s Research Team reviews the vulnerabilities and the CVE Identifiers are added to Selos de Segurança if the identifier descriptions and security bulletins matches the vulnerability check.

Map Currency Update Mechanism <CR_5.4>

Describe the mechanism used for reviewing CVE for content changes (required):

TrustSign’s Selos de Segurança only includes links to the CVE Identifier and not CVE entry content. Mappings are provided by TrustSign’s Research Team and audited both internally and from customer product use. Any discrepancies in CVE references are typically resolved in 24 hours.

Map Content Source <CR_5.5>

Describe the source of your CVE content (required):

TrustSign’s Research Team monitors the SecurityFocus Bugtraq (BID) database and the Open Source Vulnerability Database (OSVDB), understanding that each database has strengths in tracking mail lists, change logs, vendor advisories, and more.

CVE and Compatibility Documentation<CR_4.1>

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

CVE is an organization responsible for the standardization of the vulnerabilities and other expositions in the security guard of the information. The CVE Compatibility is important to our customers. TrustSign contributes together to the CVE for the standardization of new vulnerabilities.

Documentation of Finding Elements Using CVE Names <CR_4.2>

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

Our report has one hyperlink with the number of CVEID where the customer is transferred directly to the CVE Web site through the following address format:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-XXXX-YYYY.

Example: If our report points to the CVE-2002-1088 vulnerability, the report will point the link to
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2002-1088.

Documentation of Finding CVE Names Using Elements <CR_4.3>

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

Each security problem individually has its CVE name, which is supplied by the CVE project once they are assigned.

Service Coverage Determination Using CVE Names <CR_A.3.1>

Give detailed examples and explanations of the different ways that a user can use CVE names to find out which security elements are tested or detected by the service (i.e. by asking, by providing a list, by examining a coverage map, or by some other mechanism) (required):

A sample could be analyzed in our report at the Security Dashboard.

Finding CVE Names in Service Reports Using Elements <CR_A.3.2>

Give detailed examples and explanations of how, for reports that identify individual security elements, the user can determine the associated CVE names for the individual security elements in the report (required):

In this case the user wants to classify some vulnerability with a CVE number, he will have to contact us through the email: marcos.ferreira@in2sec.com, or with our responsible in the report delivery.

Finding Online Capability Tasks Using CVE Names <CR_A.4.1>

Give detailed examples and explanations of how a "find" or "search" function is available to the user to locate tasks in the online capability by looking for their associated CVE name or through an online mapping that links each element of the capability with its associated CVE name(s) (required):

The TrustSign Selos de Segurança reports are distributed in a HTML format that includes CVE names that are available on Security Dashboard. These can be searched using the native search capabilities of the browser.

Finding CVE Names Using Online Capability Elements <CR_A.4.2>

Give detailed examples and explanations of how, for reports that identify individual security elements, the online capability allows the user to determine the associated CVE names for the individual security elements in the report. (required):

All reports and vulnerability details include relevant CVE data, so an online mapping function of TrustsSign vulnerability plugins to CVE entries is not required.

Online Capability Element to CVE Name Mapping <CR_A.4.3>

If details for individual security elements are not provided, give examples and explanations of how a user can obtain a mapping that links each element with its associated CVE name(s), otherwise enter N/A (required):

1. Login to Security Dashboard
2. Select "Reports"
3. Select "Vulnerability Reports"
4. Select "Technical Report"
5. All vulnerabilities with associated CVE names are listed.

Electronic Document Format Info <CR_B.3.1>

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

The document that contains all the information is available throughout our Security Dashboard, and the customer can use the search system of the browser.

Electronic Document Listing of CVE Names <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 CVE names are listed for each individual security element (required):

All vulnerability is completely described in our reports, and it presents the problem, the description, the solution and the CVE number for later research of the detected vulnerability. The example can be verified in our Security Dashboard.

Electronic Document Element to CVE Name Mapping <CR_B.3.3>

Provide example documents that demonstrate the mapping from the capability’s individual elements to the respective CVE name(s) (recommended):

All vulnerability is completely described in our reports, and it presents the problem, the description, the solution and the CVE number for later research of the detected vulnerability. The example can be verified in our Security Dashboard.

Finding Elements Using CVE Names 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 CVE name(s) (required):

For any detected vulnerability, if there is one or more CVE entries associated with it, they will be listed in the vulnerability details. The user can use the browser search function to identify the CVE name that is a direct link to the CVE Web site, for example: http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2003-0109.

GUI Element to CVE Name Mapping <CR_B.4.2>

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

All vulnerabilities listed have the CVE-ID listed the vulnerability details. See the screen shot in CR_B.4.1, above.

Statement of Compatibility <CR_2.7>

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 CVE Compatibility Requirements as well as all of the additional mandatory CVE Compatibility Requirements that are appropriate for our specific type of capability."

Name: Marcos A. Ferreira Jr.

Title: Network Security Specialist

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 CVE entries our capability identifies."

Name: Marcos A. Ferreira Jr.

Title: Network Security Specialist

Statement on False-Positives and False-Negatives <CR_A.2.8 and/or CR_A.3.5>

FOR TOOLS 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: Marcos A. Ferreira Jr.

Title: Network Security Specialist