Security Monitoring and Incident Response
Monitoring
LabLynx conducts regular security assessments, security audits, and internal risk assessments of the information systems. The company also finds potential risks posed to the information system from external parties (e.g., service providers, contractors operating information systems on behalf of the organization, individuals accessing organizational information systems, and outsourcing entities). LabLynx conducts regular vulnerability assessments of the information systems. LabLynx employs vulnerability scanning tools that allow the list of vulnerabilities tested to be automatically updated.
We monitor for unauthorized personnel, connections, devices, and software using Alienvault USM that tracks logins and connections. The LIMS also provides successful and failed login information. Asset reviews are done every 30 days. AlienVault USM SIEM agents scan for vulnerabilities on all systems at least once per week. There are no wireless networks associated with the sensitive networks. A variety of periodic audits, including remote access, are performed.
Incident Response
Our formal incident response policy and procedures are as follows: An Incident Response Team quickly reacts to computer-related incidents such as virus infections, hacker attempts, break-ins, unauthorized disclosure of confidential information, system service interruptions, breaches of personal information, and other security events. The Incident Response Team subscribes to various security industry alert services to keep abreast of relevant threats , vulnerabilities, or alerts from actual incidents.
DevOps will serve as a central point of contact for reporting any suspected or confirmed breach of personal information on an individual. After documenting the facts presented and verifying a suspected privacy breach occurred, DevOps will open a Priority Incident Request.
Clients are provided help desk accounts, for which all ticket creation and updates are emailed to the clients. We may also directly call, or email outside of the ticketing system, if the situation warrants.