Technical Security Audit
We are accountable for the quality of the audit. We put our guarantees in the contract and work under strict NDAs.
- 2critical
- 5high
- 8medium
Three types of audit
You can order one type or several at once. We agree on the scope during a quick consultation.
- 01
Server and infrastructure audit
What it isA security check of the servers, physical and cloud, that run your company's systems and websites.
What we checkHow well your servers and cloud are protected, who has access to them, whether the system is updated on time, whether email and the domain are protected, whether you have working backups and whether you can actually restore from them.
ResultMake sure your clients' data is well protected, and reduce the risk of sudden downtime.
You will learn the real risks and see where to spend your budget first.
- 02
Service runtime environment audit (Docker)
What it isA check of the environment where separate parts of your product run (containers): how isolated they are from each other and how secure.
What we checkWhether there are misconfigurations, exposed passwords or excess permissions that could let a failure in one place affect the whole product.
ResultProtect your product from the inside.
Reduce the risk that a single vulnerability in a container gives attackers access to your entire infrastructure.
- 03
Application and integration audit
What it isAn analysis of how your software exchanges information with external platforms, payment gateways and APIs (software “bridges” between services).
What we checkHow your product exchanges data with payment systems and third-party services, and whether there are weak spots where information could be intercepted.
ResultMake sure payments and integrations are protected.
Make your connections with partners more reliable and reduce the risk of your clients' data leaking through third-party services.
Need a check of bots, assistants and AI agents? That is a separate service: AI Security
What Is Inspected
- External network perimeter and public web applications
- Internal server configuration, SSH/RDP access, Active Directory/identity controls
- Backup presence, isolation, and real restoration tests
- Cloud environments (AWS, GCP, Azure, DigitalOcean) and storage permissions
Five steps from first contact to report
- Step 1Quick consultation
We learn about your infrastructure and goals and agree on the scope, timeline and cost.
- Step 2Contract and access
We sign the contract and NDA and receive limited access to the agreed systems.
- Step 3Inspection
We examine servers, containers, applications and integrations according to the agreed plan. We change nothing without your knowledge.
- Step 4Report and plan
What we found, what it means for the business, what to do first and what it costs.
- Step 5Review with you
A call where we explain the results in plain words and answer your questions.
A report you can act on
- Executive Summary on one page
- Prioritized Bug Matrix (CVSS): critical, high and medium, with the business risk in plain words
- Technical Remediation Guide: step-by-step recommendations with time and budget estimates
- critical
- critical
- high
- high
- medium
What we usually find
Backups exist, but no one has ever tested restoring from them
Set up regular restore tests and keep a copy separate from the main system.
A former employee's access is still active
Revoke the access, turn on two-factor sign-in and keep a list of who has access to what.
Passwords and keys sit right in the code or in a shared chat
Move secrets to a secure vault and replace any that may have fallen into the wrong hands.
The payment system integration key is stored in plain text
Replace the key, move it to a secure vault and limit the integration's permissions.
Generalized examples of typical situations, not stories of specific clients.
Included in packages
All packagesIt depends on the size of your infrastructure and the checks included. We give a more precise estimate after a quick consultation. Typical timeline: 5–10 working days.