SECURITY AUDIT
Find the open doors before someone else does.
I check your cloud, your code and what you show to the internet. You get a report with what is wrong, why it matters and how to fix it.
WHAT I CHECK
Three places doors get left open.
CLOUD
Your cloud setup
Azure and AWS. Identity, network, storage, logging and backups. I read the real configuration, not the diagram.
CODE
Your code
Static analysis and secret scanning on your repositories. I read the results myself, so you do not get four hundred false alarms.
OUTSIDE
What the internet sees
Slow, throttled recon on your own domains. This is what an attacker finds in the first hour.
HOW IT WORKS
Four steps. No surprises.
- 01
Scope
We sign a scope first. It lists the accounts, repositories and domains I am allowed to look at. You confirm in writing that you own them.
- 02
Access
You give me read only access or exports. Architecture diagrams, cloud configuration, identity and policy settings, source code.
- 03
Review
I run the checks. Then I verify every finding by hand against your real environment.
- 04
Report
You get the report and a call to walk through it. Your team gets a read only checklist to prove each fix.
WHAT YOU GET
A report your team can act on.
Every finding has the same four parts. No padding and no scanner dumps.
MAPPED TO
- Microsoft Cloud Security Benchmark
- CIS Benchmarks
- ISO 27001 Annex A
- Cyber Essentials
- WHAT
- What is wrong, in plain words.
- WHY
- Why it matters for your business.
- FIX
- How to fix it, step by step.
- CHECK
- How to check the fix with read only access.
THE RULES
What I don't do.
- >> Nothing outside the signed scope.
- >> No destructive tests.
- >> No denial of service.
- >> Read only access. I do not change your systems.
- >> I do not keep your data after the job. Only the report and the notes we agreed in the contract.
ABOUT AI
I use AI tools to read code and configuration faster and to sort scanner noise.
You never talk to an AI and you never get raw AI output. I check every finding against your real environment before it goes in the report. My name is on the report and I answer for it.
WHO DOES THE WORK
I'm Michal. I do every audit myself.
I have worked in cyber security for over 12 years and my background is programming. I hold CISSP. I have implemented ISO 27001, SOC 2 and Cyber Essentials.
I led security at a global B2B payment company. Before that I built and secured Azure, AWS and Kubernetes environments. I know what a good setup looks like because I have built them.
I also teach this at Korra Academy. If I can explain it to a student, I can explain it to your board.
Start with a scope call.
Thirty minutes. You tell me what you run. I tell you what I would check and what it would take.
ASK FOR A SCOPE CALLcampus@korra.academy