|
|
Name of Your Organization:
Patchadvisor, Inc.
Web Site:
http://www.patchadvisor.com
Compatible Capability:
PA Alert!
Capability home page:
http://alert.Patchadvisor.com
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):
The service is made available to our customers via a web site on the Internet.
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):
In the Help > CVE menu it shows the current CVE version being used.
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):
Once a new CVE version is released we intend to have added new CAN and CVE numbers and remove old CAN entries within 10 working days. In addition as new vulnerabilities are identified daily we add appropriate CAN numbers daily.
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):
Our customers are emailed when we have confirmed our compliance to a new CVE version. In addition, the Help>CVE menu of the website will indicate that the new version is being used.
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):
Within the Help>CVE section of the website details are provided regarding CVE and our CVE compatibility.
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):
Within the Help>CVE section of the website details are provided on how customers can search using CVE/CAN identifiers. Each vulnerability has a CVE/CAN identifier if appropriate. In addition the database can be searched using CVE/CAN identifiers in the Database>Search>CVE menu.
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):
Each vulnerability has a primary PatchAdvisor-Sintelli identifier (SID) but also has a CVE/CAN identifier if appropriate.
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):
All documentation regarding CVE is provided in the Help>CVE menu.
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):
The CAN- prefix is used for all candidates to differentiate them from CVE entries which have the CVE- prefix.
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):
The CVE help file explains the difference between CVE and CAN entries. The explanation is based upon "The CVE Naming Process."
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):
If a CAN entry becomes a CVE entry then the entry is subsequently changed. Customers can infer the change by viewing the vulnerability entry.
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):
The database>search functionality also a customer to search our vulnerability database. To search for CAN/CVE entries the CVE search type must be selected. To search for CVE entries the criteria must be in the format CVE-YYYY-NNNN, and to search for candidates the search criteria must be CAN-YYYY-NNNN.
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):
If a customer searches for a CVE candidate entry eg CAN-YYYY-NNNN and the entry has been promoted to a CVE then no search result will be returned. The customer then must search in the format CVE-YYYY-NNNN in order to find the entry.
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):
Candidate entries are updated on a daily basis and this is explained in the CVE>Help section. The time and date a candidate number is updated is not provided to customers.
Type-Specific Capability Questions
26) 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):
For each vulnerability associated to external sources such as CVE ID, Buqtraq ID, Cert ID, Nessus ID, advisories provided. Additionally, using the Database>Search>CVE specific CVE names can be searched for.
29) 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):
The CVE name is prominently displayed in the top right of the screen in the item "CVE ID."
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):
Only html document formats are provided which can be searched using the Search or Find button of the web browser.
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):
We do not list elements by their short names. CVE names are shown in the top right of the screen.
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):
Press Database and select the Search option. Under Search Type select "CVE ID". Then enter either a CAN or CVE id eg CAN-YYYY-NNNN or CVE-YYYY-NNNN. Finally press search. Results will be displayed. Clicking on the results will show details on the entry.
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):
On the top right of each element the CVE ID is displayed, which relates to our primary identifier for the element (SID-ID). We do not provide to our customers a downloadable mapping between CVE entries and our repository. This mapping has been provided to MITRE in the cvemap.csv file.
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):
Data is sent in Text, HTML or PDF format and can be searched for CVE-related text by either using the search functionality of a web browser (HTML format), the search functionality of the text editor (Text format) or the find functionality of a PDF reader (e.g. Acrobat) for the PDF format.
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: Jeff Fay
Title: President
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: Jeff Fay
Title: President