HIPAA
HIPAA-ready remote support
Silux Connect supports covered entities and business associates under HIPAA. Sign a BAA in minutes — DocuSign or wet-signed, your choice.
Who needs a BAA?
- Covered entities: hospitals, clinics, payers, practitioners. If you create, receive, maintain, or transmit PHI through Silux Connect, you need one.
- Business associates: MSPs and IT teams who support a covered entity through Silux Connect. We can also sign sub-BAAs.
- If your use of Silux Connect cannot involve PHI (for example, you support a non-clinical office network), you don't need one.
Scope of PHI we may process
- Screen content during a remote-support session (PHI may be visible on the technician's view).
- Files transferred during a session (when used by your staff).
- Audit-log entries describing who connected to whom and when.
- Optional session recordings — saved on the technician's own computer, never on Silux servers.
Silux acts as a conduit for screen and file traffic; the relay sees ciphertext only. Recordings (if enabled) are stored encrypted and subject to your retention policy.
HIPAA-eligible AWS services we use
All PHI-handling components run in the US region (us-east-1) on services covered by the AWS BAA.
Amazon EKS
Amazon EC2
Amazon RDS for PostgreSQL
Amazon S3
AWS KMS
Amazon ElastiCache (Redis)
AWS Secrets Manager
Amazon CloudWatch
AWS CloudTrail
Amazon VPC
AWS WAF
AWS Shield Advanced
Amazon Route 53
AWS Backup
AWS PrivateLink
Source: AWS HIPAA-eligible services list. We do not route PHI to services that are not on the AWS BAA.
Request a BAA
We countersign within one business day.
Quiet confidence at the audit.
Our HIPAA program is documented, tested, and ready for your auditor. Visit the Trust Center for the full stack.