Cloud / Identity
Understand what your cloud permissions make possible.
Connect identity permissions, exposed services, and configuration weaknesses into a clear picture of cloud risk. Understand how an initial foothold could reach sensitive workloads or data.
01 / Assessment coverage
What could an attacker do with a compromised cloud identity?
I review the permissions and trust relationships around agreed resources, then validate relevant attack paths within the approved boundaries.
Identity & access management
Users, roles, policies, service identities, and permissions that exceed their intended purpose.
Trust & privilege boundaries
Role assumption, cross-account relationships, and opportunities to move into more privileged identities.
Public exposure
Internet-facing workloads, storage access, management interfaces, and unintended resource exposure.
Workload configuration
Security settings of the compute, storage, and managed services included in the engagement.
Secrets & sensitive data
Credential handling, access to secrets, and the paths that could lead to business-critical data.
Attack-path validation
Controlled validation of relevant combinations of identity, network, and configuration weaknesses.
Provider rules and service-specific restrictions are checked during scoping. Testing is limited to the customer resources and actions authorized for the engagement.
Example: AWS penetration testing policy02 / The engagement
Clear scope. Thorough testing. Useful answers.
You know what is being tested, how findings are communicated, and what happens next.
- 01
Agree the scope
Define your objectives, assets, access, testing windows, and rules of engagement. Scope and written authorization come first.
- 02
Test & validate
Combine manual testing with supporting tools. Investigate realistic attack paths and raise critical findings during the assessment.
- 03
Explain the risk
Receive a report with business impact, reproducible evidence, priorities, and practical remediation steps.
- 04
Support the fix
Walk through the findings together. Agree any remediation support and retest window in the proposal.
03 / What you receive
A report your team
can put to work.
Leadership needs the risk. Engineers need the evidence. Your report connects the two.
- Executive summary of risk and business impact
- Validated findings with evidence and reproduction steps
- Prioritized, actionable remediation guidance
- Coverage, limitations, and a findings walkthrough
04 / Before we start
A few good
questions.
Clear expectations make for a better engagement.
Which cloud platforms can you assess?
Share your provider, services, and target accounts when you enquire. Platform-specific coverage and required access are confirmed during scoping so the proposal reflects your actual environment.
Is this a configuration review or a penetration test?
That depends on your objective. A review examines configuration and access controls; a penetration test also validates agreed attack paths. The proposal states which activities and resources are included.
Do we need permission from the cloud provider?
Provider requirements vary by service and activity. We review the applicable policy before testing, confirm that you can authorize the target resources, and identify any additional approvals required.
How do you handle confidentiality and sensitive data?
Confidentiality, evidence handling, secure report delivery, and retention requirements are agreed before testing. An NDA can be arranged. Please use the initial enquiry to describe your environment without sending credentials or sensitive records.
Is retesting included?
Retesting scope, timing, and any associated fee are agreed in the proposal. When included, the retest checks the remediated findings and records their status; it is not a fresh assessment of newly added functionality.
Let’s talk about your security
Start with a conversation.
Choose a time to discuss cloud security testing, your priorities, and the scope of an assessment.
Choose from my available times through Calendly.