light weithted vul record
draft-li-sacm-light-weighted-vul-record-00

Document Type Active Internet-Draft (individual)
Authors Jiang Li  , Jun Fu  , Xiaoxiao Li  , Yexia Cheng 
Last updated 2020-11-01
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Security Automation and Continuous Monitoring                      J. Li
Internet-Draft                                                     J. Fu
Intended status: Standards Track                                   X. Li
Expires: May 6, 2021                                            Y. Cheng
                                                            China Mobile
                                                       November 02, 2020

                       light weithted vul record
               draft-li-sacm-light-weighted-vul-record-00

Abstract

   Vulnerability information will be recorded in risk detection and
   scanning.  If a vulnerability is detected in a host during one scan,
   a record will be generated and added to the database, together with a
   time-stamp when the vulnerability is detected.  If risk detection is
   carried out periodically, a series of records will be generated for
   each detection, until vulnerability is fixed.  At present, a common
   way to record vulnerabilities is a vulnerability--a detection--a
   record, a vulnerability--N detections--N records(N>1).In this way,
   the number of vulnerability records is related to the rounds of
   detection.  In the case that the number of existing vulnerabilities
   remains unchanged, more frequent vulnerabilities are scanned, more
   records are recorded In this document, a light weighted vulnerability
   recording method is proposed.  To make that, in the whole life cycle
   of a vulnerability, only one record is generated after multiple
   detections.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119][RFC8174].

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any

Li, et al.                 Expires May 6, 2021                  [Page 1]
Internet-Draft          light weithted vul record          November 2020

   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on May 6, 2021.

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Data Structure  . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Normative References  . . . . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   In the process of risk management, large enterprises and institutions
   often use the method of periodic vulnerability detection and
   scanning.  At present, the common way to record vulnerabilities is to
   keep many records for each vulnerability.  Since the vulnerability
   state is time-dependent, each vulnerability record will carry time
   information to indicate the time stamp when the vulnerability is
   detected.  A vulnerability record usually contain the following
   elements:

   1.IP address

   2.port: e.g. 23

   3.service: e.g. telnet

   4.protocol: TCP or UDP

   5.vul_name: e.g. telnet weak password

Li, et al.                 Expires May 6, 2021                  [Page 2]
Internet-Draft          light weithted vul record          November 2020

   6.vul_det_time: time stamp when the vulnerability is detected, e.g.
   2020-10-10 10:20:30

   7.vul_detail: additional information of vulnerability, in the
   scenario of weak password, vul_detail could be admin / 123456

   By using these data, security administrators can locate the
   vulnerabilities on specific hosts and specific services.

2.  Data Structure

   In the work of continuous security monitoring, if the same
   vulnerability of the same host is not repaired in time, multiple
   records will be generated.  And the more frequent periodic detection,
Show full document text