Controls Specialist, Security GRC

• Own the Common Control Framework: the canonical control set, its mappings to SOC 2, ISO 27001/42001, HIPAA, FedRAMP, and customer commitments, and the change process for adding, retiring, or rewording controls • Draft and validate control descriptions and control activities with control owners, so each control states who does what, how often, in which system, and what evidence proves it • Design and run continuous monitoring of control efficacy: define the metrics and automated tests that show operating effectiveness, tune out false positives, surface failures to owners before an auditor does, and build the controls maturity model that shows where each control domain stands and what it takes to move up a level • Verify remediation and carry it into steady state: GRC Partners lead remediation in their domains and control owners implement the fixes. This role advises on control design and implementation, confirms fixes against what the auditor actually asked for, and keeps one source of truth for control and finding status. Once a fix holds, it works with the partner to standardize the evidence pull and, where appropriate, automate it or build continuous • Map new frameworks and commitments onto the CCF as we commit to them, and support gap assessments when a new framework, certification, product, or entity comes into scope, using the CCF as the baseline and writing the requirements for each delta • Support the integrated audit and customer audits: readiness checks, walkthrough preparation, evidence request lists, and the readout of external findings back to GRC • Evaluate evidence reliability, including the completeness and accuracy of system-generated reports and AI-generated evidence, and set the standard for what audit-ready evidence looks like here • Build with Claude: automate control mapping, evidence testing, and monitoring, and verify machine-drafted control language before it becomes the record

• Several years in IT audit, security compliance, or controls assurance, including hands-on ownership of a control framework or control library across more than one framework (for example SOC 2, ISO 27001, FedRAMP, HIPAA) • Working command of audit mechanics: scoping, walkthroughs, sampling, design versus operating effectiveness, deficiency evaluation, and evidence reliability • Experience writing control descriptions, control activities, and test procedures that other teams and external auditors relied on • Experience with continuous controls monitoring or automated evidence collection, whether you built it, ran it, or audited it • Enough technical fluency to read a runbook, a configuration, or a pipeline definition and judge whether it enforces what the written control claims • Clear writing, because your control language and status reports are what auditors, engineers, and leadership work from • Ability to get control owners and partner teams to prioritize and close work without having authority over them • Have designed or rebuilt a common controls framework and led the remapping of existing frameworks onto it • Have stood up continuous controls monitoring or automated evidence programs and can speak to coverage, false-positive rates, and what changed as a result • Have applied LLMs to assurance work, such as control drafting, framework mapping, evidence testing, or monitoring • Have defined or assessed controls for AI systems or agents operating in production, or for home-built internal systems • Have provided requirements for a homegrown GRC platform and worked with the engineers who build it

About Anthropic Anthropic’s mission is to create reliable, interpretable, and steerable AI systems. We want AI to be safe and beneficial for our users and for society as a whole. Our team is a quickly growing group of committed researchers, engineers, policy experts, and business leaders working together to build beneficial AI systems. About the team Anthropic's Security Governance, Risk, and Compliance (GRC) team is the connective tissue that holds the company accountable to its security commitments. We translate regulatory, customer, and voluntary obligations into controls that teams act on, and give leadership a bird's-eye view of how well we're meeting them. We're building toward a fundamentally different kind of GRC: one that directs Claude, with the right humans in the loop, to challenge and evidence the performance of controls continuously rather than through periodic audits. Within Security GRC, Compliance & Audit Programs runs the integrated audit across our frameworks and maintains the Common Control Framework, the single set of controls that the whole program is built on. This role sits in Audit & Assurance and owns the framework and the assurance view across every control domain. About the role As part of the Security Audit & Controls team, you will own the CCF across every control domain, from access and change management to logging, encryption, and people controls: which controls we have, what each one says, how each maps to the frameworks and commitments we hold, and whether each one is actually working. You'll work with control owners and GRC Partners to draft and validate control descriptions and activities that describe reality rather than policy intent, build the monitoring that shows operating effectiveness continuously instead of once a year, and drive what monitoring finds to closure with control owners. Building with Claude is a normal part of the job: drafting and mapping controls, testing evidence, and monitoring control health, with you deciding where human judgment stays in the loop. This is an individual contributor role for someone who works well independently, writes clearly, and gets satisfaction from a control set that is accurate, tested, and trusted by auditors and engineers alike. Key responsibilities • Own the Common Control Framework: the canonical control set, its mappings to SOC 2, ISO 27001/42001, HIPAA, FedRAMP, and customer commitments, and the change process for adding, retiring, or rewording controls • Draft and validate control descriptions and control activities with control owners, so each control states who does what, how often, in which system, and what evidence proves it • Design and run continuous monitoring of control efficacy: define the metrics and automated tests that show operating effectiveness, tune out false positives, surface failures to owners before an auditor does, and build the controls maturity model that shows where each control domain stands and what it takes to move up a level • Verify remediation and carry it into steady state: GRC Partners lead remediation in their domains and control owners implement the fixes. This role advises on control design and implementation, confirms fixes against what the auditor actually asked for, and keeps one source of truth for control and finding status. Once a fix holds, it works with the partner to standardize the evidence pull and, where appropriate, automate it or build continuous • Map new frameworks and commitments onto the CCF as we commit to them, and support gap assessments when a new framework, certification, product, or entity comes into scope, using the CCF as the baseline and writing the requirements for each delta • Support the integrated audit and customer audits: readiness checks, walkthrough preparation, evidence request lists, and the readout of external findings back to GRC • Evaluate evidence reliability, including the completeness and accuracy of system-generated reports and AI-generated evidence, and set the standard for what audit-ready evidence looks like here • Build with Claude: automate control mapping, evidence testing, and monitoring, and verify machine-drafted control language before it becomes the record Minimum qualifications • Several years in IT audit, security compliance, or controls assurance, including hands-on ownership of a control framework or control library across more than one framework (for example SOC 2, ISO 27001, FedRAMP, HIPAA) • Working command of audit mechanics: scoping, walkthroughs, sampling, design versus operating effectiveness, deficiency evaluation, and evidence reliability • Experience writing control descriptions, control activities, and test procedures that other teams and external auditors relied on • Experience with continuous controls monitoring or automated evidence collection, whether you built it, ran it, or audited it • Enough technical fluency to read a runbook, a configuration, or a pipeline definition and judge whether it enforces what the written control claims • Clear writing, because your control language and status reports are what auditors, engineers, and leadership work from • Ability to get control owners and partner teams to prioritize and close work without having authority over them Preferred qualifications • Have designed or rebuilt a common controls framework and led the remapping of existing frameworks onto it • Have stood up continuous controls monitoring or automated evidence programs and can speak to coverage, false-positive rates, and what changed as a result • Have applied LLMs to assurance work, such as control drafting, framework mapping, evidence testing, or monitoring • Have defined or assessed controls for AI systems or agents operating in production, or for home-built internal systems • Have provided requirements for a homegrown GRC platform and worked with the engineers who build it You don't need to • Have done everything on this list. The scarce combination t