# Chain305 editorial policy: authors, sources and corrections > Who writes chain305.com, how vendor claims and attack results are checked against sources, how corrections are made, and where AI assistance is used. Source: https://chain305.com/editorial-policy/ --- # Editorial policy Who writes this site, what each claim is checked against, and how errors get fixed. The chain305.com editorial policy is the set of rules every page on the site follows, from the founder's signed articles, teardowns and comparisons to the product pages maintained by Chain305, the company that makes Chainsaw. Every claim about another vendor links the vendor's own documentation, and every fact is checked against a source before a page goes live, including on drafts written with AI assistance. Errors reported to sales@chain305.com are checked against the source, and a correction to a fact is noted on the page with a date. Questions and answers ## Who writes chain305.com? Muhammad Zeeshan Sultan, the founder of Chain305, writes the articles, attack teardowns, comparison pages and learn guides on chain305.com, and each of those pages carries his byline. He is a security architect with more than ten years in penetration testing, security architecture and DevSecOps, holds the CISSP and OSCP certifications, and started Chain305 in Dubai in 2026; his background is on the [About page](https://chain305.com/about/#founder). Product, feature, pricing, procurement and changelog pages describe what Chainsaw does rather than argue a position, so they carry the line “Maintained by Chain305” and the month the page last changed instead of a personal byline. Facts about Chainsaw itself come from the shipped product, its public documentation at [docs.chain305.com](https://docs.chain305.com/) and the open-source decision engine, [chainsaw-core](https://github.com/Chain305/chainsaw-core). When a page states a number, such as the 16 ecosystems or the 48-hour release hold, that number has to match the product as it ships on the date shown. ## Who writes the comparison pages, and how are vendor claims checked? The founder writes every comparison page for Chain305, the company that makes Chainsaw, so each comparison is written by an interested party and says so. Every claim about another vendor’s product is checked against that vendor’s own public documentation, and the page links the vendor document it relies on, so a reader can check the claim at the source instead of trusting Chain305’s summary. In practice, the [Socket comparison](https://chain305.com/vs-socket/) links Socket’s own firewall documentation for the Socket features it describes. Comparison pages name where the other product is stronger as well as where Chainsaw differs. Each comparison page ends with a note that names Chain305 as the author and gives a dated “Last checked” line, such as “Last checked: October 2026”: the date the vendor claims on that page were last compared with the vendor’s documentation. Chain305 does not run a fixed re-check calendar. A comparison page is re-checked when a vendor ships a relevant change or a reader reports one. ## How are the attack results tested? The [2026 attack coverage report](https://chain305.com/attack-coverage-2026/) is where chain305.com tests its own claims against real incidents. Its 25 October 2026 run takes 58 public supply-chain attacks from 2026 and checks each one against Chainsaw as it runs in production (v0.22.127), with the result for every attack published, misses included. Each outcome other than a miss is backed by a reproduction test shaped like the attack, with a harmless twin that must not trigger, and a separate reviewer tried to break the grading in both directions. The report also lists [the limits of the test](https://chain305.com/attack-coverage-2026/#what-are-the-limits-of-this-test), starting with the main one: Chain305 is the vendor, and Chain305 wrote the tests and judged the outcomes. The [attack teardowns](https://chain305.com/teardowns/) take one incident at a time and answer whether Chainsaw would have stopped it, citing the public write-ups they rely on. ## How are corrections made? Anyone who finds an error on chain305.com can email [sales@chain305.com](mailto:sales@chain305.com) with the page address and the correction, and a link to the source that shows it if there is one. Chain305 checks the report against that source. A confirmed error is fixed on the page, and when the error changed a result, a figure or a claim about another vendor, the page also says what was corrected and on what date, rather than silently replacing the old text. In practice, the attack coverage report shows how that looks: it states that the 19 October 2026 run overstated full coverage by one attack, names the attack, and gives the corrected count. Spelling and wording fixes that change no fact are made without a note. On comparison pages, a correction to a vendor claim also updates the “Last checked” date. ## Is AI used to write chain305.com? Yes, drafts of chain305.com pages may be written with AI assistance. No draft is published on that basis alone: before a page goes live, every fact in it is checked against its source, whether that is the Chainsaw code and documentation, the other vendor’s own documentation, or the public write-up of an attack. Claims that cannot be traced to a source are removed rather than published. The named author of a signed page, or Chain305 on a page marked “Maintained by Chain305”, is responsible for what the page says, whoever or whatever produced the first draft. Corrections to AI-assisted pages follow the same process as any other page on chain305.com: email [sales@chain305.com](mailto:sales@chain305.com), and a confirmed error is fixed and, where it changed a fact, noted on the page with a date. By [Muhammad Zeeshan Sultan](https://chain305.com/about/#founder), founder of Chain305 · Updated November 2026