AWS Cloud Security Engineer

Key Responsibilities

• The multi-account security foundation. AWS Organizations structure, SCPs, guardrails, a security tooling account, centralized logging, and secure baselines — delivered as infrastructure as code, not console clicks.
• Security standards and review gates. You can mandate controls and block deploys that introduce unacceptable risk, through review gates on identity and network changes, a documented exception path, and a defined escalation route.
• AWS identity and access. IAM Identity Center as the single front door, federated with Entra ID in partnership with IT, who own Entra as the source of truth. Role and group model mapping job functions to permissions; joiner/mover/leaver; privileged and break-glass access; workload identity; recurring access reviews. Hands-on at first, progressively automated so it stops being manual work.
• Cloud-to-site connectivity and segmentation — the defining part of this role. Every plant, BESS site, and remote asset that reaches our cloud does so over a path you design and defend: site-to-cloud VPN and private connectivity, hard segmentation between IT and OT zones, DMZ and broker patterns for site telemetry, certificate and device identity for field gateways, remote vendor access to sites, and strict control over what may initiate traffic in each direction. You own the cloud side of that boundary and share the path itself with the OT security owner.
• Threat detection, monitoring, and mitigation. You are expected to know how attacks actually run — credential and token abuse, cross-account privilege escalation, exposed control and management interfaces, lateral movement from a compromised site network into cloud, supply-chain and dependency compromise, ransomware staging — and to build the monitoring that catches them. GuardDuty, Security Hub, Detective, Inspector, Config, and CloudTrail tuned for real signal-to-noise, detections mapped to MITRE ATT&CK and ATT&CK for ICS, runbooks the wider team can execute, and the mitigations driven to done.
• Vulnerability management. Scanning coverage across workloads, images, and dependencies; risk-based triage and prioritization; remediation SLAs and exception handling; posture reporting. You identify and prioritize; the AWS engineers remediate in the workloads they own.

Key Requirements

• 5+ years in cloud security, security-focused infrastructure, or cloud operations, with deep hands-on AWS.
• Production experience in multi-account AWS environments.
• Demonstrable command of attacker techniques and the detections and mitigations that counter them — you can walk an intrusion path end to end and explain how you would catch it, contain it, and close it.
• Hybrid and site-to-cloud network security: segmentation, VPN, private connectivity, firewalls, routing, DNS, CIDR and subnetting — securing connections between cloud and physical facilities.
• Strong AWS identity: roles, policies, permission sets, MFA, least privilege, access reviews; IAM Identity Center federated with an external IdP, ideally Microsoft Entra ID.
• AWS-native security services: GuardDuty, Detective, Security Hub, Inspector, Config, CloudTrail, KMS, WAF.
• Infrastructure as code — CDK, CloudFormation, or Terraform. You build controls, you don't click them.
• Advanced English (B2–C1) for daily work with English-speaking teams and written security documentation.

Preferred Qualifications

• Security experience in OT- or ICS-adjacent environments: IT/OT segmentation, Purdue-model zoning, secure remote access to field sites, and protocols such as Modbus, DNP3, OPC UA, or MQTT crossing into cloud.
• Detection engineering and SIEM work; threat modelling; incident response you have personally run.
• Regulated or compliance-driven environments where access control, monitoring, and audit evidence are held to an external standard.
• Turning scanner output and audit findings into prioritized, actionable work for engineers who do not report to you.
• Troubleshooting security, identity, networking, and infrastructure issues across cloud and hybrid environments.
• Landing zones, Control Tower, and security account patterns.
• IEC 62443 or NIST SP 800-82 familiarity.
• Containers and serverless workloads.
• Energy, utilities, or other mission-critical environments.
• Wazuh, Datadog, Grafana, or similar.
• Security documentation and ADRs.

Certifications

Valued as a signal, not a substitute for experience: AWS Certified Security – Specialty; AWS Certified Advanced Networking – Specialty; AWS Certified Solutions Architect; GICSP or GIAC GRID; CISSP; CCSP; Microsoft Certified: Identity and Access Administrator Associate.

#LI-AD1