Statements (56)
| Predicate | Object |
|---|---|
| gptkbp:instance_of |
gptkb:security
|
| gptkbp:aftermath |
public awareness campaigns
security audits regulatory changes penetration testing cybersecurity frameworks financial penalties class action lawsuits reputation damage data breach response plans increased scrutiny of tech companies increased demand for cybersecurity professionals increased cybersecurity investments user education initiatives cyber insurance policies user data protection laws data breach notifications laws enhanced privacy policies government regulations on data protection monitoring services offered to users |
| gptkbp:behavior |
passwords
security questions email addresses |
| gptkbp:consequences |
gptkb:Roman_settlement
lawsuits |
| gptkbp:customer_feedback |
rebranding efforts
acquisition by Verizon |
| gptkbp:data_type |
financial information
personal information user activity logs |
| gptkbp:first_appearance |
gptkb:2016
|
| https://www.w3.org/2000/01/rdf-schema#label |
Yahoo Data Breach
|
| gptkbp:impact |
user trust
|
| gptkbp:investigates |
gptkb:FBI
gptkb:SEC |
| gptkbp:is_affected_by |
3 billion accounts
|
| gptkbp:production_company |
gptkb:Yahoo
|
| gptkbp:public_reaction |
gptkb:media_coverage
increased awareness of security risks user backlash |
| gptkbp:related_event |
gptkb:Equifax_Data_Breach
gptkb:Facebook_Data_Breach gptkb:Target_Data_Breach |
| gptkbp:response_time |
3 years
|
| gptkbp:security |
user notifications
password resets improved security measures outdated software lack of two-factor authentication poor encryption |
| gptkbp:technique |
hacking
|
| gptkbp:type |
gptkb:terrorism
|
| gptkbp:year |
gptkb:2013
|
| gptkbp:bfsParent |
gptkb:Facebook_Data_Breach
gptkb:Marriott_Data_Breach |
| gptkbp:bfsLayer |
6
|