From the PMC teamDevelopment projects start in 2027. Plan yours now to secure an early start.

Security audits

Find the weak spots before someone else does.

We review your applications, APIs, cloud setup and code for security gaps, rank every finding by risk and help you close it. For software we built, software from others and the systems around it.

  • Fast to deliver
  • Built to last
  • Secure from day one
11+years of building software for finance, IT and project teamsAbout the team
Security audits

Our security audit services

Penetration tests, code, cloud and pipeline reviews, each finding ranked by risk and checked again once it is fixed.

Penetration testing

Web applications tested from the outside, the way an attacker would.

Discuss this service

What we cover: Code reviews, penetration tests and configuration audits of web apps, APIs and infrastructure, following the OWASP Top 10 and BSI IT-Grundschutz. Scope and dates are agreed in the first call.

The team behind PMC, trusted by
  • BNP Paribas
  • Allianz
  • Hexagon
  • Hewlett Packard Enterprise
  • Enapter
Solutions

When a security audit pays off

  • Before a go-live

    A new application is checked before it faces the internet or your customers.

  • After taking over an application

    Software inherited from another team or supplier gets a clear picture of its risks first.

  • Ahead of a customer or auditor review

    Findings are closed and documented before a customer questionnaire or an audit asks about them.

  • A regular check-up

    The same review repeated after large changes, so new gaps do not stay open for long.

Going live soon, or facing a review?

Tell us the date and the scope. We propose the checks that fit, and you have the findings in time to close them.

Plan your audit
A worked example

How a project like this runs.

Example

A review before a customer portal goes live

The situation

A customer portal is about to open to the internet, with sign-in, document upload and access to order data.

What we do
  1. Scope, time window and contacts agreed in writing; intrusive checks run on the test environment.

  2. Sign-in, access rights, input handling and sessions checked against the OWASP Top 10.

  3. Cloud settings, certificates, secrets and dependencies reviewed with the administrators.

  4. Findings reported by risk, fixed with the team, then checked again.

The result

The portal goes live with the high-risk findings closed and the rest scheduled.

An illustrative example of the way we work, not a named customer.

AI inside

Security for AI and with AI

We check AI features like any other part of your application.

  • Prompt injection tests
  • Data leakage checks
  • MCP and tool permission review
  • AI-assisted code scanning
  • Dependency risk analysis
  • Readable findings reports
  • Agent action limits tested
  • Model and data access review
  • Logging of AI decisions checked
Why it pays

Why audit before someone else does

01

Every finding ranked by risk

Today
Nobody knows how exposed the application really is.
With it in place
A clear list of findings, each ranked by risk.
How we test

Careful with your systems.

The rules every audit follows, agreed before the first check.

Scope agreed in writing
We test only the systems you name, in the time window you set.
Production stays safe
Intrusive checks run against a test environment unless you decide otherwise.
Findings stay confidential
The report goes only to the people you name.
What you receive

Everything you need to own the result.

  • A report with every finding, its risk, how it was found and the fix
  • A short summary for management
  • Fixes in your code or configuration, if you want us to make them
  • A second check of every closed finding
  • Recommendations for security checks in your build pipeline

Is it right for you?

A good fit when
  • An application about to face the internet or your customers
  • Software inherited from another team or supplier
  • A customer review or an audit coming up
Not the right fit when
  • A formal certification, which an accredited body has to carry out
  • Systems you do not own or may not have tested
Speed, quality and security

Fast does not have to mean fragile.

Every project is held to the same standard, whatever the service. It is the standard we build and run PMC to every day.

  • Fast to deliver

    Results in weeks, not quarters.

    • A working version at the end of every short cycle
    • Releases through an automated pipeline, not by hand
    • Small changes shipped often, so value arrives early
  • Built to last

    Software your team can still understand and change years from now.

    • Every change built and tested automatically before it is merged
    • Unit, API and end-to-end tests in a real browser
    • Documentation and a clean handover, or we run it for you
  • Secure from day one

    Security is part of the build, not a check at the end.

    • OWASP Top 10 and BSI IT-Grundschutz as the reference
    • Dependencies and images scanned for known vulnerabilities in every build
    • Access by role, changes logged, secrets kept out of the code
How we work

From the first call to closed findings.

  1. Agree the scope

    Systems, time window and contacts are agreed in writing before the first check.

  2. Review and test

    Applications, cloud settings and code are checked against the OWASP Top 10 and BSI IT-Grundschutz.

  3. Report by risk

    Every finding with its risk, how we found it and the fix, sent only to the people you name.

  4. Fix and check again

    We close the gaps with your team or for you, then test again.

Took over an application nobody has checked?

We review the code, the dependencies and the setup, rank what we find and help your team close it.

Book a review
Ways to work with us

Choose how much of the work you hand over.

From one clearly scoped project to a team inside your business and the long-term running of what we built. Every model has one accountable partner: Virtual Eye.

  • For a defined result

    Fixed-scope project

    You know what you get before the build starts: a concept, a prototype and a fixed scope come first.

    • A workshop on your process and the result you need
    • Concept, prototype and fixed scope before production code
    • A working version at the end of every short cycle
  • When the problem is not yet clear

    Forward deployed team

    A small Virtual Eye team works inside your business, learns how work and money really move, and delivers the solution with your people.

    • One lead for management, plus the engineers who build
    • Outcome and scope agreed in writing
    • A demo every week
  • For software you already run

    Takeover and modernisation

    We take over an existing application, make it safe to change, then develop it further step by step.

    • What exists is documented and tested first
    • Stabilised before anything new is added
    • Further development in small, tested releases
  • After go-live

    Run and evolve

    We host, monitor, update and support your applications on our servers, in your cloud or on-premises.

    • Monitoring and alerts that go straight to our team
    • Backups, updates and security patches
    • Support and further development from the team that built it
Customers

What customers say about working with us.

Quotes about the Virtual Eye team from PMC projects: the same people who would work on yours.

“Well thought-out concepts, tailored precisely to us. Very competent and always friendly, even during the stressful implementation phase.”
Iris HummelManager Infrastructure Services Sales DACH, Hewlett Packard EnterpriseTranslated from German
“PMC provides valuable support in day-to-day business and the team is very reliable, serious and friendly!”
Hao LiCentral Project Office PMO, Allianz Global Corporate & Specialty SE
“As a customer from day one, we have found reliable, fitting solutions with Virtual Eye throughout the years. Above all, the fast and flexible service.”
Sebastian StepferExecutive Director Public Safety EMEA Region, HexagonTranslated from German
Tech stack

The tools we use for this.

We choose them for your systems and your team, and we document every choice.

Cloud platforms, infrastructure as code and pipelines that take every change safely to production.

Cloud platforms

  • AWS
  • Microsoft Azure
  • Google Cloud
  • DigitalOcean
  • Vultr
  • OVHcloud
  • Hetzner
  • IONOS
  • Open Telekom Cloud
  • Scaleway
  • Linode
  • Cloudflare

Infrastructure as code and automation

  • Terraform
  • Terragrunt
  • AWS CloudFormation
  • Ansible
  • Packer
  • Puppet
  • Chef
  • SaltStack

Containers and orchestration

  • Kubernetes
  • Docker
  • Red Hat OpenShift
  • Helm
  • Argo CD
  • Apache Mesos

Monitoring and observability

  • Prometheus
  • Grafana
  • ELK Stack
  • Datadog
  • Zabbix
  • AppDynamics
  • Splunk
  • Sentry
  • OpenTelemetry
  • Nagios

CI/CD

  • Jenkins
  • GitLab CI/CD
  • GitHub Actions
  • Bitbucket Pipelines
  • Azure DevOps
  • Bamboo
  • CircleCI
  • TeamCity
Your technology is not listed?

Tell us what you run. If we have not worked with it yet, we say so, and tell you how we would approach it.

Talk to our engineersSee all technologies
Industries we serve

Security audits for the industries we know

Years of PMC have taught us how these industries approve, buy, report and get audited.

Banks

Audits that prepare you for regulator and customer reviews, with findings ranked by risk.

  • Penetration tests before go-live
  • Access and permission reviews
  • Reports ready for the auditor
Questions

Questions teams ask before they start.

What do you need from us to start?

A list of the systems in scope, a contact on your side and access to a test environment. Scope and time window are agreed in writing before the first check.

Do you test our live systems?

Only if you decide so. Intrusive checks run against a test environment unless you choose otherwise, and on live systems we keep to the time window you set.

Do you also fix what you find?

If you want us to. Every finding comes with a concrete fix; we close it with your team or for you and then check again that it is closed.

Which standards do you follow?

The OWASP Top 10 for web applications and APIs, and BSI IT-Grundschutz for configuration and infrastructure.

Who sees the findings?

Only the people you name. The report is confidential and goes to no one else.

Tell us what you want to build.

Describe the process, the systems involved and when it should go live. We reply with a first assessment and the next step.

Or write to us directly: hello@virtual-eye.com

What happens next?

  1. You write to us

    What you want to build, the systems involved and when it should go live.

  2. A first assessment

    We reply with a first assessment and the next step.

  3. A workshop

    On your process and the result you need, before any technology is chosen.

  4. A fixed scope

    A concept, a prototype and a fixed scope before the first line of production code.