Access
Device, cloud and contractor accounts. Shared passwords, permissions and available multi-factor authentication.
IoT security.Clear next steps.
Know your devices, control access, and turn security gaps into a clear, tested action plan.
01 / The assessment
Know what to fix first.
For businesses running cameras, access control, sensors and gateways. We assess the devices and the accounts, networks and cloud services around them.
Exposure
Network boundaries, remote connections and the services each device needs to reach.
Lifecycle
Configuration, updates, support dates, data handling and recovery arrangements.
Your team receives
- 01
Inventory & access map
Devices, owners, support status and important connections in one working record.
- 02
Prioritised actions
Practical fixes ordered by business impact, with an owner for each action.
- 03
Verification criteria
Clear checks for each improvement, including evidence and remaining limitations.
02 / Ways to work together
Choose your starting point.
Start with an assessment, implement agreed changes, or keep security tasks under regular review.
Assessment
Understand your devices, access and exposure. Leave with a prioritised action plan.
Discuss an assessmentHardening
Put agreed configuration, account and network changes into practice. Verify and document the result.
Discuss hardeningOngoing support
Review devices, access and updates at an agreed cadence, with defined responsibilities and support hours.
Discuss ongoing support03 / In practiceDemonstration. Not a customer result.
Who still has access to the cameras?
The installation is finished. Your team needs to know whether the contractor can still connect.
- Trace
- Identify local accounts, cloud permissions and remote access routes.
- Change
- Agree necessary permissions and introduce named, time-limited contractor access.
- Verify
- Check that authorised work succeeds and revoked access fails. Record the evidence.
04 / Practical questions
Before we start.
Can you work with existing devices?
Yes, across manufacturers where access and device capabilities allow. If a control is unavailable, we consider network restrictions, operating procedures or replacement.
Will the work interrupt operations?
We agree methods and operating constraints first. Sensitive systems may need passive checks, a test environment or a maintenance window. Changes include recovery arrangements.
What determines cost and timing?
Locations, device types, available access and testing depth. We agree scope, deliverables and fees before work begins. Implementation and ongoing support can be scoped separately.
Guidance: NIST IR 8228, NIST OT security and OWASP ISTG. Controls follow the agreed scope.
Start with one environment
Diagnose a ProcessMake the next step clear.
Tell us what is connected and what needs to keep working. We’ll agree the first useful action.