23 NYCRR 500.13 Asset Management and Data Retention Requirements at a Glance
- Regulation: NY DFS Cybersecurity Requirements for Financial Services Companies, 23 NYCRR Part 500.
- Section: 23 NYCRR 500.13 Asset Management and Data Retention Requirements.
- Status: Amended by the Second Amendment, effective November 1, 2023.
- Who it applies to: Every covered entity unless exempt from Part 500 entirely. 500.13 is not waived by the 500.19(a), (c) or (d) exemptions.
- Class A companies: None beyond the general requirement.
- Limited exemption (500.19(a)): Not exempt under 500.19(a), (c) or (d).
- Compliance dates: The asset inventory requirement in 500.13(a) applied from November 1, 2025, two years after the Second Amendment took effect (500.22(d)(4)). Secure disposal in 500.13(b) existed before the amendment; amended wording applied from April 29, 2024 (500.22(c)).
Section 500.13 was retitled from Limitations on Data Retention to Asset Management and Data Retention Requirements. The new asset inventory requirement in 500.13(a) asks for more than a list of devices: each asset needs key information tracked, as applicable, and the policies must set how often the inventory is updated and validated.
The data retention part in 500.13(b) requires periodic secure disposal of personal and health nonpublic information that is no longer necessary for business operations or other legitimate business purposes, unless law or regulation requires keeping it or targeted disposal is not reasonably feasible.
What Does 23 NYCRR 500.13 Require?
The following is the text of 23 NYCRR 500.13 Asset Management and Data Retention Requirements as amended by the Second Amendment to Part 500, effective November 1, 2023. Only the formatting has been adjusted for readability.
- (a) As part of its cybersecurity program, each covered entity shall implement written policies and procedures designed to produce and maintain a complete, accurate and documented asset inventory of the covered entity’s information systems. The asset inventory shall be maintained in accordance with written policies and procedures. At a minimum, such policies and procedures shall include:
- (1) a method to track key information for each asset, including, as applicable, the following:
- (i) owner;
- (ii) location;
- (iii) classification or sensitivity;
- (iv) support expiration date; and
- (v) recovery time objectives; and
- (2) the frequency required to update and validate the covered entity’s asset inventory.
- (b) As part of its cybersecurity program, each covered entity shall include policies and procedures for the secure disposal on a periodic basis of any nonpublic information identified in section 500.1(k)(2)-(3) of this Part that is no longer necessary for business operations or for other legitimate business purposes of the covered entity, except where such information is otherwise required to be retained by law or regulation, or where targeted disposal is not reasonably feasible due to the manner in which the information is maintained.
Source: NY DFS, Second Amendment to 23 NYCRR 500 (text).
How Does 23 NYCRR 500.13 Map to the Secure Controls Framework (SCF)?
The SCF publishes a NIST IR 8477 Set Theory Relationship Mapping (STRM) between 23 NYCRR Part 500 (2023 Amendment 2) and SCF version 2026.3. It maps 23 NYCRR 500.13 to 5 SCF controls through 12 relationships (12 "intersects with").
How to read the mapping: each relationship runs from the Part 500 text to the SCF control. "Intersects with" means the Part 500 requirement and the SCF control share partial overlap. The strength of relationship runs from 1 (nominal) to 10 (strongest), where 5 is moderately strong and 10 is typically reserved for "equal" and "subset of" relationships.
- AST-02 Asset Governance. Intersects with (strength 5): 500.13(a). SCF control: Mechanisms exist to facilitate an IT Asset Management (ITAM) program to implement and manage asset management controls.
- AST-04 Asset Inventories. Intersects with (strength 5): 500.13(a), 500.13(a)(1), 500.13(a)(1)(i), 500.13(a)(1)(ii), 500.13(a)(1)(iii), 500.13(a)(1)(iv), 500.13(a)(1)(v), 500.13(a)(2). SCF control: Mechanisms exist to perform inventories of Technology Assets, Applications, Services and/or Data (TAASD) that: (1) Accurately reflects the current TAASD in use; (2) Identifies authorized software products, including business justification details; (3) Is at the level of granularity deemed necessary for tracking and reporting; (4) Includes organization-defined information deemed necessary to achieve effective property accountability; and (5) Is available for review and audit by designated organizational personnel.
- GOV-04 Publishing Security, Compliance & Resilience Documentation. Intersects with (strength 5): 500.13(a). SCF control: Mechanisms exist to establish, maintain and disseminate policies, standards and procedures necessary for secure, compliant and resilient capabilities.
- AST-22 Secure Disposal, Destruction or Re-Use of Equipment. Intersects with (strength 5): 500.13(b). SCF control: Mechanisms exist to securely dispose of, destroy or repurpose technology assets using organization-defined techniques and methods to prevent: (1) Data recovery; and (2) Components from being resold, redistributed and/or reused through unauthorized channels.
- DCH-27 Media & Data Retention. Intersects with (strength 5): 500.13(b). SCF control: Mechanisms exist to retain media and data in accordance with applicable statutory, regulatory and contractual obligations.
Mapping taken from the STRM published with SCF version 2026.3. Download it at no cost: SCF STRM for NY DFS 23 NYCRR 500 (2023 Amendment 2). The SCF explains the method in its Set Theory Relationship Mapping (STRM) guidance.
Common Pitfalls With 23 NYCRR 500.13
The following are issues teams commonly run into, not certainties. Each one is tied to the text of the regulation:
- Inventory without the required attributes. As applicable, each asset needs owner, location, classification or sensitivity, support expiration date and recovery time objectives.
- No update and validation frequency. 500.13(a)(2) requires the policies to state how often the inventory is updated and validated.
- Untracked end-of-support dates. Support expiration dates connect the inventory to end of life management, which 500.3(c) now lists as a policy area.
- Retention schedules without disposal. 500.13(b) requires secure disposal on a periodic basis, not only a retention schedule.
What Is Reasonable Evidence for 23 NYCRR 500.13?
NY DFS does not publish a fixed evidence list. Under 500.17(b)(3), records supporting the annual certification or acknowledgment must be kept for five years.
The SCF Evidence Request List (ERL) ties evidence artifacts to SCF controls. ERL items linked to the SCF controls mapped to 23 NYCRR 500.13 include:
- E-GOV-01.3 Asset Management Policy. Documented evidence of a asset management policy.
- E-GOV-01.12 Data Classification & Handling Policy. Documented evidence of a data classification and handling policy.
- E-AST-01 IT Asset Management (ITAM). Documented evidence of an IT Asset Management (ITAM) program that addresses the due diligence and due care activities associated with maintaining both secure, compliance and resilient Technology Assets, Applications and/or Services (TAAS).
- E-AST-03 Asset Disposal Evidence. Documented evidence of asset disposal/destruction (e.g., asset tracking by serial # for shredding, degaussing, etc.).
- E-AST-04 Asset Inventories - Hardware. Documented evidence of an inventory of the organization's technology hardware assets.
- E-AST-05 Asset Inventories - Software. Documented evidence of an inventory of the organization's software assets.
- E-AST-07 Cyber-Physical Systems (CPS). Documented evidence of an inventory of the organization's physical assets that process functions based on software and networks.
- E-AST-11 Data Retention Program. Documented evidence of a formal data retention program that governs the retention and destruction of data types.
Records specific to 23 NYCRR 500.13 that typically show the requirement is designed and operating:
- Asset management policy and procedures. Written documents covering inventory scope, attributes and update frequency.
- Asset inventory. An inventory with owner, location, classification, support expiration date and RTO fields populated.
- Validation records. Records showing the inventory was updated and validated at the defined frequency.
- Retention and disposal schedule. Rules for disposing of nonpublic information under 500.13(b), with exceptions noted.
- Disposal records. Certificates or logs showing periodic secure disposal.
Which ComplianceForge Documents Support 23 NYCRR 500.13?
The following ComplianceForge documents can help you document and implement 23 NYCRR 500.13 Asset Management and Data Retention Requirements:
- SCF Policies & Standards (SCRP): editable SCF-based cybersecurity policies, standards and control objectives covering all 34 SCF domains.
- SCF Procedures (CSOP): editable SCF-aligned cybersecurity procedures covering all 34 SCF domains, mapped 1-to-1 to the SCRP standards.
Frequently Asked Questions (FAQ)
What must the 23 NYCRR 500.13 asset inventory track? A method to track key information for each asset, including, as applicable, the owner, location, classification or sensitivity, support expiration date and recovery time objectives, plus the frequency required to update and validate the inventory.
What data must be disposed of under 500.13(b)? Nonpublic information identified in 500.1(k)(2) and (3), meaning personal identifying information combined with specified data elements and health information, that is no longer necessary for business operations or other legitimate business purposes, except where law or regulation requires retention or targeted disposal is not reasonably feasible.
When did the 500.13(a) asset inventory requirement take effect? Covered entities had two years from November 1, 2023, so it applied from November 1, 2025 under 500.22(d)(4).
Do small entities with a limited exemption need an asset inventory? Yes. 500.13 is not waived by the 500.19(a) limited exemption.
Bottom Line on 23 NYCRR 500.13 Asset Management and Data Retention Requirements
500.13 turns the asset inventory into a regulated record with specific attributes and a defined refresh cycle, and keeps the duty to dispose of personal and health data you no longer need. Populate the five attributes, set and follow the validation schedule, and keep disposal records.
Authoritative sources:
This page reproduces New York State regulatory text from 23 NYCRR Part 500. It is educational, not legal advice. Last reviewed: 2026-11-15.
Other 23 NYCRR Part 500 Requirements
Previous section: 500.12 Multi-Factor Authentication. Next section: 500.14 Monitoring and Training. Sections 500.0, 500.18, 500.21, 500.23 and 500.24 are covered in the NY DFS 23 NYCRR Part 500 Compliance Guide.