Guides · Methods · Open data

Digital intelligence resource centre

Resources built to turn a complex topic into a documented decision: practical steps, expected evidence, useful indicators and reusable controls.

118
in-depth guides
315
verifiable controls
4
maturity levels
Empty intelligence archive with dossiers and maps Illustration · fictional scene

Put the methods into practice

Workshops to understand evidence and numbers

Read a sourced photograph, interpret AI answers, compare recovery objectives, classify web measurements, examine extension permissions and check a detection scenario in logs. Each workshop extends a guide with an explained example and its limitations.

Recovery: separate restoration time from data age

Fictional objectives: RTO 120 min and RPO 30 min. Recovery takes 95 min, but recovered data is 45 min old: a 25-minute time margin and a 15-minute data overrun. The exercise therefore does not meet both objectives.

AI answers: make abstentions and denominators visible

Of 100 fictional questions where an answer is expected, the assistant answers 80 and 72 are validated. Quality among answers: 72/80 = 90%. Coverage: 80/100 = 80%. Success across the set: 72/100 = 72%. The 90% figure alone hides twenty unanswered questions.

Real photograph: separate image, caption and publishing page

Exercise: someone attributes this copy to Apollo 8 because it is titled “Earthrise”. The selected source page identifies Lunar Orbiter 1. You can flag that conflicting attribution without claiming to have verified the entire file history.

Read permissions through the actual task

A fictional extension must annotate the selected page after a click. The team compares an activeTab and scripting variant with one requesting standing access to every site. It also checks the absence of automatic scripts, transmitted data and annotation persistence. Narrower access does not remove the need for these checks.

From a received log to a verified response

In the fictional exercise below, a rule expects two failed sign-ins followed by a success for the same account within one minute. One failure arrives late. The team checks late-event handling before claiming the scenario is detected. This teaching rule alone cannot identify a real attack.

A zero rate does not establish zero risk

In a fictional sample of 20 independent requests, none was misclassified. The observed rate is 0%, yet the upper bound of the two-sided 95% Wilson interval is about 16.1%. This observation alone does not justify a claim of error-free operation.

Reading paths

Choose a starting point for your decision

These paths connect guides that work together. You can also browse the complete library directly.

Updated 29 October 2026

118 guides to frame, verify and act

Each guide works independently or with the shared matrix to prepare an assessment, workshop or roadmap.

118 / 118 guides shown. Search also covers questions, methods and comparisons.

Operational data

Digital maturity matrix — 315 verifiable controls

An open framework to assess the existence, application, evidence and management of essential controls. It is not a certification: it makes gaps easier to discuss and prioritise.

Assessment scale

0 — Absent

No stable practice or usable evidence.

1 — Initial

Occasional practice dependent on one person.

2 — Controlled

Documented, applied and verifiable control.

3 — Managed

Measured, reviewed and improved control.

Coverage and success: two denominators

Fictional teaching example: twelve controls are reviewed. These statuses describe the checks performed, separately from the 0–3 maturity levels.

Breakdown of the twelve example controls
  • Test passed with evidence6 / 12
  • Observed failure2 / 12
  • Not tested3 / 12
  • Justified exclusion from scope1 / 12
Test success
6 ÷ 8 = 75%

Six passes among eight tested controls. This rate does not describe the three untested controls.

Test coverage
8 ÷ 11 ≈ 72.7%

Eight tested controls out of eleven applicable controls. The out-of-scope control is excluded only because that exclusion is justified.

The three untested controls remain unknown. A non-applicable control needs a scope justification; this status must not erase a failure. Keep critical failures visible even when the success rate looks high.

DomainVerifiable controlMinimum expected evidence
OSINTDecision question defined before collectionCIE-0001 · Method and referencesDated brief with scope, audience and expected decision
OSINTSources classified by origin, date and reliabilityCIE-0002 · Method and referencesSource log and explicit scoring rule
OSINTFacts, hypotheses and unknowns kept separateCIE-0003 · Method and referencesAnalysis note with confidence levels
OSINTSensitive information minimised and protectedCIE-0004 · Method and referencesRetention rule and access register
CybersecurityInventory of exposed assets maintainedCIE-0005 · Method and referencesList of domains, services, accounts and owners
CybersecurityCritical access protected by resistant MFACIE-0006 · Method and referencesCoverage report and approved exceptions
CybersecurityPatches prioritised by exposure and impactCIE-0007 · Method and referencesDated remediation queue and closure evidence
CybersecurityBackups restored during a testCIE-0008 · Method and referencesReport from the latest restoration test
AI agentsAgent purpose, limits and owner documentedCIE-0009 · Method and referencesSystem card and responsibility matrix
AI agentsAllowed and prohibited data identifiedCIE-0010 · Method and referencesData classification and applied filters
AI agentsSensitive answers evaluated on a test setCIE-0011 · Method and referencesResults, acceptance thresholds and known errors
AI agentsLogging and manual stop availableCIE-0012 · Method and referencesExecution logs and shutdown procedure
VisibilitySearch intents connected to useful pagesCIE-0013 · Method and referencesIntent, page, action and metric map
VisibilityEntities, authors and dates are explicitCIE-0014 · Method and referencesConsistent visible markup and structured data
VisibilityMobile journeys and performance controlledCIE-0015 · Method and referencesField measurements and key action tests
VisibilityConversions connected to entry contentCIE-0016 · Method and referencesDashboard by page and business objective
Digital trustIdentity, beneficial ownership and governance verifiedCIE-0017 · Method and referencesDated source file with unresolved points clearly marked
Digital trustCritical dependencies and subcontractors mappedCIE-0018 · Method and referencesThird-party map covering services, data and fallback options
Digital trustIncidents, disputes and reputation signals qualifiedCIE-0019 · Method and referencesSourced timeline separating facts, allegations and responses
Digital trustDecision documented with conditions and monitoringCIE-0020 · Method and referencesDecision note, reservations, owner and review triggers
Secure webPerformance budget defined for critical journeysCIE-0021 · Method and referencesMobile thresholds for loading, interaction and visual stability
Secure webDependencies and third-party scripts minimisedCIE-0022 · Method and referencesInventory, rationale, owner and removal procedure
Secure webHeaders, sessions and forms hardenedCIE-0023 · Method and referencesControl report and server-side protection tests
Secure webAccessibility and key actions tested in real useCIE-0024 · Method and referencesDocumented keyboard, screen reader, mobile and error scenarios
Third-party riskCritical suppliers classified by service, data and dependencyCIE-0025 · Method and referencesSupplier register with owner, criticality and fallback option
Third-party riskContractual and operational evidence verifiedCIE-0026 · Method and referencesDated file covering security, continuity, subcontractors and data location
Third-party riskConcentration and dependency chains analysedCIE-0027 · Method and referencesMap of critical subcontractors and failure scenarios
Third-party riskExit and reversibility conditions testedCIE-0028 · Method and referencesExit procedure, controlled export and replacement exercise
Crisis managementDecision roles and fallback channels definedCIE-0029 · Method and referencesOffline crisis directory and responsibility matrix
Crisis managementIncident scenarios exercised with business teamsCIE-0030 · Method and referencesExercise report, observed decisions and gaps
Crisis managementRecovery prioritised by essential serviceCIE-0031 · Method and referencesApproved recovery order and technical test evidence
Crisis managementInternal and external communication preparedCIE-0032 · Method and referencesAdaptable templates, notification criteria and named spokesperson
RAG qualityCorpus, rights and validity dates controlledCIE-0033 · Method and referencesSource inventory, owner, update cycle and exclusions
RAG qualityRetrieval evaluated separately from generationCIE-0034 · Method and referencesQuestion set measuring passage relevance and coverage
RAG qualityCitations traced back to sourceCIE-0035 · Method and referencesFaithfulness tests, valid links and unsupported-claim rate
RAG qualityFailures and abstentions monitored in productionCIE-0036 · Method and referencesEdge-case log, escalation thresholds and drift review
Information integrityProvenance and original context retainedCIE-0037 · Method and referencesVerification log with file, source, date and transformations
Information integrityImages and video corroborated with independent cluesCIE-0038 · Method and referencesGeolocation, chronology and earlier-version record
Information integrityConfidence and unknowns explicit before publicationCIE-0039 · Method and referencesEditorial decision with confidence level and caveats
Information integrityCorrections propagated to dependent contentCIE-0040 · Method and referencesCorrection register, linked pages and reverification date
IdentityAccount lifecycle connected to HR and business eventsCIE-0041 · Method and referencesDated creation, change, suspension and deletion log with an owner
IdentityAccount recovery protected against social engineeringCIE-0042 · Method and referencesVerified procedure, independent factors, delays and escalation cases
IdentityElevated privileges limited, temporary and reviewedCIE-0043 · Method and referencesRole inventory, approvals, duration and latest access review
IdentityLost-device and lockout scenarios exercisedCIE-0044 · Method and referencesTest report covering revocation, recovery and continuity
Multilingual SEOEach language edition has a stable canonical URLCIE-0045 · Method and referencesLanguage, URL, canonical, status and editorial-owner map
Multilingual SEOLanguage alternates are reciprocal and validCIE-0046 · Method and referencesHreflang check covering return links, codes, indexable URLs and x-default
Multilingual SEOTranslations adapted to intent and marketCIE-0047 · Method and referencesLocal brief, terminology validation and edition-specific examples
Multilingual SEOIndexing, performance and conversion tracked by editionCIE-0048 · Method and referencesDashboard separating language, device, landing page and objective
Data lifecyclePurpose, owner and retention period defined at collectionCIE-0049 · Method and referencesRegister linking category, use, owner, retention basis and deadline
Data lifecycleCopies, backups and archives included in lifecycle rulesCIE-0050 · Method and referencesLocation, replication, restoration and propagation-delay map
Data lifecycleLegal holds and retention exceptions are traceableCIE-0051 · Method and referencesDated decision, scope, authority, duration and release procedure
Data lifecycleDeletion is verified and repeatableCIE-0052 · Method and referencesPurge log, control sample and failed-deletion handling
AI vendorsUse, data and decision level framed before selectionCIE-0053 · Method and referencesNeed statement, prohibited cases, owner and exit criteria
AI vendorsQuality and limitations tested on representative casesCIE-0054 · Method and referencesVersioned evaluation set, results, thresholds and known failures
AI vendorsDependencies, subprocessors and changes monitoredCIE-0055 · Method and referencesTechnical map, contractual notifications and version log
AI vendorsReversibility and data recovery exercisedCIE-0056 · Method and referencesTested export, replacement procedure, timelines and deletion evidence
AI visibilityGenerative search report tracked by page and periodCIE-0057 · Method and referencesDated Search Console export with pages, impressions and scope
AI visibilitySampled answers and citations manually verifiedCIE-0058 · Method and referencesQuery protocol, date, country, device and cited links
AI visibilityChanges connected to identifiable editorial workCIE-0059 · Method and referencesChange log and before-after comparison without assumed causation
AI visibilityTraffic and business outcomes compared with visibilityCIE-0060 · Method and referencesDashboard connecting pages, qualified visits and conversions
Software supply chainDirect and transitive components inventoried per releaseCIE-0061 · Method and referencesDated software bill of materials linked to the shipped version
Software supply chainArtifact origin and integrity verifiableCIE-0062 · Method and referencesProvenance, digest and signature check for shipped releases
Software supply chainVulnerabilities qualified by exposure and actual useCIE-0063 · Method and referencesTriage queue with component, scope, owner, decision and evidence
Software supply chainCritical component update and removal rehearsedCIE-0064 · Method and referencesReplacement, test, deployment and rollback report
Domains and DNSCritical domains and subdomains inventoried with ownersCIE-0065 · Method and referencesDated register of holder, registrar, expiry, DNS and accountable owner
Domains and DNSRegistrar access protected and changes approvedCIE-0066 · Method and referencesAccount review, strong authentication and change log
Domains and DNSDelegation and DNSSEC checked after changeCIE-0067 · Method and referencesResolution and validation results from multiple networks
Domains and DNSDNS recovery rehearsed with out-of-band contactsCIE-0068 · Method and referencesExercise report, recovery time and corrective actions
API resilienceCritical dependencies mapped to business journeysCIE-0069 · Method and referencesCall map, owners, contracts and degraded modes
API resilienceTimeouts, retries and idempotency testedCIE-0070 · Method and referencesTimeout, backoff and idempotency-key test results
API resilienceControlled degradation exercised during simulated outageCIE-0071 · Method and referencesFailure scenario and evidence of user-facing behaviour
API resilienceAlerts linked to business impact and recoveryCIE-0072 · Method and referencesDashboard, thresholds, on-call owner and restoration report
Browser extensionsInstalled extensions and owners inventoriedCIE-0073 · Method and referencesDated inventory by browser, version, team and accountable owner
Browser extensionsPermissions and site access justifiedCIE-0074 · Method and referencesReview of manifest, allowed hosts and accessible data
Browser extensionsInstallation and updates controlledCIE-0075 · Method and referencesDeployment policy, approved list and change review
Browser extensionsRemoval and incidents rehearsedCIE-0076 · Method and referencesDisablement procedure, scope and removal evidence
Backup and recoveryCritical services and dependencies prioritisedCIE-0077 · Method and referencesImpact analysis, recovery order and accountable owners
Backup and recoveryProtected and isolated copies verifiedCIE-0078 · Method and referencesCopy inventory, access rights and availability evidence
Backup and recoveryRestoration rehearsed safelyCIE-0079 · Method and referencesTimestamped test report, functional outcome and observed gaps
Backup and recoveryRecovery objectives compared with realityCIE-0080 · Method and referencesObserved recovery time and data loss during the exercise
Incident triageReporting channel and decision owner definedCIE-0081 · Method and referencesEscalation procedure, deputy and decision log
Incident triageInitial timeline and evidence preservedCIE-0082 · Method and referencesDated events, sources, integrity and access recorded
Incident triageImpact and scope reassessedCIE-0083 · Method and referencesHypotheses, affected services, decisions and next checkpoints
Incident triageLessons turned into actionsCIE-0084 · Method and referencesActions, owners, dates and closure validation
Web accessibilityScope and reference level definedCIE-0085 · Method and referencesJourneys, languages, components and selected WCAG criteria
Web accessibilityRepresentative sample examinedCIE-0086 · Method and referencesPage types, interactive states and essential content covered
Web accessibilityAutomated and manual tests combinedCIE-0087 · Method and referencesKeyboard, zoom, screen reader and human review evidence
Web accessibilityFixes retested across the journeyCIE-0088 · Method and referencesReproducible finding, owner, retest and user effect
Vulnerability managementAssets and versions assigned to ownersCIE-0089 · Method and referencesDated register of services, components and owners
Vulnerability managementKnown exploitation checkedCIE-0090 · Method and referencesCVE, CISA KEV listing and actually deployed product matched
Vulnerability managementPriority reflects exposure and impactCIE-0091 · Method and referencesDated decision with business risk, deadline and compensating measures
Vulnerability managementFix and functionality verifiedCIE-0092 · Method and referencesDeployed version, vulnerability check and critical journey test
Phishing-resistant authenticationAccounts and current methods inventoriedCIE-0093 · Method and referencesUsers, privileges, factors and applications recorded
Phishing-resistant authenticationBinding to genuine service checkedCIE-0094 · Method and referencesLegitimate-domain test and phishing scenario rejection
Phishing-resistant authenticationEnrollment and fallback protectedCIE-0095 · Method and referencesAddition, loss, revocation and notification procedure tested
Phishing-resistant authenticationMigration and exceptions trackedCIE-0096 · Method and referencesCoverage, excluded accounts, owners and closure dates
Measurement planObjective and event linkedCIE-0097 · Method and referencesDictionary with journey, event, owner and decision
Measurement planParameters and types documentedCIE-0098 · Method and referencesNames, types, units and collection rules approved
Measurement planEvents tested across statesCIE-0099 · Method and referencesConsent, duplicate, error, mobile and abandonment tests
Measurement planQuality monitored after releaseCIE-0100 · Method and referencesExpected versus received events with an assigned owner
ExperimentationHypothesis and population preregisteredCIE-0101 · Method and referencesDated protocol, primary metric and excluded segments
ExperimentationAssignment checkedCIE-0102 · Method and referencesAllocation and observed sample ratio examined
ExperimentationOperational guardrails monitoredCIE-0103 · Method and referencesErrors, latency, accessibility and checkout tracked
ExperimentationDecision and uncertainty documentedCIE-0104 · Method and referencesResult, duration, limits, segments and next action archived
Measurement and privacyTrackers and purposes inventoriedCIE-0105 · Method and referencesMap of access, recipients, retention and purposes
Measurement and privacyConfiguration assessed against applicable rulesCIE-0106 · Method and referencesDocumented CNIL conditions and consent choices
Measurement and privacyRefusal tested end to endCIE-0107 · Method and referencesEvidence before choice, after refusal and withdrawal
Measurement and privacyAccess and retention reviewedCIE-0108 · Method and referencesPermissions, periods and periodic review register
Product catalogStable identifier per offerCIE-0109 · Method and referencesVerifiable link across item, variant, URL and feed
Product catalogPrice and availability consistentCIE-0110 · Method and referencesTimestamped feed, visible page and structured data check
Product catalogVariants and images checkedCIE-0111 · Method and referencesSample of sizes, colors, visuals and descriptions
Product catalogDiscrepancies owned and fixedCIE-0112 · Method and referencesDiscrepancy log, owner, fix and recheck
Security loggingCritical sources and clocks inventoriedCIE-0113 · Method and referencesSystems, events, time sync and owner inventory
Security loggingLog integrity and access protectedCIE-0114 · Method and referencesTransfer, retention, permission and tamper checks
Security loggingCorrelation tested with a scenarioCIE-0115 · Method and referencesIdentifiers connecting sign-in, application and infrastructure
Security loggingDetection linked to responseCIE-0116 · Method and referencesTested rule, owner, timing and response evidence
Multilingual qualityLanguages and canonical versions mappedCIE-0117 · Method and referencesURL, HTML language and reciprocal alternate inventory
Multilingual qualityJourneys translated end to endCIE-0118 · Method and referencesNavigation, form, error, email and checkout tests
Multilingual qualityDirection and formats testedCIE-0119 · Method and referencesRTL, date, number, unit and overflow checks
Multilingual qualityReview and fixes recordedCIE-0120 · Method and referencesHuman sample, risk level, owner and retest
Crawling and indexingImportant URLs discoverableCIE-0121 · Method and referencesHTML links and sitemap reach accessible canonical URLs
Crawling and indexingResponses and directives coherentCIE-0122 · Method and referencesHTTP, robots, noindex and canonical sample checked
Crawling and indexingSearch Console gaps diagnosedCIE-0123 · Method and referencesURL inspection, logs and documented cause before fix
Crawling and indexingFixes retestedCIE-0124 · Method and referencesLinks, responses, tags and pages rechecked after release
Accessible formsFields named and groupedCIE-0125 · Method and referencesLabels, groups, help and keyboard order checked
Accessible formsErrors locatable and correctableCIE-0126 · Method and referencesSummary, field message and retained values tested
Accessible formsComplete states verifiedCIE-0127 · Method and referencesSuccess, server failure, delay, mobile and zoom rehearsed
Accessible formsJourney tested with assistanceCIE-0128 · Method and referencesKeyboard and relevant assistive technology on a real task
API contractsRequests and responses documentedCIE-0129 · Method and referencesOpenAPI description with examples, schemas and statuses
API contractsErrors actionable without leakageCIE-0130 · Method and referencesType, status and useful detail validated without secrets
API contractsCompatibility exercisedCIE-0131 · Method and referencesOld clients, optional fields and new versions tested
API contractsWebhooks replay-safeCIE-0132 · Method and referencesSignature, duplicate, ordering, retry and acknowledgement tested
Email deliverySender authentication checkedCIE-0133 · Method and referencesSPF, DKIM, DMARC and alignment inspected on real messages
Email deliveryMessage classes separatedCIE-0134 · Method and referencesPromotional and transactional flows and measures distinguished
Email deliveryPromotional unsubscribe testedCIE-0135 · Method and referencesVisible link and applicable one-click headers verified
Email deliveryRejections and complaints monitoredCIE-0136 · Method and referencesBounces, reputation and failure causes documented
Editorial maintenancePage tied to need and ownerCIE-0137 · Method and referencesPurpose, audience, source and owner recorded
Editorial maintenanceReview date and triggers setCIE-0138 · Method and referencesDeadline and changes in facts, service or policy tracked
Editorial maintenanceLifecycle decision documentedCIE-0139 · Method and referencesKeep, correct, merge or retire with reason
Editorial maintenanceRemoval and links checkedCIE-0140 · Method and referencesRedirects, internal references and language versions retested
Community moderationRules visible and actionableCIE-0141 · Method and referencesProhibited behaviors, actions and appeal path published
Community moderationPriorities and escalation definedCIE-0142 · Method and referencesUrgency, owner, channel and timing by scenario
Community moderationSensitive decisions reviewedCIE-0143 · Method and referencesRemoval, blocking, reporting and responses recorded
Community moderationScenarios rehearsedCIE-0144 · Method and referencesComplaint, threat and moderation-error exercise with correction
Real-world performanceSlow interactions grouped by journey and componentCIE-0145 · Method and referencesSegmented INP data and a reproduction scenario on an affected device
Real-world performanceUnexpected visual shifts checked in late statesCIE-0146 · Method and referencesCLS sample covering media, advertising and error loading
Real-world performanceCache tested for a sensitive changeCIE-0147 · Method and referencesPrice, stock, permission or publication test with measured propagation delay
Real-world performanceServer wait separated from browser renderingCIE-0148 · Method and referencesTTFB, cache, request and rendering timeline for priority pages
Interface securityAccess to each object enforced by the serviceCIE-0149 · Method and referencesRead and write tests using an object belonging to another account
Interface securityOld API versions inventoried before retirementCIE-0150 · Method and referencesConsumer list, migration deadline and remaining traffic
Interface securityRetries bounded during dependency failureCIE-0151 · Method and referencesTest of attempt count, timing, load and final failure
Interface securitySigned webhooks checked against replayCIE-0152 · Method and referencesTests with invalid signature, old timestamp and already processed identity
AI answer qualityUnanswerable questions included in evaluationCIE-0153 · Method and referencesDocumented cases and abstention rate checked after corpus changes
AI answer qualityRetrieval and answer faithfulness measured separatelyCIE-0154 · Method and referencesDocument relevance judgments and review of generated claims
AI answer qualityModel and corpus changes replayed on the same casesCIE-0155 · Method and referencesComparable results by version and investigation of regressions
AI answer qualityAgent tools restricted by actionCIE-0156 · Method and referencesAllowlist, permissions, approvals and denials tested for every tool
Catalog reliabilityStock update delay measured by channelCIE-0157 · Method and referencesTimestamps compared across source, product page, cart and external feed
Catalog reliabilityVariant selection updates every attributeCIE-0158 · Method and referencesTests of images, price, dimensions, availability and structured offer
Catalog reliabilityStockout and promotion exercised through checkoutCIE-0159 · Method and referencesDated scenarios showing consistent display, selection and final result
Catalog reliabilityData correction propagated from its sourceCIE-0160 · Method and referencesCatalog incident traced through corrected page, feed and markup
Journeys and deliveryFocus returns after error or dialog closureCIE-0161 · Method and referencesRecorded keyboard journey showing focus position and task resumption
Journeys and deliveryForm constraints known before submissionCIE-0162 · Method and referencesTest of help, accepted formats, validation and retained entries
Journeys and deliveryPermanent and temporary email bounces separatedCIE-0163 · Method and referencesSample of codes, causes and retry or removal decisions
Journeys and deliveryURL migration checked from old linksCIE-0164 · Method and referencesRedirect map, final responses, canonical and internal links retested
GraphQL securityObject and field permissions testedCIE-0165 · Method and referencesAllowed and denied cases for each role on cross-owned objects
GraphQL securityQuery cost boundedCIE-0166 · Method and referencesDepth, breadth, pagination and aliases checked on real queries
GraphQL securityErrors and introspection configuredCIE-0167 · Method and referencesPublic responses avoid sensitive detail; schema exposure decided
GraphQL securityAbuse and denials observableCIE-0168 · Method and referencesLoad and permission tests correlated with privacy-aware logs
Product variantsEach variant has stable identityCIE-0169 · Method and referencesIdentifier, distinguishing attributes and group checked in page and markup
Product variantsURL selects the intended variantCIE-0170 · Method and referencesDirect link tested with matching image, price, stock and cart action
Product variantsPrice and stock sources synchronizedCIE-0171 · Method and referencesDiscrepancies and delay measured across catalog, page, cart and feed
Product variantsStockouts and changes replayedCIE-0172 · Method and referencesUnavailable variants, promotions and substitutions tested without phantom offers
Field web metricsField data segmentedCIE-0173 · Method and referencesURL or group, device, period and population defined before comparison
Field web metricsINP tied to an interactionCIE-0174 · Method and referencesSlow actions reproduced with trace and responsible component
Field web metricsLCP and CLS attributed to elementsCIE-0175 · Method and referencesLargest element and unexpected shifts located on representative pages
Field web metricsFix tracked in field and labCIE-0176 · Method and referencesSame journey and segments measured before and after with documented limits
Social listeningCollection scope recordedCIE-0177 · Method and referencesSources, terms, languages, period and coverage gaps documented
Social listeningSignal deduplicated and contextualizedCIE-0178 · Method and referencesOriginal post, copies, apparent author and date separated
Social listeningFacts separated from interpretationCIE-0179 · Method and referencesIndependent sources, contrary evidence and confidence recorded
Social listeningUrgent cases routed and closedCIE-0180 · Method and referencesSeverity, owner, response time, action and review tracked
OAuth and OIDCCode flow and PKCE checked in deployed configurationCIE-0181 · Method and referencesVerifier, replayed-code and unregistered-redirect tests
OAuth and OIDCToken audience and issuer checkedCIE-0182 · Method and referencesRejection of valid tokens meant for another service or provider
OAuth and OIDCBusiness permissions tested by object and operationCIE-0183 · Method and referencesCross-account and cross-role cases with denial results
OAuth and OIDCRevocation exercised across sessions and tokensCIE-0184 · Method and referencesAccess-removal timeline after departure or role change
Prompt injectionUntrusted inputs and tools mappedCIE-0185 · Method and referencesChannels, sources, tools and trust-boundary inventory
Prompt injectionForbidden effects denied outside the modelCIE-0186 · Method and referencesPermission and argument tests confirming absence of effects
Prompt injectionAdversarial cases isolated from real accessCIE-0187 · Method and referencesSimulated environment with markers and recorded versions
Prompt injectionRegressions and false refusals trackedCIE-0188 · Method and referencesResults replayed after model, source or tool changes
Third-party scriptsLoading chain observed by journeyCIE-0189 · Method and referencesInitial and downstream requests by device and collection choice
Third-party scriptsTags connected to purpose and approvalCIE-0190 · Method and referencesRegister with owner, usefulness and publishing permissions
Third-party scriptsData access and cost verifiedCIE-0191 · Method and referencesObserved flows and journey comparison with and without the script
Third-party scriptsRemoval and provider outage testedCIE-0192 · Method and referencesWorking journey with no remaining indirect loading
Data reliabilityMetric contract and lineage availableCIE-0193 · Method and referencesDefinition, unit, time zone, source, transformations and history
Data reliabilityFreshness and completeness measured separatelyCIE-0194 · Method and referencesLatest processed event and reconciliation of expected items
Data reliabilityValues reconciled on known casesCIE-0195 · Method and referencesSource-to-output sample with filter and join rules
Data reliabilityReplay and partial status explicitly handledCIE-0196 · Method and referencesDuplicate-free correction and visible chart quality status
Payment recoveryPayment and order states separatedCIE-0197 · Method and referencesTransitions and authoritative source documented by payment method
Payment recoveryUncertain response checked before another chargeCIE-0198 · Method and referencesTimeout test checking the existing operation
Payment recoveryNotifications verified and deduplicatedCIE-0199 · Method and referencesSignature, repeat and reversed-order tests without duplicate fulfilment
Payment recoveryDiscrepancies reconciled with the providerCIE-0200 · Method and referencesUncertain-case queue with decision, owner and closure evidence
Editorial mediaMedia role and provenance documentedCIE-0201 · Method and referencesOrigin, status, use conditions and affected pages
Editorial mediaSynthetic illustrations disclosed to readersCIE-0202 · Method and referencesVisible distinction between fictional scenes and documentary evidence
Editorial mediaRole-appropriate alternatives and explained diagramsCIE-0203 · Method and referencesRole-based alt and textual description of complex relationships
Editorial mediaDelivered variants checked on mobileCIE-0204 · Method and referencesDimensions, bytes, readability, crop and loading checked
AI regressionReference set separate from optimisationCIE-0205 · Method and referencesProvenance and versions of development and test sets
AI regressionPaired comparison retainedCIE-0206 · Method and referencesIdentical input, configurations and outcomes for both versions
AI regressionSensitive losses separately reviewedCIE-0207 · Method and referencesSegment outcomes and blocking-case adjudication
AI regressionConfiguration rollback exercisedCIE-0208 · Method and referencesVerified restoration of model, tools and sources
Measurement uncertaintyRates accompanied by countsCIE-0209 · Method and referencesVisible numerator, denominator and unit
Measurement uncertaintyInterval assumptions and method explicitCIE-0210 · Method and referencesConfidence level, method and independence reviewed
Measurement uncertaintyCoverage and bias separate from precisionCIE-0211 · Method and referencesAbsent populations and collection limitations documented
Measurement uncertaintyInconclusive conclusion permittedCIE-0212 · Method and referencesReport without equating uncertainty to zero effect
Campaign linksShared UTM convention across publishersCIE-0213 · Method and referencesDictionary and stable campaign identifier
Campaign linksLinks checked after redirectsCIE-0214 · Method and referencesFinal URL and actually retained values
Campaign linksPersonal data excluded from URLsCIE-0215 · Method and referencesReview of published fields and parameters
Campaign linksDistribution and acquisition counters reconciledCIE-0216 · Method and referencesDocumented definitions, periods and discrepancies
Supplier portabilityTask-based exit scope definedCIE-0217 · Method and referencesAssets, essential functions and acceptable degradation
Supplier portabilityRepresentative export verifiedCIE-0218 · Method and referencesRelationships, metadata and attachments retrieved
Supplier portabilityExternal reconstruction testedCIE-0219 · Method and referencesCritical task completed in an isolated environment
Supplier portabilityEffort and cutover documentedCIE-0220 · Method and referencesMeasured or estimated costs, order and rollback
Catalog searchCatalog query set reviewedCIE-0221 · Method and referencesIntents, identifiers and expected results
Catalog searchFacet attributes normalisedCIE-0222 · Method and referencesCoherent units, unknown values and variants
Catalog searchFilters and empty states accessibleCIE-0223 · Method and referencesRemoval, keyboard and back navigation tested
Catalog searchFacet crawling policy explicitCIE-0224 · Method and referencesUseful combinations, status and canonical checked
Webhook processingAuthenticity verified before effectsCIE-0225 · Method and referencesSignature and context denial tests with no actions
Webhook processingDurable receipt before acknowledgmentCIE-0226 · Method and referencesQueue failure test and receipt state
Webhook processingConcurrent repeats without duplicate effectsCIE-0227 · Method and referencesBusiness key and simultaneous-worker test
Webhook processingMissing events reconciled and replayedCIE-0228 · Method and referencesError queue, source comparison and closure evidence
URL migrationInventory includes media and filesCIE-0229 · Method and referencesDiscovery sources and scope limitations
URL migrationJustified mapping for every old URLCIE-0230 · Method and referencesRelevant destination or explicit removal
URL migrationRedirects and signals alignedCIE-0231 · Method and referencesFinal status, links, canonical, hreflang and sitemap
URL migrationCutover monitoring operationalCIE-0232 · Method and referencesErrors, essential tasks and correction owner
Social accountsOfficial accounts and owners inventoriedCIE-0233 · Method and referencesURL, platform, owner and deputy
Social accountsAccess reviewed after departuresCIE-0234 · Method and referencesRoles and integrations checked without copying secrets
Social accountsRecovery simulated without real access lossCIE-0235 · Method and referencesProcedure and contacts located by a deputy
Social accountsImpersonation separated from compromiseCIE-0236 · Method and referencesFacts, trusted channel and closure documented
Dialogs and keyboardsNamed dialog and useful initial focusCIE-0237 · Method and referencesKeyboard opening and announced heading
Dialogs and keyboardsModal navigation and inert background verifiedCIE-0238 · Method and referencesTab, Shift+Tab and no outside interaction
Dialogs and keyboardsClosing and logical return exercisedCIE-0239 · Method and referencesEscape, button and missing-trigger tests
Dialogs and keyboardsLong states and errors tested at zoomCIE-0240 · Method and referencesNarrow-screen and assistive-technology acceptance
RAG accessPermissions enforced before model exposureCIE-0241 · Method and referencesServer decision and unauthorised-group test
RAG accessHybrid retrieval and citations coveredCIE-0242 · Method and referencesVector, lexical and direct-file tests
RAG accessCaches isolated by access contextCIE-0243 · Method and referencesSame-question replay with two distinct scopes
RAG accessRevocation replayed on an existing conversationCIE-0244 · Method and referencesAccess-removal trace and refusal after invalidation
Observable cohortsInclusion and return specified separatelyCIE-0245 · Method and referencesSpecification and member examples
Observable cohortsImmature horizons distinguished from zeroCIE-0246 · Method and referencesMaturity mask and cutoff
Observable cohortsCounts displayed alongside ratesCIE-0247 · Method and referencesNumerator, denominator and period per cohort
Observable cohortsIdentity and collection breaks documentedCIE-0248 · Method and referencesChange log and cross-device limitations
Influence evidenceBrief and criteria set before publicationCIE-0249 · Method and referencesObjective, audience and measurement period
Influence evidenceCommercial intent checked on actual contentCIE-0250 · Method and referencesReadable evidence of disclosure and advertiser
Influence evidenceDeliverables and reuse rights recordedCIE-0251 · Method and referencesPublished URL, approved version and usage scope
Influence evidenceAttribution separated from causal effectCIE-0252 · Method and referencesMethod, exclusions and evidence-limited conclusion
Project acceptanceCriteria connected to user tasksCIE-0253 · Method and referencesNeed, expectation and end-to-end scenario
Project acceptanceOutcomes separated from unexecuted trialsCIE-0254 · Method and referencesPassed, failed and untested with reasons
Project acceptanceExceptions explicitly decidedCIE-0255 · Method and referencesImpact, owner, reason and deadline
Project acceptanceHandover and recovery included in acceptanceCIE-0256 · Method and referencesDocumentation and a task replayed by support
Inventory reservationsPhysical and sellable states distinguishedCIE-0257 · Method and referencesDictionary and example per location
Inventory reservationsReservation and release definedCIE-0258 · Method and referencesPayment, cancellation and return transitions
Inventory reservationsLast unit tested concurrentlyCIE-0259 · Method and referencesTwo requests and one verified business allocation
Inventory reservationsChannel inventories reconciledCIE-0260 · Method and referencesMovements, delays and justified corrections
HTTP cachingHTTP and application layers inventoriedCIE-0261 · Method and referencesCaches and policy for each response
HTTP cachingCache directives used according to their meaningCIE-0262 · Method and referencesno-cache, private and no-store checked on responses
HTTP cachingTwo-account isolation exercisedCIE-0263 · Method and referencesFictional markers at shared URIs and warm caches
HTTP cachingInvalidation after access changes testedCIE-0264 · Method and referencesRevocation and absence of stale exposed content
JSON-LD acceptanceProperties connected to visible contentCIE-0265 · Method and referencesMarkup-to-page-evidence correspondence
JSON-LD acceptanceSyntax, vocabulary and feature support distinguishedCIE-0266 · Method and referencesValidation results and eligibility limits
JSON-LD acceptanceDates, prices and authors consistentCIE-0267 · Method and referencesCommon source and representation comparison
JSON-LD acceptanceSupport reviewed after documentation changesCIE-0268 · Method and referencesDated register without rich-result promises
Accessible videoAudio and visual needs planned in the scriptCIE-0269 · Method and referencesInformation inventory and necessary alternatives
Accessible videoCaptions reviewed and synchronizedCIE-0270 · Method and referencesNames, numbers, useful sounds and speakers checked
Accessible videoCrops and languages checked after editingCIE-0271 · Method and referencesSmall-screen acceptance and reviewed translation
Accessible videoAccessible alternative available on publicationCIE-0272 · Method and referencesWorking link and comprehension without an imposed modality
Motion and pauseMotion inventoried by triggerCIE-0273 · Method and referencesCSS, scripts, scrolling and media recorded
Motion and pauseReduced-motion preference exercisedCIE-0274 · Method and referencesLoading and live preference changes tested
Motion and pausePause and interaction criteria distinguishedCIE-0275 · Method and referencesWCAG 2.2.2 and 2.3.3 conditions documented
Motion and pauseFinal state reliable without animationCIE-0276 · Method and referencesTask, progress and error feedback verified
Structured extractionShape and factual fidelity checked separatelyCIE-0277 · Method and referencesVersioned schema, source passages and business rejections tested
Time and cutoffsPeriods and late events reconciledCIE-0278 · Method and referencesTime zone, boundaries, cutoff and revisions documented
Email preferencesOpt-out enforced through sendingCIE-0279 · Method and referencesUnsubscribe tested across imports, segments and queued campaigns
Architecture decisionsChoices and review triggers traceableCIE-0280 · Method and referencesOptions, constraints, consequences and review triggers retained
Review provenanceOrigin, moderation and rating consistentCIE-0281 · Method and referencesDates, rejection reasons and visible aggregates reconciled
API paginationComplete reading and recovery exercisedCIE-0282 · Method and referencesOrdering, continuation, permissions and exported identifiers checked
Web paginationFinal pages reachable through linksCIE-0283 · Method and referencesDistinct URLs, canonical URLs and script-free journeys tested
Social indicatorsComparisons use stable definitionsCIE-0284 · Method and referencesUnits, denominators, populations and periods displayed
Status messagesAction outcomes perceptible without losing contextCIE-0285 · Method and referencesAnnouncement, focus, persistence and recovery tested with assistance
Shared caching: test privacy, variants and invalidationInspect effective rules · Test separation between users · Exercise version correctionCIE-0286 · Method and referencesResponse captures for two fictional accounts, signed-out state and purge after a change
URL migration: prepare mappings and test redirectsChoose relevant destinations · Test responses and signals · Check journeys after switchingCIE-0287 · Method and referencesOld URL, final target, language, HTTP status and journey result mapping
Progressive releases: stop criteria and rollbackBuild a useful comparison · Set expansion conditions · Exercise complete recoveryCIE-0288 · Method and referencesTest record with population, stop criteria, recovered version and persistent effects
OCR: validate document reading before automationMeaning and source defined — Check omissions, numbers and reading order before transcription feeds search or decisions.CIE-0289 · Method and referencesIdentified source, version, scope and owner
OCR: validate document reading before automationAcceptance executed — Build a readable reference · Test consequential errors · Check structureCIE-0290 · Method and referencesInputs, expected result, observed result and correction
OCR: validate document reading before automationBoundary and handling explicit — No. Check fields whose errors change the outcome; an overall score can conceal an amount error.CIE-0291 · Method and referencesRejected or ambiguous cases, decision and recovery owner
Missing data: distinguish absence, zero and estimationMeaning and source defined — Prevent silent replacement of absent values from changing the meaning of metrics.CIE-0292 · Method and referencesIdentified source, version, scope and owner
Missing data: distinguish absence, zero and estimationAcceptance executed — Check the denominator · Compare coverage · Document estimationCIE-0293 · Method and referencesInputs, expected result, observed result and correction
Missing data: distinguish absence, zero and estimationBoundary and handling explicit — Only when the business definition establishes that absence actually means zero. Otherwise the result changes meaning.CIE-0294 · Method and referencesRejected or ambiguous cases, decision and recovery owner
Campaign QR codes: verify the printed material and destinationMeaning and source defined — Test the path from print to digital service, including redirects and campaign retirement.CIE-0295 · Method and referencesIdentified source, version, scope and owner
Campaign QR codes: verify the printed material and destinationAcceptance executed — Test final printing · Inspect the journey · Inspect circulated materialCIE-0296 · Method and referencesInputs, expected result, observed result and correction
Campaign QR codes: verify the printed material and destinationBoundary and handling explicit — Readability does not validate the destination. Compare domain and action with the material register.CIE-0297 · Method and referencesRejected or ambiguous cases, decision and recovery owner
Retiring a digital service: remaining needs, data and handoverMeaning and source defined — Organise closure without abandoning ongoing cases, users or retention responsibilities.CIE-0298 · Method and referencesIdentified source, version, scope and owner
Retiring a digital service: remaining needs, data and handoverAcceptance executed — Resolve open cases · Prepare data · Inform and test handoversCIE-0299 · Method and referencesInputs, expected result, observed result and correction
Retiring a digital service: remaining needs, data and handoverBoundary and handling explicit — No. Processing, integrations, data or requests can remain active. Verify these dependencies separately.CIE-0300 · Method and referencesRejected or ambiguous cases, decision and recovery owner
Subscriptions: connect cancellation, billing and access rightsMeaning and source defined — Verify what changes after a stop request, immediately or at a planned period boundary.CIE-0301 · Method and referencesIdentified source, version, scope and owner
Subscriptions: connect cancellation, billing and access rightsAcceptance executed — Connect systems · Test period boundaries · Confirm clearlyCIE-0302 · Method and referencesInputs, expected result, observed result and correction
Subscriptions: connect cancellation, billing and access rightsBoundary and handling explicit — Not automatically. Effects depend on contract, applicable rules and selected processing; verify states separately.CIE-0303 · Method and referencesRejected or ambiguous cases, decision and recovery owner
Asynchronous API jobs: track status, resume and cancelMeaning and source defined — Separate accepted requests, started processing and final outcomes of long-running operations.CIE-0304 · Method and referencesIdentified source, version, scope and owner
Asynchronous API jobs: track status, resume and cancelAcceptance executed — Protect tracking · Bound status queries · Test concurrent cancellationCIE-0305 · Method and referencesInputs, expected result, observed result and correction
Asynchronous API jobs: track status, resume and cancelBoundary and handling explicit — No. Processing is not necessarily complete. The client needs access to an authoritative outcome.CIE-0306 · Method and referencesRejected or ambiguous cases, decision and recovery owner
Sitemaps: verify URLs, shards and lastmod datesMeaning and source defined — Check the file offered to crawlers beyond simple XML syntax validity.CIE-0307 · Method and referencesIdentified source, version, scope and owner
Sitemaps: verify URLs, shards and lastmod datesAcceptance executed — Check contents and responses · Prepare partitioning · Make lastmod meaningfulCIE-0308 · Method and referencesInputs, expected result, observed result and correction
Sitemaps: verify URLs, shards and lastmod datesBoundary and handling explicit — No. It helps discovery. Availability, directives and content quality remain separate.CIE-0309 · Method and referencesRejected or ambiguous cases, decision and recovery owner
Community polls: interpret who responds and who is missingMeaning and source defined — Use answers as a documented signal without automatically treating them as the opinion of an entire audience.CIE-0310 · Method and referencesIdentified source, version, scope and owner
Community polls: interpret who responds and who is missingAcceptance executed — Test the question · Document recruitment · Publish countsCIE-0311 · Method and referencesInputs, expected result, observed result and correction
Community polls: interpret who responds and who is missingBoundary and handling explicit — Volume alone does not correct participant selection. Examine who could see the question and who chose to answer.CIE-0312 · Method and referencesRejected or ambiguous cases, decision and recovery owner
Localized input: resolve number and date ambiguityMeaning and source defined — Accept and confirm values without silently changing separators, units or date order.CIE-0313 · Method and referencesIdentified source, version, scope and owner
Localized input: resolve number and date ambiguityAcceptance executed — Retain raw input · Confirm the interpreted value · Test interactionsCIE-0314 · Method and referencesInputs, expected result, observed result and correction
Localized input: resolve number and date ambiguityBoundary and handling explicit — It formats values. Define and test parsing rules for your field separately.CIE-0315 · Method and referencesRejected or ambiguous cases, decision and recovery owner

How to use the matrix

  1. 01

    Score facts

    Assign a level from observable evidence, not an intention or a purchased tool.

  2. 02

    Connect to risk

    Prioritise controls that protect a critical asset, sensitive decision or important customer journey.

  3. 03

    Name an owner

    Give every action an owner, due date and simple validation criterion.

  4. 04

    Run it again

    Retain evidence and reassess after major change, an incident or at least annually.

Illustrative example

Turn a control into a verifiable decision

Suppose an ordering service depends on an email provider. Use the matrix to examine this particular service: its importance, available evidence and the action to test. The levels below illustrate a method, not an assessment of any organisation.

01

Set the scope

Order confirmation, sender identity, supplier agreement and fallback channel each have a separate owner and business effect.

02

Score with evidence

A written recovery procedure that has never been tried is not a managed control. Keep the date, result, failure and fix from the latest test.

03

Make the decision

If an outage blocks an obligation to the customer, prioritise a fallback channel and set a switchover test. Record the owner and review date.

Do not turn summed scores into a universal label. The same level can hide different impacts depending on assets, affected people and dependencies; keep that context beside the score.

References: data, uses and limitations

Documentation reviewed on .

All references · 25
References: data, uses and limitations
Source and purposeVerified data or benchmarkHow to use itLimitation to retain
FIRST · CVSS

Describe technical vulnerability severity using an explicit method and vector.

CVSS 4.0 scores run from 0.0 to 10.0. Base, Threat, Environmental and Supplemental metric groups serve different purposes. Retain the score version, vector and date. Compare it with the installed version, access paths and business consequences before ordering remediation.

Explore the method →

A high score is not evidence of exploitation; a low score does not mean a service has no risk.
FIRST · EPSS

Estimate exploitation probability for a published CVE.

The model looks ahead 30 days. Its score is a probability; its percentile ranks that score relative to other CVEs. Record the data date and distinguish probability from percentile. Add asset exposure and confirmed exploitation evidence.

Explore the method →

The model does not predict harm to your organisation. Low probability does not cancel a critical exposure.
CISA · Known Exploited Vulnerabilities

Identify vulnerabilities listed by CISA as known to be exploited.

The catalogue includes CVE, product, date added and required action. Its official repository also provides the data schema. Check applicability to your products and retain the access date. Review the requested action and vendor advisory before confirming remediation.

Explore the method →

Absence from the catalogue does not establish safety. Administrative deadlines in it are not automatically binding on every organisation.
CVE Program

Link discussions to the same vulnerability record.

A JSON schema defines the CVE record format. An identifier and the published contents of its record are distinct things. Open the record and references; check its state, described affected versions and supplier information. Keep the identifier in action tracking.

Explore the method →

A CVE identifier is neither a severity score nor proof that your installation is affected.
MITRE · Common Weakness Enumeration

Name classes of software and hardware weakness.

A CWE describes a weakness that can contribute to vulnerabilities. It does not represent a particular incident. Connect the weakness to the observed mechanism: input, processing and missing control. Use it to fix the cause and plan regression tests.

Explore the method →

A keyword in a report alone does not establish the correct CWE classification.
NIST · Cybersecurity Framework

Structure the outcomes expected from a cybersecurity programme.

CSF 2.0 has six functions: Govern, Identify, Protect, Detect, Respond and Recover. It does not prescribe a single way to achieve outcomes. Describe current and target profiles with evidence, gaps and owners. Connect each priority to the services it helps protect.

Explore the method →

Mapping to the framework is neither certification nor proof that every control works.
NIST · SP 800-61 Rev. 3

Prepare incident response within cybersecurity risk management.

Revision 3 was published in April 2025 and supersedes Revision 2. It is a CSF 2.0 Community Profile. Rehearse containment decisions, evidence preservation, communication and recovery. Compare planned actions with evidence produced during the exercise.

Explore the method →

Reading the guide does not validate a local plan. Contacts, emergency access and dependencies need local testing.
FIRST · Traffic Light Protocol

Indicate who may receive redistributed information.

TLP 2.0 uses RED, AMBER, GREEN and CLEAR; AMBER+STRICT restricts sharing to the recipient organisation. Labels must not be translated. Keep the marking with the information and check recipients before forwarding. Ask the source to clarify any ambiguity.

Explore the method →

TLP is neither a formal classification nor a reuse licence. It does not guarantee content accuracy.
OASIS · STIX 2.1

Describe threat intelligence through structured objects and relationships.

STIX 2.1 is an OASIS Standard dated 10 June 2021. It defines objects, properties and JSON serialisation. Keep identifiers, dates, provenance and relationships. Check that the recipient interprets the same object type and validity period.

Explore the method →

A syntactically valid object can still be stale, misattributed or weakly supported.
OASIS · TAXII 2.1

Exchange threat intelligence through an application protocol.

TAXII 2.1 is an OASIS Standard dated 10 June 2021. It includes service discovery and access to collections. Test authentication, collection permissions, pagination and recovery after interruption. Record which objects were actually received and processed.

Explore the method →

TAXII transports data; it replaces neither the content model nor assessment of reliability.
SPDX · Specifications

Describe components and information in a software bill of materials.

The official specifications page distinguishes SPDX 3.0 from earlier versions such as 2.3. Document version affects schema and tool compatibility. Request format, version, build scope and component identifiers. Compare the bill of materials with the delivered artefact.

Explore the method →

A bill of materials alone proves neither vulnerability absence, dependency completeness nor compliance with every licence.
OWASP · CycloneDX

Exchange bills of materials and supply-chain information.

The official overview dates specification 1.7 to 21 October 2025 and documents JSON, XML and Protobuf. Check version, component references and dependency links. Retain the connection between the bill of materials, build and deployed product.

Explore the method →

Changing format does not fix missing components. A descriptive inventory and a vulnerability impact assessment answer different questions.
MITRE ATT&CK

Connect observations with adversary tactics and techniques.

ATT&CK is a knowledge base grounded in observations. Its domains include Enterprise, Mobile and ICS. Connect a technique with a trace and detection hypothesis. Distinguish having a log source from actually testing detection.

Explore the method →

A shared technique cannot establish actor attribution. Technique coverage counts do not fully measure security.
MITRE ATLAS

Examine documented tactics, techniques and cases involving AI systems.

The official repository publishes ATLAS tactics, techniques and case-study data. They support analysis of the actual deployed system. Select scenarios matching your application’s data, interfaces and tools. Test permissions and consequences, not only model responses.

Explore the method →

A technique catalogue is neither an exhaustive coverage guarantee nor a test result for your system.
NIST · AI Risk Management Framework

Organise management of AI-related risks.

The AI RMF Core is organised around Govern, Map, Measure and Manage. It is a voluntary risk-management framework. Define intended use, affected people and error consequences. Connect each risk to an evaluation, owner and stop or recovery mechanism.

Explore the method →

The framework certifies neither a model nor an application. Using it does not remove the need to examine applicable requirements.
OWASP · LLM Top 10

Prepare tests for language-model application risks.

The 2025 edition includes Prompt Injection, Sensitive Information Disclosure and Excessive Agency. Turn a risk into an observable scenario: hostile document, restricted data or out-of-scope tool. Record expected behaviour and evidence of refusal.

Explore the method →

A risk list is not a complete assessment. Input filtering alone does not establish authorisation for every action.
W3C · WCAG 2.2

Evaluate accessibility criteria for web content.

WCAG 2.2 is a W3C Recommendation. Success criteria have A, AA and AAA levels. Define tasks, pages and states, then combine inspection, keyboard, zoom and relevant assistive technology. Keep reproduction steps for barriers.

Explore the method →

An automated scanner does not establish conformity of a complete journey. Evaluation must cover interactive states and actual content.
Google · Core Web Vitals

Distinguish loading, responsiveness and visual stability.

Good thresholds are LCP ≤ 2.5 s, INP ≤ 200 ms and CLS ≤ 0.1 at the 75th percentile, segmented by mobile and desktop. Separate field measurement from laboratory tests. Record period, URL, device, population and sample size before comparing changes.

Explore the method →

These thresholds are not measured results for this site. A good lab score alone does not establish visitor experience.
Google · AI features and your website

Understand inclusion in Google Search AI features.

Google states that AI Overviews and AI Mode add no special technical requirements beyond applicable Search fundamentals. Check page access, indexability, snippet eligibility, links and useful textual content. Measure observed appearance, clicks and business outcomes separately.

Explore the method →

Eligibility guarantees neither crawling, indexing nor display. This documentation concerns Google Search, not every AI assistant.
Google · Structured data

Describe page contents through machine-readable markup.

Structured data helps search engines understand content. Marked properties should correspond to information actually present on the page. Choose a type matching the page and verify names, dates, relationships and sources. Check final rendering rather than only the template.

Explore the method →

Valid markup alone does not guarantee a rich result. It replaces neither the content nor feature-specific eligibility conditions.
C2PA · Content Credentials

Describe and verify certain content provenance information.

C2PA specification 2.4 defines manifests, assertions and cryptographic binding mechanisms associated with media. Examine what the manifest asserts, who signed it and whether validation succeeds. Test preservation after transformations and distribution.

Explore the method →

Validated provenance does not establish the truth of a scene. Absence of a manifest does not demonstrate a fake.
ICANN · Registration Data Lookup

Consult available domain registration information.

RDAP is the registration data access protocol. ICANN Lookup provides access to available public registration data. Keep the exact domain, consultation date and result. Distinguish registrar, technical service and the entity operating a website.

Explore the method →

Data may be redacted or limited. Domain information alone cannot attribute content or an operation to a person.
NIST · Post-quantum cryptography

Identify standards relevant to cryptographic transition.

NIST distinguishes FIPS 203 for ML-KEM, FIPS 204 for ML-DSA and FIPS 205 for SLH-DSA. Key encapsulation and signatures are different functions. Inventory protocols, libraries, keys and dependencies. Ask which versions are actually implemented and test interoperability, performance and rollback.

Explore the method →

Compare post-quantum parameters and estimate their volumes →

Having a standardised algorithm does not establish security of the complete integration or a universal migration deadline.
NIST · Privacy Framework

Examine risks to people arising from data processing.

The Privacy Framework is a voluntary privacy risk-management tool. It is distinct from a universal legal compliance checklist. Describe actual processing: data, purposes, recipients, access and retention. Compare documents, settings and deletion or retrieval tests.

Explore the method →

Using the framework alone does not determine compliance with applicable law. Processing context and jurisdiction still need examination.
MDN · Cookie boundaries

Understand session-cookie scope and SameSite boundaries.

Secure, HttpOnly, SameSite and the __Host- prefix address different risks. A site can include multiple origins. Test external navigation, subdomains, provider returns and authenticated operations separately.

Explore the method →

Cookie configuration does not replace CSRF checks or server-side authorisation.