AI Attack Surface Analyst
An AI Attack Surface Analyst systematically discovers, classifies, and prioritizes vulnerabilities across an organization's entire…
Skill Guide
The operational knowledge to design, implement, and audit AI systems for compliance with the NIST AI Risk Management Framework (AI RMF) and the EU AI Act, ensuring technical risk controls map to legal obligations.
Scenario
You are tasked with documenting the governance of a new internal chatbot used for employee FAQ retrieval. It uses a pre-trained LLM.
Scenario
A fintech company is deploying an AI-driven tool to screen job applicants. The tool analyzes video interviews for non-verbal cues and assigns a 'suitability score.' Legal counsel is unsure if this falls under 'high-risk' as defined in Annex III of the EU AI Act.
Scenario
Your multinational SaaS company is launching a new AI feature for personalized pricing, available in the EU and US. It must be compliant with both the EU AI Act (likely high-risk) and demonstrate alignment with NIST AI RMF for US enterprise clients.
These are the primary reference architectures. NIST AI RMF provides a flexible risk management process. The EU AI Act is the legal text imposing specific obligations. ISO 42001 and IEEE standards offer certifiable management systems and technical processes that support compliance.
These tools operationalize governance. Platforms like IBM's provide bias monitoring, explainability, and fact sheets. Model Cards standardize documentation. Hugging Face libraries enable technical measurement of fairness and robustness metrics, which are core to both frameworks' 'Measure' functions.
Risk-Based Thinking is the core principle underlying both NIST and the EU Act. Stakeholder Analysis is critical for the 'Map' function. Documentation-as-Code (e.g., storing model cards, risk registers in Git) ensures auditability and traceability, a key requirement for technical documentation under the EU Act.
Answer Strategy
Demonstrate procedural knowledge of Annex IV of the EU AI Act. Structure the answer logically around the required sections. Sample answer: 'The technical file must be a comprehensive dossier. It starts with a general description of the system, its intended purpose, and version. It must include detailed specifications of the design, development, and validation process. Critical elements are the risk management system documentation per Article 9, data governance details per Article 10, and the results of testing for accuracy, robustness, and cybersecurity. It must also document the human oversight mechanisms and any known limitations. The file must be maintained for the system's lifetime and made available to authorities upon request.'
Answer Strategy
Tests application of the RMF's 'Map' and 'Measure' functions under business pressure, and the ability to influence without authority. Frame the response around structured risk communication. Sample answer: 'I would apply the RMF's Map function by first defining the context and potential harms-specifically, how the demographic gap could lead to biased or unfair outcomes for certain user groups. Next, using the Measure function, I would quantify the risk: run fairness metrics on a sample to demonstrate the expected disparity in error rates. Then, I'd present this as a quantifiable business risk-not just an ethical one-highlighting potential for reputational damage, loss of user trust, or future compliance issues under frameworks like the EU AI Act. I would propose a mitigation plan: using the data with clear documentation of its limitations and bias, implementing post-processing de-biasing techniques, and committing to a rapid retraining cycle with better data once available, thus managing the risk rather than ignoring it.'
1 career found
Try a different search term.