This paper presents an enterprise security plan proposal for healthcare organizations, structured around the ten domains of the Information Security Common Body of Knowledge (CBK). It examines the CIA Triad (confidentiality, integrity, and availability) as the foundation of security practice, explores security architecture models and operational security domains, and addresses the legal and ethical responsibilities of credentialed security professionals. A central focus is HIPAA Security Rule compliance, including risk analysis requirements and the federal preemption of conflicting state laws. The paper provides a practical framework for health information security governance aligned with regulatory standards.
Information security traditionally meant protecting corporate-specific information such as trade secrets and other proprietary data. However, in today's business environment, data protection means much more. Medical service and healthcare providers now store enormous amounts of patient data, making information security concerns more important than ever before. This proposal covers the ten domains of the Information Security Common Body of Knowledge, widely accepted categories of information security, principles of success, planning procedures, security policy and standards taxonomy, and policies complying with the HIPAA Security Rule as well as other regulations relevant to information security and privacy.
The ten domains of the Information Security Common Body of Knowledge are as follows:
(1) Security management practices; (2) Access control systems and methodology; (3) Telecommunications and networking security; (4) Cryptography; (5) Security architecture and models; (6) Operations security; (7) Application and systems development security; (8) Physical security; (9) Business continuity and disaster recovery planning; and (10) Laws, investigation, and ethics. (American Health Information Management Association, 2011)
Forming what is known as the CIA Triad are the three tenets of confidentiality, integrity, and availability — the measures by which security practices are tested. Primary security issues across the software development lifecycle are identified as follows:
(1) Feasibility of System: Identification of the requirement for security, policies, and standards; (2) Requirements for Software Plans: Identification of vulnerabilities, threats, and risks, along with adequate protection planning and cost-benefit analysis; (3) Design of Product: Security specifications planning in product design, including access controls and encryption; (4) Design Detail: Security controls and user relationships linked to business needs and legal liabilities; (5) Coding: Development of security-related software code and documentation; (6) Implementation: Security measures implemented and software tested prior to system roll-out; (7) Product Integration: Testing of security measures written into system software and subsequent refinements; (8) Operations and Maintenance: Ongoing monitoring of security software for threats, with changes and testing conducted as needed. (American Health Information Management Association, 2011, paraphrased)
Three types of security models exist: (1) Access Control — common in the health field, this model enables organizations to identify users and classify data for access or restriction; (2) Integrity — this model protects confidentiality and data integrity, ensuring unauthorized users cannot alter or modify data; (3) Information Flow — this model classifies information and governs how it flows according to defined security policies and rules. (American Health Information Management Association, 2011, paraphrased)
"Access control, integrity, and operational security controls"
"Ethics codes and security professional certifications"
"HIPAA risk analysis and federal preemption rules"
"Recap of CBK domains and HIPAA applicability"
You’re 38% through this paper. Sign up to read the remaining 4 sections.
Sign Up Now — Instant Access Already a member? Log inAlways verify citation format against your institution’s current style guide requirements.