Security Audits | Double Support

A security audit is a structured look at where your software and systems could be broken into, and a report you can act on. It ends with a list, in the order the problems matter.

What we do

Review the application, its access rules and the infrastructure it runs on
Check dependencies and configuration against known weaknesses
Look at who has access to what, and at what is still switched on that nobody uses
Write up what was found, in the order it should be fixed
Go through the findings with your team, so the list becomes a plan

Who it's for

Companies who want to know where they stand before a launch, before an important client's review, or after inheriting a system somebody else built.

Related security work

Penetration Testing — when you want someone to actually try to get in, not only to review.
Threat Monitoring — when the question is what happens after the fixes, day to day.
Software Security — the whole service, including hardening and keeping updates applied.

Frequently asked questions

What is a security audit?

A structured review of where your software and systems could be broken into, ending in a report ordered by how much each problem matters.

What do you review?

The application, its access rules and its infrastructure; dependencies and configuration against known weaknesses; and who has access to what, including things switched on that nobody uses.

When should we get an audit?

Before a launch, before an important client’s review, or after inheriting a system somebody else built.

What do we get at the end?

A written list of findings in the order to fix them, which we go through with your team so it becomes a plan.

Is an audit the same as a penetration test?

No. An audit reviews; a penetration test actually tries to get in. The audit usually comes first.