Third Party Security, Vendor Risk Management and Systems/Services Acquisition

2021.1

LifeOmic makes every effort to assure all third party organizations are compliant and do not compromise the integrity, security, and privacy of LifeOmic or LifeOmic Customer data. Third Parties include Vendors, Customers, Partners, Subcontractors, and Contracted Developers.

Policy Statements

LifeOmic policy requires that:

(a) A list of approved vendors/partners must be maintained and reviewed annually.

(b) Approval from management, procurement and security must be in place prior to onboarding any new vendor or contractor. Additionally, all changes to existing contract agreements must be reviewed and approved prior to implementation.

(c) A standard HIPAA Business Associate Agreement (BAA) is defined and includes the required security controls in accordance with the organization’s security policies. Additionally, responsibility is assigned in these agreements. A BAA must be signed with any vendor that may have a business need to access, and/or unsupervised access to PHI or ePHI.

(d) For any technology solution that needs to be integrated with LifeOmic production environment or operations, a Vendor Technology Review must be performed by the security team to understand and approve the risk. Periodic compliance assessment and SLA review may be required.

(f) LifeOmic Customers or Partners should not be allowed access outside of their own environment, meaning they cannot access, modify, or delete any data belonging to other 3rd parties.

Controls and Procedures

Vendor Technology Risk Review

LifeOmic security policy requires a risk review of vendor technology, prior to any technology being integrated to LifeOmic operations and/or infrastructure. Employees are required to engage security team to conduct such review. The request may be submitted by email directly to the security team, or by opening a Jira ticket through the LifeOmic internal service desk.

Security team is responsible to conduct the reviews via interviews and reviews of documentation, to ensure the vendor complies with regulatory requirements such as HIPAA and follows security best practices to minimize risk to an acceptable level.

A vendor technology risk (VTR) assessment is conducted using Google VSAQ, in the following steps:

  1. Reviewer sends questionnaire link(s) to vendor contact.
  2. Vendor completes the questionnaire(s).
  3. Vendor saves/exports answers to the assessment questionnaire(s).
  4. Vendor contact sends the answers file back to reviewer.
  5. Reviewer opens the same questionnaire(s) and loads the answers received from the vendor to complete the assessment.
  6. Reviewer follows up with vendor contact as needed.
  7. Reviewer facilities discussion with business owner to determine if the risk is acceptable. Vendor remediation may be required depending on the results.

A list of approved vendors / contractors is maintained by the Security and Operations teams.

Vendor Contractual Agreements

HIPAA. If the vendor needs access to PHI/ePHI, the vendor must be HIPAA compliant and a Business Associate Agreement (BAA) is required.

GDPR. If the vendor processes data for customers from in the European Economic Area, United Kingdom or Switzerland (the “Designated Countries”), the vendor must be GDPR compliance and a Data Processing Agreement (DPA) is required.

SLA for Service Providers. For network and infrastructure service providers that support production and/or critical operations at LifeOmic, a Service Level Agreement (SLA) is defined and included in the service contract.

As appropriate, the executed agreement(s) are linked or attached to the vendor on the approved vendors list

Monitoring Vendor Risks

Vendor contracts are reviewed either annually or according to the signed contract duration.

Based on the risk level and the sensitivity/criticality of data the vendor has access to, the vendor review may include an updated risk analysis performed by the security team in addition to legal and business review of contract terms.

Vendor Risk and Criticality Scoring

The below scoring is used to help understand Vendor risks and business criticality better. By using a scoring method such as 1-3-9 we can reliably understand which of our vendors are more risky and which vendors we rely heavily on. This can help teams reduce reliance on single vendors, as well as implement solutions to reduce dependency and implement controls on high-risk vendors.

Risk

  1. This vendor hosts no sensitive data and has no critical findings in a vendor review.
  2. This vendor hosts 1 of the three sensitive data tag (PHI, PII, PCI), or has no sensitive data but does have a critical finding in a vendor review.
  3. This vendor hosts 2 of the three sensitive data tag (PHI, PII, PCI), or hosts 1 sensitive data tags and has a critical finding.
  4. This vendor hosts 3 of the three sensitive data tag (PHI, PII, PCI), or hosts 2 sensitive data tags and has a critical finding.

Criticality:

  1. LifeOmic considers this to be a ‘quality of life’ vendor. If we had to stop using this vendor no noticeable impact would occur.
  2. LifeOmic uses this vendor in it’s daily operations, but could find a replacement quickly and without disruptions to customers or SLA’s.
  3. LifeOmic would be challenged to perform basic functionality without this vendor. Any changes in operations with this vendor will require strict review by the Security Team.
  4. LifeOmic Cannot operate without this vendor. If this vendor went out of business tomorrow we would follow suit soon after.

If the vendor is a service provider, the DevOps team monitors the service status of the provider according to its SLA. This is done by either manually reviewing the posted service status on the vendor’s status pages at least quarterly, or by setting up alarms for service interruption using automation.

Software and Systems Acquisition Process

LifeOmic Security maintains a list of pre-approved business software and a list of approved vendors / contractors.

If additional commercial software, hardware system, or cloud services is needed, a request should be submitted through LifeOmic internal service desk. This will trigger the approval by manager/security and procurement process.

As applicable, LifeOmic security team may conduct a risk analysis on the software or system to ensure it complies with LifeOmic security, compliance and legal requirements and does not interfere with the security controls. If a risk is identified, additional controls should be identified and implemented (or planned) prior to acquisition. An alternative product may be considered as a result of the risk analysis.