# HIPAA 164.306(a) — General Requirements

- Source: https://support.icompaas.com/support/solutions/articles/a_gen_hipaa_164306a_19b2b07b49-hipaa-164306a-general-requirements
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [HIPAA Readiness](https://support.icompaas.com/support/solutions/62000039493) › [Security Rule](https://support.icompaas.com/support/solutions/folders/f_gen_62000039493_securityrule)
- Last updated: 2026-05-30
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

HIPAA · Control 164.306(a) · Priority: medium · Component: Security Rule

### What this control covers

Covered entities and business associates must do the following: (1) Ensure the confidentiality, integrity, and availability of all electronic protected health information the covered entity or business associate creates, receives, maintains, or transmits. (2) Protect against any reasonably anticipated threats or hazards to the security or integrity of such information. (3) Protect against any reasonably anticipated uses or disclosures of such information that are not permitted or required under subpart E of this part; and (4) Ensure compliance with this subpart by its workforce.

### Why it matters

Risk is the language an executive team understands; this control connects technical reality to board-level decisions and budget allocation.

### How to implement

#### AWS

Codify the policy intent as **SCPs, AWS Config conformance packs, and Security Hub standards** so the cloud enforces what the document says.

#### Azure

Codify in **Azure Policy initiatives** (built-in regulatory compliance for CIS, ISO 27001, SOC 2, HIPAA) and assign at management-group level.

#### On-premises

Maintain a policy library with a documented review cadence (annual minimum); store in your GRC tool with attestation tracking. Map each policy to controls so an audit pull cites the exact policy clause.

### Evidence to collect

-   `policy_document` — A signed, version-controlled policy stating leadership intent and the named owner.

Signed policy or standard documents the safeguard. Focus: General Requirements.

### Quick checklist

-   General — Requirements / Security
-   Security — Requirements / Security
-   Workforce — Requirements / Security
-   Information — Requirements / Security
-   Business — Requirements / Security
-   Integrity — Requirements / Security

### Related articles on this site

-   [164.312(c)(2) - Mechanism to authenticate electronic protected health information](https://support.icompaas.com/support/solutions/articles/62000230567-164-312-c-2-mechanism-to-authenticate-electronic-protected-health-information)
-   [Ensure IAM password policy requires at least one uppercase letter](https://support.icompaas.com/support/solutions/articles/62000080729-ensure-iam-password-policy-requires-at-least-one-uppercase-letter)
-   [Ensure IAM password policy require at least one lowercase letter](https://support.icompaas.com/support/solutions/articles/62000080758-ensure-iam-password-policy-require-at-least-one-lowercase-letter)
-   [Ensure IAM password policy require at least one symbol](https://support.icompaas.com/support/solutions/articles/62000080773-ensure-iam-password-policy-require-at-least-one-symbol)

## Related compliance guidance

- [HIPAA compliance for SaaS: a practical implementation guide](https://support.icompaas.com/compliance/hipaa): The Security Rule safeguards this readiness item belongs to, with a phased implementation roadmap and the evidence OCR expects.
- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Most healthcare customers ask for a SOC 2 report alongside HIPAA assurances; the two share most technical controls.