Skip to content
In progressAWS Competency

Security Competency

Practice area covering residency-first architecture, least-privilege identity, and audit trails designed in from the first schema.

Status
In progress
Submitted
In progress
Decision
—
References
Pending approval

What it covers

Constraints, not configuration flags.

Our submission centres on workloads where residency and auditability were architectural constraints from the first schema — public health records and regulated lending.

Data residency

Region-pinned storage and processing designed in, not retrofitted.

Identity & access

Least-privilege models with access reviewed as a standing practice.

Audit logging

Immutable trails that stand up to external examination.

Secure delivery

Scanning and policy checks inside the pipeline, not after release.

Validation criteria

What AWS assessed.

The criteria AWS assesses for this competency, and our current status against each. Status is maintained in the CMS from AWS Partner Central.

How validation works

Regulated workloads

Public sector and fintech engagements with residency requirements.

In progress

Control mapping

PCI and SOC control coverage documented against real architectures.

In progress

Technical review

AWS reviews residency, identity, and audit controls against real architectures.

In progress

Final validation

AWS's decision once the technical review is complete.

In progress

Services

What we build it on.

  • IAM
  • KMS
  • CloudTrail
  • Config
  • WAF
  • Shield
  • Security Hub

Team on this practice

Security sits with the cloud practice — the same nine people who own the landing zone own the posture.

Work with this practice

Workload an auditor will examine?

Discovery comes first — a short, bounded review that ends in an architecture, a scope, and a price. You keep the output either way.