Information Security 3 min read

How to Classify Security Incidents: A Comprehensive Grading Policy

This document outlines a security incident grading policy that defines purpose, scope, detailed classification across application, network, host, and data layers, and provides remarks on applicability, data‑related events, and the definition of critical (S0) vulnerabilities, helping organizations assess and prioritize security faults.

Software Development Quality
Software Development Quality
Software Development Quality
How to Classify Security Incidents: A Comprehensive Grading Policy

Purpose

Establish a security incident grading policy to raise security awareness and uncover the root causes of incidents.

Scope

Applicable to all subsidiaries.

Detailed Grading

Incidents are categorized by layer (application, network, host, data) and sub‑type, with discovery channels, occurrence counts, impact, and severity levels (P1‑P4). Examples include:

Application layer – security vulnerability (S0) discovered externally, impact P1.

Network layer – unauthorized port opening reported internally/externally, severity P1.

Host layer – intrusion event reported, severity P1.

Data layer – large‑scale leakage of C3/C4 level data, impact 1% of total data, severity P1.

Remarks

This fault definition applies group‑wide; if a product line defines its own security fault level, the higher level prevails.

Data‑related security events refer to data leakage caused by system vulnerabilities.

S0 (critical vulnerability) is defined as a vulnerability that has been publicly disclosed or exploited, affecting group systems/businesses and may cause system intrusion risk, massive sensitive data compromise, availability impact on many customer transactions, asset loss, or reputational damage.

risk managementSecurityinformation securitypolicyincident classification
Software Development Quality
Written by

Software Development Quality

Discussions on software development quality, R&D efficiency, high availability, technical quality, quality systems, assurance, architecture design, tool platforms, test development, continuous delivery, continuous testing, etc. Contact me with any article questions.

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.