Quick answer: A useful security camera handover checklist records who has access, how the system is reached, which firmware is installed and who maintains it. Verify the important functions with the customer, list open items and give each one an owner. Keep passwords, recovery codes and live access tokens out of the signed record.
On this page
Why does cybersecurity need a handover record?
The live pictures look right and recording has started. Months later, somebody asks who holds administrator access, whether a departed employee can still view cameras, or who was supposed to assess firmware advisories. A normal coverage and focus checklist may not answer those questions.
The cybersecurity handover makes the agreed configuration and responsibilities easy to find. Keep it alongside the installation and commissioning checklist. It records what was configured and tested on a particular date; it does not certify that the system is immune to compromise.
A one-page summary is useful, but it cannot sensibly contain every device version, user permission and network rule for a large site. Keep the summary short and reference protected inventory, access and test records. Do not shrink the text until nobody can read it.
What should the checklist record?
Copy this fill-in table into your project form. Choose Pass, Open or N/A for each line, then fill in the owner, verification date and initials. For an open item, describe the action in the related project record and add its due date. The blanks below are intended to be completed during the job; this example is not a completed acceptance record. On a narrow screen, scroll the table sideways to see the form columns.
| Item and what to record | Result | Owner and action date | Verified on |
|---|---|---|---|
| 1. System identity Site, date, full device inventory and firmware versions; reference the protected inventory. |
Pass / Open / N/A Choice: ______ |
Name: ______ Due, if open: ______ |
Date: ______ Initials: ______ |
| 2. Default and temporary access Defaults changed or disabled as supported; temporary accounts removed; exceptions assigned. |
Pass / Open / N/A Choice: ______ |
Name: ______ Due, if open: ______ |
Date: ______ Initials: ______ |
| 3. Customer administrator Named authorized administrator and the date secure access transfer was verified. No password on this form. |
Pass / Open / N/A Choice: ______ |
Name: ______ Due, if open: ______ |
Date: ______ Initials: ______ |
| 4. Named users and roles Who may view, play back, export or administer; reference the approved access list. |
Pass / Open / N/A Choice: ______ |
Name: ______ Due, if open: ______ |
Date: ______ Initials: ______ |
| 5. Installer/service access Separate authorized service account if needed, permissions, expiry/review date and how the customer can revoke it. |
Pass / Open / N/A Choice: ______ |
Name: ______ Due, if open: ______ |
Date: ______ Initials: ______ |
| 6. Remote access Approved method, device/software scope, tested functions and account/session revocation procedure. |
Pass / Open / N/A Choice: ______ |
Name: ______ Due, if open: ______ |
Date: ______ Initials: ______ |
| 7. Exposure and unused services UPnP/inbound mappings and unused services checked against the approved design; note unresolved exceptions. |
Pass / Open / N/A Choice: ______ |
Name: ______ Due, if open: ______ |
Date: ______ Initials: ______ |
| 8. Network boundary Camera segment, addressing/port-map reference, approved management paths and boundary test result. |
Pass / Open / N/A Choice: ______ |
Name: ______ Due, if open: ______ |
Date: ______ Initials: ______ |
| 9. Time Time zone, daylight-saving setting where applicable, configured time source and a sample recording/time check. |
Pass / Open / N/A Choice: ______ |
Name: ______ Due, if open: ______ |
Date: ______ Initials: ______ |
| 10. Web management HTTPS and other required controls tested where supported; record model-specific limitations. |
Pass / Open / N/A Choice: ______ |
Name: ______ Due, if open: ______ |
Date: ______ Initials: ______ |
| 11. Configuration and records Protected backup location, recovery instructions and who may retrieve them. |
Pass / Open / N/A Choice: ______ |
Name: ______ Due, if open: ______ |
Date: ______ Initials: ______ |
| 12. Recording and retention Required recording mode; estimated retention basis; measured oldest footage where available; follow-up verification date. |
Pass / Open / N/A Choice: ______ |
Name: ______ Due, if open: ______ |
Date: ______ Initials: ______ |
| 13. Playback and export Authorized person demonstrated required playback/export and knows the approved storage/transfer procedure. |
Pass / Open / N/A Choice: ______ |
Name: ______ Due, if open: ______ |
Date: ______ Initials: ______ |
| 14. Physical access and power Recorder location, key holders, airflow/power protection checks and any agreed runtime limitations. |
Pass / Open / N/A Choice: ______ |
Name: ______ Due, if open: ______ |
Date: ______ Initials: ______ |
| 15. Ongoing responsibility Maintenance/advisory owner, next review, installer service contact and any open action with its owner/date. |
Pass / Open / N/A Choice: ______ |
Name: ______ Due, if open: ______ |
Date: ______ Initials: ______ |
The CASE NVR hardening guide explains the access and configuration checks. Record the features available on this model and firmware; a generic checklist cannot create a control that the equipment does not support.
How do you transfer access without putting passwords on the form?
Let the authorized customer administrator set or change their password through an approved process, then verify the account works. Where supported, give each user an individual account and only the permissions needed for their role. Keep routine viewing separate from administrator access.
- Use an agreed secure channel or password-management process if credentials must be delivered. Record that transfer was completed, not the secret itself.
- Do not put passwords, recovery codes, live pairing codes or access tokens in the checklist, screenshots, email trail or shared project sheet.
- Remove temporary commissioning accounts and access you no longer need.
- If ongoing support requires installer access, use a separately authorized service account where supported. Record its purpose, permissions, review or expiry date and revocation method.
- Review remote-service memberships, linked devices and active sessions where those controls are available. Removing a local recorder user may not remove every remote access path.
- Use multifactor authentication on supported accounts and remote-access services where available. If a required control is absent, resolve the deployment with the customer’s IT contact rather than claiming it exists.
Confirm CASE Connect setup and account behavior for the actual device and software version. The app’s name does not establish a particular transport, role system or revocation behavior. The recorder user roles and permissions guide helps structure the access discussion.
Test service-account revocation before you depend on it
Agree a safe test window with the customer. Where the platform supports it, use a temporary, authorized service account with the intended limited role, rather than experimenting on an active operational account. Verify the customer’s administrator can still sign in before starting.
- Confirm which local and remote paths the temporary account can use, including any separate app or remote-service membership.
- Revoke or disable that test access through the supported controls. Remove linked sessions or tokens separately where the platform requires it.
- Attempt access again through each previously confirmed local and remote path. Record which paths are blocked and whether an existing session behaves differently from a new login.
- Verify that the customer’s administrator retains the required access. Remove temporary test accounts and record the result, limitations and any follow-up action.
Never disable an active service or customer account without explicit authorization and an agreed impact/recovery plan. If a revocation path cannot be tested safely, record it as open and resolve the procedure with IT and support. Do not mark it passed from a menu label alone.
What should you demonstrate with the customer?
Use the customer’s intended account rather than your installer administrator login. Confirm that it can perform the agreed functions and cannot perform actions outside its assigned role where the platform supports those restrictions.
- Open the required live views and play back a recent recording.
- Export a short non-sensitive test clip using the approved process; verify the recipient can use it as required.
- Test the approved remote connection from outside the site where remote access is included.
- Show how access for a departing employee is removed and how the result is checked.
- Point out the service contact, maintenance owner and any unresolved limitations.
Test the configured time source on the recorder and relevant cameras. Do not assume every camera inherits the recorder’s clock. Check a sample recording against the expected time and document time zone and daylight-saving settings where applicable.
Keep the camera network design and boundary tests in the protected project record. A network diagram alone does not show that the intended restrictions work.
| Stage | Useful evidence |
|---|---|
| Before the meeting | Complete the inventory, firmware and network records. Prepare the access list and identify open items. |
| With the authorized administrator | Verify their own login, named permissions, playback/export and approved remote access where in scope. |
| Resolve or assign exceptions | Describe each gap, interim arrangement, owner and target date. Do not mark an untested item as passed. |
| Accept and distribute | Record names, roles, date/time and the accepted state. Share the record securely with the agreed recipients. |
| After handover | Complete retention or other deferred checks on the agreed date and issue a dated update when the recorded state changes. |
How should you record retention on a newly commissioned system?
A new installation cannot demonstrate weeks of stored history on its first day. Record the required retention, installed storage, recording mode and the basis of the estimate. Note that scene activity, bitrate and other settings can affect the result.
Where history exists, record the oldest usable footage checked on representative channels and the date of the check. Schedule a follow-up after the system has had enough time to establish the required history. Label estimated retention and observed retention separately.
Playback and export should still be tested at handover using recordings already available. Do not postpone those basic checks simply because the full retention period has not yet elapsed.
How do you handle remote access and exceptions?
Record the approved method and who authorized it. Avoid exposing camera or recorder management and stream ports directly to the internet. Do not turn on UPnP or add inbound mappings merely to finish commissioning faster.
If the existing design includes a risky or unapproved path, raise it with the customer’s IT contact and assign a resolution before describing the system as accepted without qualification. A signature does not make an unsafe arrangement safe. The remote access guide provides the questions to resolve.
For every exception, write the condition, affected function, interim arrangement, responsible person and review date in plain language. For example: “Remote viewing not handed over; IT approval pending; local recording and playback tested; owner and target date recorded.” That is more useful than a vague note saying “customer aware.”
What does the acceptance section say?
Use names and roles for the customer’s authorized representative and the installer, with the date, time and record version. Reference the applicable service agreement and list the related documents and open items.
Describe acceptance as acknowledgment of the configuration, demonstrations and outstanding actions recorded. Do not present the form as a general liability waiver or a substitute for project contracts. Use the organization’s approved contract language for legal responsibilities.
“This record describes the access, recording and maintenance arrangements we reviewed today. Your passwords are not included. These items passed the listed checks, and these open items have named owners. Contact the installer before changing the network or adding a new remote-access route.”
Where do you keep the record, and when do you update it?
Store the signed summary and supporting records in the protected project folder with access limited to people who need them. The network plan and access list are sensitive even when they contain no passwords. Deliver the customer’s copy through the agreed secure process.
Update the record when firmware, users, remote access, network design or maintenance responsibility changes. Keep earlier dated versions as history. A review that finds no change can still be recorded with its date and reviewer.
Connect the follow-up dates to the firmware maintenance calendar. Keep the incident contact and escalation path beside the suspected camera-system breach procedure, so the customer knows whom to call.
FAQ
Should an installer keep the customer’s administrator password?
Do not make that the default support arrangement. Agree an authorized access process and use a separate documented service account where supported and required. Keep secrets in the approved secure system, never on the handover checklist.
Does a signed checklist prove the system is secure?
No. It records the state, tests and responsibilities at a point in time. Maintain the system, review access and assess relevant advisories afterwards. Record unresolved limitations rather than treating a signature as a technical control.
Can the checklist stay on one page?
A concise summary can, especially for a small installation. Link it to the inventory, access list, network plan and test results when more detail is needed. Keep it readable instead of compressing a large system’s record into tiny text.
Can we sign off retention on installation day?
Record the requirement and estimate at commissioning, and identify the later check needed to confirm observed history. Do not describe an estimate as footage already recorded. Test available playback and export immediately.
Who should sign for the customer?
A representative authorized to accept the installation and its recorded responsibilities. Confirm the administrator and maintenance contacts separately if they are different people. Do not assume the person present on site has every required authority.
Need model-specific answers before handover? Obtain manuals and approved firmware through the Anabon Download Center, then send the full SKUs, versions and test questions to Anabon technical support. Anabon supports the installer and integrator; the customer’s service relationship remains with the partner.
