SECOPS · PARTIAL SUITE
Docker Configuration Evidence and Security Review
Make selected container configuration easier to review and discuss. Spekra evaluates supplied Docker evidence, showing failing, passing and unknown observations rather than claiming a security certification.
Guided pilot scope · Reviewed 2026-10-16. No production AI diagnosis, automatic infrastructure/DDL remediation or compliance certification is offered.
Collect the project you own
Run the Docker security collector against an intended Compose project on its Docker host. It reads selected inspection fields from running containers. An authorized organization administrator uploads the normalized snapshot for SecOps review.
The collector avoids container environment variables, command arguments and full labels. Mount paths are inspected locally to detect socket exposure; exported evidence retains the resulting boolean rather than those paths.
Inspect the versioned baseline
The custom baseline checks privileged mode, host network/PID namespaces, Docker socket mounts, public port bindings, read-only root filesystem, no-new-privileges, dropped capabilities and explicit non-root configuration.
Missing evidence is unknown. Configuration is not attestation of the process identity or public network reachability. Review why a workload needs a setting before changing it outside Spekra.
Keep evidence fresh
Filter findings by status, severity and source, then inspect their evidence and retained audit. A complete source snapshot replaces that source inventory. Fresh identical retained exports can replay without creating duplicate audit records.
After 24 hours, source checks become unknown on query. A new collection provides a fresh observation; an empty snapshot does not prove remediation.
Security review boundaries
CVE/image scanning, native cloud posture, automatic remediation and compliance certification are unavailable. The imported snapshot is administrator-supplied evidence, not a remotely attested security measurement.
Use this workflow for focused configuration review alongside your normal security tools and approvals. Source/retention limits apply; agree requirements before a pilot.
Frequently asked questions
Will Spekra find image vulnerabilities?
The current production adapter does not scan images or consume CVE feeds. It reviews selected Docker configuration evidence.
Do passing checks certify that a container is secure?
No. Passing means the supplied configuration meets that check. It does not prove runtime security, legal compliance or an independent attestation.
Why do old findings become unknown?
Configuration observations expire after 24 hours on query so stale evidence is not presented as a current passing check. Collect and import a new snapshot.
Evaluate your own workflow
Start with supported sample or staging infrastructure and agree on a success measure. Contact the operator to arrange a pilot. This static website does not create accounts or send invitations automatically.
Request a guided pilot →