Skip to main content
CMDashCybersecurity Maturity Dashboard
← Okta
Identity & Access · Privacy & Sector Regulation

Okta for HIPAA Security Rule

What Okta’s data evidences toward HIPAA Security Rule today, and how to connect it.

  • MFA & identity coverage feeds Technical Safeguards

This is where Okta’s data is documented as relevant on our HIPAA Security Rule page — not a pre-built, automatic control mapping. You configure which controls it maps to inside CMDash.

MFA enrolment and factor coverage, suspicious sign-in events, and the SaaS app catalog — the broadest identity signal cmdash ingests.

Read the Okta setup guide →

Administrative, physical and technical safeguards under 45 CFR 164, with verbatim public-domain text.

§ 164.308, § 164.310 and § 164.312 only. § 164.314 (organizational requirements) and § 164.316 (policies, procedures and documentation) are not seeded.

Read the full HIPAA Security Rule page →

Okta for HIPAA Security Rule — CMDash