Security Architect

Oracle•Seattle, WA

About The Position

You will design security and compliance reference architectures, standards, and controls for Oracle Cloud services and platforms, with a focus on continuous compliance and audit-ready engineering. This role is a hybrid of compliance engineering (building automation, evidence pipelines, compliance-as-code) and security GRC architecture (control design, framework mapping, risk decisions, and governance at scale). You will lead high-impact design reviews, control and evidence strategy, and requirements-to-implementation translation across cloud primitives (compute, network, storage), identity and access, container/Kubernetes platforms, AI/ML systems, and developer platforms. You will collaborate with senior leaders and product teams, mentor engineers, and influence roadmaps through clear writing, principled prioritization, and metrics—while directly authoring and owning OSCAL artifacts and scaling through others. Ideal candidates bring deep experience “building clouds” or securing large-scale distributed systems; strong fluency in global compliance regimes (including but not limited to NIST-800 series, SOC 2, ISO 27001, ISO 42001, PCI, FedRAMP, GDPR, and other international/regional frameworks); and a track record of delivering automation-first compliance outcomes (e.g., continuous control validation, evidence automation, and measurable reduction in audit preparation effort). You are hands-on, inclusive, and customer-obsessed, balancing rigor with velocity. Oracle’s Governance, Risk & Compliance (GRC) organization enables secure, compliant cloud delivery by partnering deeply with engineering and operations. We standardize control outcomes, strengthen evidence quality, and operationalize compliance through scalable patterns, automation, and measurable risk reduction—helping Oracle meet customer, regulatory, and industry expectations.

Responsibilities

Set strategy: Define multi-year GRC and compliance engineering strategy and roadmaps for continuous compliance, control automation, evidence pipelines, and audit readiness across Oracle products and services—focused on reducing manual audit toil through automation and standardization.
Authoritative design: Publish security/compliance reference architectures, control baselines, evidence standards, and implementation patterns; lead cross-org reviews that raise the bar on auditability and continuous assurance.
Build compliance into the cloud: Partner with core service teams (compute, networking, storage, virtualization, container/orchestration, service mesh) to drive secure-by-default and compliant-by-default designs, with controls that are measurable and operationally sustainable.
Frameworks → controls: Translate regulatory and customer requirements into engineering-ready controls, acceptance criteria, and implementation guidance across regimes including (but not limited to) NIST-800, SOC 2, ISO 27001, ISO 42001, PCI, FedRAMP, GDPR, and regional frameworks—ensuring mappings are rationalized and scalable across multiple regimes.
OSCAL ownership: Directly write, curate, and own OSCAL artifacts (e.g., catalogs/profiles/component definitions and related content as applicable), and establish scalable operating models (templates, review workflows, QA checks) so teams can contribute and maintain artifacts over time.
Compliance-as-code: Drive adoption of policy-as-code and compliance-as-code approaches (automated control validation, CI/CD gates, drift detection, and standardized attestations) to reduce manual audit effort and improve consistency.
Evidence engineering: Design and standardize evidence collection pipelines with lineage, traceability, retention, and quality controls; ensure evidence is high-signal, reproducible, and mapped to controls and system boundaries—prioritizing automation, normalization, and audit-ready reporting.
Continuous monitoring & remediation: Design scalable mechanisms to continuously detect control drift and drive remediation (automated and/or workflow-driven), with clear metrics and accountability for sustained compliance outcomes.
Risk, compliance, and safety: Partner with privacy, legal, and security stakeholders to incorporate privacy-by-design and AI governance needs (e.g., ISO 42001) into engineering controls and evidence strategies—especially for AI-enabled applications and services.
Incident leadership (compliance perspective): Ensure compliance controls remain resilient through incidents and major changes; drive post-incident reviews and systemic improvements to guardrails and evidence quality.
Influence at scale: Produce clear design docs and executive narratives; mentor engineers and program leaders; build communities of practice and reusable assets for continuous compliance.