| Base Score | 55.0 |
| KEV Penalty (3 × −15, max −30) | −30.0 |
| Credits Earned | 0 |
| Final Score | 25 |
An automated scanner finds Summit's network gateway via Shodan or Censys and identifies the three known CVEs. The exploit is public and takes under a minute to execute. No human attacker is present at this stage, this is fully automated. The attacker now has a session inside the network perimeter.
On Summit's flat, unsegmented network, every device is visible from the initial foothold: the primary server, all 58 workstations, medical devices, billing terminals, and the EHR system. The breakout time, time to reach a second device, is approximately 2 hours. With segmentation, this would take days, giving the team time to detect the intrusion.
Cached credentials are extracted from the server. Cross-referenced with the 24 dark web breach records, the attacker tests known passwords against the EHR login. Password reuse from the billing@ account, in an active healthcare credential dataset since 2024, yields a successful EHR login. The attacker now has access to patient records for every patient the billing account can reach.
Before encrypting, ransomware operators typically exfiltrate patient records for leverage. The 86,400 patient files on the primary server, PHI, insurance IDs, SSNs, clinical notes, are copied to attacker infrastructure. This data becomes the second lever: pay the ransom, or patient records are published. Under HIPAA, publication triggers mandatory breach notification to every affected patient regardless of payment.
Encryption is deployed across the flat network. Server, workstations, and any reachable backup targets are locked simultaneously. Clinical operations halt: no access to patient charts, scheduling, billing, or prescriptions. With 14 unencrypted workstations, every patient file on those devices is immediately readable by the attacker, no decryption key required on their end.
The ransom note references the exfiltrated patient data. HIPAA requires notification to affected patients within 60 days, and to HHS and media if more than 500 patients in a state are affected. Recovery without paying takes 3–6 weeks for a practice this size. Legal, notification, and PR costs frequently exceed the ransom. Average total cost for a mid-size healthcare breach: $2.1M (IBM 2024).
Three CISA KEVs on the gateway, combined with 24 dark web credentials and a flat network, create conditions that ransomware operators who specialize in healthcare specifically target. A ransomware event halts clinical operations, locks every patient record, and triggers mandatory HIPAA breach notification. Cyber insurance may deny the claim entirely if known unpatched vulnerabilities contributed to the breach.
A breach of more than 500 patient records triggers mandatory HHS OCR notification and often an active investigation. Missing HIPAA risk assessment for 3+ years, unencrypted PHI on 14 devices, and absent email security controls are independent liabilities that exist today. No breach is required to trigger OCR scrutiny.
The data discovery scan mapped $8.2M in sensitive patient data across Summit's systems. A full breach exposing 86,400 patient files triggers per-record costs, Colorado state privacy requirements, and potential class action exposure. Healthcare records sell for $250–$1,000 each on criminal forums.
| Gateway firmware patch (IT time, 4 hrs) | ~$200 |
| Password resets + MFA verification | ~$150 |
| DKIM + DMARC configuration (3 hrs) | ~$300 |
| BitLocker on 14 endpoints | ~$800 |
| Windows 11 upgrades (5 devices) | ~$1,500 |
| Email security solution (license + setup) | ~$1,200 |
| Network segmentation / VLANs | ~$2,400 |
| Backup restore test + RTO/RPO doc | ~$400 |
| HIPAA risk assessment documentation | ~$3,000 |
| Cloud email backup (license) | ~$600 |
| Total Year 1 Investment | ~$10,550 |
| Layer 1: Ransomware (midpoint) | $415,000 |
| Layer 2: HIPAA breach (midpoint) | $150,000 |
| Near-term combined midpoint | $565,000 |
What was found: The network perimeter device is running firmware with three active CVEs listed on CISA's Known Exploited Vulnerability catalog: CVE-2023-44221 (OS command injection, CVSS 7.2), CVE-2024-40766 (improper access control, CVSS 9.3), and CVE-2024-53704 (authentication bypass, CVSS 9.3). CISA's KEV catalog is reserved for vulnerabilities with confirmed active exploitation in the wild, not theoretical risks.
Business risk: An attacker exploiting CVE-2024-40766 gains access to the internal network without any credentials. From there, Summit's flat network puts the clinical server, EHR system, and all 58 workstations within reach in approximately 2 hours. This is the first entry point ransomware operators scan for, and it is currently open.
Remediation: Update the gateway firmware to the latest stable release addressing all three CVEs. The vendor published patches in Q3–Q4 2024 and Q1 2025. Estimated time: half a day with one scheduled maintenance window. This action alone removes the −30 point penalty and moves the score from Critical to At Risk immediately.
What was found: The data discovery scan identified 14 workstations storing patient records, insurance data, SSNs, and clinical notes in plain text with no disk encryption. Total sensitive data on these 14 devices exceeds $800,000 in modeled liability. The primary clinical server holds the largest concentration ($7.7M), but individual workstations carry the highest per-device risk because they are mobile and most likely to be physically lost or stolen.
HIPAA context: The HIPAA Security Rule requires technical safeguards including access controls and encryption for electronic PHI at rest. Unencrypted devices containing PHI require breach notification to patients if lost or stolen, regardless of whether the data was accessed. OCR has issued fines specifically for unencrypted device losses ranging from $150,000 to $4.3 million.
Remediation: Deploy BitLocker full-disk encryption on all 14 affected workstations. For devices running Windows 11 Pro/Enterprise, BitLocker is included and requires only policy deployment through management tooling. Estimated: 2 managed deployment sessions. Recovery keys should be escrowed to a central management system. Do not rely on individual users to retain their keys.
What was found: Dark web monitoring identified 24 credential breach records across 8 Summit staff accounts. Breakdown by account: billing@ (6 records), rtorres@ (5), jwhitfield@ (4), mreyes@ (3), admin@ (3), scheduling@ (2), front@ (1). The most recent, billing@ in a healthcare-specific credential stuffing dataset (November 2024), is the most concerning because it targets healthcare systems specifically.
Business risk: A successful login to your billing system or EHR using a breached credential exposes every patient record that account can access, enables fraudulent insurance claims, and may not trigger any alert depending on logging configuration. The billing@ account's 6 breach records, combined with the suspicious mailbox rule finding, suggest this account may already be compromised.
Remediation: (1) Immediately force password resets on all 8 accounts. (2) Confirm MFA is active on every account, MFA blocks credential stuffing even when passwords are known. (3) Audit billing@ for any unauthorized access or activity in the last 90 days. (4) Maintain ongoing dark web monitoring to detect future exposures in real time.
What was found: No DKIM records configured. No DMARC records found. SPF is passing. Without DKIM and DMARC at enforcement policy, the @summitmedgroup.com domain has no technical controls against email spoofing. Anyone can send email that appears to come from any address at your domain, physicians, billing staff, or administrators.
Healthcare-specific risk: Medical practices are a primary target for patient-facing BEC scams: fake bill collection emails, fraudulent prescription requests, insurance verification scams, and physician impersonation for wire transfers. Colorado BEC losses totaled $14.2M in 2025 (198 victims). A single successful patient scam involving your practice's domain creates legal and reputational exposure beyond the financial loss.
Remediation: Configure DKIM signing keys in your DNS. Add a DMARC record at p=quarantine: v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@summitmedgroup.com. This is typically completed in 2–3 hours and earns Credit #4 (+5 pts toward the 3D DeepDive score). Escalate to p=reject after 30 days of monitoring.
What was found: No documentation of a formal HIPAA risk assessment was provided or identified during the intake process. The last confirmed assessment dates to more than 3 years ago, predating the current network configuration, the gateway deployment, and the shift to a cloud email and productivity platform for practice communications.
Regulatory risk: 45 CFR §164.308(a)(1)(ii)(A) requires covered entities to conduct an accurate and thorough assessment of potential risks to ePHI. OCR considers absence of a documented risk assessment as willful neglect if a breach occurs, the highest HIPAA fine tier, up to $50,000 per violation. The assessment gap also means Summit lacks the documentation baseline needed to respond to an OCR audit.
Remediation: Commission a formal HIPAA Security Risk Analysis using HHS-approved methodology. The findings from this 3D DeepDive assessment provide the technical foundation for that analysis. A documented risk assessment can be completed in one day with the right framework and should be repeated annually. Castile Security can provide the risk assessment documentation as part of the remediation plan.
What was found: Identity threat monitoring flagged 1 detection on the billing@summitmedgroup.com account: a suspicious inbox rule. The rule appears to automatically process emails matching certain subject-line patterns. Given that this account also has 6 dark web breach records, the most of any account in the practice, this finding warrants immediate investigation rather than routine follow-up.
Business risk: Unauthorized inbox rules are a common persistence technique after account compromise. An attacker who gained access via a breached credential may have created a rule to forward insurance correspondence, billing confirmations, or payment notifications to an external address, while keeping messages appearing normal to the legitimate user.
Remediation: (1) Audit the full inbox rule list for billing@ immediately. (2) Export and preserve evidence before any deletion. (3) Force a full password reset and MFA re-enrollment. (4) Review the last 90 days of login history and mail send activity for anomalies. If unauthorized access is confirmed, evaluate whether a HIPAA breach notification is required.
What was found: A backup solution is in place and running. However, no restore test has been documented, and no formal RTO (Recovery Time Objective) or RPO (Recovery Point Objective) has been defined. The practice does not currently have a documented answer to: "If we are fully encrypted tomorrow, how long will it take to restore clinical operations, and how much data will we lose?"
Business risk: In healthcare ransomware events, practices that have tested backups recover in 2–5 days. Practices that discover backup issues during a live incident take 3–6 weeks, during which no patient records are accessible, no prescriptions can be verified, and clinical operations are reduced or halted.
Remediation: Schedule a backup restore test: select one week of patient records, restore them to an isolated environment, and document the process and time. Define RTO (how long is acceptable) and RPO (how much data loss is acceptable). This half-day project earns Credit #3 (+5 pts toward the score) and produces a documented recovery baseline. Repeat quarterly.
| Action | Score Impact | Effort |
|---|---|---|
| Patch gateway KEVs (removes −30 penalty) | +8 pts | Half-day |
| Configure DKIM + DMARC + earn Credit #4 | +7 pts | 2–3 hrs |
| Backup restore test + RTO/RPO + earn Credit #3 | +8 pts | Half-day |
| Network segmentation (VLANs) + earn Credit #6 | +7 pts | 1–2 sessions |
| Enable BitLocker on 14 endpoints | +5 pts | 2 sessions |
| Deploy email security + reset breached accounts | +4 pts | 1–2 sessions |
| HIPAA risk assessment + IR plan + 100% EDR | +3 pts | 1 day |
| Total projected at 90 days | +42 → ~67 (Developing) | ~4 weeks effort |
This assessment set out to answer a straightforward question: is Summit Medical Group prepared for the threats facing a 58-person healthcare practice in 2026? The honest answer is: not yet. But the gap is specific, the path is clear, and the tools to close it are already in place. The Critical score is driven entirely by a firmware update on one network device. That is not a broken security culture, it is a maintenance window that hasn't been scheduled yet.
The findings that require action are concrete and achievable. Patching the gateway removes the Critical designation in one half-day window. Forcing password resets on eight accounts closes an active attack vector in under an hour. Configuring DMARC protects every patient from physician impersonation scams in a 2–3 hour project. These are not six-month initiatives. They are tasks on a calendar, and the 90-day roadmap in this report sequences them in the order that produces the maximum score recovery and risk reduction in the shortest time.
The financial case for action is clear. Summit's realistic near-term exposure runs from $350,000 to $900,000 across the two most likely scenarios. The tail risk, a full PHI breach of the 86,400 patient files on the primary server, extends to $8.2 million. Against that exposure, the cost of the remediation plan represents approximately a 45-to-1 return on investment. In healthcare, where the average data breach now costs $9.77 million (IBM 2024), that math is compelling at every investment level.
Summit's patients trust this practice with their most personal information: diagnoses, prescriptions, financial records, and insurance details. The $8.2 million in sensitive data mapped across these systems is not a liability to be ashamed of, it is the record of years of patient care. Protecting it is a professional obligation, and it is entirely achievable within this quarter.
Castile Security will re-score Summit Medical Group at the 90-day mark to confirm progress and deliver an updated 3D DeepDive report. The target is a Developing band score of 67, meaningful progress that demonstrates to patients, payers, and partners that Summit takes information security as seriously as clinical care. This is how a practice that starts at Critical becomes one that its patients can trust with confidence.
| Pillar | Weight | Pillar Score | Contribution | Key Drivers |
|---|---|---|---|---|
| Device | 30% | 62.0 | 18.6 | EDR 91% coverage; 3 KEVs on perimeter; 5 EoL devices; no segmentation |
| User | 24% | 58.0 | 13.9 | No DMARC/DKIM; MFA partial; 8 breached accounts; no email security |
| Governance | 20% | 45.0 | 9.0 | No IR plan; HIPAA risk assessment 3+ years stale; limited logging |
| Data | 14% | 55.0 | 7.7 | PHI mapped ($8.2M); no encryption at rest; 3 files sent outside org |
| Backup | 12% | 48.0 | 5.8 | Backup running but untested; no RTO/RPO defined; no M365 backup |
| Base Score | 55.0 | |||
| KEV Penalty (3 × −15, max −30) | −30.0 | CVE-2023-44221, CVE-2024-40766, CVE-2024-53704, all reachable | ||
| Credits Earned | 0 | No credit thresholds met this period | ||
| Final Score | 25 · Critical | |||
Policy floor: Active EDR (91% coverage) and active perimeter firewall confirmed. BDR unverified (no restore test). Policy floor of 30 does not apply, all three controls (active EDR, active firewall with licensed services, active BDR) must be confirmed for floor eligibility. Score stands at 25.
Confidence: 85%, Deductions: −10 EDR coverage below 95% threshold · −5 external scan age 32 days (2 days over window). All core feeds present: endpoint protection, email security trial, data discovery scan, identity and dark web monitoring, phishing simulation platform.
| Device | User | OS | Status | Agent Ver | Last Scan |
|---|---|---|---|---|---|
| SMGSRV-CLINICAL01 | Support | Windows Server 2022 (20348) | Online | 25.1.2.100 | Mar 24, 2026 |
| SMGSRV-BACKUP01 | Support | Windows Server 2019 (17763) | Online | 25.1.2.100 | Mar 24, 2026 |
| SMGWS-BILLING01 | billing | Windows 11 Pro (26100) | Online | 25.1.2.100 | Mar 24, 2026 |
| SMGWS-DR-TORRES | rtorres | Windows 11 Pro (26100) | Online | 25.1.2.100 | Mar 24, 2026 |
| SMGWS-JWHITFIEL | jwhitfield | Windows 11 Pro (26100) | Online | 25.1.2.100 | Mar 23, 2026 |
| SMGWS-FRONT01 | s.park | Windows 10 Pro (19045) ⚠ EoL | Offline | 24.2.3.471 | Mar 22, 2026 |
| SMGWS-FRONT02 | scheduling | Windows 10 Pro (19045) ⚠ EoL | Online | 24.2.3.471 | Mar 24, 2026 |
| ... 46 additional devices in full inventory. 5 unmanaged devices pending EDR deployment (exam room tablets and 2 reception desktops). | |||||
| Breaches | Most Recent | Notable Source | |
|---|---|---|---|
| billing@summitmedgroup.com | 6 | Nov 2024 | Healthcare Credential Stuffing Dataset 2024 |
| rtorres@summitmedgroup.com | 5 | Apr 2025 | Synthient Credential Stuffing Threat Data |
| jwhitfield@summitmedgroup.com | 4 | Mar 2024 | National Public Data |
| mreyes@summitmedgroup.com | 3 | Jan 2024 | Verifications.io |
| admin@summitmedgroup.com | 3 | May 2023 | LinkedIn Scraped Data |
| scheduling@summitmedgroup.com | 2 | Nov 2022 | Lead Hunter |
| front@summitmedgroup.com | 1 | Sep 2022 | You've Been Scraped |
All 7 monitored accounts have at least one breach record. The billing@ and rtorres@ accounts are in active credential stuffing datasets targeting healthcare organizations. Immediate password resets and MFA verification are required on all 7 accounts.
| Data Classification | Files | Records | Modeled Liability | Regulation |
|---|---|---|---|---|
| United States PHI, Clinical Notes | 18,440 | 62,180 | $2,180,000 | HIPAA |
| United States PHI, Diagnoses & Rx | 14,320 | 51,440 | $1,800,400 | HIPAA |
| US Personal Legal / PII | 11,280 | 41,200 | $1,364,020 | PII |
| US Date of Birth | 22,180 | 98,440 | $984,400 | PII |
| US SSN | 4,840 | 7,200 | $180,000 | PII |
| US Health Insurance Member Number | 8,920 | 44,180 | $883,600 | HIPAA |
| Password Detection | 5,240 | 380,000 | $1,900,000 | IT |
| Credit Card, Various | 1,840 | 2,280 | $228,000 | PCI / FTC |
| US Bank Account / ACH | 480 | 3,180 | $63,600 | PII / FTC |
| Total | $9,584,020 | Modeled | ||
Note: This modeled liability represents the estimated regulatory and legal exposure per classification using current HIPAA, PCI, and state privacy law frameworks. Reported figure of $8.2M reflects the conservative (75th percentile) estimate used for 3D DeepDive scoring. Primary server (SMGSRV-CLINICAL01) holds 86,400 files worth $7.7M, the practice's primary data risk asset.