Colour theme
Book a consultation

Understanding SEC cyber disclosure requests

Distinguish SEC issuer disclosure rules from Canadian privacy duties and customer contract requests, then prepare accurate incident and control records.

An illustration of a document with a padlock against blue digital patterns.

A Canadian supplier may receive a cybersecurity questionnaire or urgent incident request from a customer subject to US securities rules. That customer’s obligation and your own obligations need separate review.

Start with the contract, the request and the legal status of the organizations involved. Don’t assume the same filing deadline applies to every Canadian business.

Understand which issuer rules are involved

The SEC’s compliance guide explains the incident and annual cybersecurity disclosures adopted in 2023.

For domestic registrants, Form 8-K Item 1.05 generally requires disclosure within four business days after determining that an incident is material. The trigger isn’t simply discovering an incident. The rules also address the timing of materiality assessment and limited delay provisions. Industry groups have petitioned the SEC to rescind the incident-reporting requirement, so check the rule’s current status with counsel.

Foreign private issuers use different forms and triggers, including Form 6-K and annual Form 20-F disclosures. Have securities counsel determine any direct obligations. A Canadian company isn’t automatically outside the rules, and ordinary business registration isn’t SEC registrant status.

Read the customer contract separately

A customer’s reporting needs may appear in supplier terms. Check the definition of an incident, notification timing, required contact and updates.

A contract can require information sooner than a public filing. Record the contract’s own deadline. Don’t borrow the four-day filing period from an article.

Ask the account owner and legal adviser to resolve unclear wording before an incident. Include subcontractor and service-provider dependencies.

Prepare facts the customer can use

Maintain a current service and data inventory. Know which customer services depend on the affected system and who can work out the scope.

During an incident, distinguish confirmed facts, preliminary findings and unanswered questions. Record the time of each update and the person who approved it.

Don’t claim a control is operating solely because a policy says it should. Use configuration records, coverage reports and test evidence when answering a questionnaire.

Keep Canadian privacy duties in view

Where PIPEDA applies, the OPC’s breach guidance sets separate reporting, notification and record-keeping obligations. Provincial and sector requirements may also apply.

Have the accountable privacy person assess those duties alongside contractual and securities requirements. Sending an update to a customer doesn’t by itself discharge them.

Assign the response process

Name the incident coordinator, customer contact and advisers who review disclosure. Preserve relevant evidence and avoid exposing unnecessary personal information in updates.

Keep this process with the vendor-incident guide. Review it when contracts or customer reporting requirements change.


Featured Image Credit