Lead AI Security Engineer - Senior Manager

We need to output HTML fragment with sections: About the role? The posting includes intro paragraphs about EY, then "The opportunity" description, then "Your Key Responsibilities", then "Skills And Attributes For Success", then "To qualify you must have ..." (Qualifications), then "Ideally, you'll also have ..." (maybe additional qualifications), then "What We Offer You" (Benefits). Also location line at top: "Location: Anywhere in Country". We should not repeat job title. We need to include sections only if real content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role (intro), Responsibilities (Your Key Responsibilities), Skills (Skills And Attributes For Success), Qualifications (To qualify you must have...), Benefits (What We Offer You). Pay: we have salary ranges; that is Pay info. So include Pay section. Schedule: not mentioned; skip. Also maybe Requirements? Could combine Qualifications and Skills? But we have separate sections: Qualifications (education, experience) and Skills (attributes). We'll follow headings: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay. Ensure we don't include empty sections. We must preserve all substantive info, not invent. Remove boilerplate: cookie/navigation/legal/EEO etc. At end there is EEO statement; remove. Also remove application instructions like "Apply today", "limit yourself to two applications", etc. Also remove "For those living in California, please click here". Also remove "EY | Building a better working world" etc. Also remove "Under our flexible vacation policy..." maybe that's benefits; keep as part of Benefits. But we need to keep substantive benefits: medical/dental, pension/401k, paid time off, flexible vacation policy, holidays, etc. Keep that. Pay section: include salary ranges as given. We need to format lists with

• . For responsibilities list: each bullet starts with a bold phrase? We'll keep as list items. We need to avoid repeating job title. No headings for Job ID. Let's extract content. Intro: "Location: Anywhere in Country At EY, we’re all in to shape your future with confidence. We’ll help you succeed in a globally connected powerhouse of diverse teams and take your career wherever you want it to go. Join EY and help to build a better working world. The opportunity We are seeking an AI Security Engineer to own the security posture of EY’s Agentic AI platform end to end. Agentic AI breaks the assumptions most enterprise security programs are built on. Systems now generate and execute their own code, invoke tools and external APIs autonomously, act on behalf of human principals across long delegation chains, and can be manipulated through the same channel that carries legitimate instructions. Perimeter controls, static code review, and human-in-the-loop approval do not contain any of this on their own. This role exists to make EY’s agentic platform defensible in the most highly regulated client environments in the world, including tax, financial services, audit, and risk. It is the security engineering and assurance authority spanning the whole stack: from silicon-level attestation and Kubernetes hardening, through supply-chain integrity and sandboxed execution, to prompt-injection defense, agent authority containment, and audit-grade evidence. This is a deliberately broad mandate. It is ideal for a principal security engineer who has genuine depth in cloud-native and platform security, who has moved decisively into AI and agentic threat models, and who is equally comfortable writing a threat model, breaking a system in a red-team exercise, defining policy-as-code, and defending the resulting engineering to a client’s CISO or a regulator." That's About the role. Responsibilities: list under "Your Key Responsibilities". We'll capture each sentence starting with a verb. List: - Own the platform threat model: covering agent autonomy, tool invocation, delegated authority, model and data supply chain, multi-tenancy, and every deployment target from cloud to air-gapped, and keep it current as the platform evolves through each build phase. - Define the security engineering and control set for every platform layer: infrastructure and boot chain, Kubernetes and cluster fabric, identity and secrets, secure execution and sandboxing, gateway and egress, data and state, delivery pipeline, and telemetry. - Set the secure-by-default contract so that platform capabilities arrive hardened, including agent templates, Helm charts, sandbox profiles, and network policy ship with correct controls rather than requiring teams to add them. - Own defense against agentic threat classes including direct and indirect prompt injection, jailbreak and instruction hijacking, excessive agency, confused-deputy and authority-escalation attacks, tool and function-call abuse, memory and context poisoning, and retrieval-augmented data exfiltration. - Work with the architecture team to help define the agent authority model: delegated and on-behalf-of authority, scope and delegation-depth limits, consent boundaries, and the non-escalation invariant that an agent never exceeds the authority of its initiating principal at any hop. - Own the sandboxing security standard for agent-generated code execution: isolation boundaries, filesystem and credential scope, egress restriction, resource containment, and the escape-test suite that proves the boundary holds. - Secure the model and knowledge supply chain: model provenance and integrity, upstream registry governance, poisoning and backdoor risk, embedding and vector-store integrity. - Secure agent-to-agent and tool protocols including MCP and A2A surfaces: discovery trust, tool registration and approval, schema validation, and authorization of inter-agent calls. - Lead AI red teaming and adversarial testing: build the offensive capability and the recurring exercise cadence that tests guardrails, sandboxes, and authority boundaries before adversaries and auditors do. - Own supply-chain integrity end to end: artifact signing and verification (Sigstore/Cosign, Notation), SBOM generation and attestation, provenance and SLSA-aligned build integrity, CVE management, dependency and license governance. - Own admission and runtime policy: policy-as-code across Kyverno and OPA, signature-verification enforcement, Pod Security Standards, and the guardrails that make non-compliant workloads unschedulable rather than merely reported. - Define Kubernetes and infrastructure hardening baselines: CIS-aligned cluster configuration, network default-deny and segmentation, node and boot-chain integrity, GPU and DPU isolation, and secrets-handling standards. - Own tenant isolation assurance: the security definition of a tenant boundary across compute, network, storage, secrets, telemetry, and evidence, and the testing that proves cross-tenant leakage is not possible. - Serve as the security authority in client engagements: lead security engineering reviews, respond to client CISO and regulator scrutiny, and produce the assurance artefacts that unblock deployment into regulated environments. - Drive security detection and response for the platform: detection engineering for agentic misbehavior, security telemetry requirements, alerting, incident response playbooks, and post-incident review. Skills And Attributes For Success: list bullet points. - Deep cloud-native security expertise: Kubernetes, container, and infrastructure security at production scale, with real operational experience rather than assessment-only exposure. - Genuine command of AI and agentic threat models, with the judgement to distinguish novel risk from familiar risk wearing new vocabulary. - Strong zero-trust and workload-identity foundations: SPIFFE/SPIRE, PKI and certificate lifecycle, secrets management, and delegated authorization patterns. - Fluency in policy-as-code, with the instinct to encode controls as enforced policy rather than documented expectation. - Software supply-chain security depth: signing, provenance, SBOM, and build integrity. - Offensive-security instinct: able to think like an attacker against systems that generate their own code and act autonomously. - Pragmatism about risk: able to distinguish controls that must exist before the first client workload from those that can follow, and to defend both decisions. - Exceptional communication: able to move between a deep technical design review, an executive risk conversation, and a regulator or client CISO discussion without losing precision. - Security-as-enablement mindset: measured by how much safe delivery velocity the controls unlock, not by how much they prevent. Qualifications: "To qualify you must have Bachelor’s or Master’s degree in Computer Science, Security, or a related technical field, or demonstrably equivalent depth.10+ years in security engineering, security engineering, or offensive security, including hands-on production ownership.Demonstrable depth in cloud-native and Kubernetes security: admission control, network policy, workload isolation, and runtime security in production.Hands-on experience with workload identity and secrets management (SPIFFE/SPIRE, Vault/OpenBao or equivalents) and with PKI and certificate lifecycle.Practical experience securing AI or ML systems in production, including familiarity with LLM and agentic attack surfaces, such as prompt injection, tool abuse, excessive agency, and model or data supply-chain risk.Threat modelling capability applied to real systems, with evidence that the resulting controls were built and verified.A track record delivering under compliance, security, or regulatory constraint with audit-grade evidence requirements.Experience defining ownership boundaries and control contracts with platform, data, runtime, and delivery teams." We could split into list items. Ideally, you'll also have ... (additional qualifications). We could include as part of Qualifications or separate? The instruction: Use headings for Qualifications, Skills, etc. We have Qualifications (mandatory) and maybe also "Ideally, you'll also have" as additional qualifications; could be part of Qualifications as well. We'll include them as list items under Qualifications. List: - Bachelor’s or Master’s degree in Computer Science, Security, or related technical field, or demonstrably equivalent depth. - 10+ years in security engineering, offensive security, including hands-on production ownership. - Demonstrable depth in cloud-native and Kubernetes security: admission control, network policy, workload isolation, runtime security in production. - Hands-on experience with workload identity and secrets management (SPIFFE/SPIRE, Vault/OpenBao or equivalents) and PKI/certificate lifecycle. - Practical experience securing AI/ML systems in production, familiarity with LLM/agentic attack surfaces: prompt injection, tool abuse, excessive agency, model/data supply-chain risk. - Threat modelling capability applied to real systems, with evidence that resulting controls were built and verified. - Track record delivering under compliance, security, or regulatory constraint with audit-grade evidence requirements. - Experience defining ownership boundaries and control contracts with platform, data, runtime, delivery teams. - Ideally: Software supply-chain security experience: artifact signing, SBOM, provenance, vulnerability management embedded in delivery pipelines. - Ideally: Policy-as-code experience with OPA, Kyverno, or equivalent admission and authorisation engines. - Ideally: Experience building or leading an AI red team, or running adversarial testing against LLM and agentic systems. - Ideally: Familiarity with confidential computing and hardware attestation (Intel TDX, AMD SEV-SNP, SGX, NVIDIA CC) and secure boot / measured boot designs. - Ideally: Working knowledge of OWASP Top 10 for LLM Applications, MITRE ATLAS, NIST AI RMF, EU AI Act as applied to real engineering. - Ideally: Experience with LLM guardrail and defense tooling (NeMo Guardrails, LLM Guard, LlamaFirewall, Guardrails AI, or equivalents) in production paths. - Ideally: Experience securing multi-tenant platforms across cloud, on-prem, edge, client-managed, and air-gapped deployment modes. - Ideally: Detection engineering and incident response experience, particularly for novel or behavioral threat classes. - Ideally: Client-facing or consulting background, with credibility in front of CISOs, auditors, regulators. - Ideally: Relevant certifications (CISSP, OSCP, GIAC, cloud security specialties) or demonstrable equivalent depth. - Ideally: Exposure to regulated industries: financial services, tax, audit, healthcare, public sector. - Ideally: Contribution to open-source security tooling, research, or public standards work in AI security. We could separate "Ideally" as separate bullet points but still under Qualifications. Benefits: "What We Offer You At EY, we harness our collective strength to empower you to shape your future with confidence through professional growth, personal fulfillment and an inclusive culture. Learn