MY공공기관
MyCERT
Incident response and security advisories in Malaysia.
국제 사이버 포털 / 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 ↗
AU공공기관
Australian Cyber Security Centre
Australian cybersecurity guidance and resources.
NC공공기관
NCSC · New Zealand
New Zealand cybersecurity guidance and information.
DG공공기관
DGSSI · Maroc
Morocco information systems security authority.
AG공공기관
Agence Nationale de la Cybersécurité · Tunisie
Tunisian national cybersecurity resources.
NG공공기관
ngCERT
Nigeria national computer emergency response team.
KE공공기관
KE-CIRT/CC
Kenya national incident response coordination.
CY공공기관
Cybersecurity Hub · South Africa
Public cybersecurity resources in South Africa.
NA공공기관
National Cybersecurity Authority · Saudi Arabia
National cybersecurity guidance and controls.
AE공공기관
aeCERT · TDRA
UAE telecommunications and cybersecurity resources.
IS공공기관
Israel National Cyber Directorate
Public national cyber directorate resources.
FI커뮤니티 및 표준
FIRST
International network of incident response teams.
CE커뮤니티 및 표준
Center for Internet Security
Security controls and benchmarks.
MI민간기업
Microsoft Security
Security research and analysis published by Microsoft.
GO민간기업
Google Threat Intelligence
Threat intelligence research publications.
UN민간기업
Unit 42 · Palo Alto Networks
Threat research and technical reports.
CI민간기업
Cisco Talos
Threat analysis and research publications.
CL민간기업
Cloudflare
Networking, security and infrastructure analysis.
FI커뮤니티 및 표준
FIRST · EPSS
Vulnerability exploitation probability model. Compare with technical severity, local exposure and business impact.
참고 자료 상세
- 확인된 데이터 또는 기준
- 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.
- 유지해야 할 한계
- The model does not predict harm to your organisation. Low probability does not cancel a critical exposure.
문서 검토일
CVSS, EPSS, KEV 및 VEX
What is the estimated probability of observing exploitation of this CVE in the next thirty days?
It does not describe compromise of your instance, its controls or business loss.
Read the CVSS, EPSS, KEV and VEX reference →
Primary sources and scope
- FIRST · EPSS Frequently Asked Questions · Living FAQ · reviewed 2026-10-22
What is EPSS? · Reading the score · Percentile · Score changes
Sources checked on
FI커뮤니티 및 표준
FIRST · CVSS
Vulnerability severity specification and calculators. A score alone does not describe organisation-specific risk.
참고 자료 상세
- 확인된 데이터 또는 기준
- 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.
- 유지해야 할 한계
- A high score is not evidence of exploitation; a low score does not mean a service has no risk.
문서 검토일
CVSS, EPSS, KEV 및 VEX
What is the technical severity under the assessed metrics?
The score proves neither exploitation nor consequences for your service.
Read the CVSS, EPSS, KEV and VEX reference →
Primary sources and scope
- FIRST · CVSS 4.0 Specification · CVSS 4.0 · document 1.2 · reviewed 2026-10-22
Overview · Assessment · Nomenclature · Supplemental Metrics
Sources checked on
CV커뮤니티 및 표준
CVE Program
Public vulnerability identifiers and records. Check products, affected versions and links to original advisories.
참고 자료 상세
- 확인된 데이터 또는 기준
- 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.
- 유지해야 할 한계
- A CVE identifier is neither a severity score nor proof that your installation is affected.
문서 검토일
NI공공기관
NIST · National Vulnerability Database
Vulnerability database and technical enrichment. Cross-check records against vendor advisories and the deployed configuration.
NI공공기관
NIST · Cybersecurity Framework
Cyber risk management framework and implementation resources. Organises intended outcomes rather than providing certification.
참고 자료 상세
- 확인된 데이터 또는 기준
- 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.
- 유지해야 할 한계
- Mapping to the framework is neither certification nor proof that every control works.
문서 검토일
사이버 사고: 복구 결정과 증거
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
10CERT / CSIRT / SOC
104 CSIRT
- 전체 명칭
- 104 CSIRT
- FIRST 프로필 분야
- Other commercial
- 소속 기관
- 104 Corporation
- 공개된 팀 유형
- CSIRT, SOC
- 공개된 설립 시기
- October 18, 2017
- FIRST 가입 시기
- December 17, 2025
데이터 수집일 · FIRST