• Aucun résultat trouvé

Security/Privacy Incident Management and Discovery: Opportunities for AI/HLT

N/A
N/A
Protected

Academic year: 2022

Partager "Security/Privacy Incident Management and Discovery: Opportunities for AI/HLT"

Copied!
1
0
0

Texte intégral

(1)

Security/Privacy Incident Management and Discovery: Opportunities for AI/HLT

Jessica Staddon

Google Inc., USA jessica.staddon@gmail.com

Keynote Abstract

The field of security/privacy incident management has grown with the increase in cybersecurity threats. It is an area of focus for technology providers, standards bodies and regulators. Incident management is also a challenging area for practitioners and has a high-rate of burnout. I’ll talk about opportunities for AI/HLT-based automation to im- prove the incident management process for practitioners and how AI/HLT can drive a better understanding of incident patterns, and potentially enable better policies, regulations and privacy discourse. This talk will emphasize user needs and open problems.

Biography

Jessica is a Research Scientist at Google and an Adjunct Associate Professor of Computer Science at NC State. At Google she leads research for enterprise security and ana- lytics products. Previously she was an area manager at Xe- rox PARC, and a research scientist at Bell Labs and RSA Labs. Her interests include usable security and privacy tools, trends in privacy-related attitudes and methods for measur- ing and predicting privacy-related behaviors, attitudes and risks. She serves regularly on the program committees of ACM and IEEE sponsored security/privacy conferences and is on the editorial boards of the Journal of Computer Secu- rity, IEEE Security Privacy Magazine and the International Journal of Information and Computer Security. Jessica holds a PhD in Mathematics from U. C. Berkeley.

Références

Documents relatifs

• The use of Description Logic (DL) ontologies for modeling and for constructing applications is well understood [9]. • The use of OWL annotations to capture

The complete cases were filtered, this correspond to the cases where an incident begins with the initial status Accepted – In Progress and ends with one of the following final

For the 843 incidents that are not handled within the KPI when the total resolution time is considered, but are handled when the time in the status “Wait –

[r]

Support teams, organizations, and function divisions which have responsibility to most of the ping pong behaviours (incident management process) Through the same way, we

We listed all support teams with the number of times the support teams used the sub status “Wait – User” versus the number of times the support teams were involved in any

Since lexographic method is the least demanding for expert information about the degree of preference for partial indicators, it is advisable to choose the lexographic method in

In the next section, we will describe a framework for limiting the effects of cyber attacks (incident response) in the time, space and data domains.. 4 A practical framework