DATPOL · DESIGN · IMPLEMENTATION · SUPPORT
Cybersecurity that supports business continuity.
Security reviews, IT/OT protection, backups and incident support. DATPOL IT and LCPD connect practical implementation with agreed ongoing services.
Discuss your site
Explore the systems and services
- Do you know what happens after an outage or attack?
- DATPOL IT: implementation and day-to-day support
- LCPD: security events and service availability
- Identities, email and endpoints
- Networks, branches and OT security
- Backups that can be restored
- Incident response and an action plan
- Documentation and organisational requirements
- Choose the scope of engagement
01 / DATPOL
Do you know what happens after an outage or attack?
Blocked email, unavailable files, a failed sales system or interrupted production are operational problems, not merely IT issues. We start with the services that sustain revenue and staff activity, establishing owners, dependencies, acceptable downtime and recovery order.
You receive prioritised risks and an action plan: urgent fixes, planned improvements and monitoring needs. The scope can cover offices, branches, servers, cloud services and industrial systems. Protection is not reduced to buying one appliance.
02 / DATPOL
DATPOL IT: implementation and day-to-day support
DATPOL IT connects security with administration of servers, workstations, networks and user services. We address accounts, permissions, updates, remote access, configurations and backups, defining responsibility for the agreed environment.
Employee support, joiner and leaver processes and change approval are agreed together. Documentation and controlled access reduce dependence on a single administrator. Detailed services and delivery commitments are contractual.
03 / DATPOL
LCPD: security events and service availability
LCPD offers a route to managed monitoring: collecting and analysing agreed logs, security signals and infrastructure availability. SOC, SIEM, XDR/MDR or NOC scope is selected around actual data sources and organisational needs.
Before activation we define coverage, alert recipients, decision owners and permitted response actions. Service hours, escalation, log retention and responsibility boundaries matter. Service levels and responsibilities are agreed, not an implied promise of continuous protection.
04 / DATPOL
Identities, email and endpoints
We deploy multi-factor authentication where supported, separate administrative accounts and reduce excessive privileges. Shared accounts, former staff and external support access are reviewed. Recovery arrangements are documented so controls do not lock the organisation out.
The scope can cover endpoint protection, encryption, updates, email policies and phishing reduction. Staff training is paired with a simple suspicious-message reporting process. Social-engineering exercises require a separately agreed scope and rules.
05 / DATPOL
Networks, branches and OT security
We design segmentation, firewall policies, VPNs and controlled service access. Internet-facing services, device management and inter-branch connections are reviewed. Guest Wi-Fi, cameras and automation should not have unrestricted access to business servers.
Safe process operation takes priority in production. Inventory, monitoring and changes account for controller limitations, maintenance windows and rollback. Active scanning and penetration tests require a written, agreed scope; intrusive testing is not a default activity on an OT network.
06 / DATPOL
Backups that can be restored
We define the data and configurations to protect, backup frequency and acceptable recovery delay. Separating backup access from production accounts and adding protection against modification can limit the consequences of a compromise.
Restoration is tested at the agreed level: a file, machine, application or complete service. A successful backup-job report does not prove business operations can resume. RPO and RTO are set for particular systems and checked through testing, rather than declared uniformly.
07 / DATPOL
Incident response and an action plan
We agree reporting, triage, escalation and authority to isolate a device or suspend an account. The plan identifies decision-makers, evidence preservation, recovery and communications. The responsible organisation assesses notification duties with appropriate legal support.
After an incident we review causes and control effectiveness and propose remedial action. Intervention scope, staffing coverage and response targets are contractual. We do not promise immunity to every attack or recovery of all data in every situation.
08 / DATPOL
Documentation and organisational requirements
We help organise asset inventories, risks, access policies, backup procedures, change processes and evidence of control operation. Where sectoral or cybersecurity requirements apply, their specific scope and specialist support needs are established with the organisation.
Buying a service, firewall or SIEM does not constitute certification or automatic compliance. Technical implementation needs a process owner, documentation, acceptance testing and periodic review. Obligations are not assigned solely from a broad industry label.
09 / DATPOL
Choose the scope of engagement
Assessment: a review of the agreed environment, risks and improvement plan. Implementation: defined controls, migration or configuration improvements with testing. Ongoing support: DATPOL IT and selected LCPD services, reviews, monitoring and contractual support.
Pricing reflects users, servers, locations, cloud and OT systems, log sources, retention and required support hours. One-off work, licences and recurring charges are separated. Send a short infrastructure overview and we will agree the first step and measurable acceptance criteria.
Plan the next step.
A new system, an upgrade or a maintenance plan? Send the site details and available documentation.
[email protected]
+48 55 621 29 29