Audit Preparation

Audit-grade preparation for the laws, regulations and contracts you must meet, whether or not an auditor is coming

Already have an IT provider? Here's how we work together.

An example

Consider an insurance agency that must certify its compliance with the New York State Department of Financial Services (NYDFS) cybersecurity regulation, Part 500, by April 15. The officers believe the agency complies. Then someone asks a simple question: “If the examiner asked to see last quarter’s access reviews, what would we hand over?”

Nobody is sure. The control may be in place, but the proof is not, and an examiner judges the proof.

The Problem

The same thing happens before a review of a medical practice under HIPAA (the Health Insurance Portability and Accountability Act), a PCI DSS (Payment Card Industry Data Security Standard) assessment of a retailer, or a cyber insurance renewal.

The gap is rarely effort. It is not knowing which proof the auditor will ask for, where that proof is, and who owns it.

Saying “yes, we do that” is not the same as showing it.

What must be met, how it is met, and how it all fits together

Three things are easy to mix up, so we keep them apart:

  • The obligation is what your organization must meet: a law or regulation such as HIPAA or NYDFS Part 500, or a contract requirement such as PCI DSS, which card-processing agreements require and which is also a standard in its own right.
  • The standard is how the obligation is met and checked: a published set of controls such as NIST (National Institute of Standards and Technology) SP 800-53 or ISO/IEC 27001.
  • The NIST Cybersecurity Framework (CSF) 2.0 is how we govern and connect it all. Each obligation and standard is mapped to it, so one program covers them together.

For example, a medical practice must meet the HIPAA Security Rule. That is the law. To meet it, we build and check the safeguards using NIST SP 800-53 controls and the NIST SP 800-53A assessment methods: examine the documents, interview the people, and test that each control works. Then we connect everything in the NIST Cybersecurity Framework 2.0, so the same proof also counts toward the next obligation or certification.

One method for any obligation or standard

The method is the same whether or not an auditor is coming: the same audit-grade rigor, the same five levels, and the same re-test every round. The levels are measured against your organization’s own goals, not a one-size checklist.

Preparing for a formal audit or examination

An auditor or examiner will judge your proof on a set date. We rehearse it first.

Examples: laws and regulations such as HIPAA and NYDFS Part 500, and contract requirements such as PCI DSS and CMMC (the Cybersecurity Maturity Model Certification required in Department of Defense contracts).

Raising maturity where there is no audit

Some frameworks have no formal audit. For those, the “audit” is our own evidence-based review against the framework, scoped to what matters for your organization.

Examples: governance frameworks such as COBIT 2019, enterprise-architecture practice such as TOGAF, the NIST Cybersecurity Framework, and privacy and AI-risk frameworks.

Security Medic is independent. We assess against these laws, standards and frameworks as a reference. We do not certify, and we are not affiliated with the bodies that publish them.

Climb from the foundation to the hardest requirements

Consider a software company that sells to hospitals. Today its customers ask about HIPAA safeguards. Next year a large customer asks for a SOC 2 (System and Organization Controls 2) Type II report. Later, a government contract asks for GovRAMP (formerly StateRAMP) or FedRAMP authorization.

These requirements share most of their controls. So we plan your path as a climb: the foundation first, then what you must meet now, then each harder step. Every step reuses the controls and proof from the step before, so nothing is done twice, and each new requirement starts higher on the five levels.

  1. 1

    Foundation

    The essentials almost every standard shares: knowing your systems, controlling access, multi-factor sign-in, tested backups, logging and an incident plan. Measured against the NIST Cybersecurity Framework 2.0 or the first tier of the CIS (Center for Internet Security) Controls. The Cybersecurity Framework also stays the frame that connects every later step.

  2. 2

    Your sector’s rules

    The laws, regulations and contracts you are held to first, such as the HIPAA Security Rule, NYDFS Part 500 or PCI DSS. These are obligations, not a separate set of controls: each requirement is met with controls from the foundation and the standards in steps 3 to 5, and we map them back so you can show where every requirement is covered.

  3. 3

    Attestation-ready

    SOC 2: first Type I (are the controls designed well?), then Type II (did they work over months?). Software and service companies selling to healthcare and finance are often asked for one.

  4. 4

    Certification-ready

    ISO/IEC 27001, an information security management system run as a cycle of review and improvement.

  5. 5

    Government-grade

    NIST SP 800-171 and CMMC Level 2, then GovRAMP (formerly StateRAMP) or FedRAMP at Moderate, and at the top, High.

The order is set for your organization: what your customers, regulators and contracts ask for first, and what you can achieve first.

On-premises, in the cloud, or both

Most organizations run some systems in their own offices or data center and others in one or more clouds: Amazon Web Services, Microsoft Azure, Google Cloud, IBM Cloud, Oracle Cloud, or the newer AI-focused GPU clouds (often called “neoclouds”).

Every cloud provider protects its own layer and publishes its own audit reports. Your part is everything you build and configure on top. For each obligation and standard, we map which controls the provider already covers, which are shared, and which are yours, and then collect your proof for your part, on-premises and in every cloud you use.

SOC 2 reports are issued by independent CPA firms, ISO/IEC 27001 certificates by accredited certification bodies, and FedRAMP and GovRAMP assessments by accredited third-party assessors. We prepare you for them; we do not issue them.

How audit preparation works

Audit preparation holds your organization to the same rigor as the real audit. It works like training for it.

We run it in rounds. Every round rates each requirement area on a five-level scale, finds the missing proof, and re-tests the last round’s work. The scale is rolling and works like the CMMI (Capability Maturity Model Integration) levels, so maturity climbs from round to round.

The five levels

  1. 1Ad hoc

    Little is known or in place. Answers are guesses.

  2. 2Partly in place

    Some controls exist, mostly on the organization’s word.

  3. 3Documented

    Policies and procedures are written and the controls are in place.

  4. 4Evidenced

    Current proof is on file for the controls.

  5. 5Audit-ready

    The controls were walked through or tested in a mock audit, and the proof is current.

Proof expires. A backup test from two years ago does not show that backups work today, so expired proof stops counting until it is renewed.

What each round delivers

A level for every requirement area

From 1 (Ad hoc) to 5 (Audit-ready), with the reason for each rating. A “yes” without proof does not count as more than Level 2.

An evidence register

For every requirement: the proof that exists, the proof that is missing, and the person who owns producing it.

A mock-audit walk-through

We ask the questions an auditor or examiner would ask. The people who will face the real audit answer and show the proof.

A plan to reach the next level

Every action has an owner and a date.

A re-test

The next round starts by checking the work, so progress is measured, not assumed.

What we prepare you for

Obligations: what must be met

Laws and regulations, including:

Contracts and customer requirements, including:

  • PCI DSS v4.0.1, required by card-processing agreements and a standard in its own right (PCI DSS Fast-Track)
  • Cyber insurance underwriting questions (Insurance Readiness)
  • SOC 2 Type I and Type II reports that customers ask for
  • CMMC Level 1 and Level 2 for defense contracts, and GovRAMP (formerly StateRAMP) and FedRAMP authorization for selling cloud services to government, at Moderate and High

Standards: how they are met and checked

  • NIST SP 800-53 Rev. 5 controls, checked with the NIST SP 800-53A Rev. 5 assessment methods (examine, interview, test)
  • NIST SP 800-171 for sensitive government information held by contractors
  • ISO/IEC 27001 readiness, and the CIS Controls
  • COBIT 2019 and TOGAF, assessed as reference frameworks, with no formal audit

The NIST Cybersecurity Framework 2.0: how it all fits together

Every obligation and standard above is mapped to the Cybersecurity Framework, so progress on one shows up in the others. Where no formal audit exists, the same levels measure progress toward the framework’s intent and your own targets.

Where it fits

  1. Free 30-minute call to talk through the obligation and its date.
  2. Scoped assessment: every requirement area of the named obligation or standard rated, with the evidence picture and a prioritized plan.
  3. Audit preparation rounds, one-off or over a 3-, 6- or 12-month commitment, timed to finish before the audit, certification or renewal date.

What we do and do not do

We do

We rate conformance, review evidence, rehearse the audit, write the plan, and specify the controls your IT team or provider must put in place. Then we check the result.

We do not

We do not certify, attest or sign on your behalf, and we do not guarantee an audit outcome. Your own officers sign your certifications.

Each engagement is scoped in a written proposal.

Start with a free 30-minute call

Bring the obligation and the date. We will talk through where your organization likely stands and what the first round would cover.

Book a free 30-minute call