|
|
Name of Your Organization:
Beyond Security Ltd.
Web Site:
www.beyondsecurity.com
www.securiteam.com
Compatible Capability:
Automated Scanning Service - Service Provider Platform
Capability home page:
http://www.beyondsecurity.com/AutomatedScanningServices_ProviderPlatform.htm
1) 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):
CVE compatibility is found throughout the system in several places:
- The report generated provides a mapping for each vulnerability with the corresponding CAN/CVE(s)
- The user can search the vulnerability test database to specific CVE and will be provided with the appropriate test, and vise versa.
4) 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):
Follow the link below to enter a demo account used for Customer Service interface available for ISPs:
https://sp.automatedscanning.com/DemoISP/CustomerZone/The username is: demo
And the password is: demo43Once logged in the system, click the Current sample report stored. The CVE mapping is done for each vulnerability in the report.
*Note: In order to do a complete check of the database, please contact aviram@beyondsecurity.com for date and NDA details.
5) 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 (recommended):
Each time a new version is released, all new entries are added to our database. Old candidates are removed.
6) 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 a newly released CVE version (recommended):
The Automated Scanning machines are updated automatically from our website 3 times a day. The CVE mapping is done as a part of these updates.
7) 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):
Documentation for the CVE compatibility can be found at:
http://www.beyondsecurity.com/CVE.htm
8) 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):
Documentation for the CVE compatibility can be found at:
http://www.beyondsecurity.com/CVE.htm
9) 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):
Every test has a 'CVE' field specified wherever it appears in the report or in the database
10) Documentation Indexing of CVE-Related Material <CR_4.4>
If your documentation includes an index, provide a copy of the items and resources that you have listed under "CVE" in your index. Alternately, provide directions to where these "CVE" items are posted on your web site (recommended):
The automated Scanning GUI include a vulnerability index. The index is searchable and fully documented.
11) Candidates Versus Entries Indication <CR_6.1>
If CVE candidates are supported or used, explain how you indicate that candidates are not accepted CVE entries (required):
This explanation appears along with the CVE description documentation.
12) Candidates Versus Entries Explanation <CR_6.2>
If CVE candidates are supported or used, explain where and how the difference between candidates and entries is explained to your customers (recommended):
This explanation appears along with the CVE description documentation.
13) Candidate to Entry Promotion <CR_6.3>
If CVE candidates are supported or used, explain your policy for changing candidates into entries within your capability and describe where and how this is communicated to your customers (recommended):
Whenever CVE decides to change the status of a CAN to CVE the status changes in the test reference.
14) Candidate and Entry Search Support <CR_6.4>
If CVE candidates are supported or used, explain where and how a customer can find the explanation of your search function's ability to look for candidates and entries by using just the YYYY-NNNN portion of the CVE names (recommended):
Search by YYYY-NNNN is available by searching CVE/CAN.
15) Search Support for Promoted Candidates <CR_6.5>
If CVE candidates are supported or used, explain where and how a customer can find the explanation of your search function's support for retrieving the CVE entry for a candidate that is no longer a candidate (recommended):
The user can find reference in the CVE documentation page: http://www.beyondsecurity.com/CVE.htm
16) Candidate Mapping Currency Indication <CR_6.6>
If CVE candidates are supported or used, explain where and how you tell your users how up-to-date your candidate information is (recommended):
Candidates and CVE version are part of the documentation explaining CVE.
Type-Specific Capability Questions
Service Questions
23) 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):
The user can request a list of tests that were performed, and their corresponding CVE names. Also, whenever vulnerabilities are discovered, the report that is sent to the user includes the CVE names of each vulnerability found.
24) 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):
The report that is sent to the user includes explicit reference to the relevant CVE names.
25) Service's Product Utilization Details <CR_A.3.4>
Please provide the name and version number of any product that the service allows users to have direct access to if that product identifies security elements (recommended):
The service may make use of Beyond Security's Automated Scanning Appliance version 2.10.
31) 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):
We support HTML, PDF and CSV outputs - all three formats are searchable and
thus the user can simply search for a specific CVE or CAN in the report
32) 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 document types contain security descriptions and CVE numbers
33) 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):
Whenever the vulnerability's name and summary appears, the applicable CVE number appears
below the description (if one exists for this vulnerability)
34) 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):
The GUI is web based, the user can use CTRL+F to open a search box
and search for the vulnerability's name and CVE number.
Both vulnerability name and CVE number appear in the vulnerabilities list
35) 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):
The vulnerability name appears together with the CVE number, and thus
the mapping between the name and CVE number are clear and evident
36) 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 CVE-related data and describe how they can be searched for specific CVE-related text (recommended):
The output formats are HTML, PDF and CSV. In all three document types the
vulnerabilities that are present appear along with the CVE numbers.
37) 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: Aviram Jenik
Title: CEO
38) 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: Aviram Jenik
Title: CEO
39) 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: Aviram Jenik
Title: CEO