Study guide
5.3 Infrastructure Privacy and Security
Certified Professional in Healthcare Information and Management Systems CPHIMS
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 Current Exam Facts 1.2 Eligibility Pathways and Qualifying Experience 1.3 Scoring, Retakes, and Recertification 1.4 Domain-Weighted Study Strategy
2 Healthcare Organizations and Relationships
2.1 Hospitals, Clinics, Ambulatory, and Community Organizations 2.2 Payers, Regulators, Research, and Academic Organizations 2.3 Interrelationships, HIE, and Continuity of Care 2.4 HIT Professional Roles and Organizational Structures
3 Policy, Accreditation, and Care Trends
3.1 Privacy and Security Law: HIPAA and HITECH 3.2 Interoperability Policy and Information Blocking 3.3 Accreditation, Patient Rights, and Environments of Care 3.4 Telehealth, Portals, Wearables, and Population Health
4 Healthcare Applications
4.1 Clinical Applications 4.2 Administrative and Financial Applications 4.3 Consumer-Facing Applications 4.4 Business Intelligence Applications
5 Technology Infrastructure
5.1 Networks and Communications 5.2 Data Integration Architectures 5.3 Infrastructure Privacy and Security 5.4 Cloud, Devices, and Identity Infrastructure
6 Clinical Language, Terminologies, and Metrics
6.1 Clinical Vocabulary 6.2 Healthcare IT Vocabulary 6.3 Clinical Terminologies: SNOMED CT, LOINC, RxNorm, and ICD 6.4 Clinical Metrics and Operational Measures
7 Clinical Effectiveness and Workflows
7.1 System Functionality for Clinical Effectiveness 7.2 Workflows, Order Sets, and Pathways 7.3 Safety, Quality, and Clinical Informatics Design
8 Informatics Analytics
8.1 Analytics Tools, Reports, Tables, and Graphs 8.2 Interpreting Clinical and Operational Outcomes 8.3 Predictive Models in Care and Operations
9 Clinical Content and Decision Support
9.1 Clinical Content Lifecycle 9.2 Clinical Decision Support Types and Design 9.3 CDS Governance, Alert Management, and Knowledge Maintenance
10 Analysis, SDLC, and Improvement Methods
10.1 Systems Development Life Cycle 10.2 Project Management: Needs, Gap, and Requirements 10.3 Process Improvement: DMAIC and PDCA 10.4 Process Maps, Flow Diagrams, and Gap Analysis
11 Analysis: Solutions and the Business Case
11.1 Disparate Data Sets and Alternate Solutions 11.2 Strategic Alignment and Cost-Benefit Analysis 11.3 Proposals, RFPs, RFIs, SLAs, SOWs, and NDAs
12 Systems Design
12.1 Interoperability of Software, Hardware, Networks, and Devices 12.2 Design Compliance and Incorporating Industry Trends 12.3 Business Continuity and Disaster Recovery Design 12.4 Emerging Technologies and Data Governance
13 Selection, Implementation, Support, and Maintenance
13.1 Solution Selection Activities 13.2 Technical Change Management, Training, and Support 13.3 Implementation: Scope, Schedule, Budget, and Quality 13.4 Maintenance, Operations, and Problem-Trend Analysis
14 Testing, Evaluation, Privacy, and Security
14.1 Testing Methodology and Internal Controls 14.2 Validation and Benefits Realization 14.3 Privacy and Security Policies, Access, and Safeguards 14.4 Vulnerabilities, Roles, Data Controls, and Ongoing Validation
15 Strategy and IT Planning
15.1 Contributing to Organizational Strategic Planning 15.2 Assessing the Organizational Environment 15.3 Forecasting Technical and Information Needs 15.4 IT Strategic Plans and Departmental Objectives
16 Performance, Policy, Ethics, and Analytics
16.1 Evaluating Performance Against SLAs and Indicators 16.2 User Satisfaction and Service Effectiveness 16.3 Policies, Legal Compliance, and Ethical Principles 16.4 Comparative Analytics and Presenting Recommendations
17 Communication, Stakeholders, and Change
17.1 Promoting Stakeholder Understanding of IT Opportunities and Constraints 17.2 Business Communications and Consultative Technology Services 17.3 Facilitating Groups, Consensus, and Conflict Resolution 17.4 Organizational Change Management and Stakeholder Relationships
18 People, Projects, Vendors, and Finance
18.1 HIT Roles, Job Descriptions, and Staff Competency 18.2 Educational Strategies and Maintaining IT Competencies 18.3 Managing Projects and Portfolios 18.4 Vendor Contracts, Budgets, and Risk Management
5.3 Infrastructure Privacy and Security
Key Takeaways Explain This Topic AI
The Security Rule requires confidentiality, integrity, and availability of ePHI through administrative, physical, and technical safeguards; addressable means a documented risk-based decision, not a skip.
Network controls that support CIA include segmentation, default-deny firewalls, encryption in transit, NAC, and no exposed remote desktop on the internet.
Identity controls include unique user IDs, role-based least privilege, MFA, joiner-mover-leaver provisioning, and audited break-the-glass.
Encryption at rest on portables, SAN or cloud stores, and backups is the operational default; unencrypted backups lose breach-notification safe harbor.
Logs must be collected, retained, protected from tampering, and reviewed—a 24-hour writable local buffer is not an audit control.
Last updated: August 2026
5.3 Infrastructure Privacy and Security
Quick Answer: Infrastructure is how the HIPAA Security Rule’s confidentiality, integrity, and availability become real. CPHIMS B.2 items test network, identity, and endpoint controls, encryption in transit and at rest, and logging—not slogan-level “we are HIPAA compliant.”
Why infrastructure security is a B.2 topic
Chapter 3 covered who is regulated and which rule applies. This section is the control plane : VLANs, TLS, endpoint detection, MFA, and the SIEM. The Security Rule at 45 CFR 164.306 requires covered entities and business associates to protect ePHI’s confidentiality, integrity, and availability (CIA) with administrative, physical, and technical safeguards. Addressable specifications still require a documented, risk-based decision .
A CPHIMS leader maps those safeguard families onto network, identity, and endpoint so an OCR investigator can see more than a policy binder. Drill mixed items at /practice/cphims . HIM retention and legal-hold questions on /study-guides/rhia depend on whether logs and backups actually exist.
CIA as an infrastructure design brief
CIA goal What it means for ePHI Infrastructure expression
Confidentiality Only authorized people and systems see it Segmentation, least privilege, encryption, DLP, screen privacy
Integrity It is not improperly altered Hashes, signed images, change control, immutable backups, audit trails
Availability It is usable when care needs it Redundant power and network, patch windows that do not kill the ED, tested restores
Confidentiality without availability is a closed hospital. Turning off wireless “for security” and leaving infusion pumps unmanaged is not a pass. Availability without confidentiality is an open share of the entire chart. Exam stems that offer “block everything” are usually wrong unless the stem says the control plane itself is owned.
The Security Rule is flexible and scalable . A 40-provider clinic and a 12-hospital system both owe CIA; they do not owe the same appliance list. What they both owe is a current risk analysis , implemented safeguards, and evidence. “We bought a firewall” is not a risk analysis.
Network controls
Network design from section 5.1 is also a technical safeguard:
Segmentation and default-deny firewalls between clinical, biomedical, guest, and management zones.
Encryption in transit — TLS for applications and FHIR APIs; IPsec or equivalent for site-to-site and many vendor tunnels. Unencrypted HL7 over the open internet is a finding, not a shortcut.
Network access control (NAC) — unknown devices land in quarantine, not the EHR VLAN.
Egress filtering — pumps and workstations should not freely reach the whole internet.
Wireless security — WPA2-Enterprise or WPA3-Enterprise for staff; guest isolated; no shared pre-shared key on clinical SSIDs.
Remote access — VPN or zero-trust with MFA; no exposed RDP to the internet.
These are technical safeguards (access control, transmission security) supported by administrative risk analysis and physical facility controls (data-center cages, locked clinic closets, camera coverage of IDF rooms). A perfectly encrypted tunnel that terminates in an unlocked wiring closet is still a physical-safeguard miss.
Identity controls
Identity is the Security Rule’s unique user identification , emergency access , automatic logoff , and encryption/decryption access-control family, plus audit.
Unique IDs — no shared “nurse” or “radiology” logins on production EHR.
Least privilege / RBAC — role plus context (unit, service) beats a global “clinical” flag.
MFA for remote, privileged, and increasingly all workforce access to ePHI.
Provisioning and deprovisioning tied to HR events; orphaned accounts are a classic OCR theme.
Break-the-glass with extra audit, not a standing God mode.
Service accounts inventoried, owned, and not used by humans.
SSO is covered in section 5.4 as an architecture; here the exam point is that identity is a technical safeguard , not a convenience feature. Automatic logoff on a shared workstation in the ED is an availability-versus-confidentiality trade that you design with clinicians, not a setting you leave at 24 hours because someone complained.
Endpoint controls
Endpoints are laptops, workstations, thin clients, smartphones, and unmanaged medical devices . Controls:
Full-disk encryption at rest on portable devices (addressable, but the operational default after years of lost-laptop breaches).
EDR / anti-malware , configuration baselines, and timely patching.
USB and print restrictions where risk analysis supports them.
Mobile device management for phones that hold ePHI or mail.
Medical devices — often cannot run agents; compensate with VLAN isolation, allow-lists, and vendor access procedures (section 5.4).
Encryption at rest also applies to SAN volumes, backups, cloud object stores, and tape. The Breach Notification Rule’s safe harbor applies to PHI that is encrypted so that it is unusable to an unauthorized person. Unencrypted backups are how a misplaced tape becomes a 60-day media notice. Hashing passwords is not backup encryption. TLS on a guest SSID is not laptop-disk encryption.
Logging and monitoring
The Security Rule requires audit controls and information-system activity review . Infrastructure must produce:
Authentication success and failure, privilege use, and admin actions.
EHR break-the-glass and sensitive-chart access.
Firewall denies that indicate scanning or exfiltration.
Interface-engine queue failures (availability and integrity).
Cloud control-plane changes (who opened a storage bucket).
Logs that nobody reviews are not a control. Feed them to a SIEM or equivalent, retain them long enough for investigation and legal holds, and protect them from the attacker who would erase the trail. Time sync (NTP) across devices is how you reconstruct an incident. A 24-hour local log that domain admins can overwrite is evidence of intent, not a safeguard.
Workforce audit of who opened a chart is a required technical safeguard. It is not a pretext for managers to snoop without a purpose, and it is not itself a Privacy Rule violation. Distinguish audit (control) from surveillance without a job need (sanctionable).
Scenarios and traps
Trap: “Addressable means optional.” Addressable means document why you implemented an equivalent or why the specification does not reasonably apply.
Trap: “Encryption in transit is enough.” Lost unencrypted laptops and open cloud buckets are at-rest failures.
Trap: “HIPAA requires a specific product.” It requires reasonable and appropriate CIA controls, not a named firewall brand.
Trap: “Guest Wi-Fi encryption replaces clinical segmentation.” Different problem.
Trap: “Logging is a privacy violation.” Audit of workforce access is a required technical safeguard.
If a stem offers shutting the entire WLAN during a ransomware event versus isolating the infected VLAN and preserving ED wireless for downtime viewers, prefer the targeted availability-preserving action unless the stem says the wireless controller itself is owned. CIA is a three-part test, not a confidentiality-only test.