Home /Modules/antivirus/SECURITY.md

SECURITY.md

antivirus/SECURITY.md · 93 line(s) · markdown

Sleelavirin Security and Release Checklist

Security posture

Sleelavirin is a signature-matching and scanner-coordination component. A no-match result is not proof that a file is safe. The native SHA-256 index imported from compatible extracted ClamAV .hsb records is only a subset of ClamAV's coverage; it is not a CVD/CLD decoder or a replacement for ClamAV's own engine.

Signature and code integrity

The manifest binds a recorded SHA-256 digest and signature count to exact index bytes. It is not a digital signature: an attacker able to replace both index and manifest can forge both. Store a trusted expected digest or sign release metadata when authenticity against a privileged attacker is required.

Scan execution and filesystem safety

Adversarial and regression testing

Before a release, test at least:

Tests must use harmless fixtures; do not commit live malware samples into the repository.

CI and release gate

The antivirus workflow runs the build and unit tests on Linux, macOS, and Windows, plus Python compilation and Bandit static analysis on Ubuntu. A release candidate is not security-verified until these jobs pass on the exact commit being released and a maintainer has reviewed the results.

Release checklist:

  1. Review the diff for unsafe process execution, path handling, privilege changes, and secret leakage.
  2. Run make -C antivirus clean test on a supported Unix host; run the Windows workflow as well.
  3. Run the manifest integrity check when a manifest is distributed with the index.
  4. Confirm the source and provenance of the active signature index.
  5. Verify report exit codes for clean, detected, and incomplete/error fixtures.
  6. Confirm quarantine and recovery behavior on the target filesystem.
  7. Record commit SHA, CI run, compiler/Python versions, signature source/version, and release artifact hashes.

Current limitations

ClamAV database acquisition and precious-file integrity

Additional operational and adversarial controls

Source-tree and release-file SHA-256 inventory

Use make -C antivirus integrity-manifest to inventory the source tree, then verify with make -C antivirus integrity-check MANIFEST=build/INTEGRITY-MANIFEST.json. The manifest includes ordinary source and documentation files as well as signature-index files, but excludes generated build/dist output and the mutable ClamAV cache, whose snapshots have their own validated manifests.

Platform release archives include an INTEGRITY-MANIFEST.json, a SHA256SUMS file, and a separate .sha256 sidecar for the ZIP. CI verifies the package manifest before creating the archive. Keep an independently trusted copy of the archive digest or use a detached signature whose public key was obtained independently; hashes stored next to the files they describe do not provide publisher authentication.