Structured access approvals
New privileges follow a formal approval process, apply least privilege, and require endorsement by an authorized employee.
VirelaGet in touch Trust by design
63 safeguards
Our security program supports HIPAA- and PHIPA-compliant deployments through access governance, encryption, operational resilience, continuous monitoring, workforce controls, and ongoing risk management.
New privileges follow a formal approval process, apply least privilege, and require endorsement by an authorized employee.
Access to sensitive information requires a submitted, approved, and monitored request.
Access to sensitive infrastructure requires documented approval and ongoing oversight.
Privileges are reviewed and removed promptly when a workforce member no longer needs them.
Accounts on critical and high-risk services are inventoried with owners, roles, privileges, and vendor relationships, and reviewed at least annually.
Administrative access to critical systems requires multi-factor authentication unless a documented technical exception applies.
Externally exposed enterprise and third-party applications enforce MFA where supported, including through SSO.
Sensitive infrastructure requires multi-factor authentication in addition to primary credentials.
Technical controls and monitoring reinforce password requirements and address non-compliance.
Password requirements mandate strong credentials and prevent reuse of previous passwords.
Sensitive information is encrypted while stored on systems and devices.
Information is encrypted while moving across internal and external networks.
Data assets are cataloged across databases, file shares, and cloud storage.
Information is labeled by classification so the appropriate access and handling safeguards can be applied.
Documented requirements govern how information is retained, managed, and disposed of throughout its lifecycle.
Automated backups protect high-risk information and critical systems.
A documented business continuity and disaster recovery policy guides response to disruptive events.
Recovery procedures address data loss, corruption, and system failure.
Disaster recovery plans are tested regularly and improved based on results.
Recovery copies are separated from production to reduce the risk of accidental overwrite or corruption.
DMARC policy and verification mechanisms help prevent domain spoofing and phishing.
Administrative access to email accounts is limited and is not delegated to unauthorized users.
Email controls block or quarantine malicious attachments, links, scripts, and other harmful content.
Anti-malware protection is deployed on laptops, workstations, and other end-user devices.
Inactive sessions lock automatically to protect unattended devices.
Information stored on laptops and mobile devices is encrypted against loss or theft.
Host firewalls are enabled and maintained on workstations and laptops.
A device-management platform applies and monitors security requirements on end-user devices.
Unapproved software is removed or covered by a documented exception, with compliance reviewed at least monthly based on risk.
Appropriate anti-malware protection is deployed on servers and infrastructure components.
Cloud storage is not publicly exposed without a documented business justification.
Firewall rules limit public access to infrastructure components.
Changes to critical infrastructure are recorded for accountability, investigation, and auditability.
Network devices receive current security patches and firmware updates.
Periodic asset reviews identify and address unauthorized infrastructure.
Production database access uses individual credentials or uniquely attributable keys.
VPN connections provide encrypted and authenticated access over untrusted networks.
A WAF helps protect applications against injection, cross-site scripting, and other application-layer attacks.
Audit-log capacity supports the required retention period and historical investigation.
Documented processes govern log collection, storage, protection, review, and monitoring.
Critical systems and applications capture security events for detection and investigation.
Documented procedures support detection, assessment, escalation, and required reporting of breaches.
A formal policy governs how security incidents are detected, contained, investigated, and recovered from.
Devices and systems capable of storing or processing information are inventoried and kept current.
A documented policy governs assets throughout acquisition, use, reassignment, and disposal.
Departing workforce members are promptly removed from relevant systems and accounts.
New workforce members receive only the access required for their responsibilities.
Facilities, equipment, and systems are limited to authorized personnel.
Documented requirements protect facilities and physical assets.
A sanctions policy establishes consequences for violations of security policies and procedures.
The workforce receives annual training on cyber threats, social engineering, authentication, and safe data handling.
A designated security official oversees safeguards, policies, and incident-response responsibilities.
Vendor agreements define security responsibilities, expectations, and service commitments.
A documented policy governs appropriate workstation use and protection against unauthorized access.
Risk assessments are performed at least annually to identify threats and vulnerabilities affecting company assets.
Vendor records include services provided, contract details, and the scope of system or data access.
A documented program assesses, monitors, and manages third-party security and compliance risk.
Vendors are classified according to the sensitivity of the information they handle.
Vendors are prioritized by risk to guide assessment depth, review frequency, and required safeguards.
Findings from penetration testing are tracked and remediated promptly.
Systems, applications, and infrastructure undergo penetration testing at least every 12 months.
Automated scans regularly evaluate infrastructure, applications, and code repositories for known weaknesses.
A documented policy defines how vulnerabilities are identified, assessed, prioritized, and remediated.