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