Cyber Risk Analytics - Parsed Cost Data
Based on client feedback that the cost of a data breach is important for analysis purposes and each cost element may need separate treatment, we are pleased to communicate a recent enhancement to Export and API that offers the ability to more easily parse both the Court Costs and the Non Court Costs data fields.
For our export clients, we have added two new fields that you can elect to enable that will allow you to easily parse the Court Cost and Non-Court Cost data from the exported .csv file. You will need to select the parsed data fields:
By selecting the parsed version of the cost fields, you will get the following results with a vertical bar (sometimes called a ‘pipe’) between each cost item.
Note that court costs are parsed into two columns Court Cost - Amount and Court Costs - Name. Non-court costs are parsed into three columns, Amount, Type, and Currency. Also note that court cost currency data does not have an associated parsed field as it is always assumed to be USD.
If you would like to enable this new parsed option, please let us know and we will enable it for you at no cost.
For our CRA APIs clients - here is an example of the output in API data (JSON format):
If you would like to enable the API option, please let us know and we will enable it for you at no cost to you. We will need to coordinate a date because once enabled, the data will immediately appear.
Cyber Risk Analytics - New People Impacted Data
RBS has recently exposed our data on the number of people affected by a breach. This will be helpful when the number of people affected by a breach differs from the number of records exposed. This new data field is available for API and export
Incident 52714 is a perfect example of the new people data field.
VulnDB - Modified_Product API enhancement
For clients digesting VulnDB data using APIs who want to maintain an updated database of all products, we have enhanced our modified_products API to surface products whenever there are material changes to the product record
- Prior API call behavior - the VulnDB API call for modified_products returned data only when the name of the VulnDB Product was changed.
- Enhanced/New API behavior
- The base modified_products API call now returns a record whenever any of the following fields are updated:
- Product name
- Vendor name
- Vendor ID
- CPE name
- Version name
- Version ID
- Product Description
- Here is the base call and results of the updated API - https://vulndb.cyberriskanalytics.com/api/v1/products/modified_products?start_date=2020-10-29&size=200
"name": "Fujitsu M10-1"
"name": "Fujitsu M10-4"
"name": "Fujitsu M10-4S"
"name": "Fujitsu M12-1"
"name": "Fujitsu M12-2"
"name": "Fujitsu M12-2S"
"name": "Compact HMI"
- In order to see additional data values for each Product you need to pass include_detail=true. Note that the detail provides the full record of that Product regardless of what fields were updated - https://vulndb.cyberriskanalytics.com/api/v1/products/modified_products?start_date=2020-10-29&size=200&include_detail=true
"name": "Compact HMI",
Alpine Linux Coverage
For client’s that subscribe to our Advanced Data Analytics, RBS monitors select Linux distributions and we continue to add new ones. Recently, we began monitoring and reporting on Alpine Packages.
The following Linux distributions are currently monitored and reported on for vulnerabilities:
- Oracle Linux
- Red Hat
Be on the lookout for future additions!
Speaking of new additions, there’s something we’re very excited to share with you. Coming soon, the Risk Based Security Platform brings together the market leading vulnerability and data breach intelligence you already know us for, in a single, unified environment, complete with fresh visuals and a number of powerful new features that we think you’re going to find really useful.
You can subscribe to updates on the The Platform on our website, and if you have questions or would like to learn more, get in touch with our support team. We would be pleased to give you a preview of what the future holds.