Dokimore Security Team
Security testing, release evidence and the rules that ask for both.
- Articles
- 5
- Topics
- 1
- Last updated
What this team covers
Articles signed by this team
- SecurityOriginal research
We Decoded 1,961 Real Windows Event Records. Two Things We Believed Were Wrong.
An analyst with a .evtx file and twenty minutes does not have a SIEM to load it into. So we built a decoder for the raw binary format, tested it thoroughly, and shipped it — and then measured it against 1,961 records from four real Windows channels. It had been dropping the entire payload of every event while decoding the envelope perfectly, which is the worst way for a parser to be wrong. Here is what the format actually does, what the measurement cost us, and what the SOC Analyst module does with the file once it is readable.
- SecurityScenario walkthrough
Use Case: Tenant Isolation Testing in a B2B SaaS, Before a Customer Finds the Gap
A scenario walkthrough, not a customer story: a B2B SaaS with 400 tenants adds a reporting API and ships it with a role check and no ownership check. Why broken object level authorization has topped the OWASP API Security Top 10 in both of its editions, the two-tenant matrix that finds it before a customer does, how to run the matrix with an API testing studio, and the three controls we use on our own platform.
- SecurityExplainer
CRA Vulnerability Reporting Began on 11 September 2026: The Evidence a QA Team Must Be Able to Produce
Since 11 September 2026, a manufacturer of a product with digital elements sold in the EU must report an actively exploited vulnerability through ENISA’s single reporting platform, with an early warning within 24 hours of becoming aware of it. The three deadlines, who counts as a manufacturer, and the four records a QA or security team needs before the clock starts: the reproduction, the scope, the fix evidence and the timeline.
- SecurityExplainer
Security in CI/CD: Gates That Developers Don’t Route Around
Teams fear that security gates will slow every deployment, so scanning is deferred to a yearly penetration test and the gate becomes theatre. Progressive scanning keeps security continuous and pipelines fast: seconds of checks on each pull request, the deep scan nightly against staging, and the release reading the latest verdict instead of waiting for a new one. Since 11 September 2026 an actively exploited vulnerability in a product sold in the EU also starts a 24-hour early-warning clock.
- SecurityExplainer
Continuous Compliance Evidence: Audit Season Shouldn’t Be Archaeology
Audit season means weeks of screenshot archaeology: exporting logs that were almost rotated away and reconstructing "who approved this" from chat threads. The alternative is to collect evidence continuously from the pipeline: a record of sign-ins and administrative changes, a scan report with the request and response behind each confirmed finding, and accessibility scan history with a VPAT draft. This article maps one control to the artefact that proves it, and says what Dokimore does not hold.
What its articles carry
- 5 of 5 list their outside sources, each with the date it was read.
- 5 of 5 say how their numbers were measured, under “How we measured this”.
- 5 of 5 answer the questions readers ask, one paragraph each.
- An article that changes after publication shows the date it was updated.