verification-layer 0.20.0 → 0.22.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +251 -615
- package/dist/cli.js +542 -0
- package/dist/cli.js.map +1 -1
- package/dist/marketplace/index.d.ts +8 -0
- package/dist/marketplace/index.d.ts.map +1 -0
- package/dist/marketplace/index.js +7 -0
- package/dist/marketplace/index.js.map +1 -0
- package/dist/marketplace/installer.d.ts +62 -0
- package/dist/marketplace/installer.d.ts.map +1 -0
- package/dist/marketplace/installer.js +254 -0
- package/dist/marketplace/installer.js.map +1 -0
- package/dist/marketplace/registry.d.ts +52 -0
- package/dist/marketplace/registry.d.ts.map +1 -0
- package/dist/marketplace/registry.js +759 -0
- package/dist/marketplace/registry.js.map +1 -0
- package/dist/marketplace/types.d.ts +123 -0
- package/dist/marketplace/types.d.ts.map +1 -0
- package/dist/marketplace/types.js +6 -0
- package/dist/marketplace/types.js.map +1 -0
- package/dist/reporters/audit-report.d.ts.map +1 -1
- package/dist/reporters/audit-report.js +180 -0
- package/dist/reporters/audit-report.js.map +1 -1
- package/dist/reporters/index.d.ts.map +1 -1
- package/dist/reporters/index.js +2612 -5
- package/dist/reporters/index.js.map +1 -1
- package/dist/scan.d.ts.map +1 -1
- package/dist/scan.js +15 -1
- package/dist/scan.js.map +1 -1
- package/dist/scanners/api-security/index.d.ts +7 -0
- package/dist/scanners/api-security/index.d.ts.map +1 -0
- package/dist/scanners/api-security/index.js +139 -0
- package/dist/scanners/api-security/index.js.map +1 -0
- package/dist/scanners/api-security/index.test.d.ts +5 -0
- package/dist/scanners/api-security/index.test.d.ts.map +1 -0
- package/dist/scanners/api-security/index.test.js +360 -0
- package/dist/scanners/api-security/index.test.js.map +1 -0
- package/dist/scanners/api-security/patterns.d.ts +32 -0
- package/dist/scanners/api-security/patterns.d.ts.map +1 -0
- package/dist/scanners/api-security/patterns.js +159 -0
- package/dist/scanners/api-security/patterns.js.map +1 -0
- package/dist/scanners/authentication/index.d.ts +7 -0
- package/dist/scanners/authentication/index.d.ts.map +1 -0
- package/dist/scanners/authentication/index.js +107 -0
- package/dist/scanners/authentication/index.js.map +1 -0
- package/dist/scanners/authentication/index.test.d.ts +5 -0
- package/dist/scanners/authentication/index.test.d.ts.map +1 -0
- package/dist/scanners/authentication/index.test.js +379 -0
- package/dist/scanners/authentication/index.test.js.map +1 -0
- package/dist/scanners/authentication/patterns.d.ts +32 -0
- package/dist/scanners/authentication/patterns.d.ts.map +1 -0
- package/dist/scanners/authentication/patterns.js +133 -0
- package/dist/scanners/authentication/patterns.js.map +1 -0
- package/dist/scanners/configuration/index.d.ts +8 -0
- package/dist/scanners/configuration/index.d.ts.map +1 -0
- package/dist/scanners/configuration/index.js +87 -0
- package/dist/scanners/configuration/index.js.map +1 -0
- package/dist/scanners/configuration/index.test.d.ts +5 -0
- package/dist/scanners/configuration/index.test.d.ts.map +1 -0
- package/dist/scanners/configuration/index.test.js +344 -0
- package/dist/scanners/configuration/index.test.js.map +1 -0
- package/dist/scanners/configuration/patterns.d.ts +32 -0
- package/dist/scanners/configuration/patterns.d.ts.map +1 -0
- package/dist/scanners/configuration/patterns.js +146 -0
- package/dist/scanners/configuration/patterns.js.map +1 -0
- package/dist/scanners/credentials/index.d.ts +7 -0
- package/dist/scanners/credentials/index.d.ts.map +1 -0
- package/dist/scanners/credentials/index.js +129 -0
- package/dist/scanners/credentials/index.js.map +1 -0
- package/dist/scanners/credentials/index.test.d.ts +5 -0
- package/dist/scanners/credentials/index.test.d.ts.map +1 -0
- package/dist/scanners/credentials/index.test.js +395 -0
- package/dist/scanners/credentials/index.test.js.map +1 -0
- package/dist/scanners/credentials/patterns.d.ts +32 -0
- package/dist/scanners/credentials/patterns.d.ts.map +1 -0
- package/dist/scanners/credentials/patterns.js +140 -0
- package/dist/scanners/credentials/patterns.js.map +1 -0
- package/dist/scanners/errors/index.d.ts +8 -0
- package/dist/scanners/errors/index.d.ts.map +1 -0
- package/dist/scanners/errors/index.js +78 -0
- package/dist/scanners/errors/index.js.map +1 -0
- package/dist/scanners/errors/index.test.d.ts +5 -0
- package/dist/scanners/errors/index.test.d.ts.map +1 -0
- package/dist/scanners/errors/index.test.js +330 -0
- package/dist/scanners/errors/index.test.js.map +1 -0
- package/dist/scanners/errors/patterns.d.ts +27 -0
- package/dist/scanners/errors/patterns.d.ts.map +1 -0
- package/dist/scanners/errors/patterns.js +97 -0
- package/dist/scanners/errors/patterns.js.map +1 -0
- package/dist/scanners/hipaa2026/index.d.ts +8 -0
- package/dist/scanners/hipaa2026/index.d.ts.map +1 -0
- package/dist/scanners/hipaa2026/index.js +345 -0
- package/dist/scanners/hipaa2026/index.js.map +1 -0
- package/dist/scanners/hipaa2026/index.test.d.ts +5 -0
- package/dist/scanners/hipaa2026/index.test.d.ts.map +1 -0
- package/dist/scanners/hipaa2026/index.test.js +332 -0
- package/dist/scanners/hipaa2026/index.test.js.map +1 -0
- package/dist/scanners/hipaa2026/patterns.d.ts +57 -0
- package/dist/scanners/hipaa2026/patterns.d.ts.map +1 -0
- package/dist/scanners/hipaa2026/patterns.js +268 -0
- package/dist/scanners/hipaa2026/patterns.js.map +1 -0
- package/dist/scanners/operational/index.d.ts +7 -0
- package/dist/scanners/operational/index.d.ts.map +1 -0
- package/dist/scanners/operational/index.js +171 -0
- package/dist/scanners/operational/index.js.map +1 -0
- package/dist/scanners/operational/index.test.d.ts +5 -0
- package/dist/scanners/operational/index.test.d.ts.map +1 -0
- package/dist/scanners/operational/index.test.js +406 -0
- package/dist/scanners/operational/index.test.js.map +1 -0
- package/dist/scanners/operational/patterns.d.ts +33 -0
- package/dist/scanners/operational/patterns.d.ts.map +1 -0
- package/dist/scanners/operational/patterns.js +151 -0
- package/dist/scanners/operational/patterns.js.map +1 -0
- package/dist/scanners/rbac/index.d.ts +7 -0
- package/dist/scanners/rbac/index.d.ts.map +1 -0
- package/dist/scanners/rbac/index.js +145 -0
- package/dist/scanners/rbac/index.js.map +1 -0
- package/dist/scanners/rbac/index.test.d.ts +5 -0
- package/dist/scanners/rbac/index.test.d.ts.map +1 -0
- package/dist/scanners/rbac/index.test.js +422 -0
- package/dist/scanners/rbac/index.test.js.map +1 -0
- package/dist/scanners/rbac/patterns.d.ts +32 -0
- package/dist/scanners/rbac/patterns.d.ts.map +1 -0
- package/dist/scanners/rbac/patterns.js +124 -0
- package/dist/scanners/rbac/patterns.js.map +1 -0
- package/dist/scanners/revocation/index.d.ts +8 -0
- package/dist/scanners/revocation/index.d.ts.map +1 -0
- package/dist/scanners/revocation/index.js +83 -0
- package/dist/scanners/revocation/index.js.map +1 -0
- package/dist/scanners/revocation/index.test.d.ts +5 -0
- package/dist/scanners/revocation/index.test.d.ts.map +1 -0
- package/dist/scanners/revocation/index.test.js +332 -0
- package/dist/scanners/revocation/index.test.js.map +1 -0
- package/dist/scanners/revocation/patterns.d.ts +27 -0
- package/dist/scanners/revocation/patterns.d.ts.map +1 -0
- package/dist/scanners/revocation/patterns.js +109 -0
- package/dist/scanners/revocation/patterns.js.map +1 -0
- package/dist/scanners/sanitization/index.d.ts +8 -0
- package/dist/scanners/sanitization/index.d.ts.map +1 -0
- package/dist/scanners/sanitization/index.js +98 -0
- package/dist/scanners/sanitization/index.js.map +1 -0
- package/dist/scanners/sanitization/index.test.d.ts +5 -0
- package/dist/scanners/sanitization/index.test.d.ts.map +1 -0
- package/dist/scanners/sanitization/index.test.js +370 -0
- package/dist/scanners/sanitization/index.test.js.map +1 -0
- package/dist/scanners/sanitization/patterns.d.ts +27 -0
- package/dist/scanners/sanitization/patterns.d.ts.map +1 -0
- package/dist/scanners/sanitization/patterns.js +117 -0
- package/dist/scanners/sanitization/patterns.js.map +1 -0
- package/dist/training/certificate.d.ts +26 -0
- package/dist/training/certificate.d.ts.map +1 -0
- package/dist/training/certificate.js +92 -0
- package/dist/training/certificate.js.map +1 -0
- package/dist/training/index.d.ts +3 -0
- package/dist/training/index.d.ts.map +1 -0
- package/dist/training/index.js +243 -0
- package/dist/training/index.js.map +1 -0
- package/dist/training/modules.d.ts +13 -0
- package/dist/training/modules.d.ts.map +1 -0
- package/dist/training/modules.js +608 -0
- package/dist/training/modules.js.map +1 -0
- package/dist/training/questions.d.ts +9 -0
- package/dist/training/questions.d.ts.map +1 -0
- package/dist/training/questions.js +505 -0
- package/dist/training/questions.js.map +1 -0
- package/dist/types.d.ts +45 -0
- package/dist/types.d.ts.map +1 -1
- package/dist/utils/npm-audit.d.ts +6 -0
- package/dist/utils/npm-audit.d.ts.map +1 -0
- package/dist/utils/npm-audit.js +95 -0
- package/dist/utils/npm-audit.js.map +1 -0
- package/dist/utils/scan-history.d.ts +59 -0
- package/dist/utils/scan-history.d.ts.map +1 -0
- package/dist/utils/scan-history.js +170 -0
- package/dist/utils/scan-history.js.map +1 -0
- package/package.json +4 -1
- package/templates/baa-verification-letter.md +105 -0
- package/templates/irp.md +545 -0
- package/templates/notice-of-privacy-practices.md +491 -0
- package/templates/physical-safeguards-checklist.md +247 -0
- package/templates/security-officer-designation.md +237 -0
|
@@ -0,0 +1,247 @@
|
|
|
1
|
+
# HIPAA Physical Safeguards Checklist
|
|
2
|
+
|
|
3
|
+
**Organization:** [ORGANIZATION NAME]
|
|
4
|
+
**Completed By:** [NAME & TITLE]
|
|
5
|
+
**Date:** [DATE]
|
|
6
|
+
**Review Period:** [PERIOD]
|
|
7
|
+
|
|
8
|
+
---
|
|
9
|
+
|
|
10
|
+
## Overview
|
|
11
|
+
|
|
12
|
+
This checklist addresses the Physical Safeguards requirements under HIPAA Security Rule 45 CFR §164.310. Physical safeguards are physical measures, policies, and procedures to protect electronic information systems and related buildings and equipment from natural and environmental hazards, and unauthorized intrusion.
|
|
13
|
+
|
|
14
|
+
**Instructions:** Check all boxes that apply to your organization's setup. Not all controls may be applicable depending on your operating model (fully remote vs. physical office).
|
|
15
|
+
|
|
16
|
+
---
|
|
17
|
+
|
|
18
|
+
## SECTION A - Equipment 100% Remoto/Cloud
|
|
19
|
+
|
|
20
|
+
**Applicable to:** All organizations, including fully remote teams
|
|
21
|
+
|
|
22
|
+
These controls apply to all workforce members working remotely or with cloud-based systems containing electronic Protected Health Information (ePHI).
|
|
23
|
+
|
|
24
|
+
### Device Security (§164.310(d)(1) - Device and Media Controls)
|
|
25
|
+
|
|
26
|
+
- ☐ **Laptops con encriptación de disco completo**
|
|
27
|
+
- FileVault (macOS) enabled and enforced
|
|
28
|
+
- BitLocker (Windows) enabled and enforced
|
|
29
|
+
- Linux: LUKS or dm-crypt full disk encryption
|
|
30
|
+
- Recovery keys backed up securely
|
|
31
|
+
- Verification: _________________________
|
|
32
|
+
|
|
33
|
+
- ☐ **VPN requerida para acceso a sistemas con PHI**
|
|
34
|
+
- Corporate VPN configured for all workforce members
|
|
35
|
+
- VPN mandatory for accessing ePHI systems
|
|
36
|
+
- Split tunneling disabled for ePHI access
|
|
37
|
+
- VPN provider: _________________________
|
|
38
|
+
|
|
39
|
+
- ☐ **Política de no-PHI en dispositivos personales**
|
|
40
|
+
- Written policy prohibiting ePHI on personal devices
|
|
41
|
+
- Policy communicated to all workforce members
|
|
42
|
+
- Alternative provided (company-issued devices or secure access methods)
|
|
43
|
+
- Policy acknowledgment on file
|
|
44
|
+
|
|
45
|
+
- ☐ **Screen lock automático ≤5 minutos de inactividad**
|
|
46
|
+
- Automatic screen lock configured: _____ minutes
|
|
47
|
+
- Password/biometric required to unlock
|
|
48
|
+
- Enforced via MDM or Group Policy
|
|
49
|
+
- Verification method: _________________________
|
|
50
|
+
|
|
51
|
+
- ☐ **Antivirus/anti-malware actualizado en todos los dispositivos**
|
|
52
|
+
- Antivirus solution: _________________________
|
|
53
|
+
- Auto-update enabled
|
|
54
|
+
- Real-time protection active
|
|
55
|
+
- Regular scans scheduled
|
|
56
|
+
- Last verification date: _________________________
|
|
57
|
+
|
|
58
|
+
- ☐ **Backups encriptados de dispositivos**
|
|
59
|
+
- Backup solution: _________________________
|
|
60
|
+
- Encryption method: _________________________
|
|
61
|
+
- Backup frequency: _________________________
|
|
62
|
+
- Backup tested within last 90 days: Yes ☐ No ☐
|
|
63
|
+
|
|
64
|
+
- ☐ **Conexión WiFi segura (WPA3 o WPA2 mínimo)**
|
|
65
|
+
- Home WiFi policy requires WPA2 minimum
|
|
66
|
+
- WPA3 recommended and documented
|
|
67
|
+
- Default router passwords changed
|
|
68
|
+
- Guest networks separated from work networks
|
|
69
|
+
- Workforce educated on WiFi security
|
|
70
|
+
|
|
71
|
+
### Additional Remote Controls
|
|
72
|
+
|
|
73
|
+
- ☐ **Remote device management (MDM) implemented**
|
|
74
|
+
- MDM solution: _________________________
|
|
75
|
+
- Remote wipe capability enabled
|
|
76
|
+
- Device compliance monitoring active
|
|
77
|
+
|
|
78
|
+
- ☐ **Lost/stolen device reporting procedure**
|
|
79
|
+
- Documented procedure in place
|
|
80
|
+
- 24/7 reporting contact: _________________________
|
|
81
|
+
- Remote wipe process tested
|
|
82
|
+
|
|
83
|
+
---
|
|
84
|
+
|
|
85
|
+
## SECTION B - Oficina Física (adicional a Sección A)
|
|
86
|
+
|
|
87
|
+
**Applicable to:** Organizations with physical office locations where ePHI is accessed, stored, or processed
|
|
88
|
+
|
|
89
|
+
These controls are **in addition to** all Section A requirements. Physical offices require both remote security controls (Section A) and physical security controls (Section B).
|
|
90
|
+
|
|
91
|
+
### Facility Access Controls (§164.310(a)(1))
|
|
92
|
+
|
|
93
|
+
- ☐ **Control de acceso a la oficina (llave, badge, o biométrico)**
|
|
94
|
+
- Access control system type: _________________________
|
|
95
|
+
- Access restricted to authorized workforce members only
|
|
96
|
+
- Access logs maintained and reviewed
|
|
97
|
+
- Lost/stolen key/badge procedure documented
|
|
98
|
+
- After-hours access requires authorization
|
|
99
|
+
|
|
100
|
+
- ☐ **Visitantes escoltados y registrados**
|
|
101
|
+
- Visitor log maintained (name, date, time in/out, purpose)
|
|
102
|
+
- All visitors escorted by authorized workforce member
|
|
103
|
+
- Visitor badges issued and collected
|
|
104
|
+
- Log retention: 6 years minimum
|
|
105
|
+
- Log location: _________________________
|
|
106
|
+
|
|
107
|
+
### Workstation Security (§164.310(c))
|
|
108
|
+
|
|
109
|
+
- ☐ **Monitores posicionados para evitar shoulder surfing**
|
|
110
|
+
- Workstations positioned away from windows/public view
|
|
111
|
+
- Privacy screens installed where necessary
|
|
112
|
+
- Hot-desking/shared workspace policy addresses ePHI security
|
|
113
|
+
- Desk arrangement reviewed: _________________________
|
|
114
|
+
|
|
115
|
+
- ☐ **Política de escritorio limpio (clean desk policy)**
|
|
116
|
+
- Written clean desk policy in place
|
|
117
|
+
- No ePHI left visible when unattended
|
|
118
|
+
- Documents secured at end of day
|
|
119
|
+
- Policy communicated and enforced
|
|
120
|
+
- Random compliance checks conducted
|
|
121
|
+
|
|
122
|
+
### Device and Media Controls (§164.310(d)(1))
|
|
123
|
+
|
|
124
|
+
- ☐ **Documentos físicos con PHI bajo llave**
|
|
125
|
+
- Locked file cabinets for ePHI documents
|
|
126
|
+
- Keys restricted to authorized personnel
|
|
127
|
+
- File cabinet locations: _________________________
|
|
128
|
+
- Access log maintained
|
|
129
|
+
|
|
130
|
+
- ☐ **Destrucción segura de documentos (shredder cross-cut)**
|
|
131
|
+
- Cross-cut shredder available (DIN P-4 or higher)
|
|
132
|
+
- Shredder location: _________________________
|
|
133
|
+
- Secure disposal bins for ePHI documents
|
|
134
|
+
- Shredding log maintained
|
|
135
|
+
- Certificate of destruction obtained (if using service)
|
|
136
|
+
|
|
137
|
+
### Additional Physical Controls
|
|
138
|
+
|
|
139
|
+
- ☐ **Cámaras de seguridad en áreas con acceso a PHI**
|
|
140
|
+
- Camera coverage of: _________________________
|
|
141
|
+
- Recording retention period: _____ days
|
|
142
|
+
- Footage access restricted to: _________________________
|
|
143
|
+
- Camera system tested and maintained
|
|
144
|
+
|
|
145
|
+
- ☐ **Server/network equipment physically secured**
|
|
146
|
+
- Server room/closet locked
|
|
147
|
+
- Key access restricted to: _________________________
|
|
148
|
+
- Environmental controls (temperature, humidity, fire suppression)
|
|
149
|
+
- Equipment maintenance logs maintained
|
|
150
|
+
|
|
151
|
+
- ☐ **Alarm system installed and monitored**
|
|
152
|
+
- Alarm type: _________________________
|
|
153
|
+
- Monitoring service: _________________________
|
|
154
|
+
- After-hours intrusion alerts configured
|
|
155
|
+
|
|
156
|
+
---
|
|
157
|
+
|
|
158
|
+
## Contingency Operations (§164.310(a)(2))
|
|
159
|
+
|
|
160
|
+
Applicable to all organizations:
|
|
161
|
+
|
|
162
|
+
- ☐ **Disaster recovery plan documented**
|
|
163
|
+
- Plan addresses facility access during emergency
|
|
164
|
+
- Alternative work site identified (if applicable)
|
|
165
|
+
- Plan tested within last 12 months
|
|
166
|
+
|
|
167
|
+
- ☐ **Emergency power (if applicable)**
|
|
168
|
+
- UPS for critical systems
|
|
169
|
+
- Generator backup (if applicable)
|
|
170
|
+
- Last test date: _________________________
|
|
171
|
+
|
|
172
|
+
---
|
|
173
|
+
|
|
174
|
+
## Device Disposal and Media Re-use (§164.310(d)(2))
|
|
175
|
+
|
|
176
|
+
- ☐ **Secure device disposal procedure**
|
|
177
|
+
- Hard drives physically destroyed or wiped (DoD 5220.22-M or NIST 800-88)
|
|
178
|
+
- Certificate of destruction obtained
|
|
179
|
+
- Disposal log maintained
|
|
180
|
+
- Last disposal date: _________________________
|
|
181
|
+
|
|
182
|
+
- ☐ **Media sanitization before re-use**
|
|
183
|
+
- Procedure documented
|
|
184
|
+
- Verification process in place
|
|
185
|
+
- Re-use log maintained
|
|
186
|
+
|
|
187
|
+
---
|
|
188
|
+
|
|
189
|
+
## Accountability (§164.310(d)(1))
|
|
190
|
+
|
|
191
|
+
- ☐ **Hardware inventory maintained**
|
|
192
|
+
- All devices containing ePHI tracked
|
|
193
|
+
- Inventory updated quarterly
|
|
194
|
+
- Last update: _________________________
|
|
195
|
+
|
|
196
|
+
- ☐ **Device check-in/check-out log**
|
|
197
|
+
- Portable devices tracked
|
|
198
|
+
- Checkout authorization required
|
|
199
|
+
- Return inspection process
|
|
200
|
+
|
|
201
|
+
---
|
|
202
|
+
|
|
203
|
+
## Annual Review & Attestation
|
|
204
|
+
|
|
205
|
+
### Findings Summary
|
|
206
|
+
|
|
207
|
+
**Compliant Items:** _____ / _____
|
|
208
|
+
**Items Requiring Remediation:** _____
|
|
209
|
+
**Target Remediation Date:** _________________________
|
|
210
|
+
|
|
211
|
+
### Remediation Plan
|
|
212
|
+
|
|
213
|
+
| Item | Priority | Responsible Party | Target Date | Status |
|
|
214
|
+
|------|----------|-------------------|-------------|--------|
|
|
215
|
+
| | | | | |
|
|
216
|
+
| | | | | |
|
|
217
|
+
| | | | | |
|
|
218
|
+
|
|
219
|
+
### Attestation
|
|
220
|
+
|
|
221
|
+
I certify that this checklist accurately reflects the physical safeguards in place for our organization as of the date above. I understand that physical safeguards must be maintained continuously and reviewed at least annually per HIPAA requirements.
|
|
222
|
+
|
|
223
|
+
**Signature:** \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
|
|
224
|
+
|
|
225
|
+
**Name:** [NAME]
|
|
226
|
+
|
|
227
|
+
**Title:** [TITLE]
|
|
228
|
+
|
|
229
|
+
**Date:** \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
|
|
230
|
+
|
|
231
|
+
---
|
|
232
|
+
|
|
233
|
+
## References
|
|
234
|
+
|
|
235
|
+
- **45 CFR §164.310(a)(1)** - Facility Access Controls
|
|
236
|
+
- **45 CFR §164.310(a)(2)(i)** - Contingency Operations
|
|
237
|
+
- **45 CFR §164.310(b)** - Workstation Use
|
|
238
|
+
- **45 CFR §164.310(c)** - Workstation Security
|
|
239
|
+
- **45 CFR §164.310(d)(1)** - Device and Media Controls
|
|
240
|
+
- **45 CFR §164.310(d)(2)** - Data Backup and Storage
|
|
241
|
+
|
|
242
|
+
**Retention:** This checklist must be retained for a minimum of six (6) years from the date of its creation or the date when it last was in effect, whichever is later (45 CFR §164.316(b)(2)).
|
|
243
|
+
|
|
244
|
+
---
|
|
245
|
+
|
|
246
|
+
*Generated using vlayer - HIPAA Compliance Scanner*
|
|
247
|
+
*https://github.com/Francosimon53/verification-layer*
|
|
@@ -0,0 +1,237 @@
|
|
|
1
|
+
# HIPAA SECURITY OFFICER DESIGNATION
|
|
2
|
+
|
|
3
|
+
**Organization:** [COMPANY NAME]
|
|
4
|
+
**Date:** [DATE]
|
|
5
|
+
**EIN/Tax ID:** [EIN] *(optional)*
|
|
6
|
+
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
## DESIGNATION
|
|
10
|
+
|
|
11
|
+
Pursuant to **45 CFR §164.308(a)(2)**, [COMPANY NAME] hereby designates the following individual as the **HIPAA Security Officer** responsible for the development, implementation, and maintenance of policies and procedures required by the HIPAA Security Rule to protect electronic protected health information (ePHI).
|
|
12
|
+
|
|
13
|
+
> **REGULATORY REQUIREMENT**: The HIPAA Security Rule mandates that covered entities and business associates must "identify the security official who is responsible for the development and implementation of the policies and procedures required by this subpart for the entity." This designation fulfills that requirement.
|
|
14
|
+
|
|
15
|
+
---
|
|
16
|
+
|
|
17
|
+
## DESIGNATED SECURITY OFFICER
|
|
18
|
+
|
|
19
|
+
**Name:** [FULL NAME]
|
|
20
|
+
**Title:** [JOB TITLE]
|
|
21
|
+
**Email:** [EMAIL]
|
|
22
|
+
**Phone:** [PHONE]
|
|
23
|
+
**Start Date:** [DATE]
|
|
24
|
+
|
|
25
|
+
---
|
|
26
|
+
|
|
27
|
+
## RESPONSIBILITIES
|
|
28
|
+
|
|
29
|
+
The Security Officer shall be responsible for:
|
|
30
|
+
|
|
31
|
+
1. **Overseeing compliance** with the HIPAA Security Rule (45 CFR Part 164, Subpart C)
|
|
32
|
+
|
|
33
|
+
2. **Conducting and documenting risk analyses** at least annually, identifying threats and vulnerabilities to ePHI
|
|
34
|
+
|
|
35
|
+
3. **Developing and maintaining** security policies and procedures covering:
|
|
36
|
+
- Administrative safeguards
|
|
37
|
+
- Physical safeguards
|
|
38
|
+
- Technical safeguards
|
|
39
|
+
- Organizational requirements
|
|
40
|
+
- Documentation requirements
|
|
41
|
+
|
|
42
|
+
4. **Managing the security incident response process**, including:
|
|
43
|
+
- Incident detection and reporting
|
|
44
|
+
- Investigation and containment
|
|
45
|
+
- Breach risk assessments
|
|
46
|
+
- Notification to affected individuals and HHS when required
|
|
47
|
+
- Post-incident analysis and corrective actions
|
|
48
|
+
|
|
49
|
+
5. **Ensuring workforce security awareness training** is completed annually for all workforce members with access to ePHI
|
|
50
|
+
|
|
51
|
+
6. **Reviewing and approving access** to electronic systems containing ePHI, including:
|
|
52
|
+
- Access authorization procedures
|
|
53
|
+
- Access establishment and modification
|
|
54
|
+
- Access termination procedures
|
|
55
|
+
- Periodic access reviews
|
|
56
|
+
|
|
57
|
+
7. **Overseeing Business Associate compliance verification**, including:
|
|
58
|
+
- Reviewing Business Associate Agreements (BAAs)
|
|
59
|
+
- Monitoring BA security practices
|
|
60
|
+
- Coordinating incident response with BAs
|
|
61
|
+
|
|
62
|
+
8. **Maintaining documentation** of security measures for a minimum of **6 years** from creation or when last in effect, whichever is later (45 CFR §164.316(b)(2))
|
|
63
|
+
|
|
64
|
+
9. **Coordinating penetration testing and vulnerability scanning** to identify security weaknesses
|
|
65
|
+
|
|
66
|
+
10. **Reporting security matters** to organizational leadership, including:
|
|
67
|
+
- Annual risk assessment results
|
|
68
|
+
- Security incidents and breaches
|
|
69
|
+
- Compliance status updates
|
|
70
|
+
- Resource needs and budget requests
|
|
71
|
+
|
|
72
|
+
---
|
|
73
|
+
|
|
74
|
+
## AUTHORITY
|
|
75
|
+
|
|
76
|
+
The Security Officer has the authority to:
|
|
77
|
+
|
|
78
|
+
- ✓ **Approve or deny access** to systems containing ePHI based on job responsibilities and the principle of minimum necessary
|
|
79
|
+
|
|
80
|
+
- ✓ **Initiate security incident response procedures** immediately upon detection of a security incident
|
|
81
|
+
|
|
82
|
+
- ✓ **Require workforce members to complete security training** as a condition of maintaining access to ePHI
|
|
83
|
+
|
|
84
|
+
- ✓ **Recommend disciplinary action** for security policy violations, up to and including termination of access or employment
|
|
85
|
+
|
|
86
|
+
- ✓ **Engage external security consultants** as needed for assessments, audits, incident response, or specialized expertise
|
|
87
|
+
|
|
88
|
+
- ✓ **Implement technical and administrative controls** necessary to protect ePHI in accordance with the Security Rule
|
|
89
|
+
|
|
90
|
+
- ✓ **Suspend or revoke access** to ePHI in emergency situations or when a security threat is identified
|
|
91
|
+
|
|
92
|
+
- ✓ **Coordinate with legal counsel** on breach determinations and regulatory notifications
|
|
93
|
+
|
|
94
|
+
---
|
|
95
|
+
|
|
96
|
+
## REPORTING STRUCTURE
|
|
97
|
+
|
|
98
|
+
**Reports To:** [EXECUTIVE TITLE, e.g., CEO, CTO, Compliance Officer]
|
|
99
|
+
|
|
100
|
+
**Collaborates With:**
|
|
101
|
+
- Privacy Officer (HIPAA Privacy Rule compliance)
|
|
102
|
+
- IT Department (technical implementation)
|
|
103
|
+
- Legal/Compliance (regulatory guidance)
|
|
104
|
+
- Human Resources (workforce security)
|
|
105
|
+
|
|
106
|
+
---
|
|
107
|
+
|
|
108
|
+
## BACKUP/INTERIM SECURITY OFFICER
|
|
109
|
+
|
|
110
|
+
In the event the designated Security Officer is unavailable (vacation, leave, resignation), the following individual shall serve as the interim Security Officer:
|
|
111
|
+
|
|
112
|
+
**Backup Name:** [FULL NAME]
|
|
113
|
+
**Title:** [JOB TITLE]
|
|
114
|
+
**Email:** [EMAIL]
|
|
115
|
+
**Phone:** [PHONE]
|
|
116
|
+
|
|
117
|
+
---
|
|
118
|
+
|
|
119
|
+
## TERM
|
|
120
|
+
|
|
121
|
+
This designation is effective from [START DATE] and continues until:
|
|
122
|
+
- Resignation or termination of the Security Officer
|
|
123
|
+
- Appointment of a successor Security Officer
|
|
124
|
+
- Organizational restructuring requiring reassignment
|
|
125
|
+
|
|
126
|
+
Any changes to this designation must be documented in writing and retained for **6 years**.
|
|
127
|
+
|
|
128
|
+
---
|
|
129
|
+
|
|
130
|
+
## COMPLIANCE OBLIGATIONS
|
|
131
|
+
|
|
132
|
+
The Security Officer must ensure the organization complies with all applicable HIPAA Security Rule standards:
|
|
133
|
+
|
|
134
|
+
### Administrative Safeguards (§164.308)
|
|
135
|
+
- Security management process (risk analysis, risk management, sanction policy, information system activity review)
|
|
136
|
+
- Assigned security responsibility *(this designation)*
|
|
137
|
+
- Workforce security (authorization, supervision, termination, clearance)
|
|
138
|
+
- Information access management
|
|
139
|
+
- Security awareness and training
|
|
140
|
+
- Security incident procedures
|
|
141
|
+
- Contingency planning (data backup, disaster recovery, emergency mode, testing, applications and data criticality)
|
|
142
|
+
- Evaluation (periodic technical and non-technical evaluations)
|
|
143
|
+
- Business associate contracts
|
|
144
|
+
|
|
145
|
+
### Physical Safeguards (§164.310)
|
|
146
|
+
- Facility access controls
|
|
147
|
+
- Workstation use and security
|
|
148
|
+
- Device and media controls
|
|
149
|
+
|
|
150
|
+
### Technical Safeguards (§164.312)
|
|
151
|
+
- Access control (unique user identification, emergency access, automatic logoff, encryption)
|
|
152
|
+
- Audit controls
|
|
153
|
+
- Integrity controls
|
|
154
|
+
- Transmission security
|
|
155
|
+
|
|
156
|
+
### Organizational Requirements (§164.314)
|
|
157
|
+
- Business associate contracts and other arrangements
|
|
158
|
+
|
|
159
|
+
### Policies, Procedures, and Documentation (§164.316)
|
|
160
|
+
- Documentation requirements (time limit, availability, updates)
|
|
161
|
+
|
|
162
|
+
---
|
|
163
|
+
|
|
164
|
+
## ACKNOWLEDGED AND APPROVED
|
|
165
|
+
|
|
166
|
+
By signing below, the authorizing officer confirms the designation of the Security Officer and grants the authority necessary to fulfill the responsibilities outlined in this document.
|
|
167
|
+
|
|
168
|
+
**Signature:** ___________________________________
|
|
169
|
+
**Name:** [AUTHORIZING OFFICER NAME]
|
|
170
|
+
**Title:** [AUTHORIZING OFFICER TITLE, e.g., CEO, President]
|
|
171
|
+
**Date:** ___________________
|
|
172
|
+
|
|
173
|
+
---
|
|
174
|
+
|
|
175
|
+
## ACCEPTED
|
|
176
|
+
|
|
177
|
+
By signing below, the designated Security Officer acknowledges acceptance of this appointment and the responsibilities, authorities, and obligations outlined in this document.
|
|
178
|
+
|
|
179
|
+
**Signature:** ___________________________________
|
|
180
|
+
**Name:** [SECURITY OFFICER NAME]
|
|
181
|
+
**Title:** [JOB TITLE]
|
|
182
|
+
**Date:** ___________________
|
|
183
|
+
|
|
184
|
+
---
|
|
185
|
+
|
|
186
|
+
## DISTRIBUTION
|
|
187
|
+
|
|
188
|
+
This designation document should be distributed to:
|
|
189
|
+
|
|
190
|
+
☐ Designated Security Officer
|
|
191
|
+
☐ Executive Leadership
|
|
192
|
+
☐ Human Resources
|
|
193
|
+
☐ Privacy Officer
|
|
194
|
+
☐ IT Department
|
|
195
|
+
☐ Legal/Compliance Department
|
|
196
|
+
☐ All workforce members (notification of designation)
|
|
197
|
+
|
|
198
|
+
---
|
|
199
|
+
|
|
200
|
+
## DOCUMENT CONTROL
|
|
201
|
+
|
|
202
|
+
**Document ID:** SEC-OFF-[YEAR]-001
|
|
203
|
+
**Version:** 1.0
|
|
204
|
+
**Effective Date:** [DATE]
|
|
205
|
+
**Next Review Date:** [DATE + 1 YEAR]
|
|
206
|
+
**Retention Period:** 6 years from creation or last effective date
|
|
207
|
+
|
|
208
|
+
### Revision History
|
|
209
|
+
|
|
210
|
+
| Version | Date | Changes | Approved By |
|
|
211
|
+
|---------|------|---------|-------------|
|
|
212
|
+
| 1.0 | [DATE] | Initial designation | [NAME] |
|
|
213
|
+
| | | | |
|
|
214
|
+
|
|
215
|
+
---
|
|
216
|
+
|
|
217
|
+
## NOTES
|
|
218
|
+
|
|
219
|
+
**For Small Organizations:**
|
|
220
|
+
The Security Officer role can be fulfilled by the same individual serving as Privacy Officer, Compliance Officer, or other leadership role. HIPAA does not require this to be a full-time dedicated position, but the responsibilities must be fulfilled regardless of organization size.
|
|
221
|
+
|
|
222
|
+
**For Remote/Cloud Organizations:**
|
|
223
|
+
Even if your organization operates entirely in the cloud without physical facilities, you must still designate a Security Officer responsible for ePHI security across all cloud services and platforms.
|
|
224
|
+
|
|
225
|
+
**Annual Review:**
|
|
226
|
+
This designation should be reviewed annually to ensure it remains current and the designated individual has the necessary authority and resources to fulfill their responsibilities.
|
|
227
|
+
|
|
228
|
+
---
|
|
229
|
+
|
|
230
|
+
**Retention:** This document must be retained for a minimum of **six (6) years** from the date of its creation or the date when it last was in effect, whichever is later (45 CFR §164.316(b)(2)).
|
|
231
|
+
|
|
232
|
+
---
|
|
233
|
+
|
|
234
|
+
*This Security Officer Designation template was generated using vlayer - HIPAA Compliance Scanner*
|
|
235
|
+
*https://github.com/Francosimon53/verification-layer*
|
|
236
|
+
|
|
237
|
+
*Template complies with 45 CFR §164.308(a)(2) - Security Management Process: Assigned Security Responsibility*
|