Client Support 248-284-7171 servicedesk@centaris.com
All Posts
Cybersecurity
10 min read

Cybersecurity Risk Assessment: What It Covers and What's Next

A cybersecurity risk assessment should show what is exposed, what to fix first, and who owns each fix. See what gets reviewed and what happens next.

By Centaris Team

Two professionals reviewing cybersecurity risk assessment findings on a tablet in a manufacturing warehouse.

Most mid-sized organizations order a cybersecurity risk assessment because someone made them. An insurer added questions at renewal, or a hospital partner wanted a current risk analysis. Leadership skims the report, and the findings sit in a shared drive until the next request shows up.

IBM's 2026 Cost of a Data Breach Report put the global average breach at $4.99 million, and IBM's security leadership named the lag between finding a weakness and fixing it as a direct driver of that cost. For a 200-person manufacturer in Macomb County or a clinic network in West Michigan, three questions matter more than the page count. What was tested? What turned up? Who is fixing it, and by when?

Infographic listing three questions a cybersecurity risk assessment should answer: what was tested, what turned up, and who is fixing it.

Those same questions are a fair way to judge any provider of IT and security support across the Great Lakes. For the wider view of consulting and response, start with Cybersecurity Services in Michigan: The Complete Guide.

What Does a Cybersecurity Risk Assessment Include?

A cybersecurity risk assessment identifies the systems and data your business depends on, tests the controls protecting them, rates each weakness by likelihood and impact, and turns the results into a ranked remediation plan. The NIST Cybersecurity Framework 2.0 follows the same arc in its risk assessment category, which starts with recording vulnerabilities and ends with tracking a response to each risk.

A review that audits the office network but skips the plant floor misses the path an attacker would take. A complete security risk assessment should reach every area below, with evidence you can see for each.

Area reviewedWhat gets examinedEvidence you should see
Assets and dataDevices, cloud tenants, SaaS apps, sensitive data locationsCurrent asset inventory and data-flow diagram
Identity and accessMFA coverage, admin rights, dormant accountsConditional access export and privileged account list
Endpoints and serversPatch levels and EDR coveragePatch compliance and EDR coverage reports
NetworkInternet exposure and office-to-plant or clinical segmentationExternal scan results and a segmentation test
Backup and recoveryIsolation and restore capabilityDated restore test with recovery time
Third partiesVendor remote access and integrationsVendor access inventory with review dates
Microsoft 365 and cloudTenant settings, sharing, app consentsBaseline comparison and audit retention settings
AI toolsApproved and unapproved useAcceptable-use policy and data loss reports

Organizations that run on Microsoft 365 should add a deeper tenant review, the kind described in Microsoft 365 Security Assessment: Are You Ready?

Proof Beats Attestation

Ask for evidence on every finding that matters. A dated restore test shows what would happen in a real outage, which a green backup dashboard can't. An exported conditional access policy does the same for MFA and usually surfaces the exemptions everyone forgot, like the ERP service account.

Staff AI use needs to be in scope too. Verizon's 2026 Data Breach Investigations Report found that 45% of employees regularly use AI on corporate devices, up from 15% a year earlier. You'll want to know what's being pasted into those tools before a customer's drawings end up in one.

The Risk Assessment Process, Step by Step

A professional risk assessment process moves from scoping and discovery through testing and analysis to a leadership readout. Each stage should leave behind a document that someone outside the project could read.

  1. Scoping. Leadership and the assessor agree on which sites and frameworks are in play. You get a written scope statement and schedule.

  2. Discovery. Interviews and read-only automated tools build an asset inventory, which usually turns up at least one forgotten system.

  3. Testing. Scans and configuration reviews check whether controls work as described, with spot checks like a sample restore.

  4. Analysis. Each finding gets a likelihood and impact rating, then gets mapped to the framework that governs you, such as HIPAA or NIST SP 800-171.

  5. Readout. Leadership walks through the results in business terms and receives a ranked roadmap with owners and dates.

Five-stage risk assessment process timeline from scoping and discovery through testing and analysis to a readout with a ranked roadmap.

Protect the interview time in the first two weeks. Whoever runs your backups probably knows which job has been failing since spring, and a rushed risk assessment process rarely gets far enough to hear about it.

What Cybersecurity Gaps Do Assessments Usually Find?

Most assessments surface the same short list of problems in machine shops and clinics across Michigan, led by unpatched internet-facing systems and stale accounts. Exploited vulnerabilities have overtaken stolen credentials as the top way attackers get in, accounting for 31% of breaches in Verizon's 2026 data.

6 Findings That Show Up in Most Reports

  1. Internet-facing systems missing critical patches. Attackers scan for VPN appliances and firewalls first. In the median case, organizations in Verizon's data had 50% more critical vulnerabilities to patch than a year earlier.

  2. Accounts that outlived their owners. Former employees and old contractors keep working logins for months, and service accounts with domain admin rights rarely get reviewed.

  3. Plant-floor and clinical workarounds. Programs reach CNC machines on USB drives, and shipping stations share one login. Each workaround needs documented compensating controls.

  4. Flat networks between the office and operations. A compromised front-office laptop shouldn't be able to reach an HMI or an imaging system. Segmentation gets assumed far more often than it gets tested.

  5. Vendor access that never expired. Remote tunnels for machine builders and EHR vendors outlast their projects. Verizon found that third parties took almost 8 months to resolve half of their weak password and permission findings.

  6. Recovery plans no one has rehearsed. Backup jobs report success more reliably than they restore data. If leadership expects the plant back in eight hours and the last restore took three days, the plan is off by more than two days of production.

Someone on your IT team probably knows about most of these cybersecurity gaps already. A good assessment writes each one down with its business impact and a named owner.

How Are Assessment Findings Prioritized?

Findings are ranked by how likely an attacker is to use them and how much damage that would cause, then adjusted for the effort a fix takes. A missing patch on an internet-facing VPN outranks a dozen medium findings on internal file servers, whatever the scanner's severity column says.

Multiply likelihood by impact, each on a 1 to 5 scale, and every finding gets a score out of 25.

Finding (illustrative)LikelihoodImpactScoreFix effortPriority
Unpatched VPN appliance on CISA's Known Exploited Vulnerabilities list5525LowWithin days
Active accounts for 14 departed employees4416LowWithin days
No timed restore test in 18 months3515MediumThis quarter
Office and plant systems on one flat network3515HighPlanned and budgeted
Audit logs retained for only 90 days236LowThis quarter

Scores and tiers above are illustrative and will vary with your environment.

The restore test and the flat network both score 15, but segmentation needs downtime windows on the production schedule, so the two land in different tiers. The departed-employee accounts still belong in the first sprint because disabling them takes an afternoon.

Risk matrix plotting five illustrative findings by likelihood and impact, from an unpatched VPN scoring 25 to short log retention scoring 6.

What Happens After a Cybersecurity Risk Assessment?

After the readout, findings move into a remediation roadmap with named owners and target dates. Quick fixes get closed and verified, larger projects get budgeted, and anything the business chooses to carry gets documented as an accepted risk.

Set those dates on day one because known problems tend to linger. In Verizon's 2026 data, organizations fully remediated only 26% of the critical vulnerabilities on CISA's Known Exploited Vulnerabilities list, and the median time to full resolution grew to 43 days.

Security Remediation in Four Tiers

Time windows give leadership an order of work and something concrete to check at the next meeting.

Auditors and regulators ask about that last tier more than the others. A signed, dated decision to carry a known risk is something you can defend when an incident later brings it to light.

Four security remediation tiers, from fixes within days to documented risk acceptance, with Verizon data showing 26% of critical flaws fully fixed.

Retest, Then Assign the Work

Ask for a retest of every high-priority item before it's marked closed, and file the before-and-after evidence with the report. Capacity is the usual sticking point after a cybersecurity assessment because internal teams are buried in tickets. Some organizations hand the security remediation roadmap to managed cybersecurity services. Others add co-managed IT support for workstreams like patching, with written lines on who owns what.

Between assessments, keep the findings in a risk register that leadership reviews quarterly. The next assessment then starts from a known baseline, and you can show an insurer exactly what moved.

Who Needs a Security Risk Assessment?

Any organization that holds regulated data or sells into a regulated supply chain should have one on the calendar, as should anyone facing an acquisition, a major migration, or new IT leadership.

Healthcare organizations can't treat it as optional because the HIPAA Security Rule requires an accurate and thorough risk analysis. In July 2026, HHS's Office for Civil Rights settled with OSF Healthcare, which has providers in Illinois and Michigan, for $552,250 after a ransomware attack. The first potential violation OCR listed was the failure to conduct an accurate and thorough risk analysis. If your healthcare organization can't produce a current one, you already have your first finding.

Defense suppliers carry a similar duty. CMMC's third-party certification phase is suspended while the Department of War reviews the program, yet self-assessments under NIST SP 800-171 remain in force. A manufacturer in the defense supply chain that signs an affirmation without a recent assessment behind it takes on legal exposure. IT Compliance and Security Readiness: The Complete Guide walks through each framework's requirements.

Who Should Conduct It?

An independent reviewer who knows your industry and framework should lead it, working with your internal IT lead. Self-checks help, but an outside cybersecurity assessment catches what the people who built the environment have stopped noticing. Get a second opinion if your provider grades its own work.

The right assessor tests configurations directly. Ask how they handle USB controls on a plant floor, or medical devices a vendor won't let you patch, and whether the same team stays through remediation. Be wary of a scan with a logo on it or a fully remote review of a plant floor. No technology provider can certify you, since accredited third parties handle CMMC certification and TISAX labels.

Frequently Asked Questions

How long does a cybersecurity risk assessment take?

For a mid-sized organization, expect a few weeks from kickoff to readout, depending on the scope. Multi-site manufacturers take longer. Most of your team's time goes into interviews early on.

Is a vulnerability scan the same as a cybersecurity assessment?

No. A scan lists technical weaknesses in systems it can reach. An assessment adds control testing and business context, then ranks what to fix.

How often should you repeat a security risk assessment?

Plan on once a year, plus after an acquisition, a major migration, or a security incident. HIPAA-regulated organizations should also update their risk analysis whenever systems change in a meaningful way.

Does an assessment make you compliant?

No. It shows where you stand against a framework and what closing the gaps will take. Compliance comes from doing that work and keeping evidence that controls keep operating.

See What Your Environment Is Actually Exposing

Most findings above can be fixed faster than leadership expects once each one has an owner. The organizations in OCR press releases were usually missing a current picture of their own environment.

Centaris is an IT and cybersecurity partner for manufacturers and healthcare organizations across Michigan and the Great Lakes region, along with other regulated businesses. Our engagements start with an assessment because recommending tools before understanding your exposure is guesswork. We show you what we find in plain business terms and let you decide what to address first. Our in-house team can then handle security remediation fully managed or alongside your IT staff, and the same people stay involved if something goes wrong.

Schedule a no-obligation assessment and find out where your cybersecurity gaps actually are.

Ready to Talk?

Schedule a no-obligation assessment and get clarity on your environment.

Schedule an Assessment →