/Cloud security and compliance
AWS security and compliance with automated controls
We review your AWS environment the way an attacker would, and the way an auditor will. We find excessive access, exposed resources, plaintext secrets and missing logs, and fix them through pull requests. Then we automate detection and evidence with Security Hub, GuardDuty and Config, so SOC 2 or ISO 27001 compliance becomes continuous.
/Diagnosis
Signs it is time
An audit on the calendar
A customer requires SOC 2 or ISO 27001, or you are selling to the public sector in Spain and need ENS, and you have to close technical gaps and gather evidence before the date.
Access nobody reviews
IAM users with old keys, administrator permissions handed out freely and accounts for people who left the company long ago.
Endless security questionnaires
Every enterprise deal comes with a security questionnaire your team answers with doubts and no evidence at hand.
No visibility into threats
You would not know if someone were using stolen credentials or if a bucket went public until someone else told you.
/What we deliver
Concrete deliverables, in your repository
Security assessment
A review of identities, networking, encryption, secrets, logging and backups, with findings prioritized by real risk.
Remediation through pull requests
Terraform fixes for every critical finding, reviewed by your team and applied without service interruption.
Least-privilege access
IAM Identity Center with role-based access, MFA, no long-lived keys and periodic permission reviews.
Continuous detection
Security Hub, GuardDuty, AWS Config and IAM Access Analyzer active across the whole organization, with alerts routed to your team.
Control mapping and evidence
Technical controls mapped to the framework you need, with automated evidence through AWS Config and AWS Audit Manager.
Incident response plan
Runbooks for compromised credentials, data exposure and suspicious activity, with defined roles and steps.
/How we work
Our process
Assessment
With read-only access we audit the entire organization and prioritize findings by exploitability and impact.
Remediation
We fix critical issues first, through Terraform pull requests, coordinating with your team on changes that touch production.
Automation
We turn on detection and preventive controls so the issues we fixed do not come back.
Continuous compliance
We keep evidence up to date, review new findings and support you through audits and questionnaires.
AWS security audit: what we review
We start with identities, because most cloud incidents involve credentials. We review IAM users, access keys, over-permissioned roles, cross-account trust relationships and MFA usage. Then we move to the network: open security groups, resources with public IPs, shared S3 buckets and snapshots, and services exposed without a WAF in front of them.
We complete the assessment with encryption at rest and in transit, secrets management, CloudTrail log coverage, retention and backups. Each finding is ranked by exploitability and impact; the severity a tool assigns is just one input. A broad permission in an isolated test account does not carry the same weight as an exposed key with access to production.
Automated controls and continuous threat detection
Fixing findings once is not enough if nothing stops them from coming back. We enable AWS Security Hub with the AWS best practice standards in every account, Amazon GuardDuty to detect anomalous behavior, IAM Access Analyzer to find unintended external access and Amazon Inspector for vulnerabilities in instances, container images and Lambda functions.
Preventive controls complement detection. Service control policies block anyone from disabling CloudTrail or creating resources in unapproved regions, and AWS Config rules flag configuration drift. Findings are routed to your team's channels with enough context to act, instead of piling up in a console nobody checks.
AWS compliance: SOC 2, ISO 27001, ENS, PCI DSS and HIPAA
Compliance frameworks require you to prove that controls exist and keep working over time. On AWS, much of that evidence can be generated automatically: configurations evaluated by AWS Config, access records in CloudTrail, verifiable encryption with KMS and AWS Audit Manager reports. We map the technical controls of the framework you need and make clear what AWS covers, what the platform covers and what depends on your processes.
We do not replace the auditor or issue certifications. Our job is to make sure the technical side on AWS is solved and documented by the time the audit arrives, and that your answers to customer security questionnaires rest on real evidence. That shortens enterprise sales cycles and reduces the effort of every annual audit.
Shared responsibility and security incident response
AWS protects the physical infrastructure, the hypervisor and managed services; configuration, access and data are your responsibility. Many incidents start with a misreading of that boundary, such as assuming an inherited policy is still safe or that a managed database is already encrypted with your own keys. We check those assumptions one by one.
We also prepare the response. We define what happens when credentials are compromised, a bucket is exposed or GuardDuty detects suspicious activity: who decides, how resources are isolated, how evidence is preserved and how it is communicated. A rehearsed runbook cuts reaction time when every minute counts.
/FAQ
Security and compliance: frequently asked questions
Another question? Write to hello@nubent.com and an engineer will answer.
What does an AWS security audit include?
It covers identities and permissions, network exposure, encryption, secrets management, logging, backups and service configuration across every account and region. The result is a list of findings prioritized by real risk, with a proposed fix for each one. In our case, we also implement the critical fixes through pull requests.
How do I prepare for SOC 2 on AWS?
Start by defining the scope and the Trust Services Criteria that apply. Then implement the technical controls, such as least-privilege access, encryption, logging, monitoring, backups and change management, and automate evidence collection. SOC 2 also requires organizational policies and processes, which you work on with your auditor or a compliance consultant.
What does it take to certify ENS with a platform on AWS?
Spain's National Security Framework (ENS) is required for anyone providing services to the Spanish public sector. AWS has its infrastructure certified at the high category, but that covers its side: the configuration of your accounts, access, encryption, backups, monitoring and incident management are yours. We prepare those technical controls, the infrastructure documentation and the evidence the auditor asks for. We have already prepared the technical side of an ENS certification, with the evidence and documentation the audit required.
Is AWS secure by default?
AWS protects the infrastructure your services run on, but securing what you configure is your responsibility. Permissions, security groups, encryption with your own keys, bucket exposure and secrets management depend on your team. Most cloud incidents come from misconfigured accounts far more often than from provider failures.
What is AWS Security Hub?
It is the AWS service that centralizes security findings from several sources, such as GuardDuty, Inspector, Config and Access Analyzer, and evaluates your accounts against best practice standards. It gives you the security posture of your whole organization in one place and lets you automate responses to specific findings.
Does Nubent certify that my company complies with ISO 27001?
No. Certifications are issued by independent bodies and auditors. We implement and document the technical controls on AWS, automate the evidence and support you during the audit to answer questions about the platform. That way you walk into the assessment with the technical side solved and verifiable.
Related services
AWS Landing Zone
A multi-account AWS foundation with Control Tower, Organizations, SCPs, IAM Identity Center and centralized logging, automated in Terraform.
Learn moreWell-Architected Review
A review of your workloads across the 6 AWS Well-Architected pillars, with Generative AI and SaaS lenses and a remediation plan you can actually execute.
Learn moreIncidents and availability
AWS incident response and high availability: stabilization, root cause analysis, Multi-AZ architecture and disaster recovery with defined RTO and RPO.
Learn moreBuilding on AWS
AWS architecture designed and built from scratch: accounts, networking, access, CI/CD and observability in Terraform, ready to grow without a rebuild.
Learn moreFinOps and cost optimization
AWS cost optimization: spend visibility, rightsizing, Savings Plans, removal of idle resources and FinOps practices that keep the results in place.
Learn moreNext step
Let's talk about your Security and compliance project
30 minutes with an engineer. Concrete next steps, whether or not you work with us.