Independent technical practice

New York private information gathering package

Organize New York private-information records, data maps, safeguards and breach facts for a privacy or cybersecurity specialist.

Bagged hard drive beside a forensic write blocker.

Global Digital Forensics · Information gathering library · October 18 2026

Edition GATHER-20261018-01 · Information-gathering edition

Read this guide freely. Request download access with your name and email.

GDF records the selected resource in its lead intake and private Stats.

Open your emailed link for seven days of preparation downloads in this browser.

No marketing subscription is created. Keep completed records in controlled systems.

Find where New York residents information is held and assemble existing safeguards and incident records for a privacy or cybersecurity specialist.

Owners, lawyers, privacy and risk managers, office administrators and client IT

General Business Law 899-aa and 899-bb preparation, with a separate branch for state entities and sector-specific obligations. It is not a universal New York privacy certification.

Before you gather

  • PII is a useful broad working label. New York statutory private information under 899-aa has a particular definition, while DFS nonpublic information and HIPAA protected health information have different scopes. Inventory the actual fields and combinations before the specialist makes the legal classification.
  • The current 899-aa text reviewed includes medical and health-insurance information as well as specified identifiers, financial-access information, biometrics and online credentials. A checklist based only on Social Security and credit-card numbers can miss relevant data.
  • For owners/licensees, 899-aa(2) uses prompt notice with a 30-day outer limit after discovery, subject to its terms. The maintainers branch in 899-aa(3) calls for immediate notice to the owner/licensee, with a 30-day limit. These are distinct from DFS incident/payment clocks. Obtain dates and decisions; counsel determines notices.
  • 899-bb has a safeguard-compliance route for a person subject to and in compliance with specified regulatory regimes. Being regulated is not enough by itself. Its small-business provision tailors safeguards to the business; it is not a blanket exclusion.
  • State Technology Law 208 is a separate branch, with its own state-entity definition and local-government provisions. Do not copy the GBS definitions, deadlines or recipients into that branch. General hospitals, schools, employers, financial firms and government bodies may need additional specialist modules.

Give each request to the suggested owner. Record what is available and what is unknown in the editable CSV checklist. Use a secure evidence location agreed with the recipient; the checklist is an index, not a place for passwords, real patient data or controlled technical information.

Records to find

Download the editable gathering checklist. CSV files contain plain records, without saved column widths or workbook formatting. Import as UTF-8, keep IDs as text, wrap text and widen columns before use. Blank client fields are intentional.

NY-R01 Organization and legal context

Ask
Legal or business owner
Gather
Legal entity, ownership/government status, business activities, resident populations and contracts or regulator requests.
Where to ask
Corporate files and business sponsor
Why it may be needed
Routes the facts to the right law and sector.
If missing or uncertain
Ask counsel which regime applies; keep the branch unresolved.

Reference: NY01 2; NY02 2; NY03 1(c), 10

NY01 NY02 NY03

NY-R02 Data field and combination inventory

Ask
Business process owners
Gather
Field names and masked samples; people concerned; purpose; volumes; residence facts; data combinations; encryption and key exposure facts.
Where to ask
HR, payroll, customer, financial and medical systems
Why it may be needed
Supports classification without collecting real identifiers in the checklist.
If missing or uncertain
Name the owner who can supply a schema or masked example; no guessed counts.

Reference: NY01 1; NY02 1; DFS01 500.1(k)

NY01 NY02 DFS01

NY-R03 Information journey

Ask
IT and business owners
Gather
Where information is collected, used, shared, exported, archived, backed up and disposed; devices, tenants, integrations, paper copies and recipient organizations.
Where to ask
Data-source atlas, purchasing and application diagrams
Why it may be needed
Reveals extra copies and processors that a device list misses.
If missing or uncertain
Mark each unconfirmed location as a candidate, not a fact.

Reference: NY02 2(b)

NY02

NY-R04 Responsibility and risk records

Ask
Management and security lead
Gather
Program coordinator, risk assessments, decisions, policy set and business changes since last review.
Where to ask
Policy and risk systems
Why it may be needed
Organizes administrative safeguard records for the recipient.
If missing or uncertain
Name the person who may have records; lack of a found document is not a final control finding.

Reference: NY02 2(b)(ii)(A)

NY02

NY-R05 Personnel and supplier safeguards

Ask
HR and procurement
Gather
Training records, confidentiality/access procedures, provider list, selection reviews, contracts requiring safeguards and change/reassessment records.
Where to ask
HR, procurement, provider agreements
Why it may be needed
Supplies the actual administrative and provider arrangements.
If missing or uncertain
Request actual signed terms and records for the period rather than a sales brochure.

Reference: NY02 2(b)(ii)(A)

NY02

NY-R06 Technical protection records

Ask
IT and service providers
Gather
Access/MFA scope, secure configurations, patch/change history, monitoring coverage, existing test reports and response procedures for the relevant data flows.
Where to ask
Identity, endpoint, application and provider records
Why it may be needed
Lets the consultant assess existing technical safeguards.
If missing or uncertain
Request a scoped explanation of missing or outsourced records; no new testing without authorization.

Reference: NY02 2(b)(ii)(B)

NY02

NY-R07 Physical records and disposal

Ask
Facilities and records manager
Gather
Storage, transport and visitor procedures; cabinet/media controls; retention schedules; destruction certificates and holds that prevent disposal.
Where to ask
Facilities, offsite storage and media vendor
Why it may be needed
Includes paper, portable media and disposal, not only cloud security.
If missing or uncertain
Identify storage sites and providers not yet contacted.

Reference: NY02 2(b)(ii)(C)

NY02

NY-R08 Incident facts and chronology

Ask
Counsel and incident owner
Gather
Discovery/detection/determination timestamps, system events, affected fields, persons/residences, access versus acquisition evidence, encryption/key facts and provider notice.
Where to ask
Restricted incident file
Why it may be needed
Supports legal notice analysis while preserving unknowns.
If missing or uncertain
Escalate live matters; label suspected facts and dates as unconfirmed.

Reference: NY01 1(c), 2, 3; NY03

NY01 NY03

NY-R09 Notification and decision file

Ask
Counsel and compliance
Gather
Notice decisions and basis, templates, dates/recipients, agency receipts, any law-enforcement delay determination and updates.
Where to ask
Counsel and incident correspondence
Why it may be needed
Allows review of actual actions and applicable branches.
If missing or uncertain
Keep legal advice segregated; provide counsel-approved factual chronology and privilege handling instructions.

Reference: NY01 2, 4, 7, 8, 9

NY01

NY-R10 Regulated-entity or size support

Ask
Finance and legal
Gather
Other applicable security regimes, actual compliance records relied on, small-business facts and the prior determination.
Where to ask
Legal, finance and other assessment files
Why it may be needed
Supports the specific 899-bb route without assuming regulation proves compliance.
If missing or uncertain
Send the available facts and the proposed basis to the specialist.

Reference: NY02 1 and 2(b)-(c)

NY02

NY-R11 Government and sector routing

Ask
Legal or privacy lead
Gather
State/local status, governmental policy, actual healthcare/school/financial licenses, contractual requirements and regulator orders.
Where to ask
Legal records and sector owner
Why it may be needed
Identifies which specialist should add a tailored module. Hospital guidance alone does not establish all operative clauses.
If missing or uncertain
Current 405.46 text was not fully retrieved in this research path; obtain it before building a hospital requirement list.

Reference: NY03; NY04; HE01; DFS01

NY03 NY04 HE01 DFS01

NY-R12 Gaps and transmittal

Ask
Coordinator
Gather
Completed source inventory, request responses, periods not covered, access restrictions and named follow-up owners.
Where to ask
This package and receiving specialist
Why it may be needed
Creates an honest, navigable handoff.
If missing or uncertain
Keep Unknown or Partially received visible; ask recipient which gap is first priority.

Reference: Preparation method; NY02

NY02

Questions for client IT and owners

Download the response template. A useful answer names the actual system, period, supporting record and limits. If you do not know, name the person or provider who can answer.

1. What exact information fields and combinations do you hold about New York residents?

Suggested responder
Client IT or system owner
Useful supporting record
Schema and masked examples, including credentials, medical and health-insurance fields.

2. Which outside parties hold the same information or additional copies?

Suggested responder
Client IT or system owner
Useful supporting record
Provider list, contracts, tenants, exports and return/deletion terms.

3. What can you say about encryption and who could obtain the decryption keys?

Suggested responder
Client IT or system owner
Useful supporting record
Configuration description and responsible owner; do not attach keys.

4. Which safeguards were in operation during the period, rather than added later?

Suggested responder
Client IT or system owner
Useful supporting record
Dated settings, reports, tickets and change history.

5. Are accounts, archives, paper stores or backups outside the main system inventory?

Suggested responder
Client IT or system owner
Useful supporting record
One inventory row for each actual location and owner.

6. If an incident is relevant, what happened, when was each fact learned and what remains uncertain?

Suggested responder
Client IT or system owner
Useful supporting record
Counsel-approved chronology with evidence pointers.

7. What records were already supplied to a regulator, insurer or prior assessor?

Suggested responder
Client IT or system owner
Useful supporting record
Copies, scope and receipts subject to authorized disclosure.

8. Which people can explain a missing record or technical limitation?

Suggested responder
Client IT or system owner
Useful supporting record
Contact roster and next action per gap.

Missing facts and specialist decisions

These are explicit handoff questions. Marking records Received does not resolve them. Add client-specific questions and a responsible person.

NY-Q01 Which statutory definition and organizational branch apply?

Ask
Counsel and privacy specialist
Gather
Entity status, fields, residents, sector licenses and contracts
Resolution needed
Written scope and definitions for the actual recipient; do not generalize GBS to every public body.

NY-Q02 Which additional sector or other-state modules are necessary?

Ask
Counsel and specialist
Gather
Business locations, customers, patients, students, contracts and regulator orders
Resolution needed
A named list of additional work; this first edition does not complete every state or sector.

Download the open-question register

Preparing the handoff

  • Data map uses actual fields and repository owners rather than a generic PII label.
  • Government, DFS and healthcare branches remain separate.
  • An active incident is escalated outside the ordinary preparation schedule.
  • Specialist receives a record index, masked examples and explicit limitations.

Download the record index. Use the shared walkthrough for custody, restricted records, missing information and receipt steps.

Sources for this package

Official laws/rules establish duties within their scope. Guidance explains programs; NIST supplies methods; vendor documentation describes possible product behavior. Actual contracts, facts, configuration and case orders still matter.

Privacy center

Choose your site settings

Optional technology stays off until you choose otherwise. You can change these browser settings at any time. Access to the core site does not depend on optional technologies.

Technology preferences
Sale or cross-context sharing: not used GDF does not sell or share website personal information for cross-context behavioral advertising.