@proseid v1.0.0 US

SEC material cybersecurity incident disclosure record

Tracks the materiality determination, Form 8-K Item 1.05 content, filing deadline, permitted Attorney General or FCC-rule delay, and amendment status for a material cybersecurity incident.

Compatible with

FormGuided assessmentDeterminationCompliance checklistAPI

Use Schema in a Flow

Publication

Protocol: Proseid_v1.0
Version: v1.0.0
Applies in: United States
Fields: 18
Flow price: $0.20
Publisher fee: None

Legal history

Time periods

item_105_all_domestic_registrants2024-06-15 → continues indefinitely

Current

Controlling sources

Legal references

Form 8-K Item 1.05(a)–(d)

Source ↗

FCC breach-notification rule 47 CFR § 64.2011

Source ↗

Securities Exchange Act Release No. 97989 Cybersecurity Risk Management, Strategy, Governance, and Incident Disclosure

Source ↗

SEC Division of Corporation Finance statement Disclosure of material and other cybersecurity incidents (21 May 2024)

Source ↗

Schema fields

18 fields

Field

Type

Description

Req

Material or reasonably likely material impact

String

—

Opt

Form 8-K Item 1.05 filed

Boolean

—

Opt

Registrant type

Select

Choices: Domestic Form 8k Filer, Foreign Private Issuer, Not Sec Registrant

Req

Disclosure track

String

—

Opt

Required information was undetermined or unavailable at filing

Boolean

—

Opt

FCC-rule notification date, time, and zone

String

—

Opt

Date materiality was determined

Date

—

Opt

47 CFR 64.2011 requires this registrant to delay public disclosure

Boolean

—

Opt

The U.S. Attorney General made the required delay determination and notified the SEC in writing

Boolean

—

Opt

The planned delay stays within the FCC period and Item 1.05 limit

Boolean

—

Opt

Required Form 8-K amendment filed when information became available

Boolean

—

Opt

Last permitted date under the FCC delay route

Date

—

Opt

Materiality assessment

Select

Choices: Assessment Pending, Determined Not Material, Determined Material

Req

SEC delay correspondence submitted through EDGAR by the ordinary Item 1.05 due date

Boolean

—

Opt

Internal incident reference

String

—

Req

Filed within four business days after materiality determination

Boolean

—

Opt

Material aspects of nature, scope, and timing

String

—

Opt

Registrant

String

—

Req

Example payload

JSON

{
  "responses": {
    "material_impact": "",
    "item_105_filed": false,
    "registrant_type": "",
    "information_unavailable_at_filing": false,
    "fcc_required_notification_at": "",
    "materiality_determination_at": "",
    "fcc_delay_required_under_47_cfr_64_2011": false,
    "ag_delay_determination_and_sec_notice": false,
    "fcc_delay_within_item_105_limit": false,
    "amendment_filed_when_available": false,
    "fcc_delay_end_date": "",
    "materiality_status": "",
    "sec_edgar_delay_correspondence_submitted_on_time": false,
    "incident_reference": "",
    "filed_within_four_business_days": false,
    "nature_scope_timing": "",
    "registrant_name": ""
  },
  "effective_at": "2026-07-23"
}

The request body this schema expects. Fill in responses and keep the field IDs unchanged. Validation becomes callable after you use this release in a published Flow.

API usage

Create a Flow from this schema, then replace the route placeholders with that Flow's organization and address. Validation is free and runs against the exact release bound to the Flow. It returns the engine's resolved fields and legal time period when ready, or a structured error with field-level issues.

cURL

curl -X POST https://proseid.com/api/v1/validate/{your-org}/{flow-slug} \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d @payload.json

200 OK

{
  "valid": true,
  "status": "READY",
  "definitions": { ... },
  "issues": [],
  "effective_at": "2026-07-19",
  "temporal_context": {
    "logic_version": "current",
    "valid_range": ["2026-01-01", null]
  }
}

422 Invalid

{
  "error": {
    "code": "validation_failed",
    "message": "the document did not pass validation",
    "details": {
      "status": "INCOMPLETE",
      "issues": [{
        "field_id": "material_impact",
        "kind": "missing_required",
        "severity": "error",
        "trigger": "completion",
        "message": "Required field is missing"
      }]
    }
  }
}

A completed webhook also depends on the Flow's experience, signing, pricing, and delivery settings. Create a Flow with this schema, then use Send sample completion in its delivery settings to receive the full signed JSON without using your balance. Webhook guide

Published versions

Permanent, attributable versions

Loading published versions…

Trust ledger

Crowd → credentialed

Provenance

Community publisher (unverified)

@proseid · latest v1.0.0

Community signal

0 votes

No votes yet.

Attestations · by version

0 total

No attestations yet. A verified professional can vouch for a specific version.

Discussion

0 comments

to join the discussion.

Time periods

Legal references

Schema fields

Example payload

API usage

Published versions

Trust ledger

Discussion

EU right-of-withdrawal record

OSHA fatality or severe-injury reporting determination

California CCPA consumer-request lifecycle

HIPAA breach-notification determination