SRTool User Page - Revision history

David Reyna: /* Overview of the SRTool Records */

2019-01-24T23:41:27Z

Overview of the SRTool Records

← Older revision		Revision as of 23:41, 24 January 2019
Line 62:		Line 62:
	Here is a picture of the high level SRTool record structure:		Here is a picture of the high level SRTool record structure:

			[[File:Records_Packages_under_SRTool.png\|border\|SRTool Record Structure]]

David Reyna: /* Overview of the SRTool Records */

2019-01-24T23:38:32Z

Overview of the SRTool Records

← Older revision		Revision as of 23:38, 24 January 2019
Line 62:		Line 62:
	Here is a picture of the high level SRTool record structure:		Here is a picture of the high level SRTool record structure:

	~~[[File:Records_under_SRTool.png\|border\|SRTool Record Structure]]~~

David Reyna at 09:24, 29 December 2018

2018-12-29T09:24:33Z

← Older revision		Revision as of 09:24, 29 December 2018
Line 2:		Line 2:

	This page summarizes the Security Response Tool (SRTool) user documentation.		This page summarizes the Security Response Tool (SRTool) user documentation.

	~~Parent Wiki page: [https://wiki.yoctoproject.org/wiki/Contribute_to_SRTool Contribute to SRTool]~~
	__FORCETOC__		__FORCETOC__
	<br/>		<br/>

David Reyna at 09:23, 29 December 2018

2018-12-29T09:23:55Z

← Older revision		Revision as of 09:23, 29 December 2018
Line 3:		Line 3:
	This page summarizes the Security Response Tool (SRTool) user documentation.		This page summarizes the Security Response Tool (SRTool) user documentation.

			Parent Wiki page: [https://wiki.yoctoproject.org/wiki/Contribute_to_SRTool Contribute to SRTool]
	__FORCETOC__		__FORCETOC__

	<br/>		<br/>
	== Goals ==		== Goals ==

David Reyna: /* Defect Record */

2018-12-29T05:15:44Z

Defect Record

← Older revision		Revision as of 05:15, 29 December 2018
Line 58:		Line 58:

	* A "Defect" is the representation of the organization’s defect (Jira, Bugzilla)		* A "Defect" is the representation of the organization’s defect (Jira, Bugzilla)
	* It ~~normally~~ connects to a CVE via an Investigation record and a Vulnerability record		* It connects to a CVE via the parent Investigation record and Vulnerability record

	=== Overview of the SRTool Records ===		=== Overview of the SRTool Records ===

David Reyna at 05:14, 29 December 2018

2018-12-29T05:14:24Z

@@ Line 30: / Line 30: @@
 ** <strong>The column filter</strong>: when you click on the 'cone' symbol in a column title you can select a filter based on that column's data
 ** At the bottom of each table you can set the page size and jump to diff pages
-* <strong>User Model</strong>: The SRTool used the Django User Access Model
+* <strong>User Model</strong>: The SRTool uses the Django User Access Model
 <br/>
@@ Line 66: / Line 63: @@
 Here is a picture of the high level SRTool record structure:
@@ Line 115: / Line 114: @@
 * The Products page shows the organization's products that are attached to the SRTool
 * Links are provided to view the product's Vulnerabilities, Investigations, and Defects

David Reyna: /* Overview of the SRTool Records */

2018-12-29T05:04:57Z

Overview of the SRTool Records

← Older revision		Revision as of 05:04, 29 December 2018
Line 65:		Line 65:
	=== Overview of the SRTool Records ===		=== Overview of the SRTool Records ===

			Here is a picture of the high level SRTool record structure:


	<br/>		<br/>

	== Usage Guide ==		== Usage Guide ==

David Reyna at 05:03, 29 December 2018

2018-12-29T05:03:56Z

Show changes

David Reyna: User documentation for the SRTool

2018-12-29T04:07:55Z

User documentation for the SRTool

New page

[[Category:SRTool]]

This page summarizes the Security Response Tool (SRTool) user documentation.

__FORCETOC__

 
== Goals ==

* A common system to track and share security issues, combining community CVE's </li>
* A simple yet flexible interface for reporting and exploring the security issues </li>
* A place to upload and share attachments, including patches, fixes, emails, and documents </li>
* The ability to generate accurate and up-to-date reports and exports</li>
** Status on a given CVE and its defects, for a specific product or for all affect products</li>
** Compliance reports on sensitive CVE's, for example the chain of events and who-knew-what-when</li>
** Status of each product, for the related CVE defects Compliance reports on sensitive CVE's, for example the chain of events and who-knew-what-when</li>
** Ability to easily export that data to spreadsheets and to the public CVE database </li>
* The ability to securely store embargoed CVE's and data, complete with user protection and data encryption</li>
* Tools to help manage the ongoing influx of CVE's (around 1000 per month) so that expert time is not wasted and crucial CVE's are not lost </li>
* In general, a managed and automated tool set based on open source to replace splintered email threads and brittle manual systems</li>

 
== Basic Introduction ==

* This demo's data set contains the integrated CVE, Defect, and Sustaining data for 'CVE-2015-*' to 'CVE-2018-*'
* The title bar "SRTool:Security Response Tool" will always link you back to the home page
* In tables there are three ways to adjust the data set, and they can be used separately and/or together to get the best results
** The search bar: most of the text fields are searchable. Enter a value (like 'meltdown'), all records that have that string in those fields will appear
** The column sort: all column titles that appear in blue can be used to sort using that column. Click a second time to reverse the sort
** The column filter: when you click on the 'cone' symbol in a column title you can select a filter based on that column's data
** At the bottom of each table you can set the page size and jump to diff pages
* The user access model is simulated in this demo
** By default you can see that you are logged in as "Guest" in the top right corner
** If you click to log-in you can become a system admin, and can see the hidden management data tables
** If you click again to log out, you will return to the 'Guest' account
* The top bar also includes general and page-specific tools actions, for example:
** Export: Generate and download an export or report
** New CVE or Vulnerability: Create a new custmer CVE, or create a new exploratory Vulnerability
** Fetch alt data: Fetch additional CVE data source data for a given CVE

 
== Basic Records Objects ==

=== CVE's ===
** The CVE page is based on the NIST public page, and includes the V3 and V2 severities information, download links, and CPE's
** There are tabs to see (a) the original NIST source data, (b) alternate CVE sources, and (c) SRTool edits (if added)
** At the top is a place for the internal tags to help lookups and track status
** At the top is a place to see the publishing state. It can include future dates, plus a "Publish Now" button
** The "New CVE" link createa a new custom local CVE record
** The "Fetch alt data" link adds Mitre, Debian, and other data to this CVE
** The "Export" link provides CVE specific reports

=== Vulnerabilities ===
** Vulnerability records track the overall status of CVE (or a group of tightly related CVE's)
** Multiple related CVE's can be attached
** Multiple Investigations can be attached, one per product
** Comments and attachments can be added by logged-in users (for traceability)
** Users can sign up for change notification emails
** Vulnerabilities can be public, or locked to an invitation-only list of users
** The "Edit Status ..." button allow changes to the fields like the status, priority, comments
** The "Create Notification..." button is for notifying owners of status changes for the record
** The "Delete" button is for deleting this record
** The "Add product ..." button is for attaching a product and creating a respective Investigation record
** The "New Vulnerabilities" link createa a new vulnerability record
** The "Export" link provides Vulnerability specific reports

=== Investigations ===
** Investigation records track the status of a CVE for a given product
** Multiple defect links can be attached
** Comments and attachments can be added by logged-in users
** Users can sign up for change notification emails
** Investigation can be public, or locked to a controlled list of users
** The "Edit Status ..." button allow changes to the fields like the status, priority, comments
** The "Create Notification..." button is for notifying owners of status changes for the record
** The "Delete" button is for deleting this record
** The "Export" link provides Investigation specific reports

=== Defects ===
** This table lists all of the defects being tracked by the Vulnerabilities and Investigations
** A quick status overview of the defects is provided
** A quick summary page per defect is provided, with a link to the actual defect

=== Products ===
** Products tracked in this tool
** Access to each product's Vulnerabilities, Investigations, and Defects

=== Package CPE's ===
** This table tracks the packages that have been identified as vulnerable
** It also maps this package to the affected CVE's, Vulnerabilities, Investigations, and finally the related defects
** This data can help assist in CVE triage and risk analysis

=== CWE's ===
** The 'Common Weakness Enumerations' (CWE) found in the vulnerable CVE records
** These fundamental weaknesses are also tracked in this table to the related CVE's