[OPSEC][Errata Verified] RFC9424 (7964)
RFC Errata System <rfc-editor@rfc-editor.org> Wed, 05 June 2024 18:35 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: opsec@ietf.org
Delivered-To: opsec@ietfa.amsl.com
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 26149C180B69; Wed, 5 Jun 2024 11:35:11 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 834E7C000063; Wed, 5 Jun 2024 11:35:10 -0700 (PDT)
To: andrew.s2@ncsc.gov.uk, kirsty.ietf@gmail.com, ollie@binaryfirefly.com, james.sellwood.ietf@gmail.com, andrew.s2@ncsc.gov.uk
From: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20240605183510.834E7C000063@rfcpa.rfc-editor.org>
Date: Wed, 05 Jun 2024 11:35:10 -0700
Message-ID-Hash: LCOURNGLRZ7FLWXDHKS43UICAJLRZM56
X-Message-ID-Hash: LCOURNGLRZ7FLWXDHKS43UICAJLRZM56
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-opsec.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: warren@kumari.net, iesg@ietf.org, opsec@ietf.org, iana@iana.org, rfc-editor@rfc-editor.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [OPSEC][Errata Verified] RFC9424 (7964)
List-Id: opsec wg mailing list <opsec.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsec/aby2Au3QVo74cTADK0MS2U2-kx4>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsec>
List-Help: <mailto:opsec-request@ietf.org?subject=help>
List-Owner: <mailto:opsec-owner@ietf.org>
List-Post: <mailto:opsec@ietf.org>
List-Subscribe: <mailto:opsec-join@ietf.org>
List-Unsubscribe: <mailto:opsec-leave@ietf.org>
The following errata report has been verified for RFC9424, "Indicators of Compromise (IoCs) and Their Role in Attack Defence". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid7964 -------------------------------------- Status: Verified Type: Technical Reported by: Andrew Shaw <andrew.s2@ncsc.gov.uk> Date Reported: 2024-05-30 Verified by: Warren Kumari (Ops AD) (IESG) Section: 3.2.3 Original Text ------------- At its simplest, this indicates that the receiver may share with anyone (TLP:CLEAR), share within the defined sharing community (TLP:GREEN), share within their organisation and their clients (TLP:AMBER+STRICT), share just within their organisation (TLP:AMBER), or not share with anyone outside the original specific IoC exchange (TLP:RED). Corrected Text -------------- At its simplest, this indicates that the receiver may share with anyone (TLP:CLEAR), share within the defined sharing community (TLP:GREEN), share within their organisation and their clients (TLP:AMBER), share just within their organisation (TLP:AMBER+STRICT), or not share with anyone outside the original specific IoC exchange (TLP:RED). Notes ----- The definitions of TLP:AMBER and TLP:AMBER+STRICT are the wrong way round in the original text. -------------------------------------- RFC9424 (draft-ietf-opsec-indicators-of-compromise-04) -------------------------------------- Title : Indicators of Compromise (IoCs) and Their Role in Attack Defence Publication Date : August 2023 Author(s) : K. Paine, O. Whitehouse, J. Sellwood, A. Shaw Category : INFORMATIONAL Source : Operational Security Capabilities for IP Network Infrastructure Stream : IETF Verifying Party : IESG
- [OPSEC][Errata Verified] RFC9424 (7964) RFC Errata System