Skip to content

Data Classification

Overview

Data Classification is the process of categorizing enterprise data based on sensitivity, criticality, and regulatory requirements.
A consistent classification framework enables appropriate handling, security, retention, and sharing of data across Nissan North America (NNA).

This section provides the classification model, handling rules, and implementation guidance for all data assets.


Purpose

The objectives of data classification are:

  • Identify sensitive and critical data requiring special protection.
  • Ensure compliance with regulatory requirements (e.g., GDPR, CCPA, industry standards).
  • Enable risk-based decision-making for data handling, sharing, and retention.
  • Provide guidance for access control, storage, and lifecycle management.

Classification Levels

Level Description Examples Handling Guidelines
Public Data intended for public disclosure. Marketing brochures, product specs, press releases No special restrictions; can be shared externally.
Internal Data for internal use only. Internal policies, operational procedures, non-sensitive reports Access limited to NNA employees; do not share externally.
Confidential Data with potential business impact if disclosed. Customer lists, pricing, internal forecasts, vendor contracts Restricted access; encryption recommended; external sharing requires approval.
Sensitive / Restricted Highly sensitive data with legal, financial, or reputational risk. PII/PHI, financial statements, strategic plans Strict access controls; encrypted storage; monitoring and auditing; sharing requires executive approval.

Note: Classification levels can be adapted for specific domains or regulatory requirements.


Classification Criteria

Data should be classified based on multiple dimensions:

  1. Sensitivity: Potential harm from unauthorized access or disclosure.
  2. Regulatory / Legal Requirements: Obligations under laws, contracts, or industry standards.
  3. Criticality: Importance to business operations and decision-making.
  4. Confidentiality Impact: Consequences of accidental exposure.
  5. Retention Requirements: Lifecycle and archival rules associated with the classification level.

Data Handling Guidelines

Classification Level Access Control Storage Transmission Retention & Disposal
Public Open Standard storage Any method Standard retention policies
Internal Employee-only Internal systems Internal email or systems Standard retention policies
Confidential Role-based access Encrypted or secure storage Secure channels only Follow retention & disposal policies
Sensitive / Restricted Strict, need-to-know Encrypted, monitored storage Encrypted and logged Follow retention & secure disposal policies

Classification Process

  1. Identify Data Assets: Catalog all datasets, files, and systems.
  2. Assess Risk & Sensitivity: Evaluate data against classification criteria.
  3. Assign Classification Level: Determine Public, Internal, Confidential, or Sensitive/Restricted.
  4. Apply Controls: Implement access, storage, transmission, and retention controls.
  5. Review & Update: Periodically reassess classification based on business changes, audits, or regulatory updates.

Implementation Considerations

  • Roles & Responsibilities:
  • Data Owners: Assign classification and approve changes.
  • Data Stewards: Monitor compliance and enforce handling rules.
  • IT / Security Teams: Implement technical controls based on classification.
  • Automation: Use tools for tagging, monitoring, and access enforcement.
  • Training: Educate employees on classification rules and handling requirements.
  • Integration: Align classification with other governance processes (data quality, retention, security).

Visual Representation

flowchart TB
    A[All Data Assets] --> B{Classification Level?}
    B --> C[Public]
    B --> D[Internal]
    B --> E[Confidential]
    B --> F[Sensitive / Restricted]
    C --> G[Standard Access & Storage]
    D --> H[Internal Access & Security]
    E --> I[Restricted Access & Encryption]
    F --> J[Strict Access, Encryption, Monitoring]