Security and Privacy at Fourier Health

Last Updated: August 15th, 2024

Governance

Fourier’s Security and Privacy teams establish policies and controls, monitor compliance with those controls, and prove our security and compliance to third-party auditors.

Data Protection

Data at Rest

  • All datastores with customer data, in addition to S3 buckets, are encrypted at rest. This means the data is encrypted even before it hits the database so that neither physical access, nor logical access to the database, is enough to read the most sensitive information.

Data in Transit

  • Fourier uses TLS 1.2 or higher everywhere data is transmitted over potentially insecure networks. We also use features such as HSTS (HTTP Strict Transport Security) to maximize the security of our data in transit. Server TLS keys and certificates are managed by AWS and deployed via Application Load Balancers.

Secret Management

  • Encryption keys are managed via AWS Key Management System (KMS). KMS stores key material in Hardware Security Modules (HSMs), which prevents direct access by any individuals, including employees of Amazon and Vanta. The keys stored in HSMs are used for encryption and decryption via Amazon’s KMS APIs.

    Application secrets are encrypted and stored securely via AWS Secrets Manager and Parameter Store, and access to these values is strictly limited.
  • Product Security

    Fourier engages with one of the best penetration testing consulting firms in the industry at least annually. Our current preferred penetration testing partner is Cobalt.

    All areas of the Fourier product and cloud infrastructure are in-scope for these assessments, and source code is fully available to the testers in order to maximize the effectiveness and coverage.

    Vulnerability Scanning

    Fourier requires vulnerability scanning at key stages of our Secure Development Lifecycle (SDLC):

    • Static analysis (SAST) testing of code during pull requests and on an ongoing basis
    • Software composition analysis (SCA) to identify known vulnerabilities in our software supply chain
    • Malicious dependency scanning to prevent the introduction of malware into our software supply chain
    • Dynamic analysis (DAST) of running applications
    • Network vulnerability scanning on a period basis
    • External attack surface management (EASM) continuously running to discover new external-facing assets