Bahmni Security Agents

 

Context

We have lot of guidance documented for right security practices while installing Bahmni e.g. setting up right permission, root access etc. but currently there is no way to keep the respective implementation support / maintenance team informed about possible vulnerabilities.

Feature

Bahmni security agents would run on Linux machines (on-prem or cloud) where bahmni is installed and would scan for possible vulnerabilities with respect to

  • Policies (inappropriate permissions, root access etc)

  • Open ports

  • Libraries / Dependencies used by the application that have know vulnerabilities

  • OS Security updates missing

🔰Options

For Vulnerability Checks, Kubernetes Cluster Scanning & Container Images:

Trivy:

Bahmni team is using TRIVY for security scanning of all code, images, libraries, etc. This runs for every deployment to our environments.

See here, Security Scanning with Trivy

For Scanning OS:

OpenSCAP:

See here, Security Compliance Testing of Bahmni Servers using OpenSCAP

  • Open Source tool backed by RedHat.

  • Compliance as Code approach.

  • Built on top of SCAP standard and tests.

  • More focussed on performing configuration compliance and vulnerability scanning on local system.

  • Ref:

For Scanning Secrets:

In order to prevent leakage of secrets it is highly recommended to install Talisman as a global pre-commit hook in the developer’s machine.

Talisman:

Trufflehog:

Trivy:

See here, Secrets Scanning with Trivy

Other tools explored:

OpenVAS:

Vuls :

References

The Bahmni documentation is licensed under Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)