A local check your customers can repeat
When a customer's security questionnaire asks where documents go, answer with something they can run themselves. sirdas comprobar checks the Sırdaş engine on your machine and writes a report with a fingerprint; with the same version and configuration, anyone gets the same fingerprint.
It is a check your team runs on its own machine, not a certification, an audit or a statement by Sırdaş about your company. It says what the engine does here; it says nothing about the rest of your systems.
Reviewed:
What it checks
- The engine runs with networking cut off, and any connection attempt is counted.
- Invented names, SSNs, EINs, emails and ID numbers in English and Spanish are replaced with placeholders, and the map restores the original byte for byte.
- The per-agent policy (SIRDAS_POLICY) loads, and the audit log chain (SIRDAS_AUDIT_LOG) is intact.
- Whether the MCP server is read-only or confined to a folder, and the sha256 of the installed program, to compare with the published package.
How to repeat it
- Run: sirdas comprobar -o report.json. It exits with 1 if a check fails, so it also works in CI.
- The fingerprint covers the version and the results, not the date or the machine. Run it with the same version and configuration and compare.
- Or drop the report below: the page recomputes the fingerprint in your browser and tells you whether the report was edited.
Verify a report and get the badge
The report stays in this tab: nothing is sent or saved.
Teams that publish their check
No team is listed yet. This list only grows with written permission and a public page of their own that shows the badge or the report.
To be listed, write to hola@sirdaspdf.com with the link to your page.