참고 자료 · 41

취약점 공개의 체계적 관리: 접수, 수정 및 알림

외부 보고를 위한 안전한 경로 구축, 영향 평가, 관련 당사자 조정 및 유용한 지침 게시

업데이트됨 · 16 min

사람이 없는 가상의 사이버 실험실. 호박색 조명의 어두운 작업대에 장비 케이스와 네트워크 패널이 있다. AI로 생성한 편집용 일러스트

이 가이드가 달성하는 목표

  • 보고를 가능하게 하고 안전하게 만듭니다.
  • 모든 보고서에 담당자를 지정합니다.
  • 검증 가능한 수정 사항을 조정합니다.
  • 사용자에게 실행 가능한 지침을 제공합니다.

빠른 확인

  • 고객 계정 없이 보고서를 보낼 수 있습니까?
  • 범위 및 허용된 테스트가 명확합니까?
  • 주요 담당자 부재 시 누가 응답합니까?
  • 어떤 제품 및 공급업체가 해당 결함을 공유합니까?
  • 어떤 임시 완화 조치가 유용합니까?
  • 권고 사항에 실제로 영향을 받는 버전이 명시되어 있습니까?

단계별 방법

  1. 1

    명확한 정책을 게시하십시오.

    범위, 피해야 할 테스트, 연락 채널, 유용한 보고서 세부 정보 및 대응 프로세스를 명시하십시오. 해당 정책을 귀사의 상황에 맞게 검토받으십시오.

    결과물: 게시된 정책 및 모니터링 채널.

  2. 2

    증거를 확인하고 보호하십시오.

    수신을 확인하고 식별자를 할당하고 민감한 정보의 배포를 제한하며 문제를 재현하는 데 필요한 증거만 요청하십시오.

    결과물: 담당자가 지정된 날짜가 기재된 보고서.

  3. 3

    범위를 평가하고 확장하십시오.

    시스템에 피해를 주지 않고 재현하십시오. 악용 가능성, 자산, 버전, 데이터 및 다른 제품이나 공급업체와 공유하는 구성 요소를 검토하십시오.

    산출물: 영향 평가 및 이해관계자 지도.

  4. 4

    문제 해결 조정

    보고자 및 관리자와 정기적으로 소통합니다. 검증 마일스톤에 합의하고 위험 또는 배포 방식이 변경될 경우 커뮤니케이션을 조정합니다.

    산출물: 공유된 타임라인, 수정 사항 및 회귀 테스트.

  5. 5

    게시 및 후속 조치

    영향을 받는 버전, 수정 사항 또는 완화 조치, 사용자 조치 및 불확실성을 설명합니다. 배포를 확인하고 사실 관계가 변경될 경우 권고 사항을 업데이트합니다.

    산출물: 버전별 권고 사항 및 배포 증거.

가상 예시

예시 상황

한 연구원이 이전 API 버전에서 접근 제어 오류를 보고했습니다. 팀은 이를 인지하고 승인된 환경에서 사례를 재현하여 공유 구성 요소가 두 제품에 영향을 미치는 것을 발견했습니다.

결정 및 예상 증거

계획은 관리자, 버전, 수정 테스트 및 임시 완화 조치를 연결합니다. 최종 권고 사항은 사용자에게 명확한 조치를 제공하고 합의된 대로 연구원의 공로를 인정합니다.

관리 지표

지표측정 대상첫 번째 조치
영수증 추적 완료담당자 및 최초 응답 날짜가 포함된 보고서비공개 채널 수정
범위 설정 완료영향을 받는 제품, 버전 및 종속성 확인 완료최종 권고 전 검색 범위 확장 완료
수정 사항 검증 완료출시된 버전에서 원본 및 관련 사례 재현 완료취약한 변종은 닫지 않음
사용자에게 알림지침이 영향을 받는 대상에게 전달됨필요한 채널 및 번역 업데이트 완료

일반적인 실수

  • 위험도와 관계없이 하나의 마감일 약속
  • 보고자에게 과도한 개인 정보 요구
  • 확인을 수정으로 간주
  • 사용 가능한 완화 조치 전에 상세한 악용 증거 게시
  • 파트너가 포함시킨 버전 고려 안 함

자주 묻는 질문

공개 정책이 버그 현상금인가요?

아니요. 정책은 보고 및 조정 방법을 설명합니다. 보상에는 별도의 규칙과 리소스가 필요합니다.

소통은 항상 문제 해결을 기다려야 합니까?

아니요. 시기는 위험, 임시 조치 및 영향을 받는 당사자에 따라 다릅니다. 결정을 기록하고 다시 검토하십시오.

조정자는 언제 도움을 주어야 합니까?

조정자는 여러 공급업체가 영향을 받거나, 담당자가 응답하지 않거나, 공유 일정을 맞추기 어려운 경우 도움을 줄 수 있습니다.

참고 자료: 데이터, 용도와 한계

문서 검토일 .

이 언어판의 상세 참고 설명은 영어로 제공됩니다.

참고 자료: 데이터, 용도와 한계
출처와 목적확인된 데이터 또는 기준사용 방법유지해야 할 한계
CVE Program

Link discussions to the same vulnerability record.

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.

security.txt와 취약점 공개

이 언어판의 상세 참고 설명은 영어로 제공됩니다.

security.txt: find a reporting channel and check its context

A researcher may find a flaw without finding the right recipient. A security.txt file makes reporting channels and disclosure policies easier to discover. Its value then depends on monitored contacts, current information and a process that connects the report to the affected product.

This reference explains the format described in RFC 9116, an IETF Informational publication dated April 2022. The eight fields below are those defined by that RFC, rather than an exhaustive list of later extensions. Examples are fictional, using .example domains reserved for documentation. This page retrieves, validates, signs and publishes no real security.txt file.

사람이 없는 가상의 사이버 실험실. 호박색 조명의 어두운 작업대에 장비 케이스와 네트워크 패널이 있다. AI로 생성한 편집용 일러스트
A fictional empty disclosure coordination laboratory. This scene depicts neither an actual facility nor evidence of security.

Six discovery and publication checks

Six discovery and publication checks
CheckRFC 9116 reference pointUseful record
LocationFor a web service, publish at /.well-known/security.txt. If both root and well-known files exist, use the well-known version.Retrieved URL, response and any difference from /security.txt at the root.
TransportRetrieve using HTTPS with HTTP 1.0 or later; referenced web URIs also use HTTPS.Certificate check and retrieval result, separately from checks of the file’s fields.
FormatUTF-8 plain text; Content-Type text/plain with charset=utf-8. Each field occupies its own line.Received header, observed encoding and a dated copy of the text examined.
ScopeThe file applies to the domain or IP address in its retrieval URI; parent domains and subdomains are not inherited automatically.Exact host, affected product and scope explained in the linked policy.
RedirectsA redirect may be legitimate but needs further inspection. The RFC recommends keeping a record.Redirect chain, host changes and the reason for using an external provider.
MaintenanceExpires is mandatory. Contacts, links and keys need to remain accessible and controlled by the organisation.Publication owner, verification date and a local review deadline before expiry.

Eight fields defined by RFC 9116

Eight fields defined by RFC 9116
FieldPresence and repetitionUseful interpretationPitfall
ContactRequired; one or more occurrences.Contact URI, such as mailto: or an HTTPS page. Occurrences should follow the publisher’s preference order.An email address without mailto: is not a conforming Contact URI. Publishing a channel does not establish that it is monitored.
ExpiresRequired; exactly one occurrence.RFC 3339 timestamp after which the data is stale and should not be used. A date less than one year ahead is recommended.That recommendation is neither a mandatory one-year duration nor a vulnerability remediation deadline.
CanonicalOptional; may repeat.Canonical URIs where the file is published. If the retrieval URI is absent from these fields, the RFC recommends not trusting the contents.Listing several Canonical URIs does not authenticate every listed host. An additional trust mechanism remains useful.
EncryptionOptional; may repeat.URI locating an encryption key; the key itself must not appear in this field.The referenced key is not necessarily the file’s signing key. Its presence proves neither authenticity nor that a report was encrypted.
PolicyOptional; may repeat.Link to the disclosure policy: scope, reporting practices and conditions explained by the organisation.The file does not replace that policy or by itself define a reward, response deadline or testing permission.
Preferred-LanguagesOptional; at most one occurrence, containing at least one language.Comma-separated language tags with equal priority regardless of order. If absent, English may be assumed.fr, en does not prioritise French. Several Preferred-Languages lines do not replace a single list.
AcknowledgmentsOptional; may repeat.Link to a page recognising people who helped remediate vulnerabilities.Coordinate public credit; it does not authorise premature disclosure of flaw details.
HiringOptional; may repeat.Link to the organisation’s security-related vacancies.Do not confuse a hiring link with the reporting channel.

Annotated fictional example: contact, time, origin and policy

Training reading at the fictional instant 22 October 2026, 10:00 UTC. The two Contact occurrences are ordered; the two languages have equal priority. Expiry is six months later. This is not Cyber Intelligence Embassy’s security.txt file and provides no real reporting channel.

# Fictional training example, not this site's reporting policy
Contact: mailto:security@publisher.example
Contact: https://publisher.example/report
Expires: 2027-04-22T10:00:00Z
Canonical: https://publisher.example/.well-known/security.txt
Policy: https://publisher.example/disclosure-policy
Preferred-Languages: fr, en

This example remains unsigned. Canonical identifies the expected URI but does not replace authenticity evidence. Before sending a sensitive report, verify the recipient, policy and appropriate transmission protections.

Eight situations separating format, freshness and trust

Each excerpt isolates one question; no conclusion is a complete file validation. Observations and proposed next steps are editorial guidance. Addresses shown in excerpts are not links to contact.

Essential fields are present

Fictional retrieval URI : https://publisher.example/.well-known/security.txt

Contact: mailto:security@publisher.example
Expires: 2027-04-22T10:00:00Z
Canonical: https://publisher.example/.well-known/security.txt

A contact, future expiry and the expected canonical URI appear in this excerpt.

Continue checking transport, recipient identity and policy. These fields prove neither mailbox operation nor testing permission.

Contact contains a bare email address
Contact: security@publisher.example
Expires: 2027-04-22T10:00:00Z

The mailto: scheme is missing; the value lacks the URI form required for Contact.

Correct the source publication. A tool’s possible tolerance does not establish format conformity.

Expires occurs twice
Contact: mailto:security@publisher.example
Expires: 2027-01-22T10:00:00Z
Expires: 2027-04-22T10:00:00Z

Two occurrences conflict with the Expires uniqueness rule.

Publish one expiry after correcting the file. Silently choosing the more convenient date conceals the publication defect.

The expiry date has passed
Contact: mailto:security@publisher.example
Expires: 2026-10-21T10:00:00Z

At the fictional evaluation instant the file expired twenty-four hours earlier.

Treat its data as stale and seek a verified current channel. Retain the old copy as history without presenting it as a current contact.

Canonical omits the retrieval URI

Fictional retrieval URI : https://api.publisher.example/.well-known/security.txt

Contact: mailto:security@publisher.example
Expires: 2027-04-22T10:00:00Z
Canonical: https://publisher.example/.well-known/security.txt

The file retrieved for api.publisher.example lists only publisher.example in Canonical.

Apply the recommendation not to trust these contents in this context and request publication verification. Similar hostnames do not resolve the mismatch.

The report concerns a subdomain

Fictional retrieval URI : https://publisher.example/.well-known/security.txt

Host concerned by the report : https://api.publisher.example/

Contact: mailto:security@publisher.example
Expires: 2027-04-22T10:00:00Z

The file belongs to publisher.example; the reported asset is api.publisher.example.

Do not infer subdomain coverage. Check its own discovery location and the product scope explicitly described in the policy.

The file redirects to a provider

Fictional redirect chain : https://publisher.example/.well-known/security.txt → https://intake.partner.example/security.txt

Contact: https://intake.partner.example/report
Expires: 2027-04-22T10:00:00Z

The redirect chain changes host and ends at intake.partner.example.

Document each hop and verify the channel delegation. Using a provider proves neither fraud nor authenticity.

An encryption key is referenced, but not authenticated
Contact: mailto:security@publisher.example
Expires: 2027-04-22T10:00:00Z
Encryption: https://publisher.example/report-key.asc

Encryption supplies an HTTPS key URI without local evidence of the key’s identity.

Authenticate the key through an appropriate means before use. Separate report encryption, file signing and actual protection of the submitted message.

From discovered channel to disclosure case: six useful records

The CERT/CC guide distinguishes finding a contact, providing a useful report and coordinating disclosure. The following outline is a local working proposal, imposing neither a universal fix deadline nor automatic publication.

From discovered channel to disclosure case: six useful records
RecordHow it helpsLimit to state
Product and versionConnect the report to a team and affected releases.A website and an embedded component may have different owners.
Observed behaviourExplain expected and actual results with appropriate reproduction steps.Separate reproduced facts, impact hypotheses and untested conditions.
Channel and recipientsKeep the discovery URL, chosen contact and consulted policy.Send sensitive evidence only after verifying the recipient and transmission protection.
Owner and follow-upRecord acknowledgement, case identifier and agreed next contact.Acknowledgement confirms neither impact nor remediation.
Affected partiesIdentify maintainers, suppliers and products sharing the component.A supplier’s fix does not establish deployment by every consumer.
Fix and communicationConnect fixed versions, remaining limits and actions expected from users.Record the agreed timetable and revisit it as facts change; Expires does not dictate a public disclosure date.

Three limits to keep visible

  • The presence or absence of security.txt alone neither grants nor denies testing permission; applicable conditions need separate verification.
  • RFC 9116 recommends an OpenPGP signature for the file; verifying a signature and establishing trust in its key remain distinct questions.
  • A compromised site can publish a false contact. Intrusions or suspected file tampering may call for an independent channel; this mechanism primarily addresses vulnerability response.

Primary sources and scope

Sources checked on

공식 참조

참조는 방법을 뒷받침합니다. 상황에 맞게 검사를 조정하십시오. 이는 인증이 아닙니다. 원본 참조 제목 및 소스 문서는 다른 언어로 작성되었을 수 있습니다.

참고 자료 확인일 .