Subject: [OPSEC] Fw: New Version Notification for draft-paine-smart-indicators-of-compromise-02.txt

From: Kirsty P <[email-masked]>
Date: Tue, 26 Jan 2021 11:19:28 +0000

Hi OPSEC,

Please see below for details of our new draft on Indicators of Compromise (IoCs), updated based on previous comments. We think it might be suitable for OPSEC, but we'd like to hear your comments, discussion or feedback on this draft - please get in touch!

Kirsty & Ollie

________________________________
From: [email-masked] <[email-masked]>
Sent: 13 January 2021 17:44
To: Kirsty P <[email-masked]>; Kirsty P <[email-masked]>; Ollie Whitehouse <[email-masked]>
Subject: New Version Notification for draft-paine-smart-indicators-of-compromise-02.txt

A new version of I-D, draft-paine-smart-indicators-of-compromise-02.txt
has been successfully submitted by Kirsty Paine and posted to the
IETF repository.

Name:           draft-paine-smart-indicators-of-compromise
Revision:       02
Title:          Indicators of Compromise (IoCs) and Their Role in Attack Defence
Document date:  2021-01-13
Group:          Individual Submission
Pages:          18
URL:            https://www.ietf.org/archive/id/draft-paine-smart-indicators-of-compromise-02.txt
Status:         https://datatracker.ietf.org/doc/draft-paine-smart-indicators-of-compromise/
Htmlized:       https://datatracker.ietf.org/doc/html/draft-paine-smart-indicators-of-compromise
Htmlized:       https://tools.ietf.org/html/draft-paine-smart-indicators-of-compromise-02
Diff:           https://www.ietf.org/rfcdiff?url2=draft-paine-smart-indicators-of-compromise-02

Abstract:
   Indicators of Compromise (IoCs) are an important technique in attack
   defence (often called cyber defence).  This document outlines the
   different types of IoC, their associated benefits and limitations,
   and discusses their effective use.  It also contextualises the role
   of IoCs in defending against attacks through describing a recent case
   study.  This draft does not pre-suppose where IoCs can be found or
   should be detected - as they can be discovered and deployed in
   networks, endpoints or elsewhere - rather, engineers should be aware
   that they need to be detectable (either by endpoints, security
   appliances or network-based defences, or ideally all) to be
   effective.  The purpose of this draft is to document both the
   operational issues, but also the best practices associated with use
   of IoCs today.  This draft provides a foundation for proposals for
   new approaches to operational challenges in network security.

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat
This information is exempt under the Freedom of Information Act 2000 (FOIA) and may be exempt under other UK information legislation. Refer any FOIA queries to [email-masked]. All material is UK Crown Copyright ©