Scope
Identify data, users, devices and suppliers.
Understand the difference between data protection law, security standards and the controls agreed for your Fleetly deployment.
Identify data, users, devices and suppliers.
Obtain current technical and contractual evidence.
Record required controls and responsibilities.
Review access and assurance as the service changes.
Fleet information can include locations, identifiable drivers and video evidence. A security review should cover the service, connected devices, user access, integrations and the people who administer them—not just the hosting provider.
This page explains the assurance questions to resolve. It does not assert that Fleetly holds ISO certification, Cyber Essentials Plus certification or a particular audited control. Request current evidence for the contracting entity and service scope.
Explore the operational requirements and confirm the scope for your selected Fleetly service.
These are data protection requirements, not product certifications. Define processing purposes, responsibilities, retention and rights handling in the relevant agreements.
A standard for an information security management system. If certification is required, check the legal entity, service scope, issuing body and validity of the certificate.
A certification scheme with independent technical testing of baseline cyber controls. Check the current certificate and scope; it is not proof of GDPR compliance.
Request details of authentication, permission boundaries, encryption, logging, vulnerability management and incident handling for the service you will use.
Use your vehicles, devices, users and operating scenarios to check the proposed solution before rollout.
Fleetly makes sophisticated fleet technology usable by connecting each signal to a decision, an owner and an outcome.
Identify data, users, devices and suppliers.
Obtain current technical and contractual evidence.
Record required controls and responsibilities.
Review access and assurance as the service changes.
Ask for the applicable data processing terms, subprocessor information, retention arrangements, incident reporting process and evidence of relevant security testing. Sensitive technical details may need to be shared through an appropriate review process.
A cloud provider’s certification does not automatically certify Fleetly. Contractual assurances should identify the actual services and data flows covered, including connected devices and external integrations.
Explore the open Fleetly ecosystemTalk to Fleetly for a solution assessment based on your vehicles, devices, operating model and required outcomes.
No current certificate is presented on this page. Request documentary confirmation of the legal entity, scope and validity before treating certification as a procurement requirement met.
No. Location is one part of the review; processing purposes, access, security, retention, transparency and transfer arrangements also matter.
We will focus the demonstration on your vehicles, risks, workflows and existing technology.