PromptBase
PromptBase SelectGet Select
Close icon
General
Home
Marketplace
Create
Hire
Login
Chat
Sell
Explore

Prompt Details

Model
(claude-5-sonnet)
Token size
1,355
Example input
[Organization Name]: MediCore Health Network • Industry: Healthcare (Multi-Hospital System with Outpatient Clinics) [Operating systems, frameworks, databases, cloud providers]: Windows Server 2016/2019, .NET Framework applications, SQL Server 2017, EPIC EHR system, HL7 message broker, VoIP telephony system, legacy DICOM imaging servers [Web Apps / Mobile Apps / APIs / Internal Systems]: Electronic Health Records (EHR), Patient Portal (web + mobile), Lab Information System (LIS), Pharmacy Management, Medical Imaging Archive, Billing & Claims Processing, Telehealth Platform [Phishing / Ransomware / Weak IAM / Legacy Systems / Shadow IT]: Ransomware targeting healthcare sector rising, medical devices running unsupported OS versions, USB flash drive usage for patient data transfers, staff sharing login credentials on medical systems, outdated backup recovery procedures untested in 3 years, legacy DICOM servers patched only when system fails [Security Audit / Compliance Assessment / Risk Reduction / Security Modernization]: Achieve HIPAA compliance audit readiness + Eliminate ransomware attack vectors within 18 months
Example output
### 🧭 OUTPUT ### 📊 SECTION 1 — Executive Security Assessment 🎯 **Overall Security Posture:** Fragmented with critical compliance gaps and significant ransomware vulnerability 🎯 **Attack Surface:** Extremely High — Legacy medical devices, unpatched systems, outdated protocols (DICOM), staff credential sharing, manual backup processes create operational technology (OT) security nightmare 🎯 **Business Risk:** Patient care disruption, massive HIPAA violation fines ($100K-$1.5M per violation), medical identity theft, regulatory decertification risk, reputational damage in tight-knit healthcare market 🎯 **Security Maturity:** Level 1-2 (Ad hoc processes, minimal automation, compliance driven by audit cycles rather than continuous security) 🎯 **Resilience Rating:** Poor — Recovery procedures untested, single points of failure in backup infrastructure, no rapid incident response capability --- ### 🔐 SECTION 2 — Identity & Access Management 🔓 **Authentication & Credential Management Issues:** • EPIC EHR enforces weak 4-digit PIN authentication (not HIPAA standard) • Medical device access uses default/hardcoded credentials (anesthesia machines, infusion pumps, ventilators) • Nursing staff shares single "NurseStation" login across 15 people on med-surg floor • Physician credentials used by residents/interns without audit trail differentiation • No centralized password management — physicians write passwords on sticky notes near terminals 🔓 **MFA Status:** • Zero MFA deployment across any system • HIPAA guidance recommends MFA for remote access — none implemented • Telehealth platform accessible with username/password only (privacy exposure) 🔓 **RBAC & Separation of Duties Failures:** • Lab technicians can modify test results after authorization (audit trail missing) • Billing staff can access patient clinical notes (inappropriate privilege) • IT administrator account used for routine password resets (no separation of duties) • Patient Portal administrators can modify other users' prescriptions 🔓 **Privileged Access Problems:** • Domain admin password same across all staff (reset quarterly with email notification) • Database admin passwords stored in unencrypted text file on shared drive • EHR superuser account accessed by 8 IT staff members • No audit logging of who performed privileged actions (SQL Server audit disabled to improve performance) 🔓 **Account Lifecycle Failures:** • Physician departures — average 45 days to deactivate accounts • Contractor accounts (IT vendors, consultants) never removed (35+ active accounts from terminated vendors) • Student/intern rotations — accounts created manually, rarely deleted • Shared department accounts active for 10+ years with no ownership --- ### ☁️ SECTION 3 — Infrastructure & Cloud Security 🏗️ **Data Center & Physical Security:** • Single data center facility (no geographic redundancy until DR site built) • Server room access via swipe card (logs not reviewed) • Backup tapes stored in unlocked cabinet adjacent to data center • Visitor log maintained but not cross-checked with building access records 🏗️ **Network Architecture & Segmentation:** • Clinical network isolated from administrative network (good) but enforcement via VLAN only • Medical device network connected to clinical network with no firewall between them • No demilitarized zone (DMZ) for patient portal — web server on clinical network • Guest WiFi connected to main network (no isolation) • Remote access via VPN uses preshared key (no certificate-based authentication) 🏗️ **Server Infrastructure Issues:** • Windows Server 2016 — 80+ servers nearing end of support (2027) • SQL Server 2017 — 5+ databases running unpatched versions (critical vulnerabilities known) • DICOM servers running Windows XP + Windows 7 (unsupported, patching risk to imaging functionality) • No patch management process — vendors patch on emergency basis only • Tape backup servers rarely restarted (uptime claim: 847 days, likely unpatched) 🏗️ **Storage & Encryption Gaps:** • Patient data on file shares encrypted with BitLocker (good) but encryption keys stored on same server • Database encryption at rest not enabled (HIPAA Breach Notification Rule requirement) • Backup tapes labeled with patient data — stored in unencrypted format • USB drives used for lab result transfers between facilities — no encryption, no logging • Disaster recovery copies of production database transferred via FTP (unencrypted) 🏗️ **Disaster Recovery & Business Continuity:** • DR site operational but RPO 48 hours (patient data loss exposure) • RTO target 8 hours but last successful failover test was 2018 • Backup tape recovery procedure untested — only restore verification is media integrity check • Single backup operator knowledge — no cross-training documented • Telehealth platform has zero redundancy (single server failure = service outage) --- ### 🌐 SECTION 4 — Application & API Security 🛠️ **EHR System Security:** • EPIC patient portal login vulnerable to brute force (no account lockout after 10 failed attempts) • Patient search function allows wildcard SQL queries (potential information disclosure) • Session timeouts never enforced (physicians leave workstations logged in overnight) • Audit logs stored in EPIC database (modified by EPIC admin accounts without authorization logging) • API connections to external lab providers use HTTP (unencrypted HL7 messages with patient data) 🛠️ **Patient Portal Web Application:** • Password requirements: 6+ characters, no complexity (HIPAA expects stronger standards) • Prescription refill feature allows requesting any medication (no authorization check) • Download functionality returns PDF with patient data but no watermarking or DLP • Forgot password flow sends patient SSN in email confirmation link (exposure risk) • Mobile app stores authentication token in app cache (jailbroken phone can extract) 🛠️ **Lab Information System (LIS) Vulnerabilities:** • Result entry module accessible via shared "LAB" login account (40 lab technicians) • Amendment functionality logs changes but doesn't require approval (CLIA violation) • External interface sends lab data to physicians' personal email (no encryption) • Interfacing protocol uses HL7 v2 with no encryption or digital signature verification • No input validation on result entry — free text fields allow any data 🛠️ **Telehealth Platform Security:** • Video meetings use unencrypted RTP streams (patient conversations potentially intercepted) • Patient consent not electronically captured (paper consent in folder, manual verification) • Recording feature active by default (compliance with state consent laws uncertain) • Call metadata (patient names, times) stored in unencrypted database backup --- ### 🛡️ SECTION 5 — Network Security 🌍 **Perimeter & Access Control:** • Palo Alto firewall configured with allow-all rules for internal subnets • Remote access VPN uses group authentication credentials shared across 200+ users • No egress filtering — internal systems can reach any external destination • DNS queries unencrypted (no DNS security filtering for malware C&C detection) • Email gateway antivirus signatures last updated 6 months ago 🌍 **Medical Device Network Security:** • Medical device vendors prohibit firewall rules between devices (creates flat network) • Infusion pump software requires unencrypted telnet access (vendor refuses secure alternative) • Anesthesia machines connected to network for compliance reporting — no network segmentation • Ventilators on clinical network without any firewall protection • PACS (Picture Archiving Communication System) servers on same network as EHR with no microsegmentation 🌍 **Intrusion Detection & Prevention:** • No IDS/IPS deployed (detection capability: none) • Manual log review quarterly (detection latency: months) • Antivirus configured to delete alerts automatically after 30 days (alert loss) • No network-based sandboxing for suspicious files 🌍 **VPN & Remote Access:** • Staff VPN uses pre-shared key (all users know the password) • No certificate pinning — users could be MitM'd if WiFi compromised • Idle timeout set to 8 hours (user leaves office, VPN active all day) • No multi-factor authentication on VPN access • Telehealth physicians use unencrypted WiFi at home to access EHR (clinical data exposure) --- ### 📋 SECTION 6 — Compliance & Governance 📜 **HIPAA Compliance Status:** • Security Rule (45 CFR §164.300-318): 40% compliant - Access controls absent (shared credentials violates §164.312(a)(1)) - Audit controls inadequate (no centralized logging violates §164.312(b)) - Integrity controls missing (no data amendment controls violates §164.312(c)(1)) - Transmission security non-compliant (unencrypted HL7 violates §164.312(e)(2)(i)) • Privacy Rule (45 CFR §164.500-534): 55% compliant - Business Associate Agreements (BAAs) missing with 8 vendors - Minimum Necessary not enforced (lab technician access to all patient data) - Patient authorization for research data sharing not documented • Breach Notification Rule (45 CFR §164.400-414): 30% compliant - No breach incident log - Notification procedures exist but untested - No process to determine breach risk assessment threshold 🏥 **HITECH Act Requirements:** • Encryption not enforced on backup media (violation of HITECH notification exemption) • Audit logs not retained for minimum 6-year period • Business Associate risk assessments not conducted 🏥 **Data Protection & Classification:** • No data classification policy (all data treated equally) • Protected Health Information (PHI) not identified in systems • No Data Loss Prevention (DLP) tools • USB drives and email used to transfer PHI without encryption • Patient records printed and left on desks (physical security gap) 🏥 **Security Policies & Procedures:** • Security Plan document last updated 2016 (due for revision) • Incident response plan minimal (3 pages, no roles/escalation defined) • Acceptable Use Policy vague ("Respect patient privacy") • Change management process bypassed for urgent patches (no documentation) • Security awareness training last conducted in 2019 (outdated, no annual refresh) --- ### 🚨 SECTION 7 — Threat & Risk Analysis 🔴 **CRITICAL RISKS (Immediate Action Required)** • **Ransomware Infection via Unpatched Medical Devices:** - Windows XP/7 DICOM servers vulnerable to EternalBlue/WannaCry class exploits - Flat medical device network enables rapid propagation to clinical systems - Single server compromise → EHR downtime → patient care disruption → surgical cancellations - Business Impact: $5M+ recovery costs, patient safety incidents, regulatory investigation - Likelihood: Critical (5/5) | Exploitability: Critical (5/5) • **Ransomware Encryption via Shared Credentials & Backup Access:** - Nursing staff sharing "NurseStation" login + domain admin password known to 15+ people - Backup tapes stored in accessible cabinet with no audit trail - Attackers compromise user account → access backups → encrypt backups too → RTO becomes weeks - Business Impact: Complete EHR unavailability, patient data loss, HIPAA violation - Likelihood: Critical (5/5) | Exploitability: High (4/5) • **Patient Data Breach via Unencrypted Transfers:** - USB drives + unencrypted HL7 messages + patient portal downloads all contain PHI - No DLP to detect data exfiltration - Insider threat or compromised device → 50K+ patient records exposed - Business Impact: $2.5M+ HIPAA fines (potentially $1.5M per violation × 5+ violations) - Likelihood: High (4/5) | Exploitability: High (4/5) • **HIPAA Audit Failure & Decertification:** - CMS audit discovers shared credentials, missing audit logs, unencrypted backups - Joint Commission audit identifies patient safety risks from incomplete access controls - Facility loses accreditation → patient census drops 30% → revenue loss $3M+ annually - Business Impact: Regulatory enforcement, corrective action plan, reputational damage - Likelihood: Critical (5/5) | Exploitability: N/A (assessment-driven) 🟠 **HIGH RISKS (Address Within 30 Days)** • **Medical Device Compromise Leading to Patient Harm:** - Flat network + unpatched devices + no network segmentation = attacker modifies infusion pump settings - Patient receives incorrect medication dosage (adverse event) - Business Impact: Patient death/injury litigation, federal investigation, criminal liability - Likelihood: Medium-High (3/5) | Exploitability: High (4/5) • **Insider Data Theft via Excessive Privileges:** - Lab technician can modify test results, billing staff can access clinical notes - Disgruntled employee extracts patient data for competitor healthcare system - Business Impact: $1M+ HIPAA breach notification costs, loss of patient trust - Likelihood: Medium (3/5) | Exploitability: High (4/5) • **Disaster Recovery Failure:** - Last successful tape recovery was 2018 (likely format obsolescence) - DR site has 48-hour RPO but backup media never tested for recoverability - Production database corrupted → backup media unreadable → permanent data loss - Business Impact: Multi-week EHR unavailability, patient safety incidents, malpractice claims - Likelihood: Medium (3/5) | Exploitability: High (4/5) • **Telehealth Eavesdropping & Privacy Violation:** - Unencrypted RTP streams + physicians using home WiFi = patient conversations intercepted - Recordings active without consent in states requiring explicit consent - Class action lawsuit from patients whose confidential conversations were recorded - Business Impact: $500K+ settlement, regulatory fine, license suspension risk - Likelihood: Medium (3/5) | Exploitability: High (4/5) 🟡 **MEDIUM RISKS (Address Within 90 Days)** • **Physician Credential Abuse & Audit Trail Loss:** - Residents use physician credentials → actions appear to come from attending physician - No audit log of actual person performing critical clinical actions (e.g., lab order cancellation) - Malpractice litigation → cannot prove physician ordered treatment - Business Impact: Legal liability, licensure investigation, $250K+ litigation costs - Likelihood: Medium (3/5) | Exploitability: Medium (3/5) • **Phishing Attack Leading to EHR Compromise:** - No security awareness training since 2019 - Staff sharing credentials makes credential-stealing phishing valuable - Attacker gains employee login → EHR access → exfiltrates patient data - Business Impact: $500K+ breach notification, HIPAA violation - Likelihood: Medium (3/5) | Exploitability: Medium (3/5) • **Third-Party Vendor Breach:** - 8+ vendors without Business Associate Agreements accessing patient data - Lab result transmissions to external vendors via unencrypted email - Vendor compromise → patient data exposed, organization liable - Business Impact: HIPAA liability despite vendor breach, breach notification - Likelihood: Medium (3/5) | Exploitability: Medium (3/5) 🟢 **LOW RISKS (Monitor & Include in Roadmap)** • **Patient Portal Data Exposure via Forgotten Device:** - Mobile app stores authentication token in cleartext cache - Lost phone with app cache → patient health records accessible - Business Impact: Individual patient privacy violation, limited breach exposure - Likelihood: Low (2/5) | Exploitability: Medium (3/5) --- ### 🔄 SECTION 8 — Incident Response & Recovery 📊 **Current Monitoring & Alerting:** • Antivirus on endpoints with alerts auto-deleted after 30 days (alerts: untracked) • Firewall logs generated but not reviewed • No SIEM deployment (log analysis: manual spot-checks only) • Backup tape completion logged but not verified for integrity • EHR audit logs stored in database, not exported for analysis 📊 **Incident Response Maturity:** • Incident response plan exists (3 pages, minimal detail) • No incident response team designated (ad hoc response by available IT staff) • No retainer agreement with external incident responders • No prior incident response exercises or tabletop drills • Breach notification procedures defined but untested • Average incident detection latency: 14 days (discovered during backup recovery) 📊 **Disaster Recovery Assessment:** • Backup strategy: Daily incremental tape backups (47-year-old tape technology) • Last successful recovery test: 2018 (tape format potentially unreadable today) • RPO target: 24 hours (actual — incremental backups taken daily) • RTO target: 8 hours (untested; likely 24+ hours in real scenario) • DR site operational but database replication untested • Tape rotation procedure manual (human error risk in tape handling) • Backup media stored in cabinet accessible to multiple staff (no restricted access) 📊 **Resilience Assessment:** • EHR availability during incident: Estimated downtime 3-5 days • Workaround procedures documented: Paper-based workflows for 1 day max • Telehealth platform: Single point of failure (0 redundancy) • Patient notification procedure: Manual phone calls (labor-intensive, slow) • Staff communication during outage: No centralized crisis communication system • Vendor support SLAs: Reactive only (no proactive monitoring) --- ### 🚀 SECTION 9 — Security Improvement Roadmap **PHASE 1 — IMMEDIATE ACTIONS (0–30 Days)** **Task 1: Emergency Medical Device Segmentation & Patching** • Deploy network firewall between medical device network and EHR network (zero trust model) • Isolate Windows XP/7 DICOM servers into segregated subnet (accept remote patching risk) • Block USB port access on clinical workstations via Group Policy • Disable default credentials on network-connected medical devices (coordinate with vendors) • Implementation Effort: 120 hours | Risk Reduction: Critical → High | Business Impact: Ransomware propagation blocked, patient device safety restored **Task 2: Credential & Access Control Emergency Fix** • Remove shared "NurseStation" login — create individual accounts for each nurse (LDAP integration) • Rotate domain admin password, restrict to 3 IT staff only, use password manager • Force EPIC password change to 12+ characters with complexity • Disable default medical device accounts, replace with vendor-provided secure access • Implementation Effort: 60 hours | Risk Reduction: Critical → High | Business Impact: Audit trail establishes individual accountability **Task 3: Backup Security & Recovery Validation** • Move backup tape storage to restricted access cabinet with audit logging • Encrypt all backup media (retroactive for new tapes) • Conduct full recovery test of recent backup to verify tape integrity & recoverability • Document recovery procedure with step-by-step instructions • Engage backup vendor for emergency support SLA agreement • Implementation Effort: 40 hours | Risk Reduction: Critical → High | Business Impact: Recovery confidence restored, RTO/RPO validated **Task 4: HIPAA Audit Readiness Quick Wins** • Export all audit logs from EHR database, store in centralized immutable log system (SIEM alternative) • Create Business Associate Agreements (BAAs) for all vendors, audit within 30 days • Develop data classification policy (PHI/PII/Public), communicate to staff • Disable HL7 message transmission via unencrypted channels (deploy SFTP alternative) • Implementation Effort: 80 hours | Risk Reduction: High → Medium (compliance) | Business Impact: HIPAA audit readiness up 25% **PHASE 2 — SHORT-TERM IMPROVEMENTS (30–90 Days)** **Task 5: Multi-Factor Authentication Deployment** • Deploy Okta or Azure AD MFA for VPN access (immediate for remote physicians) • Implement MFA for patient portal login (SMS or authenticator app) • Enable MFA for EHR remote access (token-based, managed via Okta) • MFA enforcement target: 100% of remote access, 80% of clinical staff by 60-day mark • Implementation Effort: 140 hours | Risk Reduction: High → Medium | Business Impact: Credential-based attacks prevented **Task 6: Network Segmentation & Microsegmentation** • Deploy DMZ for patient portal (isolate web traffic from clinical network) • Implement VLAN segmentation + firewall rules between: Clinical / Administrative / Medical Devices / Guests • Enable network access control (NAC) on clinical systems to enforce device compliance (antivirus running, patched) • Deploy microsegmentation via firewall rules: EHR → Database / EHR → Backup / Devices → Isolated Subnet • Implementation Effort: 200 hours | Risk Reduction: High → Medium (lateral movement) | Business Impact: Ransomware propagation time increased from hours to days **Task 7: Telehealth Security Hardening** • Deploy encrypted telehealth platform (WebRTC with TLS 1.3 end-to-end encryption) • Implement consent management system for call recording (electronic capture with patient signature) • Migrate from personal WiFi to secure corporate network access via VPN + MFA • Deploy endpoint detection on physician laptops (EDR with ransomware detection) • Implementation Effort: 160 hours | Risk Reduction: High → Low (privacy) | Business Impact: HIPAA compliance restoration, state law compliance **Task 8: Patch Management & Vulnerability Program** • Establish monthly patch deployment schedule (security patches within 30 days of release) • Deploy patch management tool for automatic patch distribution & compliance reporting • Assess Windows XP/7 end-of-life servers — plan replacement within 12-month roadmap • Conduct quarterly vulnerability scans, remediate critical findings within 15 days • Implementation Effort: 180 hours | Risk Reduction: High → Low | Business Impact: Known exploit surface eliminated **PHASE 3 — LONG-TERM STRATEGY (3–18 Months)** **Task 9: HIPAA-Grade Infrastructure Modernization** • Migrate Windows Server 2016/2019 → Server 2022 (modern baseline, extended support) • Upgrade SQL Server 2017 → 2019+ (encryption at rest, improved audit features) • Deploy transparent data encryption (TDE) on all clinical databases • Implement column-level encryption for SSN/DOB fields • Enable SQL Server Always-On for high availability (eliminate single server failure risk) • Implementation Effort: 400 hours | Risk Reduction: Medium → Low | Business Impact: Disaster recovery RTO reduced to 2 hours **Task 10: Comprehensive Audit Logging & SIEM Deployment** • Deploy enterprise SIEM (Splunk, ELK, or Microsoft Sentinel) for centralized log aggregation • Configure audit logging on: EHR / SQL Server / AD / Firewall / Patient Portal / Telehealth • Implement log retention policy: 7 years for clinical logs (per HIPAA), 3 years for infrastructure • Enable real-time alerting on: Unauthorized access attempts, privileged account changes, mass data downloads, failed login patterns • Implementation Effort: 240 hours | Risk Reduction: Medium → Low (detection) | Business Impact: Mean time to detect reduced from 14 days to 4 hours **Task 11: Regulatory Compliance & Formal Assessment** • Conduct internal HIPAA risk assessment (document controls, identify gaps, remediate) • Engage external HIPAA compliance auditor for formal assessment • Participate in CMS/OCR audit preparation (mock audit, documentation readiness) • Complete corrective action plan for audit findings • Target: Zero findings related to critical security controls by month 12 • Implementation Effort: 200 hours | Risk Reduction: Governance → Certified | Business Impact: Regulatory confidence, license protection **Task 12: Security Awareness & Incident Response Training** • Develop annual HIPAA privacy & security awareness training (mandatory for all staff) • Quarterly phishing simulation campaign (target: reduce click-through from baseline 25% to <5%) • Conduct tabletop incident response exercise (ransomware scenario) quarterly • Establish Security Awareness Champion program (physician champions in each department) • Cross-train incident response team (3 IT staff + backup), conduct annual exercises • Implementation Effort: 100 hours | Risk Reduction: Medium → Low (human vector) | Business Impact: Staff security maturity doubled **Task 13: Data Loss Prevention & Privacy Protection** • Deploy Data Loss Prevention (DLP) tool on network boundaries & endpoints • Implement email gateway scanning for PHI exfiltration • Block USB drive usage via Group Policy (exception process for approved uses) • Watermark patient portal downloads (audit trail of document access) • Implement automatic email encryption for PHI transmission • Implementation Effort: 120 hours | Risk Reduction: High → Low | Business Impact: Insider threat attack surface reduced 80% --- ### 🧾 FINAL CYBERSECURITY REPORT — EXECUTIVE SUMMARY **1. Executive Security Summary:** MediCore Health Network operates with a severely fragmented security posture (Level 1-2 maturity) heavily dependent on vendor management rather than systematic controls. Critical gaps in credential management, backup security, and medical device protection create unacceptable ransomware risk and HIPAA non-compliance. Immediate 30-day emergency actions to segment medical devices, validate backup recoverability, and eliminate shared credentials are non-negotiable. The organization faces imminent HIPAA audit failure and potential regulatory decertification if current trajectory continues. With focused 90-day execution on Phases 1-2, HIPAA compliance readiness is achievable; full modernization within 18 months is essential for industry-standard security posture. **2. Overall Security Maturity Score:** 28 / 100 (Baseline; critical gaps in multiple domains) **3. Identity & Access Assessment:** 22 / 100 (Shared credentials, no MFA, excessive privileges, poor audit logging) **4. Infrastructure & Cloud Security Review:** 25 / 100 (Unpatched servers, flat medical device network, inadequate encryption, untested disaster recovery) **5. Application & API Security Assessment:** 30 / 100 (HIPAA-specific violations in EHR/portal, unencrypted HL7 messages, inadequate input validation) **6. Compliance Readiness Score:** 32 / 100 (HIPAA 40%, HITECH 30%, Breach Notification 30%) **7. Enterprise Risk Matrix:** • Critical Risks: 4 (Ransomware device compromise, shared credential abuse, unencrypted backups, HIPAA audit failure) • High Risks: 4 (Medical device patient harm, insider data theft, DR failure, telehealth eavesdropping) • Medium Risks: 3 (Credential abuse, phishing, vendor breach) • Low Risks: 1 (Mobile device token exposure) **8. Incident Response Readiness:** 20 / 100 (Plan exists but untested, no dedicated team, unrealistic RTO targets, backup recovery unvalidated) **9. Top 10 Security Recommendations:** • (1) Emergency: Segment medical device network from EHR network + firewall enforcement • (2) Emergency: Eliminate shared login accounts, implement individual LDAP-based access • (3) Emergency: Validate backup tape recoverability + move backups to restricted access storage • (4) Emergency: Deploy MFA on VPN + patient portal access • (5) Encrypt all patient data in transit (HL7 messages, SFTP, TLS 1.3) • (6) Create Business Associate Agreements with all vendors within 30 days • (7) Deploy SIEM for centralized audit logging + real-time alert capability • (8) Modernize Windows/SQL Server infrastructure, plan medical device OS upgrades • (9) Implement patient consent management for telehealth recording (electronic capture) • (10) Establish security awareness program + quarterly incident response tabletop exercises **10. Enterprise Cybersecurity Roadmap:** • Phase 1 (0–30 days): Medical device segmentation, credential elimination, backup validation, HIPAA audit readiness — Target: Eliminate critical risks, achieve 45/100 maturity score • Phase 2 (30–90 days): MFA deployment, network segmentation, telehealth hardening, patch management program — Target: Reduce high risks, achieve 55/100 maturity score • Phase 3 (3–18 months): Infrastructure modernization, SIEM deployment, formal HIPAA assessment, compliance certification — Target: Achieve 75+/100 maturity score, HIPAA certified compliance, patient safety assurance --- This sample demonstrates your framework applied to a realistic healthcare scenario with HIPAA-specific compliance requirements, medical device security challenges, and implementation-ready remediation roadmap.
Claude

Enterprise Cybersecurity Audit System

Add to Cart
Instant accessInstant access
Usage rightsCommercial use
Money-back guaranteeMoney‑back
By purchasing this prompt, you agree to our terms of service
CLAUDE-5-SONNET
Tested icon
Guide icon
4 examples icon
Free credits icon
Cybersecurity isn't just about preventing attacks—it's about identifying weaknesses before attackers do. ⚠️ This prompt acts as a Principal Cybersecurity Consultant, performing a comprehensive enterprise security assessment across infrastructure, applications, APIs, cloud services, identity management, networks, DevSecOps, compliance, and incident response. It identifies vulnerabilities, prioritizes risks, recommends mitigation strategies, and builds a production-ready cybersecurity roadmap.
...more
Added over 1 month ago
Report
Browse Marketplace