Table of Contents
EHS software security matters because safety records can contain employee identities, injury details, medical information, investigation statements, photographs, and commercially sensitive operational data. A convenient cloud platform can organize those records, but convenience alone says little about how access is controlled or how information is protected.
A useful security review connects the vendor’s controls to your actual workflows. Who uploads information? Who can see it? What happens if an account is compromised or a service becomes unavailable? Use the following questions to build an evidence-based discussion with EHS, IT, privacy, and procurement before uploading sensitive records.
1. What Information Will the Platform Hold?
Start with a data inventory rather than a generic questionnaire. Identify the categories of information, the people involved, and the business purpose for storing them. Separate routine inspection observations from restricted occupational health records. The level of sensitivity should influence access design, review depth, and contractual requirements.
Also decide what does not need to be collected. A hazard report may not require a worker’s personal address or full medical history. Reducing unnecessary collection makes the workflow easier to manage and limits exposure. Review the occupational health tracking overview when deciding which health-related information needs a separate access path.
2. Who Can Access Each Type of Record?
Ask the vendor to demonstrate permissions using real roles: a reporting worker, supervisor, investigator, occupational health specialist, and system administrator. Verify access to individual records, attachments, dashboards, searches, and exports. Restricting a screen is insufficient if the same information remains available through a report.
Define access by job responsibility and location where appropriate. Test whether a manager can view a sensitive case outside the manager’s assigned scope. Include temporary users and contractors in the demonstration. Request evidence of how permissions are reviewed and how access changes are documented.
3. How Are Users Authenticated?
Check support for your identity provider, single sign-on, and multifactor authentication. Ask whether these protections apply to administrators, ordinary users, support personnel, and mobile access. CISA recommends multifactor authentication to strengthen account protection. The practical purchasing question is whether the vendor supports the controls your IT team intends to enforce.
Furthermore, test how the system handles account recovery. A secure login process can be weakened by a poorly controlled reset procedure. Ask how lost devices, changed phone numbers, and emergency administrator access are handled. Document the customer responsibilities rather than assuming the vendor controls every authentication setting.
4. What Happens When Someone Changes Roles or Leaves?
Access should follow employment and responsibility changes. Ask how quickly a departure removes active access and whether transfers update site permissions. Confirm that removing an account does not erase historical attribution from investigations, approvals, or training records.
Also examine shared accounts. They make it harder to determine who performed an action and complicate access removal. Where shared devices are necessary, evaluate individual authentication and session controls. Assign responsibility for periodic access reviews so account cleanup continues after the implementation project ends.
5. How Is Information Protected in Transit and Storage?
Request a clear explanation of encryption for data sent between devices and services and for stored records. Ask whether protection covers attachments, backups, exports, and integration traffic. Have IT review the technical details and key-management arrangements instead of accepting a marketing phrase as sufficient evidence.
Encryption is one control within a larger security design. It does not prevent an authorized user from downloading an inappropriate report or resolve excessively broad permissions. Evaluate how the platform limits access and supports monitoring alongside its encryption claims.
6. Where Is Data Stored and Who Else Processes It?
Ask for the hosting locations and relevant subprocessors involved in support, analytics, messaging, and other services. Determine whether the answer covers production data, backups, and disaster recovery. Review the proposed arrangement against your organization’s privacy, procurement, and jurisdiction-specific requirements.
If AI features are available, ask whether customer information is sent to additional providers and whether those features can be disabled. The AI feature evaluation guide explores that additional review. Avoid assuming that an approved core platform automatically makes every optional service appropriate for sensitive records.
7. Can the Organization Reconstruct Important Activity?
Ask which actions generate logs. Useful events may include sign-ins, permission changes, record edits, downloads, exports, and administrator actions. Check whether logs identify the actor, time, affected object, and action in a form your team can investigate.
Additionally, clarify log retention, access, export, and protection against alteration. CISA’s logging guidance supports a discussion about collecting and reviewing system activity. Ask the vendor to show an example relevant to an EHS record rather than presenting an unrelated technical log.
8. What Independent Evidence Supports the Security Claims?
Request available assurance reports, certification scopes, penetration-testing summaries, and information about remediation. Review their dates and coverage. A report for a parent company or hosting provider may not assess the application features your team will use.
Certifications and audit reports can support due diligence, but they do not guarantee that every customer configuration is secure. Ask which responsibilities belong to the vendor and which belong to you. If evidence is shared under confidentiality terms, have the appropriate reviewer examine it and record the decision without distributing restricted documents broadly.
9. How Are Vulnerabilities and Product Changes Managed?
Ask how the vendor receives vulnerability reports, prioritizes fixes, and communicates material changes. Find out whether customer administrators receive advance notice of changes affecting permissions, integrations, or authentication. Include mobile applications and third-party components in the discussion.
The NIST Cybersecurity Framework 2.0 offers a structure for organizational risk management. Use it as a discussion framework with IT, not as proof that a vendor’s product meets every requirement. Translate broad security answers into ownership, evidence, and follow-up actions.
10. How Will the Vendor Respond to a Security Incident?
Clarify notification commitments, contact channels, investigation support, and access to relevant evidence. Identify who at your organization receives the initial message and who can coordinate the response outside normal business hours. Contract terms should be reviewed for your circumstances rather than copied from a generic checklist.
Ask how the vendor handles customer containment requests, compromised credentials, and suspected unauthorized exports. Run a tabletop discussion using a hypothetical incident. The goal is to identify unanswered responsibilities before a real event requires urgent coordination.
11. Can Records Be Recovered and Operations Continue?
Backups need a demonstrated recovery process. Ask what is backed up, how restoration is tested, and what recovery commitments apply. Distinguish recovery time, which concerns service restoration, from recovery point, which concerns how much recent data could be lost.
Discuss what the safety team does while the platform is unavailable. Establish approved reporting and escalation routes that remain usable during an outage. Keep a practical continuity plan for critical workflows, and confirm how information collected during an interruption is reconciled afterward.
12. What Happens to Information When the Contract Ends?
Review export formats, attachment access, historical logs, support charges, and the time available to retrieve records. Ask about deletion from production systems and the treatment of backups. Your obligations to retain or protect information may continue after the subscription ends.
The EHS buying mistakes guide explains why long-term requirements belong in the initial evaluation. Add exit testing to procurement so the organization knows what it can retrieve before depending on the platform as its primary record system.
Turn the Answers Into a Reviewable Decision
Record each question, the vendor’s evidence, the internal reviewer, and any remaining condition. Prioritize gaps according to the sensitivity of the data and the importance of the workflow. Resolve essential issues before production use and assign owners for lower-priority improvements.
Finally, revisit the review when the platform’s scope changes. Adding occupational health records, connecting another system, or enabling an AI service can change the risk. Security works best as an ongoing responsibility with visible ownership and practical checks.
Frequently Asked Questions
Is cloud-based EHS software inherently less secure than on-premises software?
No deployment model guarantees security. Evaluate the provider’s controls and your organization’s ability to maintain its responsibilities. On-premises systems also require patching, access management, monitoring, backup, and recovery. Compare the actual operating arrangements rather than the hosting label alone.
Should a small business request the same security evidence as a large enterprise?
The review should reflect data sensitivity and operational risk. A smaller organization may use a simpler process, but it still needs clear access controls, account protection, incident contacts, and usable exports. Ask for evidence that answers those needs without making the process unnecessarily complicated.
Can a trial use real employee injury records?
Prefer synthetic or appropriately de-identified records until the trial’s access, processing, and deletion arrangements have been reviewed. A trial environment is still a place where information is stored and accessed. Obtain the appropriate internal approval before introducing identifiable or sensitive material.
Browse Our EHS Resources



