EXPERTISE / DAT
Data protection
Know which data require protection, who may use them and how they may leave, be retained or be deleted.
WHAT TO ADDRESS
Choose the right engagement.
Minimisation, proportionality and investigation confidentiality must be scoped. No guarantee of zero leakage or comprehensive legal opinion.
6 results
DAT-01 / Data protection
Sensitive-data discovery and classification
Identify information requiring protection, where it resides, who owns it and how sensitive it is. Classification provides a practical basis for access, sharing, retention and protection decisions.
DAT-02 / Data protection
Multichannel data loss prevention — DLP
Detect and govern sensitive-data transfers through selected channels: email, cloud services, endpoints or removable media. DLP combines classification, policies, exceptions and human review of events.
DAT-03 / Data protection
Secure sharing and external collaboration
Enable exchanges with customers and partners without permanently exposing data to an overly broad audience. The project addresses links, guests, permissions, shared workspaces and removal procedures.
DAT-04 / Data protection
Encryption, key and certificate management
Protect data and communications through cryptography while organising key and certificate storage, rotation and recovery. Encryption that prevents recovery can itself become a risk.
DAT-05 / Data protection
Personal-data security and technical DPIA support
Assess and strengthen technical and organisational measures protecting personal data, supporting the DPO and controllers. The project supplies security evidence; it does not replace their legal assessment.
DAT-06 / Data protection
Insider data-risk management and proportionate investigation
Organise prevention and analysis of internal activity that may expose sensitive information without treating an alert as proof of misconduct. The programme combines data rules, investigation procedures and privacy safeguards.
No matching results. Try a broader term or another family.
SET THE BOUNDARIES
What we agree
before we start.
- Customer: business data owners, DPO/legal/HR as relevant, administrators and retention rules. Provider: technical design and verification within agreed permissions.
- Repositories, volumes, categories, channels, populations, formats and permission quality. DLP/classification licensing and event handling are separate from deployment.
Technology names in service descriptions are implementation examples, not claims of partnership or licence entitlement.
START A CONVERSATION
Let’s put the next step in focus.
Tell us what you need to protect, change or understand. We will start with the scope, not a product list.