Editorial and Review Policy
The publication gate Cyber VK applies before draft security-learning content may be indexed, including sourcing, review, corrections and AI disclosure.
- Effective from
- Last updated
Bad security advice gets someone owned. That is the whole reason this page exists, and it is why every claim below is a process rather than an intention.
Who writes what you read
The learning library is currently a pre-publication preview. Role-based labels show which internal team owns each draft, but those labels are not people and do not claim credentials. These URLs remain noindex and stay out of the sitemap until every page carries a verified named author with relevant visible credentials and a different named technical reviewer.
The review process
- The author writes the piece and tests every command, request and rule in it against a real target they control.
- A technical reviewer with relevant experience reproduces the technical claims independently. Not reads them: reproduces them.
- Anything that touches a live vulnerability is checked against the CVE content and disclosure policy before it can be scheduled.
- Only after approval do the reviewer name and review date go on the page and into structured data. Enabling CONTENT_INDEXING_ENABLED is the final operational gate after that audit, not a substitute for it.
What AI is and is not used for
AI tools may assist with pre-publication drafts, summarise source material a responsible editor has already read, or propose variations of practice questions from an authored template. AI output is never treated as reviewed evidence and cannot cross the indexing gate without human testing, correction and approval.
Sources and attribution
Factual claims carry a source and the date it was checked. Where we cite a number, the number is attributed to whoever produced it: NVD for vulnerability records, FIRST for EPSS, CISA for the KEV catalogue, the vendor for its own advisory. Where we disagree with a source, we say so and explain why rather than quietly using a different figure.
Dates mean what they say
The publication date is when the page first went live and it never changes. The updated date changes when the content changes, and not when a typo is fixed or a template is redeployed. A site that refreshes its dates to look current is lying to its readers about how fresh its research is, and it is a practice this platform will not adopt.
Corrections
- A factual error is corrected as soon as it is confirmed, and the page carries a dated correction note describing what was wrong.
- A correction note is never removed later. The history is part of the record.
- Where an error was significant enough that a reader could have acted on it, the correction says so explicitly rather than being phrased as a clarification.
- Every page carries a report-an-error control, and reports are read by the author.
Commercial independence
We do not accept payment for coverage, we do not publish sponsored guides, and we do not rent sections of the domain to third parties. Where a comparison mentions a competitor, the comparison is written by someone who has used both and the criteria are stated before the conclusion.
Affiliate links, if we ever use them, will be disclosed on the page that carries them and will never influence a recommendation. As of this version, there are none.
Content that stops being useful
Pages that no longer serve a reader are improved, merged into a better page, or removed with a proper redirect. Leaving stale content up because it still gets traffic is how a reference site stops being one.
Who reviews what you read
Draft pages use role-based ownership labels. Search indexing stays disabled until a verified named author and a different technical reviewer approve the page.
Cyber VK Security Curriculum
Pre-publication content owner
This role-based label identifies the Cyber VK team responsible for maintaining the draft web-security curriculum. It does not represent a named person or claim a professional credential. A verified author and a separate technical reviewer are required before this material is submitted for indexing.
Cyber VK Defensive Research
Pre-publication content owner
This role-based label identifies the Cyber VK team responsible for maintaining draft defensive-security material. It does not represent a named person or claim a professional credential. A verified author and a separate technical reviewer are required before this material is submitted for indexing.
Cyber VK Lab Engineering
Pre-publication content owner
This role-based label identifies the Cyber VK team responsible for maintaining draft lab material and walkthroughs. It does not represent a named person or claim a professional credential. A verified author and a separate technical reviewer are required before this material is submitted for indexing.
Cyber VK Certification Desk
Certification and voucher research
The Certification Desk is the Cyber VK team responsible for tracking exam pricing, voucher validity terms, retake policies and certification requirements across the vendors Cyber VK is an authorised reseller for. Pricing and voucher terms published under this byline are maintained against vendor source material and against Cyber VK’s own supplier catalogue. This is an organisational byline rather than an individual, and it claims no personal certification.
Cyber VK Store Operations
Voucher fulfilment and vendor terms
Store Operations runs voucher procurement and fulfilment at Cyber VK. In an editorial capacity the team reconciles every published price, discount claim, validity window and redemption instruction against current supplier records before the page is released, and re-checks them when supplier terms change. This is an organisational byline rather than an individual, and it claims no personal certification.
Publication gate: confirm each contributor’s name, consent, biography, credentials, profile links, and review record before enabling editorial indexing. Role labels never substitute for a person in structured data.