Skip to main content

Security & Compliance · AWS Select Tier Partner

AWS Security & Compliance, Built to Audit Standards

Misconfiguration — not sophisticated exploits — is behind most AWS breaches. We harden IAM, deploy native detection, and produce the evidence your auditors actually request — across HIPAA, SOC 2, PCI DSS 4.0.1, ISO 27001:2022, NIST CSF 2.0, GDPR, DORA, and the EU AI Act.

Select Tier
AWS Consulting Partner
50+
AWS Certifications
6 Frameworks
HIPAA · SOC 2 · PCI DSS · ISO 27001 · DORA · EU AI Act
24/7
Managed SOC Coverage

Last updated: April 2026 — currency review: Audit Manager closure, Security Hub Essentials pricing, Bedrock Automated Reasoning, KMS post-quantum, DORA, EU AI Act  ·  Reviewed by: FactualMinds AWS-certified architects (Solutions Architect – Professional)

AWS Shared Responsibility Model

Where AWS ends — and where you (and we) begin

Most AWS breaches happen on the customer side of the line. That is the side we live on.

AWS publishes the Shared Responsibility Model so customers can see exactly which controls AWS operates and which controls remain with the workload owner. The line is sharp and well-documented — but in practice, most teams underestimate the customer side until the first audit (or the first incident).

Our engagements operate entirely on the customer side of the line. We do not patch hypervisors, we do not run AWS data centres, and we do not need to — AWS does that under SOC 1/2/3, ISO 27001/17/18, PCI DSS, HITRUST, and FedRAMP. What we do is the rest: identity, network, application, data, and the evidence pipeline that ties them all back to your auditor's checklist.

AWS owns

Physical data centres, hardware, hypervisor, host OS for managed services, and the global network backbone. Audited under SOC 1/2/3, ISO 27001/17/18, PCI DSS, HITRUST, FedRAMP — attestations on AWS Artifact.

Joint

Patch management for managed services, configuration baselines, awareness training, and incident response coordination. AWS provides the controls — you choose how to deploy them.

You own

IAM and access policies, encryption decisions, network design, application security, OS patching for EC2, and data classification. This is where most AWS breaches happen — and where we operate.

AWS Well-Architected — Security Pillar

Aligned to all seven Security Pillar design principles

Our engagements deliver each principle as a measurable outcome — not a slide deck.

The AWS Well-Architected Framework defines six pillars; the Security Pillar is the one that decides whether your next audit becomes a sprint or a slog. Every engagement we run maps directly to its seven design principles.

Implement a strong identity foundation

Centralised identity (IAM Identity Center), least privilege, no long-lived keys, and ABAC at scale.

Maintain traceability

CloudTrail (multi-region, validated, immutable), CloudTrail Lake or Security Lake on OCSF 1.1, and tamper-evident log retention.

Apply security at all layers

Edge (WAF, Shield), network (Network Firewall, security groups), workload (Inspector, GuardDuty), and data (KMS, Macie).

Automate security best practices

AWS Config conformance packs, Security Hub Essentials, IaC guardrails, and auto-remediation for high-confidence findings.

Protect data in transit and at rest

TLS 1.3 (ML-KEM hybrid where supported), KMS-CMK encryption for everything regulated, and key rotation as policy.

Keep people away from data

Read-only access by default, break-glass with MFA, query-based access (Athena, Lake Formation) over direct console access.

Prepare for security events

Documented runbooks, tabletop exercises, and pre-staged forensic tooling (Detective, IAM Access Analyzer, EventBridge response automations).

Featured Guides

One marquee guide per subtopic

The guides our clients most often cite when asked "send me one link to ground the conversation."

HIPAA on AWS: The Compliance Lead's Audit-Ready Checklist

An audit-prep checklist for Compliance Leads, Security Officers, and CISOs — BAA execution, documented Security Risk Assessments, workforce training, audit cadence, and the evidence packages OCR investigators expect when they show up.

Learn more

AWS IAM Best Practices: Least Privilege Access Control

Least privilege is a slogan. Working IAM at production scale is a different problem. Roles vs users, permission boundaries, SCPs, identity federation, and the access-control patterns that keep teams fast without leaving keys lying around.

Learn more

AWS GuardDuty Threat Detection: A Production Setup Guide

How to deploy, tune, and operationalize Amazon GuardDuty for production threat detection — covering finding types, multi-account setup, automated response, and reducing false positives.

Learn more

AWS S3 Security Best Practices: Preventing Data Exposure

S3 misconfigurations are still the leading cause of headline data breaches. Bucket policies, encryption, access logging, Block Public Access, and the practices that keep "developer left the bucket public" from being your incident.

Learn more

AWS WAF: Web Application Firewall Configuration for Production

AWS WAF blocks attacks. It also blocks legitimate users when the rules are wrong — and that's a worse incident. Managed rule groups, custom rules, rate limiting, bot control, and the layered defense strategy that protects without flooding your support queue.

Learn more

How to Set Up Amazon Bedrock Guardrails for Production

Amazon Bedrock Guardrails protect foundation models from harmful outputs — filtering on prompt injection, jailbreaks, toxicity, and PII. This guide covers setup, testing, cost optimization, and production safety patterns for GenAI applications.

Learn more

How we engage

Date-bound engagement, not an open-ended retainer

Discovery is read-only — we never push remediation in week one. Assessment outputs a prioritised findings register tied to exploitability and audit impact. Remediation is IaC-driven, reviewed change-by-change, and reversible. After go-live, the evidence pipeline runs continuously without our team in the loop.

Week 1 — Discovery

Read-only IAM Access Analyzer, Security Hub baseline scan, Config conformance pack deployment. We learn your environment before we propose anything.

Weeks 2–3 — Assessment

Findings prioritised by exploitability and audit impact. Threat model, IAM blast-radius map, network segmentation review, evidence-pipeline gap analysis.

Weeks 4–8 — Remediation

IaC-driven hardening, WAF/Network Firewall rollout, encryption uplift, multi-account guardrails. Every change reviewed and reversible.

Ongoing — Evidence Pipeline

Continuous Security Hub + Config + Inspector v2 evidence flowing into your GRC tool (Vanta / Drata / Secureframe) on the cadence your auditor expects.

Outcomes we sign our name to

Numbers from the case studies above

Every figure here is in the linked case study, with the architecture and the assessor type named.

12 → 0

Weeks of QSA audit prep

Cut to days for a Level 1 fintech (PCI DSS).

0 %

CDE scope reduction

Cardholder Data Environment trimmed via tokenisation and segmentation.

0 wks

Engagement to production

For a HIPAA-compliant telehealth platform on AWS.

0 /100

Security Hub score

On the same telehealth platform at go-live.

FAQ

Frequently asked questions about AWS security and compliance

The questions buyers actually ask before signing — multi-framework scope, evidence ownership, GRC tool integration, and ongoing cost.

We need HIPAA, SOC 2, and PCI DSS — can you handle multi-framework scope?
Yes. Most regulated SaaS clients land with overlapping scope, so we map the controls once against AWS-native services (Audit Manager, Security Hub, Config) and reuse the same evidence pipeline for each framework. Where the frameworks diverge — for example, PCI DSS 4.0.1 script integrity (Requirement 6.4.3) or HIPAA-specific BAA boundaries — we add the framework-specific controls without duplicating the foundational work. Net effect: a single integrated audit prep instead of three sequential ones.
What is your AWS-native evidence pipeline now that Audit Manager is closed to new customers?
AWS Audit Manager closed to new customers on 30 April 2026. Existing customers can keep using it, but we no longer recommend new engagements adopt it. Our current pipeline pairs AWS Config conformance packs (regulator-aligned control sets — CIS AWS Foundations, NIST 800-53 r5, HIPAA, PCI DSS 4.0, FedRAMP Moderate, K-ISMS, RBI, MAS — deployable Organization-wide via CloudFormation StackSets) with Security Hub Essentials on its 2025-revised resource-based pricing. Security Hub runs the continuous standards checks; Config conformance packs hold the rule-by-rule compliance state; CloudTrail Lake or Security Lake (OCSF 1.1) holds the auditable event store. Your team — or our consultants — still owns the policy library, risk assessments, and vendor reviews; the AWS-native stack collects the technical evidence.
When do we need a 3PAO vs. CPA firm vs. notified body?
Different frameworks require different assessor types. SOC 2 audits must be conducted by a licensed CPA firm. PCI DSS Level 1 (≥6M transactions/year) requires a Qualified Security Assessor (QSA), and FedRAMP requires a Third Party Assessment Organization (3PAO) listed on the FedRAMP marketplace. ISO 27001 certification requires an accredited certification body (notified body in EU terminology). HIPAA has no formal certification — it is enforced by HHS OCR, so the bar is "demonstrate due diligence" rather than "pass a specific assessor." Our gap-assessment phase always confirms the right assessor type before quoting a timeline.
Do you provide the BAA, or just the AWS-side controls?
AWS provides the Business Associate Addendum directly through AWS Artifact — that covers AWS as your subprocessor. We help you (a) confirm you only use HIPAA-eligible services on the workload side, (b) implement the technical safeguards (encryption, access logging, transmission security) under HIPAA §164.312, and (c) draft your downstream BAAs with anyone you share PHI with. We do not act as your covered-entity-side legal counsel — your healthcare attorney owns the BAA terms and Notice of Privacy Practices.
How do AI workloads (Bedrock, SageMaker) change the compliance scope?
AI changes the audit conversation in three concrete ways: (1) BAA boundaries shift — your Business Associate Addendum must reflect that a foundation model now processes PHI; AWS Bedrock and Bedrock AgentCore are HIPAA-eligible (AgentCore added February 2026), but every model and feature you use needs to be on the current AWS HIPAA Eligible Services list. (2) SOC 2 CC6.1 (logical access) and CC7.1 (system monitoring) extend to prompt and inference logs; HIPAA §164.312 transmission security and §164.308 access management both apply to inference paths. (3) Risk management documentation expands — NIST AI RMF for US, EU AI Act high-risk Annex III (enforceable 2 August 2026) for EU. Bedrock Guardrails (PII redaction, text and image content filters, denied topics, word filters, contextual grounding, and Automated Reasoning checks for math-validated factuality) are HIPAA-eligible and become evidence for those control extensions. We treat AI compliance as additive on top of HIPAA/SOC 2/PCI DSS — not a replacement.
What evidence packages do you produce, and who owns them post-engagement?
You own everything we produce: control narratives mapped to the framework, AWS architecture diagrams (Security Hub findings, Config rules, IAM Access Analyzer reports), the policy library (information security, access control, incident response, vendor management), risk-assessment workbook, and the Audit Manager evidence pipeline. Everything lives in your AWS account and your document repository. The only thing we keep is a redacted reference architecture for our internal patterns library.
Can you integrate with our existing GRC tool (Vanta, Drata, Secureframe)?
Yes. We work with Vanta, Drata, Secureframe, and Tugboat Logic regularly. The pattern is consistent: the GRC tool is your control inventory and evidence dashboard for auditors, AWS Config + Security Hub is the source of truth for technical findings, and we wire the read-only AWS integration so the GRC tool reflects live state instead of point-in-time snapshots. We do not push you off your existing tooling — most of our clients arrive with one already in place.
What does ongoing compliance monitoring cost after the initial engagement?
Two cost components: AWS service costs and engagement costs. AWS-side: Security Hub repriced to resource-based "Security Hub Essentials" in 2025 — unlimited checks/findings, billed per protected resource (EC2 instance, container image, Lambda function, IAM principal); typical mid-market spend $300$1,500/month. AWS Config moved to tiered per-region pricing — $0.001 / $0.0008 / $0.0005 per evaluation across the 100K / 100K–500K / >500K bands. Amazon GuardDuty is $4.00 per million CloudTrail management events plus add-on protection plans (EKS, S3, RDS, Lambda, EC2 Runtime) billed separately. Add Inspector v2 (per-resource per-month for EC2, ECR, Lambda + code scanning) and CloudTrail Lake / Security Lake storage as needed. Mid-market regulated workloads land at $800$3,500/month for the full security stack. Engagement-side: our managed compliance retainer covers quarterly control reviews, annual policy refresh, audit liaison, and on-call support during your audit window — $4K–$12K/month depending on framework count and account scale. Assessor fees (CPA, QSA, 3PAO, certification body) sit on top and we do not control those.

Need Expert Help?

Our articles share what we know. Our consulting engagements apply that knowledge to your specific environment, regulatory scope, and threat model.