Zanshin
Novidades do Zanshin | Setembro de 2026 commercialThe section your link pointed to isn't on Zanshin's page any more, so we've brought you to the top.
Summary
Zanshin is a commercial cloud security posture managementcloud security posture managementCloud security posture management, checking cloud resources for risky settings and policy violations. It helps teams find exposed services, overly broad permissions and other configuration gaps. platform that continuously monitors and assesses cloud infrastructure for vulnerabilities and misconfigurations. It is run as a service and is for compliance owners evaluating third-party risk. Its documentation positions it alongside governance assessment tooling. Users can configure questionnaires with weighted scoring and automatic recommendation thresholds, and reports can generate ISOISOA widely adopted international standards body that publishes technical specifications; cyber tools cite ISO standards to signal compliance with recognized benchmarks for quality, security, or interoperability. 27001 and PCI DSSPCI DSSThe Payment Card Industry Data Security Standard, security requirements for protecting payment account data. It covers organizations that store, process or transmit that data and relevant service providers. coverage details, with 10 releases in the window tracked and the last release occurring this week.
How Zanshin helps
Which of our suppliers are dragging down our third-party risk posture?
scores each vendor's self-assessment answers by configured severity weight and rolls them into an automatic Accept, Reject, or Request Clarification recommendation against the thresholds we defined
Which questionnaire answers still need a human to look at them before we can sign off?
flags free-text and evidence-file responses for mandatory review and withholds a final grade until a reviewer confirms or overrides the automated score
Which parts of a supplier's environment are we not actually watching?
lists unmonitored scan targets in a dedicated gap section of the third-party report, so blind spots in supply-chain visibility show up by name
Can we hand this supplier report to a partner who doesn't read English?
generates the same findings, including compliance coverage and environment gaps, fully in Portuguese
Are we covered for ISO 27001 and PCI DSS on this vendor?
displays coverage against both frameworks directly in the generated third-party report
Who do we actually contact at this vendor when something needs escalating?
organization profiles hold separate named contacts per department — security, compliance, legal — instead of one generic email
Languages
Screenshots
From the release notes, newest first. Click one to see it full size.Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
Five scores for Zanshin, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail Zanshin puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Website history
tenchisecurity.com, every changeTenchi Security's home page and 24 more pages as they looked each month from September 2021 to October 2026: 35 renders, 3 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
See plans → Already subscribed? Sign in →← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
Releases
10 entries
No entries match these filters.
- September 20262
- May 20261
- February 20261
- October 20251
- September 20251
- June 20251
- May 20251
- April 20251
- March 20251
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.