Cloud Security Architect
Description
Position Summary
GardaWorld's Global Cybersecurity organization is hiring a Cloud Security Architect dedicated to Crisis24 - Integrated Risk Management (C24-IRM).
This is a hands-on architecture and engineering role within Cybersecurity Architecture (CSA). The role secures the AWS platform behind the IRM product estate, including Horizon, CRC & OCN (Masscomm), and Legacy Masscomm platforms.You will design and implement the cloud security guardrails that allow IRM engineering teams to move faster with less risk: AWS account structure, landing zones, IAM and SCP controls, EKS and container security, network exposure reduction, secrets and encryption patterns, cloud logging, posture management, and infrastructure-ascode guardrails.
This role reports through CSA, with dedicated day-to-day alignment to C24-IRM CloudOps, DevOps, platform engineering, and the product-security resources in PSOE.
Reports to: Director, EngineeringDedicated to: Crisis24 - Integrated Risk Management (C24-IRM)Key partners: C24-IRM CloudOps / DevOps, Product Security & Offensive Engineering (PSOE), IAM Architecture, CyberOps, GRC, and IRM engineering leadership
Why This Role Matters
C24-IRM runs a large, client-facing product estate on AWS. The security of that estate depends heavily on the quality of its AWS foundation: how accounts are structured, how privileges are controlled, how workloads are segmented, how EKS is hardened, how secrets are handled, how cloud activity is logged, and how misconfigurations are prevented before production.
Without a dedicated AWS cloud-security owner, each engineering team is forced to solve platform security differently. That creates inconsistent controls, duplicated effort, and repeated cloud findings.
This role creates the secure AWS patterns once and helps IRM teams reuse them across products. The goal is a hardened, self-service AWS foundation where engineering teams can ship safely without waiting for one-off security reviews.
Team Context
Global Cybersecurity operates as one unified team across Strategic Cyber Office, GRC, CyberOps, Product Security & Offensive Engineering, Cybersecurity Architecture, and divisional security partners.Within this model, CSA owns enterprise security architecture, technical standards, IAM/PAM architecture, and cloud security architecture. This role is a CSA resource dedicated to C24-IRM because the immediate risk and execution need are concentrated in the IRM AWS estate.
The role is distinct from the IRM product-security roles in PSOE:CSA / this role: secures the AWS platform, cloud guardrails, account patterns, EKS baseline, cloud logging,and platform-layer controls.
PSOE: secures application code, APIs, secure SDLC, product vulnerability remediation, CI/CD applicationgates, and developer enablement.
CyberOps: owns 24/7 detection and incident response operations.
GRC: owns policy, risk, audit, certifications, TPRM, and formal exceptions.
Key Deliverables (First 12-18 Months)
AWS Foundation Security
Current-state map of the IRM AWS estate: accounts, landing zones, identity paths, exposed services, EKSclusters, data stores, logging, and critical posture findings.
Target-state AWS security reference architecture for the IRM estate.
Prioritized remediation roadmap for critical and high AWS platform risks.
Guardrails and Reusable Patterns
Reusable account, IAM, SCP, network, encryption, logging, and secrets-management patterns adopted byIRM teams.
Infrastructure-as-code and policy-as-code guardrails that prevent or detect high-risk cloudmisconfigurations.
Baseline EKS / container security pattern for IRM workloads.
Detection, Resilience, and Handoff
Cloud telemetry architecture handed to CyberOps with clear alert routing and escalation paths.
GuardDuty, Security Hub, CloudTrail, and cloud logging coverage aligned to the IRM risk profile.
Resilience and recovery design validation for at least one critical IRM workload.
Evidence and Metrics
Practical AWS security scorecard for IRM and Cyber leadership.
Compliance-supporting technical evidence for GRC where cloud controls support SOC 2, ISO 27001, HIPAA,
FedRAMP-aligned, or client assurance needs.
Core Responsibilities
1.AWS Security Architecture and Account Guardrails
Own the AWS security reference architecture for the IRM estate.
Define secure account, landing-zone, SCP, and service-control patterns.
Design least-privilege AWS access patterns in coordination with the enterprise IAM Architect.
Review high-risk AWS architecture changes and product onboarding paths.
2. Workload, Network, and EKS Security
Define secure patterns for VPC segmentation, ingress/egress control, private connectivity, edge protection,and workload isolation.
Set EKS and Kubernetes security standards, including pod security, network policy, admission control, imagecontrols, and runtime protection.
Harden serverless and managed-service configurations against common AWS attack paths.
3. Cloud Posture, Infrastructure-as-Code, and Policy-as-Code
Operate cloud posture and cloud-native application protection standards across the IRM AWS estate.
Translate posture findings into corrected infrastructure and reusable controls.
Encode guardrails into infrastructure-as-code and policy-as-code so controls are repeatable and auditable.
Partner with IRM CloudOps / DevOps so security controls are automated and developer-friendly.
4. Data Protection, Secrets, and Cloud Identity
Define encryption, KMS, key lifecycle, and data-protection patterns for IRM cloud services.
Establish secrets-management patterns that reduce hard-coded credentials and improve rotation.
Coordinate AWS-account-level identity decisions with the enterprise IAM Architect.
Align cloud data controls to IRM's client and regulatory obligations.
5. Detection Architecture, Resilience, and Compliance Alignment
Design cloud telemetry and threat-detection architecture, then hand operational monitoring to CyberOps.
Support resilience and recovery design for high-criticality IRM workloads.
Provide technical evidence and remediation support to GRC for audits, certifications, client assurance, andrisk reviews.
Ladder the IRM AWS estate toward approved CSA hardening tiers and technical standards.
Key Performance Indicators:
AWS Account Coverage: IRM AWS accounts mapped, risk-ranked, and assigned to approved guardrail patterns
Critical Cloud Findings: Material reduction in critical/high cloud misconfiguration and exposure findings
Guardrail Adoption: New IRM AWS initiatives using approved account, IAM, network, logging, and secretspatterns
EKS / Container Baseline: Priority EKS and container workloads aligned to the approved security baseline
Logging and Detection Handoff: Cloud telemetry routed to CyberOps with clear ownership and escalation paths.
Policy-as-Code Coverage: Preventive or detective guardrails implemented for priority cloud risk classes
Engineering Enablement IRM CloudOps / DevOps teams able to reuse patterns without repeated one-off reviews.
Required Qualifications
Experience
Senior hands-on experience securing production AWS environments for client-facing or mission-criticalworkloads.
Proven experience with AWS Organizations, multi-account architecture, landing zones, SCPs, IAM, VPC networking, EKS / Kubernetes, KMS, secrets management, and cloud logging.
Practical experience turning cloud posture findings into remediated infrastructure and reusable patterns.
Experience working with DevOps, CloudOps, platform engineering, and product teams in delivery-orientedenvironments.
Technical Skills
Strong AWS architecture and security engineering skills.
Infrastructure-as-code and policy-as-code experience, preferably with Terraform or equivalent tooling.
Working knowledge of CSPM / CNAPP concepts, container security, cloud detection, and cloud resilience.
Ability to design controls that are automated, auditable, and usable by engineering teams.
Familiarity with CIS AWS Benchmarks, NIST CSF, NIST SP 800-53, and Zero Trust concepts.
Soft Skills and Behaviors
Practical architecture judgment: able to reduce real risk without creating review bottlenecks.
Strong communication with platform engineers, product leaders, CyberOps, GRC, and executives.
Comfortable operating through influence in a federated environment.
Bias toward reusable patterns, measurable remediation, and clear ownership.
Certifications (Preferred)
AWS Security - Specialty, AWS Solutions Architect Professional, or equivalent cloud-security credentials.
CISSP, CCSP, Kubernetes security, or infrastructure-security certifications are assets.
Organizational Placement
Reports to: Director, Engineering
Dedicated / dotted-line stakeholders:
C24-IRM CTO and engineering leadership
IRM CloudOps / DevOps and platform engineering
Horizon, CRC & OCN, and Legacy Masscomm technical leads
Collaborates closely with:
Product Security & Offensive Engineering (PSOE) for application-layer CI/CD gates, product risk, and developer workflows
IAM Architecture for identity and privilege patterns
CyberOps for detection handoff, alert routing, and incident escalation
GRC for policy, risk, audit, certification, and client assurance evidence
Success Roadmap
First 30 Days
Map current AWS accounts, EKS clusters, key services, access paths, and highest-risk exposure areas.
Establish working relationships with CSA, IRM CloudOps / DevOps, product-security resources, CyberOps, GRC, and IRM engineering leadership.
Identify the first critical/high AWS risks to remediate.
First 90 Days
Publish the first IRM AWS security baseline and priority guardrail patterns.
Deliver initial remediation for the highest-risk cloud findings.
Stand up or improve CSPM / CNAPP coverage, cloud logging, and policy-as-code guardrails for priority risk classes.
Agree the cloud detection handoff model with CyberOps.
First Year
Demonstrate measurable reduction in high-severity cloud findings.
Drive broad adoption of approved AWS account, IAM, network, EKS, logging, and secrets patterns.
Provide a practical AWS security scorecard for IRM and Cyber leadership.
Validate resilience and recovery architecture for at least one critical workload.
Long-Term Vision
Establish a hardened, self-service AWS foundation where IRM teams build securely by default.
Reduce repeated cloud findings through reusable guardrails and engineering-owned patterns.
Create a CSA model that can be reused for other division-dedicated cloud security needs.
Professional Development and Career Path
Development Opportunities
Deep ownership of a complex, client-facing AWS SaaS estate.
Advanced cloud security architecture, EKS security, policy-as-code, and detection engineering exposure.
Partnership with CSA, CyberOps, PSOE, GRC, and senior IRM engineering leadership.
Future Growth Paths
Enterprise cloud security architecture leadership.
Broader CSA leadership for cloud, platform, or secure-by-design architecture.
Principal or director-level security architecture roles across federated business units.
What Makes This Role Unique at GardaWorld
You will secure the AWS foundation behind high-visibility Crisis24 IRM products.
You will work at the point where cloud architecture, product delivery, client assurance, and operational resilience meet.
You will build reusable guardrails that make secure delivery easier for large engineering teams.
You will help prove a repeatable model for division-funded, Cyber-owned, embedded cloud security.
Location and Travel
Location: Bangalore, India
Travel: Occasional travel for engineering workshops, architecture reviews, onboarding, and key stakeholdersessions.
Skills
Sign in to read and join the discussion.