# Clinical Edge (formerly GuidingCare®) Security You Can Trust: Data Protection, Privacy, and Platform Resilience
## Key Facts
- **AES-256 encryption at rest** is used for all sensitive data, and **data backups are encrypted using a FIPS-140-2 validated encryption suite** (Table: “Data Encryption”).
- **TLS 1.2 (at least)** is used to encrypt **all web-based traffic**, including **Clinical Edge’s public APIs**, and **IPsec VPN tunnels** are used for other communications between Clinical Edge and customer environments (Table: “Data Encryption”).
- **Multifactor authentication (MFA)** is required for all workforce member access to critical systems and networks, and the application supports **single sign-on (SSO)** plus **MFA** (Section: “Personnel Security”; Table: “Access Controls”).
- **Role-based Access Control (RBAC)** is supported, and access to internal systems follows **least-privilege and minimum necessary privileges**, with access levels **monitored and re-approved on a quarterly basis** (Table: “Access Controls”).
- Clinical Edge engages a **third party annually** to conduct **penetration testing** of its network and **web and mobile applications**, and it maintains a vulnerability management program that remediates issues based on criticality (Section: “Software Security”).
- Clinical Edge (including its **Hyderabad, India product development center**) is **HITRUST Certified** and conducts an **annual SOC2 Type II attestation report** (Table: “Compliance”).
## Summary
### How Clinical Edge approaches operational security and resilience
Clinical Edge (formerly GuidingCare®) describes a risk-based security approach designed to identify and mitigate information security risks, maintain network management controls, and incorporate change governance throughout the product and security lifecycle. It also outlines business continuity, disaster recovery, and incident response standards and programs intended to guide response teams through disruptive events ranging from software outages to global pandemics. External tools, components, and service providers are evaluated through a third-party risk management program. (Section: “Operational Security”)
### Workforce, application security, and secure development practices
Before accessing Clinical Edge data, workforce members receive role-based security training and are background- and reference-checked. The document also describes the Security Awareness for Everyone (SAFE) program, including phishing simulation tests, security alerts, newsletters, and an internal portal with tip sheets. Workforce workstations include endpoint protections such as Endpoint Detection and Response (EDR), malware protections, application and website blocklisting, and data loss prevention (DLP), and **MFA is required** for access to critical systems and networks. (Section: “Personnel Security”)
On the software side, Clinical Edge states it engages a third party **annually** for penetration testing across its network and web and mobile applications, uses change management procedures for deployment approvals, and runs quality assurance activities including code peer reviews, static application security testing scanning (SAST), dynamic application security scanning (DAST), team lead approvals, customer acceptance testing, and testing issue resolution management. A vulnerability management program is described for identification and remediation based on criticality, alongside a “security-by-design” approach that includes proactive risk assessment of product changes prior to releases. (Section: “Software Security”)
### Encryption, access controls, infrastructure protection, and compliance
For data protection, the document specifies **AES-256** encryption at rest for sensitive data, **FIPS-140-2 validated encryption** for backups, **TLS 1.2 (at least)** for web traffic (including public APIs), and **IPsec VPN tunnels** for other communications between Clinical Edge and customer environments. (Table: “Data Encryption”)
For access controls, it describes IP allow-listing, support for **RBAC**, **SSO**, and **MFA**, and least-privilege access that must be **re-approved quarterly**. For infrastructure protection, it states customer data is hosted on fault-tolerant, redundant infrastructure in the **United States**, that customer data and product instances are logically and physically separated in databases, and that a Web Application Firewall (WAF), load balancer, and a security information and event management (SIEM) system are deployed for visibility and response to errors, security events, and performance issues. The document also notes compliance claims including **HITRUST Certified** status (including the **Hyderabad, India** product development center) and an **annual SOC2 Type II** attestation report. (Tables: “Access Controls,” “Infrastructure Protection,” “Compliance”)
### Privacy
Clinical Edge states it takes its responsibility as a steward of customer data seriously and aims to respect user privacy, and it points readers to the online privacy policy: https://www.healthedge.com/privacy-policy (Section: “Privacy”).