Folksoft Blog

Building HIPAA Compliance on a Lean Engineering Team: A Practical Framework

Building HIPAA Compliance on a Lean Engineering Team: A Practical Framework
Profile picture of Grishma Managooli
Grishma Managooli

Healthcare data breaches have reached a scale that makes compliance a survival issue, not a checkbox. HIPAA Journal’s 2024 report recorded 725 large healthcare data breaches in its January 28, 2025 snapshot. Its later annual analysis reported that 289,162,330 individuals had their protected health information exposed or impermissibly disclosed during 2024. The Change Healthcare incident alone ultimately affected approximately 192.7 million individuals. For 2025, HIPAA Journal reported 710 large breaches in its February 2026 analysis and at least 61,556,256 affected individuals. These figures are reported as affected individuals, not a count of unique data records; the number of records and the number of people affected are not interchangeable. The totals may change as late reports and updated breach counts are added to the OCR portal. HIPAA Journal’s 2024 Healthcare Data Breach Report and 2025 Healthcare Data Breach Report provide the underlying figures. These numbers represent real liability for your startup and a concrete barrier to hospital procurement.

At Folksoft, we help lean engineering teams scope and implement HIPAA compliance without a dedicated compliance department. The path is tractable when approached in the right order: establish your role, scope your infrastructure to HIPAA-eligible services, complete your Business Associate Agreement (BAA) chain, enforce multi-factor authentication (MFA) at every layer, and run a repeatable annual review cycle.

This article follows that sequence: pre-launch readiness, vendor and infrastructure scoping, and ongoing compliance operations.

1. Know Your HIPAA Role Before Writing a Single Policy

HIPAA divides the healthcare ecosystem into covered entities (hospitals, clinics, health plans, and clearinghouses) and business associates (vendors that create, receive, maintain, or transmit protected health information on behalf of a covered entity). Most healthcare SaaS vendors are business associates, not covered entities.

Your first compliance task is confirming that classification for your product. Business associates are directly liable for compliance with the HIPAA Security Rule, applicable provisions of the Privacy Rule, and relevant obligations under the Breach Notification Rule. These responsibilities include safeguarding ePHI, using and disclosing PHI only as permitted by the BAA and HIPAA, and notifying covered entities when a reportable breach occurs. OCR can investigate and impose penalties on business associates for applicable violations. Knowing your role before writing policies prevents misallocating controls. See the HHS
Business Associates FAQs for an explanation of the provisions that apply directly to business associates.

Map your electronic protected health information (ePHI)

Walk every system your product touches and ask: Can this system receive, store, process, or transmit ePHI? Document the result as a data flow diagram. This map becomes the foundation for every BAA you sign, every AWS service you configure, and every audit log you retain.

Systems that never touch ePHI, such as a marketing analytics tool or a public-facing blog CMS, may fall outside your HIPAA scope, depending on how they are used and what information they receive.

At Folksoft, we start every engagement by building this ePHI map with your team, because scoping errors at this step create the most expensive remediation work downstream.

Protecting patient data requires securing ePHI across healthcare systems, cloud infrastructure, and access points to maintain HIPAA compliance.

2. Restricting ePHI to AWS HIPAA-Eligible Services

AWS supports HIPAA-eligible workloads, but the obligation to configure those workloads correctly falls on you. AWS aligns its HIPAA risk management program with NIST 800-53, which maps to the HIPAA Security Rule. There is no formal HIPAA certification for AWS or any other cloud provider; certification language in vendor marketing does not transfer legal compliance to your application.

The AWS Business Associate Addendum (BAA) is executed through AWS Artifact in the AWS Management Console. You must sign the BAA before storing or processing any ePHI on AWS. The BAA governs only HIPAA-eligible services; processing ePHI on non-eligible services is a compliance gap regardless of whether you hold a signed BAA.

AWS services commonly used in HIPAA-related architectures

Services AWS designates as HIPAA-eligible and relevant to many SaaS stacks include the following:

  • Compute and containers: Amazon EC2, Amazon ECS, Amazon EKS, AWS Fargate (ECS and EKS engines only), and AWS Lambda.
  • Storage and databases: Amazon S3, Amazon RDS (MySQL, PostgreSQL, SQL Server, Oracle, MariaDB, and Db2 engines), Amazon DynamoDB, and Amazon Aurora.
  • Security, identity, and monitoring: AWS KMS, Amazon Cognito, AWS IAM Identity Center, AWS CloudTrail, Amazon CloudWatch, Amazon CloudWatch Logs, and Amazon GuardDuty.

The list is maintained at AWS HIPAA Eligible Services Reference and is updated periodically. Before scoping any new workload to handle ePHI, verify service eligibility and applicable conditions using current AWS documentation and AWS Artifact rather than relying on cached documentation.

The eligible service catalog is substantially longer than the core services listed above. Additional services such as Amazon VPC, AWS Config, AWS Secrets Manager, AWS Security Hub CSPM, and Amazon Inspector may also be relevant to a HIPAA-compliant architecture. Verify the current eligibility status of each service before use.

The practical scoping rule: If a service is not on the eligible list, it must not receive ePHI—not in request parameters, log payloads, or error messages.

HIPAA cloud security starts with protecting ePHI through eligible AWS services, secure infrastructure, and connected safeguards.

This is among the most common compliance gaps in early-stage healthcare SaaS architectures.

Enable AWS Config to track resource configurations continuously. Any new resource deployed to an ePHI-carrying account should be evaluated against your HIPAA baseline before it goes live.

3. Identity and Access Controls

The HIPAA Security Rule requires covered entities and business associates to implement technical safeguards that protect ePHI from unauthorized access. MFA is a high-impact control for lean teams because it helps address credential-based attacks.

Enforce MFA at every layer that can reach ePHI:

  • The AWS root user account, using hardware or virtual MFA.
  • IAM user accounts, with appropriate MFA enforcement.
  • Application-layer access through your Cognito user pool or identity provider.
  • VPN or bastion access to environments that can reach ePHI.

Eliminate long-lived IAM user credentials where possible and use IAM Identity Center instead when appropriate.

Centralize identity with single sign-on (SSO)

Rather than managing credentials in each service independently, deploy SSO through AWS IAM Identity Center or an external identity provider such as Okta, using SAML 2.0 or OIDC.

IAM Identity Center integrates with AWS Organizations and can help centralize access governance. External identity providers can federate into IAM Identity Center when you have multi-cloud or SaaS dependencies. Verify BAA availability and applicable service coverage directly with each provider before finalizing your choice.

Apply least-privilege access

The Security Rule requires appropriate access controls, and the HIPAA minimum necessary standard applies where relevant. Access to ePHI should be limited to what is needed for the intended purpose.

In AWS terms:

  • Avoid wildcard IAM policies on roles that handle ePHI.
  • Use service-specific roles for each Lambda function or ECS task.
  • Conduct regular access reviews to remove stale permissions.
  • Document access decisions and review outcomes.

At Folksoft, we configure role hierarchies that enforce least privilege from day one, so your team is not retrofitting permissions when a hospital security team reviews your access control documentation during procurement.

4. Keeping ePHI and Secrets Out of Source Control

Source control repositories are a persistent, searchable record of everything committed to them. An accidental commit of a patient record or other ePHI can create a serious security and privacy incident that requires prompt investigation. An exposed API key or other credential can also create a security incident, particularly if it could provide access to systems containing ePHI. However, accidental exposure of a credential does not automatically trigger HIPAA breach notification. The organization must investigate what happened, determine whether unsecured PHI was impermissibly accessed, acquired, used, or disclosed, and apply the HIPAA Breach Notification Rule’s requirements—including the applicable risk assessment and any relevant exceptions.

Three rules apply.

1. Never commit ePHI to a repository.

Code review gates, pre-commit hooks, and automated secret-scanning pipelines reduce the risk, but they are not a substitute for developer education and architectural discipline.

2. Store secrets securely.

Secrets and credentials must be stored in appropriate services, such as AWS Secrets Manager or AWS Systems Manager Parameter Store, after verifying the relevant service's HIPAA eligibility and BAA coverage. Hard-coded credentials create significant security risk. Rotate secrets programmatically and audit access through CloudTrail where appropriate.

3. Enforce managed identity for repository access.

Enable organization-level SSO enforcement in your source control platform so that every repository access is tied to a managed identity.

If your source control provider could receive ePHI through pull request descriptions, issue comments, or CI/CD pipeline output, verify whether that provider offers a BAA by checking its Trust or Security portal directly.

5. Support Systems and Vendor BAAs

The BAA requirement extends to third-party systems that receive or maintain ePHI on your behalf, whether intentionally or through user error.

Common gaps include:

  • Helpdesk and ticketing platforms: Support tickets sometimes contain PHI submitted by end users.
  • Error monitoring and application performance monitoring (APM) tools: Stack traces may include ePHI if application code is not carefully structured.
  • Log aggregation platforms: Payloads must be scrubbed of ePHI before export to services that are not appropriately covered.
A HIPAA Business Associate Agreement (BAA) formalizes the responsibilities of healthcare providers and vendors in protecting sensitive patient information.

The BAA chain rule

A BAA between your hospital client and its cloud provider does not cover your infrastructure. You need your own BAA with each vendor that acts as a business associate for your organization and handles ePHI on your behalf.

The safest architecture keeps ePHI within your AWS environment and scrubs log payloads before they reach any external SaaS logging tool. CloudWatch Logs can serve as a primary log store for relevant systems, with sanitized logs forwarded to your preferred SIEM or observability platform. This approach can limit the number of vendors that require separate BAAs.

Before signing a BAA with any vendor, confirm that the agreement covers your specific use case. Generic BAA templates sometimes exclude certain product features or data processing activities. Vendor-specific BAA information is typically available on Trust or Security portals; verify directly rather than relying on third-party summaries.

6. The Ongoing Compliance Cycle

HIPAA compliance is not a one-time certification. It is a continuous operational posture. Three practices define a maintainable cycle for lean teams.

6.1 Security Rule Risk Analysis and Periodic Review

The Security Rule requires covered entities and business associates to conduct a risk analysis of the confidentiality, integrity, and availability of ePHI.

For a SaaS startup, this means:

  • Documenting all ePHI systems.
  • Identifying threats and vulnerabilities.
  • Assessing existing controls.
  • Assigning risk levels.
  • Documenting a remediation plan with owners and timelines.

Annual reviews can help maintain a repeatable compliance cycle, but HIPAA does not prescribe a universal annual-only cadence. Reassess risks when significant infrastructure, operational, or threat changes occur.

6.2 Breach Notification Readiness

As a business associate, your breach notification obligation generally runs to your covered entity clients. Following discovery of a breach of unsecured PHI, you must notify the covered entity without unreasonable delay and no later than 60 calendar days after discovery, subject to the applicable rule. The 60-day period is the federal outer limit, not a recommended response target.

Business associates should also review their contractual notification obligations, as BAAs may require reporting security incidents or breaches within shorter timeframes than the statutory maximum. Check the BAA for the events that must be reported, the required notification channel, and the information that must be provided.

The covered entity is generally responsible for notifying affected individuals and OCR as required under the Breach Notification Rule, although the BAA may delegate certain notification tasks to the business associate. See the HHS Breach Notification Rule for the federal requirements.

Test your internal breach identification and notification procedure regularly. A tabletop drill with engineering and legal stakeholders can help a lean team assess its readiness. Document the drill, findings, and follow-up actions so you can demonstrate that the procedure is operational rather than merely written.

6.3 Continuous Drift Detection

AWS Config rules and AWS Security Hub CSPM can help evaluate your environment against security baselines.

Config rules can flag non-compliant resources, such as:

  • Unencrypted S3 buckets.
  • Missing CloudTrail logging.
  • Overly permissive security group rules.

Security Hub can aggregate findings from services such as GuardDuty, Inspector, and Config into a central dashboard. Verify the current eligibility and configuration requirements for the AWS services used in your environment.

NIST SP 800-53 can support security control mapping, but the precise mapping to HIPAA requirements should be documented and reviewed for your environment.

Document retention

HIPAA generally requires specified compliance documentation to be retained for six years from its creation date or the date it was last in effect, whichever is later. This does not automatically mean every audit log or every record containing PHI has the same HIPAA retention period.

Establish retention schedules based on the applicable requirements, contractual obligations, state laws, and operational needs. Configure CloudTrail and CloudWatch Logs retention policies to support those requirements before going live with any ePHI workload.

Frequently Asked Questions

If our SaaS customers have their own AWS BAA, do we still need one for our account?

Yes. Your customers' BAAs cover their own arrangements with AWS and do not automatically cover your organization's AWS account. If your organization uses AWS to create, receive, maintain, or transmit ePHI on behalf of covered entities, you need an appropriate BAA with AWS. Execute the applicable agreement through AWS Artifact before using AWS for ePHI workloads.

What is the best identity provider for a small team?

AWS IAM Identity Center is a strong fit for teams whose infrastructure is primarily AWS-native. It supports centralized access management and integrates with AWS Organizations. Okta may be suitable for teams with multi-cloud infrastructure or a need to manage access across non-AWS SaaS systems.

Evaluate MFA enforcement, centralized access reviews, integrations, and BAA availability directly with each provider before finalizing your choice.

How long must HIPAA audit logs be retained?

HIPAA requires specified documentation to be retained for six years from the date of creation or the date it was last in effect, whichever is later. Not every audit log automatically falls under the same retention rule. Determine the applicable requirements for each log type and configure retention policies accordingly.

Conclusion

For lean engineering teams, HIPAA compliance is most tractable when approached as a sequence: map your ePHI, complete your BAA chain, restrict infrastructure to AWS HIPAA-eligible services, enforce MFA and least-privilege access, and run a repeatable risk and breach-readiness cycle.

No single vendor delivers compliance on its own. It is assembled from controls across your infrastructure, identity, source control, and vendor relationships.

The breach landscape makes this work urgent. HIPAA Journal’s annual reports recorded 289,162,330 individuals affected in 2024 and at least 61,556,256 in 2025. These figures show why healthcare organizations expect vendors to demonstrate that they can protect ePHI, respond to incidents, and maintain documented compliance practices. Hospitals and health systems increasingly assess these capabilities as part of vendor due diligence and procurement.

At Folksoft, we scope which systems in your stack need BAAs, audit logging, and MFA enforcement, and help build a compliance cycle your team can maintain without a dedicated compliance officer.

Visit Folksoft to scope your stack to HIPAA requirements.

Sources

Ready to get started?

See how Folksoft can help your business

Book a Demo

More Stories

Best Delve Alternatives for Startups in 2026

Best Delve Alternatives for Startups in 2026

Navigating SOC 2 and security compliance in 2026 shouldn't mean dumping endless manual tasks onto your engineering team. While Delve offers fast AI-driven evidence gathering, many early-stage startups quickly hit friction with limited integrations, passive alerts, and a lack of active remediation. Discover the top 5 Delve alternatives—including Folksoft, Vanta, Drata, Sprinto, and Secureframe—and learn how to choose the right compliance platform for your startup's specific growth stage, technical stack, and operational bandwidth.

Profile picture of Grishma Managooli
Grishma Managooli
One Control Library, Two Frameworks: The Series A Approach to ISO 27001 and SOC 2

One Control Library, Two Frameworks: The Series A Approach to ISO 27001 and SOC 2

Learn how to achieve ISO 27001 and SOC 2 compliance together without duplicating work. Discover how SaaS companies can build a unified control library, manage shared security evidence, coordinate audit timelines, and address framework-specific requirements. Explore practical steps to simplify compliance preparation, strengthen information security, and support enterprise sales with a coordinated compliance programme.

Profile picture of Grishma Managooli
Grishma Managooli