August 25, 2021

One of the biggest issues for many companies is ensuring compliance. This work becomes easier with identity and access management (IAM) software. IAM allows administrators to specify strict access protocols to control which networks and resources users can use and how they can use them. In short, the software provides visibility into and governance over what employees can and cannot do.

Let’s look closely at four different compliance requirements—SOX, HIPAA, HITECH, and PCI—to evaluate how IAM simplifies compliance.

businessman hand working with modern technology and digital layer effect as business strategy conceptSOX Compliance and IAM

In 2002, following financial scandals, the Sarbanes-Oxley Act, called Sarbox or SOX for short, was enacted into law. Its aim was to improve investor confidence by making corporate practices more transparent. Among others, requirements include measures for:

  • Policy enforcement

  • Risk assessment

  • Fraud reduction

  • Compliance auditing

SOX security standards call for internal controls that are tested and documented to be in place for preparing financial reports and for protecting the data integrity of the accounting information going into these reports.

IAM solutions that address SOX compliance requirements include:

  • Centralization administration of access management and identity governance.

  • Enforcement of segregation of duties (SoD) policies.

  • Regular auditing to verify user rights and permissions across the infrastructure

  • Automatic logging and tracking tools that generate clear reports for compliance audits

SOX addresses both physical and digital records making IAM an integral part of compliance, but the key to aligning with SOX requirements is the ability to produce on-demand evidence for an audit. By automating IAM activities including user provisioning and de-provisioning, granular conditional access controls, and implementing accurate access logging and usage tracking companies improve their security posture and reduce the risk of data breaches.

HIPAA Compliance and IAM

HIPAA, the Health Insurance Portability and Accountability Act, was enacted in 1996. One of its goals was to establish national standards governing the privacy of protected health information. Among other functions, the law is intended to strike a balance between individual needs for privacy and the need for medical professionals to share health information to safeguard the patient and the public. Readers may be familiar with consent forms and other documents deriving partially from HIPAA standards.

IAM can make it much easier for organizations to ensure HIPAA compliance. For example, identities based on informed consent categories, such as those who have opted in versus those who have opted out, maybe enforced strongly. If a patient opts out of sharing information from one medical professional with another, the organization can be confident the latter professional will be denied access to the restricted data.

IAM can also implement policies like that across a wide span of diverse systems. That reassures executives that compliance will take place despite the variety of information technology in use. Okta’s HIPAA-compliant cell is specifically designed to meet HIPAA requirements for service providers.

HITECH Compliance and IAM

The Health Information Technology for Economic and Clinical Health Act (HITECH) is often discussed in the same breath as HIPAA, but it is a different set of requirements. HITECH was enacted into law in 2009 as part of the economic stimulus bill. One of its purposes was launching public investment in a nationwide network of electronic health records (EHRs). 

Among other measures, HITECH mandates federal breach notification for stored health information that is not encrypted. In addition, HITECH extended certain HIPAA requirements beyond entities that were covered in the past—payors, providers, and clearinghouses—to their business partners.

What does all this mean for IAM?

One advantage IAM offers here is that the software can supply identity federation. Access doesn’t have to exist only within a single organization; it can be federated outside the boundaries of an organization to permit secure access to electronic health records by more than one group. This helps with HITECH’s extended requirements. An IAM solution capable of satisfying HITECH precautions will include identity federation and single sign-on to enable scalable and secure user authentication throughout the environment. This supports enforcement of authentication policies to ensure that only the right people have access to the right resources and information

PCI

PCI is short for PCI DSS, or the Payment Card Industry Data Security Standard. Unlike the above compliance standards, PCI does not arise from government law. It is a proprietary information security standard for companies that manage major credit cards. Full compliance means companies encrypt payment card data in transmission, submit to penetration testing, and more. PCI does not mandate specific technologies but explains industry best practices.

IAM software can help achieve PCI compliance by maintaining the privacy of payment card data. For instance, there are certain PCI requirements about limiting the number of employees who can access payment card data to the absolute minimum who need to know this information. And of course, IAM shines here. It can ensure, for example, that privileged users are granted only the fewest privileges necessary to complete their work. That prevents unnecessary escalations of privilege that can result in privacy violations.

The IAM solution here should ensure that each user has a unique ID and that the cardholder data available across the apps, APIs, and URLs is accessible to only those who have appropriate authorization. This is an IAM solution, with Data Governance. MFA is a requirement for accessing the cardholder data environment. The IAM solution can also manage the secure sharing and protection of the cardholder data stored in the directory. Finally, all privilege accounts in a cardholder environment should be maintained with caution and all access to the cardholder environment should be logged. This bodes well for a PAM solution, that is also part of an IAM program.

Identity and Access Management (IAM) for Compliance

Whether your organization needs to ensure compliance with any of the four regulations described above or with other standards specific to your industry, identity and access management solutions can simplify the task by providing better governance over users’ identity and what they can and cannot access on the organization’s networks. With the right IAM solution, your organization can maintain secure, audited infrastructure and processes that keep your organization’s service highly secure and available to assist in your compliance initiatives.

Download our Compliance IAM Mapping Matrix to see how IAM solutions can help ensure compliance for your organization. 

Matrix: Compliance IAM Mapping

Identity + Access Management Identity Governance + Administration IAM Consulting Security Compliance

August 13, 2021
You may have noticed in the technology world that we use acronyms a lot. It’s a bit of a running joke in the industry

Identity + Access Management

July 31, 2019
How can you raise cybersecurity awareness within your organization? The cybercrime wave that has been the hot topic

Identity + Access Management IAM Design

October 14, 2021
Identity and access management (IAM) is one pillar of a modern and distributed workforce. As important as it is for