isny
Services
Managed ITManaged SecurityMicrosoft 365 & GoogleComplianceAI SolutionsBusiness Phone (VoIP)vCIO & Consulting
Industries
HealthcareInsuranceLegal
Compliance AI Solutions Pricing
What Clients Say
Client TestimonialsGoogle Reviews
Company
Our TeamLife at ISNYCareersBlogContact
Client Tools
Remote SupportTicket PortalPayment PortalUser Hub (Forms)
All articles
Compliance

Security Risk Assessments: How to Run One That Actually Holds Up in an Audit

October 12, 2026
Security Risk Assessments: How to Run One That Actually Holds Up in an AuditCompliance

Nearly every compliance framework your business answers to asks for the same thing in different words: know your risks, write them down, and show what you did about them. HIPAA calls it a security risk analysis. The FTC Safeguards Rule calls it a risk assessment. 23 NYCRR 500 requires one too. Cyber insurers now ask for evidence of one at renewal.

Despite that, the risk assessment is often the weakest document in a small firm’s compliance file. It is either a generic template with the company name swapped in, or it was done once, years ago, and never touched again. Here is how to build one that stands up when a regulator, auditor, or underwriter asks to see it.

What a Risk Assessment Is (and Is Not)

A risk assessment is a structured look at the threats and weaknesses that could affect the confidentiality, integrity, or availability of the sensitive data you hold, and a decision about how to handle each one. It is not a vulnerability scan, a penetration test, or a checklist of controls. Those are useful inputs, but none of them tells you which risks matter most to your business.

The assessment connects three things: what you have, what could go wrong, and what you are doing about it. If any of those is missing, the document will not hold up.

A Practical Process

You do not need a hundred-page report. You need a repeatable process with clear records:

  • Define the scope. List every system, application, device, and vendor that stores, processes, or transmits sensitive data, including cloud services and personal devices if staff use them for work.
  • Map where the data lives. Client records, financial data, health information, and email attachments all end up in more places than most owners expect. An accurate asset inventory makes this much easier.
  • Identify threats and vulnerabilities. Think ransomware, phishing, lost laptops, misconfigured cloud storage, departing employees, vendor breaches, and simple human error. Pair each with the weakness that would let it succeed.
  • Rate likelihood and impact. A simple high, medium, low scale is fine, as long as you apply it consistently and can explain the reasoning.
  • Document existing controls. Note what already reduces each risk, such as multi-factor authentication, encryption, backups, or training.
  • Decide on a treatment. For each remaining risk, choose to reduce it, transfer it (for example, through insurance), accept it, or avoid it. Assign an owner and a target date.

Where Assessments Fall Apart

Auditors see the same weaknesses again and again:

  • Generic content. If the document could describe any company, it does not describe yours. Specific systems, vendors, and workflows are what make it credible.
  • No follow-through. Identifying a risk and then doing nothing is worse than not listing it. Every high-rated item needs a documented plan and a record of progress.
  • Stale dates. An assessment from several years ago does not reflect your current environment. Plan to review it at least annually, and again after major changes such as a new platform, an office move, a merger, or a security incident.
  • Leaving out vendors. Your risk includes the third parties that touch your data. Include your key vendors and note what you have done to evaluate them.
  • No management sign-off. Leadership should review and approve the results and the remediation priorities. That shows the process is taken seriously.

Keep It Alive

The best assessments work as a running register, not a one-time report. When something changes, such as a new tool, a new vendor, or a near miss, you update the register. When a risk is addressed, you record what was done and when. That living record is what proves to an auditor that security is a managed process in your business, not a yearly scramble.

If you are not sure where to begin, a good starting point is an honest inventory of your systems and data, followed by a short working session with the people who know how the business actually runs. A managed IT and compliance partner can facilitate that process, bring outside perspective, and help turn the findings into a prioritized plan.

This is general guidance, not legal advice.

Back to all articles

Want this handled for your business?

Book a free assessment and we'll map exactly what your environment needs.

Book a free assessment