Indexing AI Risks with Incidents, Issues, and Variants
원문 초록
Two years after publicly launching the AI Incident Database (AIID) as a collection of harms or near harms produced by AI in the world, a backlog of "issues" that do not meet its incident ingestion criteria have accumulated in its review queue. Despite not passing the database's current criteria for incidents, these issues advance human understanding of where AI presents the potential for harm. Similar to databases in aviation and computer security, the AIID proposes to adopt a two-tiered system for indexing AI incidents (i.e., a harm or near harm event) and issues (i.e., a risk of a harm event). Further, as some machine learning-based systems will sometimes produce a large number of incidents, the notion of an incident "variant" is introduced. These proposed changes mark the transition of the AIID to a new version in response to lessons learned from editing 2,000+ incident reports and additional reports that fall under the new category of "issue."
함께 살펴볼 논문
공통 태그를 근거로 연결했습니다. 실제 인용 관계나 논문의 우수성을 뜻하지 않습니다.
Emergent Misalignment: Narrow finetuning can produce broadly misaligned LLMs
CySecBench: Generative AI-based CyberSecurity-focused Prompt Dataset for Benchmarking Large Language Models
SecQA: A Concise Question-Answering Dataset for Evaluating Large Language Models in Computer Security
Understand Waiting Time in Transaction Fee Mechanism: An Interdisciplinary Perspective
Not what you've signed up for: Compromising Real-World LLM-Integrated Applications with Indirect Prompt Injection
SoK: Explainable Machine Learning for Computer Security Applications
토론
이 논문과 연결된 포럼 글이 아직 없습니다.