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