YCCERT / CSIRT / SOC
YCERT
- 完整名称
- Yarix Computer Emergency Response Team
- FIRST资料所属领域
- Other commercial
- 所属组织
- Yarix S.R.L.
- 所声明的团队类型
- CSIRT
- 所声明的成立时间
- September 1, 2009
- FIRST加入时间
- September 28, 2016
数据获取日期 · FIRST
国际网络安全门户 / DIRECTORY
连接全球专业知识。
公共机构、响应团队、企业与研究。寻找适合您所在国家和需求的信息源。
FIRST资料分布 · 883
快照中的资料数 : 883 ·
- Government, Private and Public sectors
252 / 883 252 - Other commercial
207 / 883 207 - Industrial sector
95 / 883 95 - Financial sector
94 / 883 94 - ICT vendor customer base
57 / 883 57 - 未说明领域
50 / 883 50 - Government & military
46 / 883 46 - Research & education
45 / 883 45 - ISP customer base
37 / 883 37
国家和领域不能确定其服务范围。请在官方资料中确认服务条件。 FIRST ↗
YKCERT / CSIRT / SOC
YKB-CERT
- 完整名称
- YapiKredi Bank CERT
- FIRST资料所属领域
- Financial sector
- 所属组织
- YapiKredi Bank
- 所声明的团队类型
- CSIRT
- 所声明的成立时间
- January 1, 2015
- FIRST加入时间
- April 15, 2021
数据获取日期 · FIRST
YSCERT / CSIRT / SOC
YSTW-CSIRT
- 完整名称
- YSTW-CSIRT
- FIRST资料所属领域
- Financial sector
- 所属组织
- Yuanta Securities Co., Ltd.
- 所声明的团队类型
- CSIRT, SOC
- 所声明的成立时间
- December 21, 2023
- FIRST加入时间
- December 17, 2025
数据获取日期 · FIRST
Z-CERT / CSIRT / SOC
Z-CERT
- 完整名称
- Stichting Z-CERT
- FIRST资料所属领域
- Government, Private and Public sectors
- 所属组织
- -
- 所声明的团队类型
- CSIRT
- 所声明的成立时间
- November 28, 2016
- FIRST加入时间
- May 23, 2019
数据获取日期 · FIRST
ZACERT / CSIRT / SOC
ZATCA DFIR
- 完整名称
- ZATCA Digital Forensics and Incident Response Team
- FIRST资料所属领域
- Government, Private and Public sectors
- 所属组织
- Zakat, Tax, and Customs Authority - ZATCA
- 所声明的成立时间
- September 1, 2018
- FIRST加入时间
- November 20, 2024
数据获取日期 · FIRST
ZECERT / CSIRT / SOC
Zendesk CSIRT
- 完整名称
- Zendesk
- FIRST资料所属领域
- ICT vendor customer base
- 所属组织
- Zendesk
- 所声明的团队类型
- CSIRT
- 所声明的成立时间
- January 1, 2018
- FIRST加入时间
- May 23, 2019
数据获取日期 · FIRST
ZECERT / CSIRT / SOC
ZeroFox
- 完整名称
- ZeroFox
- FIRST资料所属领域
- Other commercial
- 所属组织
- ZeroFox
- 所声明的团队类型
- SOC
- 所声明的成立时间
- January 1, 2013
- FIRST加入时间
- August 19, 2026
数据获取日期 · FIRST
ZFCERT / CSIRT / SOC
ZF SOC
- 完整名称
- ZF Security Operations Center - SOC
- FIRST资料所属领域
- Industrial sector
- 所属组织
- ZF Group
- 所声明的团队类型
- SOC
- 所声明的成立时间
- January 1, 2014
- FIRST加入时间
- August 17, 2023
数据获取日期 · FIRST
ZMCERT / CSIRT / SOC
ZmCIRT
- 完整名称
- Zambia Computer Incident Response Team
- FIRST资料所属领域
- Government, Private and Public sectors
- 所属组织
- Zambia Information and Communication Technology Authority
- 所声明的团队类型
- CSIRT
- 所声明的成立时间
- September 20, 2012
- FIRST加入时间
- August 18, 2017
数据获取日期 · FIRST
ZTCERT / CSIRT / SOC
ZTE PSIRT
- 完整名称
- ZTE Product Security Incident Response Team
- FIRST资料所属领域
- ICT vendor customer base
- 所属组织
- ZTE Corporation
- 所声明的团队类型
- PSIRT
- 所声明的成立时间
- October 15, 2013
- FIRST加入时间
- January 25, 2015
数据获取日期 · FIRST
Z�CERT / CSIRT / SOC
Zürcher Kantonalbank - CSIRT
- 完整名称
- Zürcher Kantonalbank - CSIRT
- FIRST资料所属领域
- Financial sector
ZUCERT / CSIRT / SOC
ZUSO Advanced Research Team
- 完整名称
- ZUSO Advanced Research Team
- FIRST资料所属领域
- Other commercial
- 所属组织
- ZUSO Generation
- 所声明的成立时间
- April 30, 2019
- FIRST加入时间
- January 17, 2025
数据获取日期 · FIRST
ZYCERT / CSIRT / SOC
Zyxel
- 完整名称
- Zyxel Corporation
- FIRST资料所属领域
- ICT vendor customer base
- 所属组织
- Zyxel Group Corporation
- 所声明的团队类型
- PSIRT
- 所声明的成立时间
- April 21, 2021
- FIRST加入时间
- October 16, 2025
数据获取日期 · FIRST
CI公共机构
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.
- 需要保留的局限
- Absence from the catalogue does not establish safety. Administrative deadlines in it are not automatically binding on every organisation.
文档核查日期
CVSS、EPSS、KEV 与 VEX
Is the vulnerability listed as known to be exploited?
Listing does not establish that the product exists in your estate; absence does not establish safety.
Read the CVSS, EPSS, KEV and VEX reference →
Primary sources and scope
- CISA · KEV official data schema · Official CISA mirror · reviewed 2026-10-22
Catalog properties · vulnerability properties · required fields
Sources checked on
浏览 CISA KEV 目录
此语言版本的详细参考说明以英语提供。
Scope of the KEV dataset
Entries preserve the CVE identifier, vendor or project, product, dates, action and published indicators. The schema distinguishes required and optional fields; absence must not silently become a negative value.
The data’s CC0 licence grants no rights to CISA’s logo or content on linked third-party websites.
1754 记录 · 2026.10.21
官方参考资料 ↗MI研究与教育
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.
- 需要保留的局限
- A keyword in a report alone does not establish the correct CWE classification.
文档核查日期
NI公共机构
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.
- 需要保留的局限
- Reading the guide does not validate a local plan. Contacts, emergency access and dependencies need local testing.
文档核查日期
网络事件：恢复决策与证据
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 →
Primary references and limits
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.
- NIST · SP 800-61 Rev. 3 · Final · 2025-04-03
Community Profile CSF 2.0 ; remplace / supersedes Rev. 2 - NIST · SP 800-61r3 — recommandations détaillées / detailed recommendations · April 2025
Pages imprimées / printed pages 27–29, 34–35 : RS.MA, RS.AN, RC.RP, RC.CO - NIST · Cybersecurity Framework 2.0 · 2024-02-26 · NIST CSWP 29
Appendix A, printed pages 22–23 : official outcome identifiers - NIST · SP 800-184 — Guide for Cybersecurity Event Recovery · Final · 2016-12-22
Recovery planning, playbooks, testing and improvement
References reviewed
OA社区与标准
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.
- 需要保留的局限
- A syntactically valid object can still be stale, misattributed or weakly supported.
文档核查日期
STIX 指标与 TLP 共享
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 →
References and verification scope
- OASIS · STIX 2.1 · OASIS Standard · 2021-06-10
§3.2, §3.6, §4.7, §4.14, §5.2, §7.2 - OASIS · STIX 2.1 Errata 01 · Draft 01 · 2025-04-02 · OASIS Standard incorporating Draft 01 of Errata 01
Status / Citation format · draft status identified separately
Sources checked on
OA社区与标准
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.
- 需要保留的局限
- TAXII transports data; it replaces neither the content model nor assessment of reliability.
文档核查日期
OW社区与标准
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.
- 需要保留的局限
- Changing format does not fix missing components. A descriptive inventory and a vulnerability impact assessment answer different questions.
文档核查日期
GO私营部门
Google Chrome documentation · extension permissions
Official Chrome permission reference: APIs, declarations and conditions for site access.
扩展：权限与访问
此语言版本的详细参考说明以英语提供。
Google Chrome documentation · extension permissions
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
MI私营部门
Microsoft Learn · Edge extension policies
Edge policy documentation for managing permissions, site access and extension installation.
扩展：权限与访问
此语言版本的详细参考说明以英语提供。
Microsoft Learn · Edge extension policies
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
NI公共机构
NIST · SP 800-88 Rev. 2 · Media Sanitization
SP 800-88 Revision 2: Clear, Purge and Destroy methods, sanitization program and evidence.
介质：清理与证据
此语言版本的详细参考说明以英语提供。
NIST · media sanitization
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
IA公共机构
IANA · syslog Parameters
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.
syslog代码与采集证据
此语言版本的详细参考说明以英语提供。
IANA: identify a syslog code before interpreting it
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
IA公共机构
IANA · HTTP Problem Types
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.
API错误：类型、状态与证据
此语言版本的详细参考说明以英语提供。
IANA: HTTP problem types and references
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