国际网络安全门户 / DIRECTORY
公共机构、响应团队、企业与研究。寻找适合您所在国家和需求的信息源。
快照中的资料数 : 883 ·
国家和领域不能确定其服务范围。请在官方资料中确认服务条件。 FIRST ↗
Name classes of software and hardware weakness.
文档核查日期
Prepare incident response within cybersecurity risk management.
文档核查日期
Qualifying a signal, preserving investigative material and restoring a service answer different questions. CSF 2.0 distinguishes recovery initiation, integrity of restoration assets, validation of restored assets and the end of recovery. These are outcomes to document, not certification or one mandatory procedure.
The twelve entries below are a selected, paraphrased part of CSF 2.0. Evidence columns, timelines and injects are original teaching proposals. They do not replace a local plan and imply no universal timing, severity level or authority. SP 800-61 Revision 3 has been final since April 2025 and supersedes Revision 2.
Explore NIST outcomes and the timeline →
Identifiers and outcome meanings come from CSF 2.0; SP 800-61r3 adds incident response and recovery recommendations. Evidence tables, times and scenarios are educational, with no client results, certification or actual notification.
References reviewed
Describe threat intelligence through structured objects and relationships.
文档核查日期
Structured intelligence retains provenance and a version history. For an actionable OSINT note, separate collected facts, the producer’s assertion and the local conclusion, then state what still needs confirmation.
Version note: at review time the OASIS latest-stage URL points to a document dated 2 April 2025 titled STIX 2.1 Errata 01, incorporating Draft 01. Its draft errata status is retained in the citation; it is not presented as a newly approved final version. Agree marking encodings with the recipient and check the edition actually used.
Read the STIX, observations and TLP sharing reference →
Sources checked on
Exchange threat intelligence through an application protocol.
文档核查日期
Describe components and information in a software bill of materials.
文档核查日期
Exchange bills of materials and supply-chain information.
文档核查日期
Evaluate accessibility criteria for web content.
文档核查日期
此语言版本的详细参考说明以英语提供。
WCAG 2.2 is connected here to a selection of 17 form-related criteria: labels, errors, keyboard, focus, status messages and authentication. Understanding documents and WAI tutorials are informative. The calculator compares an opaque sRGB pair with contrast thresholds; it performs neither a journey audit nor a complete evaluation of exceptions.
Open the WCAG review grid and contrast calculator →
W3C · Web Content Accessibility Guidelines (WCAG) 2.2 · Recommendation · 12 December 2024
Distinguish loading, responsiveness and visual stability.
文档核查日期
Understand inclusion in Google Search AI features.
文档核查日期
Google states worldwide rollout of the Search generative AI control on 31 August 2026. Its effective value may be inherited from a parent property. Record the exact property, explicit or inherited setting and observation date; do not infer the value from robots.txt alone.
The Search generative AI control does not govern model training. Google points to Google-Extended for that separate usage; Search AI exclusion does not mean general deindexing. This distinction belongs to the documented Google service and needs review when policies change.
Compare AI controls and report data →
REP rules come from RFC 9309; Google-specific details are attributed to its own documentation. Examples and the diagram are educational. Filtering performs no crawling and the tables contain no client results.
References reviewed
Describe page contents through machine-readable markup.
文档核查日期
Describe and verify certain content provenance information.
文档核查日期
A provenance report combines findings with different scopes. Signature, credential trust, content binding and scene context are separate assurances. Retain the exact asset and full report before summarising a result.
This JSON-LD representation is a derived view of C2PA data for reporting and interoperability. It is not independently verifiable or a validation input format.
Open the C2PA explorer and publication cases →
References consulted on
Identify standards relevant to cryptographic transition.
文档核查日期
Examine risks to people arising from data processing.
文档核查日期
Official Chrome permission reference: APIs, declarations and conditions for site access.
此语言版本的详细参考说明以英语提供。
Vendor reference for permission names, declarations, temporary access and API-specific requirements. The CIE guide connects a selection of 20 names to review questions. Granted settings, policies and behaviour cannot be read from a manifest alone. The reading covers activeTab, cookies, identity and nativeMessaging among others.
Read the permission directory and manifest examples →
Google Chrome · Permissions · Documentation consulted 2026-10-23; browser behaviour remains version-dependent
Edge policy documentation for managing permissions, site access and extension installation.
此语言版本的详细参考说明以英语提供。
Administrative documentation distinguishing permission blocking, runtime-host restrictions and installation rules. A blocked permission can disable an extension without uninstalling it. Policy patterns must not be confused with Chrome manifest match patterns.
Read the permission directory and manifest examples →
Microsoft Learn · Manage Microsoft Edge extensions using group policies · Enterprise policy documentation consulted 2026-10-23
SP 800-88 Revision 2: Clear, Purge and Destroy methods, sanitization program and evidence.
此语言版本的详细参考说明以英语提供。
The final Revision 2 of 26 September 2025 supersedes withdrawn Revision 1. It distinguishes technical verification from outcome validation and addresses cryptographic erase and logical storage. The FAQ of 16 July 2026 complements it. The 20 CIE-SAN references are editorial selection linked to sections, not NIST certification.
Read the methods, evidence points and annotated situations →
NIST · SP 800-88 Rev. 2 · Guidelines for Media Sanitization · Final · 2025-09-26 · consulted 2026-10-23
NIST · FAQ for SP 800-88r2 · Published 2026-07-16 · consulted 2026-10-23
The syslog Parameters registry publishes facility and severity codes as well as structured-data identifiers. This selection covers only the 24 facilities and 8 severities.
此语言版本的详细参考说明以英语提供。
IANA maintains the value registry; RFC 5424 describes the format. Notes about overlapping codes and local families help prevent assigning product meaning or incident urgency to a single number. The educational calculator uses a dated copy without accessing real logs.
Read syslog codes and try the PRI calculation →
IANA · syslog Parameters · Registry updated 2016-04-26 · consulted 2026-10-23
IETF · R. Gerhards · RFC 5424 · The Syslog Protocol · March 2009 · §6.2.1 PRI · §6 format · §8 security
The HTTP Problem Types registry associates URI, title, recommended HTTP status and reference. This dated copy contains six entries, including about:blank and three digest entries whose draft-kind references are preserved.
此语言版本的详细参考说明以英语提供。
The registry can verify a common problem identity. It lists neither every application type nor certified servers, and does not replace distinguishing received HTTP status from advisory body status. The guide workshop provides eight fictional responses for testing this reading.
Explore problem types and eight fictional responses →
IANA · HTTP Problem Types · Registry updated 2026-06-26 · consulted 2026-10-23
IETF · M. Nottingham, E. Wilde, S. Dalal · RFC 9457 · July 2023 · obsoletes RFC 7807 · §3.1, §3.2, §4.2, §5
The IANA CSP registry lists sixteen names in this snapshot with CSP2 references. The guide distinguishes that registry from fallback chains published in the CSP3 Working Draft dated 16 September 2026.
此语言版本的详细参考说明以英语提供。
IANA registration does not demonstrate browser enforcement. Twelve fetch chains, three independent checks and eight scenarios help distinguish name, fallback, mode and delivery without testing an external site.
Read CSP fallback orders and explore eight scenarios →
IANA · Content Security Policy Directives · Registry updated 2023-02-03 · consulted 2026-10-23
W3C · Content Security Policy Level 3 · Mike West, Antonio Sartori · Working Draft · 2026-09-16 · work in progress · §2.2.1, §3, §6.8.3–6.8.4, §8.1
Specification of the GraphQL language, type system and execution results.
此语言版本的详细参考说明以英语提供。
The September 2025 edition defines request errors, execution results, response paths and Non-Null propagation. The CIE dossier offers eight fictional scenarios and a limited list model. GraphQL over HTTP is separately identified as a working draft; no HTTP status is inferred from the errors field alone.
Explore GraphQL responses and nullability →
GraphQL over HTTP · Current Working Draft · Working draft consulted 2026-10-23 · may change
GraphQL Specification · September 2025 · Published edition · September 2025
Google documentation on aggregated Chrome experience data at page or origin level.
此语言版本的详细参考说明以英语提供。
CrUX describes an eligible population and aggregated metrics. The CIE dossier connects PSI thresholds, URL/origin scope, the 28-day window and comparison limits. The p75 reader uses entered values; it retrieves no CrUX data and measures no site.
Read the thresholds and try the p75 reader →
Chrome for Developers · CrUX API · Living documentation · consulted 2026-10-23
Google · About PageSpeed Insights · Living documentation · consulted 2026-10-23
GS1 references on trade-item identifiers and numeric GTIN representations.
此语言版本的详细参考说明以英语提供。
The CIE guide separates arithmetic coherence, identifier allocation and variant consistency. Modulo-10 calculation is detailed using the GS1 NZ guide; 8-, 12-, 13- and 14-position examples are sourced to GS1 Retail 1.1.0. The reader queries no registry.
Explore identifiers and check a GTIN digit →
GS1 · 2D Barcodes at Retail POS Implementation Guideline · Release 1.1.0 · ratified December 2025 · §4.3 / Table 4-2
Google Search Central · Product variant structured data · Updated 2026-09-08 · consulted 2026-10-23
Government Communications framework for organising monitoring, preparing analysis and tracking response effectiveness.
此语言版本的详细参考说明以英语提供。
Published on 29 October 2025, RESIST 3 contains six stages. Its quick reference presents ABCDE for structuring a briefing. This communication framework is neither source certification nor an automated attribution method.
Read the method and explore citation chains →
Government Communications · RESIST 3 · RESIST 3 · 2025 · consulted 2026-10-23
Government Communications · RESIST 3 quick reference · RESIST 3 · 2025 · consulted 2026-10-23
Experimentation Platform resource on sample allocation discrepancies in A/B tests.
此语言版本的详细参考说明以英语提供。
The 2020 article distinguishes assignment, execution, log processing and analysis. Its p < 0.0005 threshold concerns the ExP practice described at that date; it does not alone validate an experiment or conversion result.
Explore the allocation check and its limitations →
Microsoft Research · Diagnosing Sample Ratio Mismatch · Published 2020-09-14 · consulted 2026-10-23
NIST/SEMATECH · Binomial distribution · e-Handbook §1.3.6.6.18 · consulted 2026-10-23