https://api.bitsighttech.com/ratings/v1/news
Get recent data breach news.
Parameters
See query parameters for details on the following parameters:
limit
(Default: ↻100
)sort
offset
Parameter | Values |
---|---|
show_on_dashboard [Query] Specify if the News page should be displayed in the Portfolio Dashboard. |
[Boolean]
|
Example Request
curl https://api.bitsighttech.com/ratings/v1/news -u api_token:
Example Response
{ […] "results":[ […] { "date":"2019-06-15", "date_created":"2019-06-16", "event_type":"Phishing", "event_type_description":"An attack in which fraudulent email is used to masquerade as an employee or legitimate contact", "severity":1, "text":"This company fell victim to a phishing attack, which compromised the personal information of an unknown number of individuals.", "preview_url":"https://www.examplesource.com/news/security/example-company-discloses-breach/", "company":{ "guid":"888888aa-88a8-8a88-8a8a-a888a88888a8", "name":"Example Company" } } ] }
Response Attributes
Field | Description | |
---|---|---|
dateString [ YYYY‑MM‑DD ] |
The date when the news article was published and when the event will begin to impact the rating. | |
date_createdString [ YYYY‑MM‑DD ] |
The date when the event was logged into the Bitsight Security Ratings Platform. | |
event_typeString |
A designation that categorizes the data breach (incident type). |
|
event_type_descriptionString |
An account of what occurred, in accordance with the incident type. | |
severityInteger |
The severity of the event, which is determined by the number of points lost from the rating. Values: |
|
textString |
An account of what occurred. | |
preview_urlString |
The URL web address of the source news article. | |
companyObject |
Contains the details of the affected company. | |
guidString [ entity_guid ] |
The unique identifier of the affected company. | |
nameString |
The name of the affected company. |
- October 19, 2023: Redefined Security Incident severity and linked to resource.
- July 10, 2023: Removed PDF.
- July 17, 2019: Published.
Feedback
0 comments
Please sign in to leave a comment.