Key Takeaways
- The proposed HIPAA Security Rule update would require vulnerability scans at least every six months and annual penetration tests. It is not final, and the current Security Rule still applies. As proposed, these duties would bind all covered entities and business associates.
- Healthcare data breaches hit record highs in 2024. They exposed over 275 million records. Each one cost an average of $7.42 million.
- The proposal would add technical rules for network segmentation, multi-factor authentication, encryption at rest and in transit, and 72-hour recovery.
Healthcare faces a steep climb in 2026. The Department of Health and Human Services (HHS) has proposed the biggest overhaul of the HIPAA Security Rule in over a decade. The ground under healthcare security is shifting.
These updates are not small tweaks. They answer a brutal year. In 2024, the health sector had its worst run of data breaches ever. Over 275 million records were exposed.
If finalized, the proposal would end flexible, "addressable" safeguards. What was once best practice would become the rule. Vulnerability scanning would sit at the heart of HIPAA compliance.
You may run a covered entity. You may serve as a business associate. Either way, the proposed rules would apply to you. Compliance is not just about dodging fines. It is about guarding the health data of millions of patients who trust you.
Rule status: The HIPAA Security Rule update is a proposed rule, published in the Federal Register on January 6, 2025. The public comment period closed on March 7, 2025. HHS's regulatory agenda now lists final action for July 2027, so the current Security Rule still governs today.
The checklist below separates what applies now from what the proposal would add.
What the HIPAA Security Rule Requires Today
The current Security Rule sets no fixed schedule for scans or penetration tests. It sets general duties and a required risk analysis instead. Under 45 CFR 164.306(a)(1), covered entities and business associates must:
Ensure the confidentiality, integrity, and availability of all electronic protected health information the covered entity or business associate creates, receives, maintains, or transmits.
The risk analysis rule at 45 CFR 164.308(a)(1)(ii)(A) is marked Required. It reads:
Conduct an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity, and availability of electronic protected health information held by the covered entity or business associate.
The definitions in 45 CFR 164.304 say what counts as a security measure:
Security or Security measures encompass all of the administrative, physical, and technical safeguards in an information system.
For HIPAA vulnerability compliance today, the risk analysis is the anchor. It must identify potential risks and vulnerabilities to the electronic protected health information (ePHI) you create, receive, maintain, or transmit. Regular scans are a practical way to find flaws that could allow unauthorized access.
You must protect ePHI with administrative, physical, and technical safeguards, not tools alone. Section 164.308(a)(8) adds "a periodic technical and nontechnical evaluation," repeated when environmental or operational changes affect security. Document each evaluation, scan, and fix so you can show how you reduce the risk of a security incident.
Understanding the 2025 HIPAA Security Rule Updates
The Proposed End of "Addressable" Requirements
The deepest proposed change would remove the split between "required" and "addressable" specs. Under the current rule, you can weigh an addressable item against your size, your setup, and your budget. If the standard step does not fit, you can pick another route.
The proposal would take that leeway away. HHS said it worries that "some regulated entities proceed as if compliance with an addressable implementation specification is optional." It said that interpretation "is incorrect and weakens the cybersecurity posture of regulated entities."
Under the proposal, each safeguard would be a must. That would cover vulnerability scanning, penetration testing, encryption, and network segmentation. Your size and budget would no longer change the bar.
Why These Changes Matter Now
Health data breaches cost more than those in any other sector. Healthcare has held that grim title for 14 years in a row. In 2025, a health breach costs $7.42 million on average. That is close to triple the global average across all industries.
Health breaches are also the slowest to catch and close. They run 279 days on average. The global average is 241 days.
The harm goes past money. Ransomware hit Change Healthcare in early 2024. The attack exposed an estimated 190 million patient records. It also froze core systems and stalled payments to providers. Some practices took out loans just to stay open.
Care slowed across the country. That is the real lesson. A security failure can hurt patients, not just budgets.
Core Vulnerability Scanning Requirements
How Often the Proposal Would Require Scans
The January 2025 proposal would turn vulnerability scanning into a hard, countable duty. You would have to run automated vulnerability scans at least every six months. For many teams, that is twice the current pace.
Six months would be the floor, not the goal. Your risk analysis may mark you as high risk. If it does, scan more often.
The proposal's "qualified person" standard applies to penetration testing, not to automated scans. Still, the people who run scans need to know generally accepted cybersecurity principles. That does not force you to hire outside help. Your own security team can scan if it has the skill. But plan to log the training and credentials of each person who scans.
Scope and Coverage Requirements
Your vulnerability scanning should reach each system that creates, receives, keeps, or sends electronic protected health information (ePHI). That scope covers three groups.
Infrastructure:
- Servers and databases that hold ePHI.
- Network gear such as routers, switches, and firewalls.
- Backup systems and disaster recovery gear.
- Cloud and hybrid setups.
Endpoint Devices:
- Desktops used by clinical and admin staff.
- Phones and tablets that reach ePHI.
- Medical devices on the network.
- Remote access points and VPN endpoints.
Apps and Services:
- Electronic Health Record (EHR) systems.
- Patient portals and telehealth tools.
- Third-party links and APIs.
- Custom-built healthcare apps.
Records and Reporting Standards
The January 2025 proposal would add detail on what you must write down for compliance. Keep records that show your plan and your results.
Scan Planning Records:
- Scan schedules and methods.
- Asset lists that show each system in scope.
- A risk-based reason for any scan pace above the floor.
- Proof that the people who scan are qualified.
Results and Fix Tracking:
- Full scan reports with time stamps and scope.
- A risk score and a class for each flaw found.
- Fix plans with named owners.
- Proof that patches went in and flaws are closed.
- A written reason for any risk you accept, plus the controls you put in place.
Keep all of this for at least six years. The Office for Civil Rights (OCR) may ask for it during an audit or a probe. They want proof of steady compliance, not a snapshot from one day.
Penetration Testing: The Proposed Annual Requirement
Understanding Penetration Testing Requirements
Vulnerability scanning finds weak spots. Penetration testing goes further. It mimics a real attack to prove what those weak spots allow.
The January 2025 proposal would require penetration testing at least once every 12 months. Finding a flaw would no longer be enough. You would need to know how someone could use it.
Your penetration testing should be broad. It should include three kinds of work.
- External Testing: The tester attacks from outside your network edge. Targets include internet-facing systems, web apps, and remote access points that could open a path to ePHI.
- Internal Testing: The tester works as a logged-in user or a rogue insider. This checks lateral movement and privilege escalation paths. It also checks access to sensitive data stores.
- Social Engineering Assessment: This one tests people. It uses phishing drills, pretexting, and physical security checks where they fit.
Key Differences from Vulnerability Scanning
Vulnerability scanning and penetration testing both find weak spots. But they play different roles in your security plan.
Vulnerability scanning is broad and automated. It finds known flaws across your whole estate, and it works fast. Scans run often and disrupt little. The reports rank patches and config fixes. Think of it as a vital-signs check that catches trouble early.
Penetration testing shows real-world impact by hand. Skilled testers chain flaws together. They show how an attacker could break in. A scan may flag one old server. Penetration testing shows whether that server opens the door to your whole patient database. People catch logic flaws and long attack paths that tools miss.
How to Pick a Testing Partner
The proposed rule would require a "qualified person" with "appropriate knowledge" of cybersecurity principles to run penetration tests. Weigh each partner with care. That goes for any cybersecurity advisory services you may hire. Look for these traits.
Essential Qualifications:
- Health sector work and a clear grasp of how ePHI moves.
- Certs such as OSCP, GPEN, or CEH that prove technical skill.
- A proven method tied to a standard such as NIST or OWASP.
- Clear reports that turn technical findings into business risk.
Critical Compliance Factors:
- A signed Business Associate Agreement (BAA) before testing starts.
- Proof of professional liability insurance.
- References from other healthcare organizations.
- Written test steps that keep disruption low.
Technical Rules the Proposal Would Add
Network Segmentation Rules
The proposal would make network segmentation a core duty. A hard shell around a soft network no longer works. The proposed rule would have you add technical controls that split your systems in a "reasonable and appropriate manner." The goal is simple. Stop an attacker from roaming once inside.
Good segmentation for HIPAA compliance calls for three things.
- Clinical System Isolation: Keep Electronic Health Records (EHR), imaging, and lab systems apart from the main office network. Then a hacked desktop in accounting cannot reach patient records.
- Workload Segmentation: Split ePHI by how sensitive it is and who needs it. Research databases, billing systems, and clinical care tools each need their own border.
- Zero Trust Architecture: Modern design goes past VLANs to identity-based microsegmentation. Each connection gets checked, wherever it starts. Stolen credentials alone will not open the whole network.
Old gear makes this hard. Many health networks grew by accident over decades. The result is a flat network that needs a real redesign. The proposal grants no way out. Segmentation would be a must. If the full rollout takes time, you would still need a written plan.
Proposed Multi-Factor Authentication (MFA) Requirement
The January 2025 proposal would require MFA for all access to systems that hold ePHI. Only a few legacy systems would get a pass. So would FDA-approved medical devices made before March 2023. Even then, you would need a written plan to move to MFA-capable systems.
Your MFA rollout should handle three areas.
- Clinical Workflows: Balance security with speed at the bedside. Fast user switching, proximity badges, and biometrics keep staff moving without weakening access control.
- Legacy Application Support: Many health apps cannot do MFA on their own. You can add MFA at the network layer, use privileged access management, or modernize the app.
- Remote Access: Each remote link to an ePHI system would need MFA. That covers vendor support, telehealth tools, and staff working from home. There would be no exceptions.
Encryption Standards
The proposal would move encryption from addressable to required, both at rest and in transit. It would remove the old wiggle room. Here is what you would owe.
- Data at Rest: Encrypt all ePHI on servers, desktops, mobile devices, and removable media. Use industry-standard algorithms. Backups, archives, and temp files count too. If you use managed cloud services, you can often inherit encryption from your cloud provider.
- Data in Transit: Encrypt ePHI any time it moves across a network. That holds inside your walls and across the internet. It covers email, file transfers, system-to-system traffic, and cloud sync.
- Key Management: Build sound key handling. That means secure key creation, hand-off, and storage. It also means key rotation and recovery. A lost key is never a valid excuse for lost data.
One exception would stand. A patient may ask for their own records in the clear. Even then, you would need their written note that they know the risk.
Building Your 2026 Compliance Strategy
Risk Analysis and Assessment Updates
The January 2025 proposal would widen what a risk analysis must cover. Many teams treated it as a yearly checkbox. It would become an ongoing job. Your risk analysis would need four parts.
- Technology Asset Inventory: Write down each piece of hardware, software, and system that can create, receive, keep, or send ePHI. This is not a one-off task. Update the list at least once a year, and again after any big change.
- Network Mapping: Draw how ePHI moves through your teams. The maps should show connection points, data flows, and trust borders. HHS wants proof that you know your attack surface.
- Threat and Vulnerability Identification: Go past the list of flaws. Write down each threat you can reasonably expect. Judge how likely each one is. Cover insider threats, ransomware, supply chain attacks, and new threats aimed at healthcare.
- Risk Scoring and Prioritization: Score each risk by odds and impact. That gives you a ranked fix list. Say why you fix some risks first. If you accept a risk, name the controls that offset it.
Creating a Vulnerability Management Program
A sound vulnerability management program is more than two scans a year. Vulnerability management has to live inside how your teams work. Four habits make that happen.
- Establish Clear Governance: Set roles across IT, security, and clinical teams. Name vulnerability management owners who run scans, track fixes, and report to leaders. Write escalation steps for critical flaws that cannot wait. Many teams add virtual CISO services for expert help without a full-time exec salary.
- Implement Consistent Processes: Use one set of steps to find, judge, fix, and verify flaws. Set service level agreements (SLAs) for patching. Push critical patches within 30 days. Push high-priority ones within 60 days. Save routine updates for quarterly maintenance windows.
- Leverage Automation Strategically: Run continuous vulnerability scanning tools that alert you to new threats in real time. Automate patching where you can. Keep a human in the loop for clinical systems, where an update could touch patient care. Use security orchestration to route and track each fix.
- Measure and Improve: Track mean time to detect (MTTD) and mean time to remediate (MTTR). Track the share of systems that meet patch targets. Review the numbers often. They point to better steps and show auditors steady gains.
Timeline: What to Do and When
The comment period on the proposed HIPAA Security Rule closed in March 2025. HHS now lists final action for July 2027. Plan your compliance work in three waves.
Immediate Actions (Now):
- Run a gap analysis against the proposed rules.
- Start your technology asset inventory and network maps.
- Review what your vulnerability scanning and penetration testing can do today.
- Flag legacy systems that would need an MFA or encryption exception.
Near-Term Priorities (Before the Final Rule):
- Expand vulnerability scanning to hit the six-month pace.
- Hire penetration testing services for the yearly check.
- Roll out MFA at each ePHI access point.
- Plan or start network segmentation.
Ongoing Compliance (After the Final Rule):
- Set up continuous monitoring and review.
- Run the yearly compliance audit.
- Keep full records of each security task.
- Get ready for more OCR enforcement.
Do not wait for the final rule to start. The final rule may differ, but scans and testing already support the risk analysis required today. An early start gives you an edge. It also shows HHS good-faith compliance work.
Common Pitfalls and How to Avoid Them
Incomplete Asset Discovery
Most vulnerability scanning failures start with a missing asset. Teams scan the known live systems and stop there. Shadow IT, forgotten dev servers, and stray cloud instances never get checked. Attackers hunt for exactly those unpatched, unowned boxes.
How to Avoid It: Use continuous asset discovery tools that spot new devices as they join the network. Blend active scans, passive network monitoring, and a feed from your configuration management database (CMDB). Match what you find against your official list. Then chase each gap.
Fixes That Never Happen
Many teams are good at finding flaws and poor at fixing them. Scan reports stack up while patches sit undeployed. That builds a false sense of safety. Under the January 2025 proposal, a known flaw with no fix would be proof of non-compliance.
How to Avoid It: Build clear fix workflows with named owners, due dates, and escalation paths. Set maintenance windows that respect both security and daily care. If a system cannot be patched now, write down the controls that offset the risk. Get a leader to sign off on the risk you accept.
Focusing Only on Technical Controls
The January 2025 proposal leans on technical rules. Even so, admin and physical safeguards carry equal weight. A team with great vulnerability scanning but weak staff training still leaves a hole.
How to Avoid It: Tie vulnerability management into your wider security work. Let technical findings shape training. If a phishing drill succeeds, teach more. Link physical security checks to your network segmentation plan. Treat compliance as one system, not a pile of separate rules.
Thin Records
OCR investigations cite record-keeping failures again and again. Strong security does not help if you cannot show it. Without records, you cannot prove HIPAA compliance at all.
How to Avoid It: Write things down with an audit in mind. Build templates for risk assessments, scan reports, and fix tracking. Put each security document under version control. Assign the write-up along with the technical task, so records never lag.
Tools That Help
Vulnerability Scanning Platforms
The right vulnerability scanning platform balances broad coverage with health sector needs. You have three main paths.
- Enterprise Platforms: Tenable Nessus, Qualys VMDR, and Rapid7 Nexpose cover a wide range of flaws and report against HIPAA. They offer authenticated scans for a deep look inside systems. They also run credentialed database scans and link to asset management tools.
- Healthcare-Focused Solutions: Some tools are built for health workflows and ePHI. They ship with policies tuned to HIPAA. They throw fewer false alarms in clinical settings. They can also scan medical devices without knocking them over.
- Cloud-Native Options: Health data keeps moving to the cloud. Tools like AWS Inspector, Azure Security Center, and Google Cloud Security Command Center scan those workloads. They also map results to compliance rules.
Security Information and Event Management (SIEM)
A SIEM tool pulls security monitoring into one place. That gives you the steady oversight HHS expects.
Core Capabilities for HIPAA Compliance:
- Real-time matching of scan results against live threats.
- Automatic alerts on odd access to ePHI systems.
- Audit trails kept for the required six-year window.
- Dashboards that show your security posture over time.
Rollout Notes: Splunk, QRadar, and Microsoft Sentinel all need heavy tuning for health settings. Start with a few high-value cases. Watch privileged access to ePHI. Catch ransomware signals. Track how fast flaws get fixed. Widen coverage as your team gains skill.
Continuous Compliance Monitoring
Modern compliance tools gather proof for you and watch controls all year. They help in three ways.
- Automated Evidence Collection: The tool gathers proof that each control works. No more screenshot hunts before an audit. It watches patch levels, config standards, and access rules. Then it alerts you when a system drifts out of compliance.
- Risk Quantification: Some tools turn technical flaws into business risk. They model breach costs, rank fixes by ePHI exposure, and show risk falling over time. That helps leaders judge security spend.
- Audit Preparation: When OCR arrives, the tool prints reports mapped to specific HIPAA rules. You get a history of your compliance work and a record of each issue you closed.
Costs and ROI
Budget Planning for Compliance
The proposed HIPAA Security Rule updates would cost real money. Falling short on compliance costs far more.
Direct Compliance Costs:
- Vulnerability scanning tools: $15,000-$50,000 a year, based on size.
- Annual penetration testing: $25,000-$100,000, based on scope.
- MFA rollout: $5-$15 per user per month for enterprise tools.
- Network segmentation: $100,000-$500,000 for full microsegmentation.
- Encryption: $50,000-$200,000, including key management.
Ongoing Operating Costs:
- Security staff or managed services: $150,000-$300,000 a year.
- Monitoring and SIEM upkeep: $50,000-$150,000 a year.
- Training and certs for security staff: $10,000-$25,000 a year.
- Records and audit prep: 10-15% of your security team's time.
What a Breach Costs
Set that spend against what a breach does to you.
- Financial Impact: The average health breach costs $7.42 million. That figure leaves out class action suits, fines, and lost business. Fines run from $100 to $50,000 per violation, up to $2 million a year. Downtime can last weeks or months. Nearly half of breached organizations raise prices by 15% or more to recover.
- Operating Fallout: A breach also breaks daily work. Clinical systems go dark, so staff fall back to paper. Scheduling stops, so care slips. Recovery takes over 100 days on average. Output drops and patient trust erodes.
- Reputational Damage: Healthcare runs on trust. After a breach, patients leave for rivals. Doctors hesitate to refer. Payers and partners watch you harder. Rebuilding takes years, and it costs far more than the safeguards would have.
Showing Security ROI
Pitch security as a business tool, not a tax. Three angles work well.
- Competitive Edge: Patients now weigh data safety when they pick a provider. Strong security sets you apart. Show it through industry certs and a public stand on privacy.
- Better Operations: Security work often speeds things up. Network segmentation trims broadcast traffic. MFA cuts password reset calls. Automated patching saves manual hours. Those gains offset the cost.
- New Partners: Solid security opens doors. Payers favor secure providers. Vendors pick secure customers for pilots. Research partners demand proven data protection.
Tie each security dollar to a business outcome. HIPAA compliance then turns from a burden into an edge.
Future-Proofing Your Security Program
What Comes Next
The January 2025 proposal is a start, not an end. Health security rules will keep changing as threats change.
Expected Near-Term Changes:
- Closer ties to the NIST Cybersecurity Framework 2.0.
- Specific rules for artificial intelligence and machine learning security.
- Tougher duties around third-party risk.
- Faster incident response times, beyond today's 72-hour notice.
How to Prepare: Build slack into your security program. Pick tools that bend as rules change. Keep vendors who feed you news on the rules. Join trade groups that help shape them. Write your program down in full, so any future audit is simple.
New Threats and New Tech
Healthcare faces threats few other sectors see. Three deserve early work.
- IoMT and Medical Device Security: Connected medical devices keep multiplying, and each one widens your attack surface. Expect rules on device inventory, segmentation, and monitoring. Add device behavior analytics to catch a hacked device before it harms a patient.
- AI and Machine Learning Risks: Health teams now use AI to help with diagnosis and care plans. That brings new flaws. Adversarial attacks can skew AI output. Model poisoning can taint training data. Expect rules on model validation and decision audit trails.
- Quantum Computing Impact: Quantum computers are still small. In time, they will break today's encryption. Start listing systems that will need quantum-resistant cryptography. Plan the switch for data you must protect for decades.
Building Real Resilience
Real security goes past a checklist. It builds a team that bends without breaking.
Create a Security Culture: Make security everyone's job, not just IT's. Train staff often, and tie each lesson to patient care. Give people a clear way to report worries. Praise the ones who speak up. When each employee knows their role, HIPAA compliance follows.
Build Incident Response: You will face an incident. The only question is how you answer. Run tabletop drills to test your steps. Write plans for what you will tell patients, media, and HHS. Sign an incident response retainer now, so help arrives fast. Test your recovery steps for real.
Keep Getting Better: Security is a journey, not a spot to reach. Review each event for lessons. Benchmark against peers. Join threat-sharing groups. Invest in your team. Teams that keep learning stay ahead of both threats and rules.
The January 2025 proposal would require vulnerability scanning every six months and penetration testing every year. It would also require network segmentation and multi-factor authentication. Together these would set a new floor for guarding patient data.
The reason is blunt. Healthcare is now the most targeted sector, the most expensive to breach, and the slowest to recover.
There is upside here too. Teams that go past the minimum will stand out in a market that cares about safety. Patients weigh data protection when they choose a provider. Partners seek out secure organizations. Insurers offer better rates when you can show a strong security posture.
The path is clear. Start with a full gap analysis. Rank the work by risk, not just by rule. Build security into how you operate instead of bolting it on later. Write it all down. Perfect security is out of reach, but steady progress is not.
Treat these rules as a base for change rather than a burden. Do that, and you will lead in the next era of digital healthcare. Once a final rule takes effect, OCR enforcement will make sure you meet the bar. The real question is whether you use this moment to build a tougher, safer, patient-first team.
Your patients trust you with their most private data. The January 2025 proposal gives you a frame to honor that trust. The time to act is now.
FAQ Section
Q: When would the proposed HIPAA vulnerability scanning requirements take effect?
A: Not yet, because the rule is still a proposal. The comment period closed on March 7, 2025, and HHS now lists final action for July 2027. Until a final rule takes effect, the current Security Rule applies, including its risk analysis requirement.
Q: Do small practices need to meet the same vulnerability scanning requirements as large hospitals?
A: Under the January 2025 proposal, yes. It would drop the split between "required" and "addressable" specs. All covered entities and business associates would meet the same bar, whatever their size. How you get there can differ. A small practice might use cloud-based scanning tools and hire out penetration testing. A large hospital might keep an in-house security team.
Q: What qualifications should vulnerability scanning personnel have?
A: The proposal's "qualified person" standard covers penetration testing, not automated scans. No single cert is named. Still, OCR will want proof of training or hands-on work. Common credentials include CompTIA Security+, CySA+, and GIAC GSEC, paired with health sector know-how. Keep a file on each person who scans.
Q: Can we use free or open-source vulnerability scanning tools for compliance?
A: Yes. Free tools like OpenVAS or Nmap can count toward compliance. They just take more skill to set up and read. Most teams run more than one tool for full coverage. What matters is simple. Your tools must find flaws across the whole ePHI estate, and skilled people must read the output.
Q: How is penetration testing different from vulnerability scanning under the proposed rule?
A: Under the proposal, vulnerability scanning would run at least every six months. It uses automated tools to spot known flaws across your systems. Penetration testing would run at least once a year. Skilled people try to exploit those flaws and show the real-world impact. Vulnerability scanning is a broad health check. Penetration testing is a stress test.
Q: What happens if we find vulnerabilities we can't immediately fix?
A: Write it down. The rules accept that some flaws cannot be fixed at once, above all in medical devices and legacy systems. Log the flaw. Judge its risk. Add controls that offset it, such as network segmentation or extra monitoring. Then build a fix plan with dates. A leader should approve any risk you accept, and you should review it often.
Q: Do these requirements apply to cloud-based EHR systems?
A: Yes, but the load is shared. Your cloud provider is a business associate. It must secure the gear it runs. You still own your configs, access controls, and monitoring inside your tenant. Make sure your Business Associate Agreement (BAA) states who does what. Then scan the parts you control.
Q: How much should we budget for compliance with these proposed requirements?
A: It depends on your size and where you start. A small practice might spend $50,000-$100,000 up front. A large health system could spend millions. Big line items include scanning tools ($15,000-$50,000 a year) and penetration testing ($25,000-$100,000 a year). Add staff or managed services to run it all. Set that against the average $7.42 million cost of a health breach.
Q: Can we perform penetration testing and vulnerability scanning internally?
A: Yes, if your people are qualified. Many teams still value an outside view. A hybrid model works well. Your own team runs vulnerability scanning all year, with a third-party check once a year. Outside experts run penetration testing for an attacker's view. Keep records of what each of them can do.
Q: What if our medical devices can't support the proposed security requirements?
A: The proposal allows narrow exceptions for FDA-approved medical devices made before March 2023 that cannot do MFA or encryption. You would still have work to do. Log each exception. Add controls that offset it, such as network isolation. Build a plan to replace or upgrade the device. The exception would be temporary, and you would have to show progress.

