COPRSETR WORKSHEET
Australian smart device security evidence
Australia smart device security · Step 2 · Verify passwords, reporting and support disclosures- Who prepares it
- Product security + firmware + customer support
- When to prepare it
- Before approving the model for supply
Worked example
This example uses fictional details. Use the same fields with evidence from your work.
- Fictional test entry
- On two initial production samples, setup requires a user-defined password. A second reviewer repeats the check after reset and signs the evidence record.
- Publication evidence
- The manufacturer saves dated copies of its reporting instructions, firmware support end date and separate companion app support end date.
Gather first
- Production model and firmware
- Setup and reset documentation
- Software component list
- Published reporting and support pages
- Schedule 1
How to prepare it
- Verify the applicable password flow on production-representative devices and software. Record the unique or user-defined route and review the method against the generation restrictions.
- Review the published public reporting contact and promised timing for acknowledgement and status updates. Confirm that English guidance is free and available without sign-in or requesting personal information to display it.
- Record each updateable component in scope and its defined support end date. Test the manufacturer-controlled product pages and record where the support information appears.
Review
A reviewer can verify each of the three Schedule 1 requirements against the actual device and public information.
Handoff
Give the manufacturer signer the reviewed evidence and give Support the reporting and update commitments.
Use the issuer’s current instructions and any required forms when you submit.
Schedule 1 security requirements (opens in a new tab)