Category: Compliance Standards

Staying informed about all of the cyber security compliance standards is essential to keeping your company safe from hackers. Read on to learn about the various steps you can take to stay up to date with your industry’s compliance standards.

  • What Happens If You Violate HIPAA?

    What Happens If You Violate HIPAA?

    The Health Insurance Portability and Accountability Act (HIPAA), signed into law in 1996, established strict requirements for protecting the privacy and security of individuals’ health information. Its primary goal is to ensure that sensitive patient data, known as protected health information (PHI), is properly safeguarded by healthcare organizations and their business associates. HIPAA is divided into five titles, each designed to improve health insurance portability, standardize administrative processes, and enforce consistent protections for PHI across the healthcare industry. Before HIPAA, there were few universally accepted standards for securing health data, leaving patients vulnerable to misuse, loss, or unauthorized disclosure. The introduction of HIPAA policies and enforcement mechanisms marked a turning point for healthcare compliance. Patients gained greater confidence that their personal health information would remain private, while healthcare organizations were held to clear accountability standards. However, HIPAA compliance is still not prioritized by every organization. Some healthcare entities cut corners in an effort to reduce costs, placing sensitive PHI at risk. These lapses often result in data breaches, regulatory investigations, and the consequences of HIPAA violations.

    The consequences of HIPAA violations can be costly. In 2016 alone, the U.S. Department of Health and Human Services’ Office for Civil Rights (OCR) collected a record-breaking $23 million in HIPAA fines, far exceeding the previous record of $7.4 million set in 2014.

    To avoid the consequences of HIPAA violations, including financial, legal, and reputational damage, organizations must understand which types of violations most commonly lead to enforcement actions. Learning from past compliance failures can help healthcare organizations strengthen their HIPAA programs and reduce their risk of costly penalties. (more…)

  • Overview of CMMC Level 2 Requirements

    Overview of CMMC Level 2 Requirements

    CMMC Level 2 requirements are part of the U.S. Department of Defense’s Cybersecurity Maturity Model Certification (CMMC) framework and apply to contractors that handle Controlled Unclassified Information (CUI). This guide provides a clear, practical overview of what CMMC Level 2 requires, who it applies to, and how organizations can prepare for compliance.

    As the second installment in our CMMC series, this article focuses specifically on Level 2 requirements. If you’re looking for information on other maturity levels, explore our detailed guides on CMMC Levels 1, 3, 4, and 5. (more…)

  • What Does Protected Health Information Include?

    What Does Protected Health Information Include?

    The Health Insurance Portability and Accountability Act of 1996 (HIPAA) designates forms of patient-related records that need to be protected. These records are “protected health information” (PHI). Guarding these documents is critical to the safety of patients and providers alike. Read on for several examples of protected health information, the US Department of Health and Human Services (HHS) strict regulations surrounding them, and how to safeguard your company.


    What Does Protected Health Information Include?

    Given how critical safeguarding PHI is, all businesses in and adjacent to the healthcare industry need to understand its importance, why it’s so essential, and how to protect it per HIPAA standards. This blog will break down:

    • Everything protected health information includes and its basic definition
    • How to protect physical and digital PHI per the HIPAA Privacy Rule
    • How the HIPAA Security Rule applies to electronic PHI (ePHI) specifically
    • How the Breach Notification Rule applies to all forms of PHI and ePHI

     

    Personal Health Information Examples and Definition

    The best way to understand what protected health information involves understanding what protected health information includes. The primary examples of PHI are all patients’ medical and payment documents that contain personally identifiable information, such as records of doctor visits, prescriptions, bills, and privileged communications with providers. This includes nearly all patient-related documents stored or processed by covered entities.

    HIPAA applies unilaterally to all businesses in the healthcare field and many other businesses adjacent to it. Covered entities comprise healthcare providers, health plans, and health clearinghouses. Furthermore, the business associates of these parties are also required to be compliant.

    Request a Free Consultation

    Identifiable Characteristics for Protected Health Information

    PHI is health information with personally identifiable information about a patient. If all 18 kinds of personally identifiable data are removed or redacted from a PHI document, it may no longer qualify as PHI under the “safe harbor” provision. The identifying categories include:

    • The names associated with a patient, including first, last, initials, and aliases
    • The location of a patient, including geographical identifiers smaller than a state
    • All essential dates associated with a patient (birth, etc.) other than the year of birth
    • All phone numbers associated with the patient, including home, cell, and work
    • All fax numbers associated with the patient, including home, cell, and work
    • All personal and professional email addresses related to the patient
    • The patient’s social security number and equivalent tax-relevant identifiers
    • The numbers and codes related to all of a patient’s medical records
    • The health insurance beneficiary details related to a patient’s plan
    • The account numbers tied to a patient’s medical and financial accounts
    • All certificate and license numbers related to the patient’s vehicles
    • All vehicle identifiers, such as license plate and vehicle serial numbers
    • All serial or identification numbers associated with a patient’s devices
    • Uniform Resource Locators (URLs) related to a patient’s web presence
    • Internet Protocol (IP) addresses or numbers related to a patient’s devices
    • All biometric identifiers of a patient, such as a finger, retinal, or voiceprints
    • The likeness of a patient, as captured in full-face photographic images
    • All other unique identifying numbers, characteristics, or codes of the patient

    The process of removing all these identifiers is called the de-identification of PHI. Companies can also achieve de-identification via expert determination that the document is not identifiable.


    The HIPAA Privacy Rule: Uses and Disclosures of PHI

    The Privacy Rule within the HIPAA framework applies to all PHI, both physical and digital, and delineates the specific use cases under which parties other than PHI subjects can access PHI. It also guarantees that PHI is accessible by its subjects or representatives, along with select other parties, such as law enforcement.

    Protections under the Privacy Rule may be considered a “whitelist” approach, wherein use cases are disallowed unless otherwise specified. To that effect, the rule’s “basic principles” include that a covered entity may not disclose or use PHI in any way except those defined as permitted or required or as formally requested in writing by the PHI’s subject or representative.


    Rules and Requirements for Privacy Rule Protection of PHI

    The HHS’s Privacy Rule Summary breaks down the following permitted use cases for PHI:

    • Use by, of, or for or disclosure to the individual subject or a designated representative.
    • Uses and disclosures are undertaken for treatment, payment, and healthcare operations.
    • Uses or disclosures for which the subject has been granted an opportunity to consent.
    • Incidental uses or disclosures related to other permitted or required uses or disclosures.
    • Uses or disclosures undertaken in the general public interest or for a public benefit project.
    • Use of a limited data set needed for approved research or public health care operations.

    All permitted uses and disclosures except select required cases, such as to the subject of law enforcement, must also be limited to the minimum necessary extent to avoid breach conditions.


    The HIPAA Privacy Rule: Safeguards for Electronic PHI

    The second prescriptive rule applicable to PHI in the HIPAA framework is the Security Rule. The Security Rule applies to electronic PHI (ePHI) only, unlike the Privacy Rule, which applies to PHI in all formats. The Security Rule resulted from the HITECH Act of 2009, which increased HIPAA’s oversight on electronically generated and processed PHI, along with increases to enforcement penalties.

    In particular, the Security Rule exists to ensure the confidentiality, integrity, and availability of ePHI. It also specifies risk analysis or assessment methods to identify and address credible threats to the Security and Privacy of ePHI and prevent them before they turn into total breaches. It does this by detailing specific safeguards all covered entities must implement.


    Rules and Requirements for the Security of Electronic PHI

    The HHS’s Security Rule Summary breaks down three kinds of safeguards for ePHI security:

    • Administrative safeguards – Controls to guide company-wide procedures:
        • Establishment of security management processes and resources
        • Allocation of security personnel and resources to enforce policy
        • Management of information access for all uses and disclosures
        • Training and assessment of behaviors across all security staff
        • Evaluation of IT and security measures consistent with HIPAA
    • Physical safeguards – Controls for the level of individual spaces and hardware:
        • Restriction of physical access to defined security perimeters
        • Restriction of physical access to individual workstations
    • Technical safeguards – Controls for devices, software, and network infrastructure:
      • Monitoring and restricting access to ePHI in transit or storage
      • Regular auditing and audit logging for privacy and security
      • Visibility and assurance of ePHI integrity (no undue changes)
      • Monitoring and restriction of communications involving ePHI

    These protections ultimately build on the Privacy Rule’s guidance to define parameters for PHI’s safekeeping. If any statute is broken, the PHI will be considered breached.


    Breach Notification for Compromises to PHI or ePHI

    Finally, the last HIPAA rule pertaining to PHI is not a prescription for its protection but a failsafe if compromised. The Breach Notification Rule applies to all PHI and ePHI; it requires covered entities to notify three distinct parties if any element of the Security or Privacy Rule is breached:

    • Individuals impacted by a breach of PHI or ePHI must be notified by the covered entities in writing as soon as possible and within 60 days of the breach’s discovery in all cases.
    • The secretary of the HHS must be notified as soon as possible (within 60 days) in cases impacting 500 or more individuals or within 30 days of year’s end if more are affected.
    • Local media outlets must be notified as soon as possible in cases impacting 500 or more individuals within a defined geographical location serviced by the specific media outlet.

    Failure to meet these requirements does more than compromise PHI. It can also result in civil money penalties or criminal charges, per the Enforcement Rule.


    Safeguard Protected Health Information Professionally

    To avoid non-compliance penalties and other potentially dangerous cybercrime threats, working with a qualified HIPAA compliance advisor can offer an optimal return on investment. There are countless examples of protected health information-related crimes and HIPAA violations that involve well-meaning companies with inadequate staffing or resources. If compliance is a concern for you, contact RSI Security today to see how easy it can be.

    Download Our HIPPA Checklist


  • The Five-Step Process to HITRUST Healthcare Auditing

    The Five-Step Process to HITRUST Healthcare Auditing

    The healthcare industry faces unique security and privacy challenges due to the constant exchange of sensitive patient data. Meeting compliance requirements for regulations like HIPAA, PCI DSS, and SOC 2 can be complex — especially while staying competitive in the marketplace. HITRUST healthcare auditing helps organizations simplify compliance by aligning security controls with multiple regulatory frameworks while strengthening data protection. Through HITRUST assessments, healthcare organizations can demonstrate their commitment to safeguarding protected health information (PHI) and maintaining a strong cybersecurity posture.
    (more…)

  • Q&A: The DoD’s Acquisition and Sustainment CISO Talks Compliance Best Practices

    Q&A: The DoD’s Acquisition and Sustainment CISO Talks Compliance Best Practices

    DoD contractors and vendors must constantly stay one step ahead in the ever-changing compliance landscape. The DoD, along with other U.S. federal agencies, regularly introduces new frameworks and requirements to protect sensitive government and military information.

    For vendors and contractors looking to work with the DoD or U.S. military, compliance isn’t optional,  it’s a critical business necessity. Navigating these requirements can be complex, but understanding them is key to maintaining eligibility and operational security.

    We recently spoke with Katherine Arrington, the DoD’s Chief Information Security Officer (CISO) for Acquisition and Sustainment (A&S), for insights on DoD contractor compliance. Katherine also serves as a former House Representative of South Carolina’s 94th Congressional District and previously held the position of DoD-wide CISO.

    In our conversation, she shared her perspective on new regulatory frameworks like the Cybersecurity Maturity Model Certification (CMMC) the evolving compliance landscape, and practical steps DoD contractors can take to prepare themselves.

    (more…)

  • HITRUST vs. HIPAA: What’s the Difference?

    HITRUST vs. HIPAA: What’s the Difference?

    Enacted in 1996, the Health Insurance Portability and Accountability Act (HIPAA) sets essential rules for protecting the privacy and security of medical information. While HIPAA continues to play a critical role in healthcare compliance, many organizations encounter confusion when comparing it to the Health Information Trust Alliance (HITRUST). HITRUST is often mistakenly thought to be the same as HIPAA. In this article, we’ll break down HITRUST vs HIPAA, explain their differences, and help you understand which framework applies to your organization. (more…)

  • Your CMMC Self-Assessment Checklist

    Your CMMC Self-Assessment Checklist

    Prepare for Certification With Clarity, Not Guesswork

    CMMC 2.0 is reshaping how defense contractors protect sensitive data, and how they demonstrate compliance. For organizations across the Defense Industrial Base (DIB), the pressure to meet evolving requirements is increasing, especially as formal third-party assessments approach. A CMMC self-assessment removes much of the uncertainty from the process. Instead of reacting at the last minute, organizations can proactively evaluate their security posture, understand where they stand against CMMC requirements, and plan remediation with confidence.

    In this guide, we explain how CMMC self-assessments fit into the broader certification process, what they can and cannot accomplish, and how to use them to uncover compliance gaps and accelerate readiness, without confusion or wasted effort. (more…)

  • CMMC Implementation Timeline, Why You Must Act Now

    CMMC Implementation Timeline, Why You Must Act Now

    The CMMC implementation timeline is no longer a distant concern for DoD contractors, it’s an urgent priority. The Department of Defense (DoD) is enforcing cybersecurity requirements through the Cybersecurity Maturity Model Certification (CMMC) 2.0 framework, with all new contracts requiring compliance by 2026. At the same time, the Defense Federal Acquisition Regulation Supplement (DFARS) requires organizations to implement NIST SP 800-171 controls as the baseline for security.

    Delaying CMMC implementation now puts contractors at risk of disqualification from future defense contracts, a risk that will only grow as competition intensifies.

    (more…)

  • What is CUI Basic?

    What is CUI Basic?

    Sensitive information that could affect the safety and security of U.S. citizens is often classified by the federal government. However, not all important data meets the criteria for formal classification. This type of information is known as Controlled Unclassified Information (CUI), and it falls into two categories: CUI Basic and CUI Specified.

    CUI Basic refers to unclassified data that still requires safeguarding and handling practices, even though it is not protected by specific laws or regulations.

    (more…)

  • Top Emerging Security Threats in Healthcare

    Top Emerging Security Threats in Healthcare

    15 percent of all cyber-attacks targeted the healthcare industry in 2020, with most of those threats being malware and ransomware attacks. However, due to technological advancement in the healthcare sector, emerging security threats are on the rise.

    Malicious actors constantly develop complicated methods and tools to infiltrate information systems that affect quality care in the healthcare industry. To prevent a system compromise, you must be aware of the emerging threats peculiar to the healthcare sector.

    Cybersecurity threats are constantly evolving, especially cyber-attacks that affect healthcare systems. Here are the newest, emerging security threats in healthcare and some tactics for guarding against them. (more…)