One Net
Talk to an expert

Sentrify

Maritime security. Backed by specialists.

Protect vessel endpoints and networks with Sentrify. Choose endpoint security or add SIEM and 24/7 SOC monitoring through Managed Security.

Talk to an expert
SentrifyManaged cybersecurity
EndpointSentinelOne

Threat detection & containment

NetworkWatchGuard

Traffic control & inspection

VisibilityRa Security

Vulnerability scanning & reporting

One Net specialistsMonitor. Investigate. Coordinate.

Managed maritime cybersecurity

Turn security signals into coordinated action.

Connect endpoint and network controls with specialist oversight. Agree who investigates, approves and acts before monitoring begins.

Bring the signals together

Endpoint protection, network controls and security-event monitoring cover different parts of the environment.

Investigate the context

Specialist monitoring supports assessment of the event and the affected systems.

Coordinate the response

Work through agreed incident responsibilities, remediation and security reporting.

Capabilities

Protection across devices and networks.

Endpoint protection

SentinelOne supports threat detection, device controls and containment at the endpoint.

Network defence

WatchGuard controls and inspects traffic at the network boundary.

Vulnerability scanning

Ra Security scans the systems in scope for vulnerabilities and provides findings for review and remediation planning.

Managed monitoring and response

Managed Security includes 24/7 SOC monitoring, SIEM, incident analysis and fleet security reporting.

Inside the service

Understand each layer of protection.

Sentrify combines specialist security operations with endpoint, event and network controls. The service configuration determines which components are deployed and which monitoring, investigation and response responsibilities One Net takes on.

SentinelOne endpoint protection

Behavioural detection helps identify malicious activity on protected endpoints. Device and USB controls, network containment and remediation capabilities support the response to malware and ransomware.

  • Confirm the devices and operating systems to be protected.
  • Agree agent deployment, policy ownership and containment permissions.
  • Review endpoint alerts alongside the wider vessel context.
Ra Security vulnerability scanning

Vulnerability scanning identifies findings for the security team to assess. The tool contributes evidence about exposure; investigation, incident response and remediation responsibilities belong to the managed service and the people authorised to act.

  • Agree the systems and network segments included in the assessment.
  • Review findings in the context of the equipment and its operational role.
  • Prioritise remediation, approvals and follow-up checks with your team.
Logging and security-event review

The security engagement defines which events and logs specialists use when investigating an issue. Source coverage, collection and reporting are part of the agreed service scope, rather than an assumed capability of every installed tool.

  • Identify the endpoint, firewall and other sources available for review.
  • Agree access to records, retention requirements and handling responsibilities.
  • Confirm any additional SIEM, operational-equipment monitoring or forensic requirements with the security specialist.
WatchGuard gateway controls

The firewall provides a separate control point at the network boundary. Unified Threat Management, intrusion prevention, application control, gateway antivirus and advanced-threat inspection complement endpoint security.

  • Define the vessel’s business, crew and operational network boundaries.
  • Agree application policies, web filtering and permitted traffic.
  • Review firewall events together with endpoint and security-event information.
Security operations and reporting

The managed service provides a route from alerts to investigation, coordinated response and fleet security briefings. Published services include vulnerability assessment, incident analysis and forensic support; the engagement defines their availability and scope.

  • Agree monitoring coverage, severity levels and escalation contacts.
  • Record who may isolate equipment or authorise remediation.
  • Use vulnerability reports, incident trends and fleet briefings to prioritise the next actions.
Evidence for maritime cyber-risk management

Technical controls and reporting support the work of your safety, security and IT teams. They do not by themselves certify a vessel or establish regulatory compliance.

  • Review the requirements applicable to your fleet and Safety Management System.
  • Agree the reports, incident records and configuration evidence needed for reviews.
  • Confirm the responsibilities of the owner, operator, service provider and relevant approval bodies.
Discuss the service scope

Choose the service relationship

Choose the security scope first.

Choose Endpoint Security for protection and basic alerts, or Managed Security for 24/7 SOC monitoring, SIEM and deeper reporting.

Bronze covers up to 9 devices, Gold up to 14 and Platinum up to 19. We’ll confirm the devices, components and service commitments in your proposal.

Compare support plans

Define the response boundary

Agree the response before it is needed.

Review an incident from first signal to next action: the systems covered, the people authorised and the records retained.

What is covered

List the endpoints, gateways and event sources included in the service.

Record systems outside the scope, particularly equipment with manufacturer-controlled access.

Who may act

Confirm who investigates, who approves containment and who communicates with the vessel.

A monitoring licence does not by itself assign authority to interrupt an operational system.

What is recorded

Review the incident and vulnerability information included in the reporting arrangement.

Keep findings, response actions and outstanding remediation distinct so each has an owner.

Connected services

Connect Sentrify to the wider operation.

Combine security oversight with Zwana’s onboard infrastructure and abela IT maintenance through one service relationship.

Plan your deployment

Know what your security service covers.

Agree the protected systems, monitoring coverage and response responsibilities before the service starts.

Can Sentrify work with our current controls?

One Net first reviews existing tools, endpoints and network arrangements. The managed scope is then agreed around that environment.

Who decides on remedial action?

Investigation, coordination and approval responsibilities are agreed with your team as part of the service scope.

How is it different from managed IT?

Sentrify focuses on security. abela IT focuses on infrastructure visibility, maintenance and remote remediation. The two disciplines work alongside one another.

Scope follows your environment

One Net reviews the endpoints, network arrangements and security tools you already run. The managed boundary is agreed around that environment rather than around a standard package.

Response responsibilities are named

Define who investigates, coordinates and approves action on both sides, including the permissions and escalation routes in the service scope.

Talk to One Net

Build the right protection for your fleet.

Tell us about your devices, network and existing security tools. We’ll help you choose the Sentrify plan and response model that fit your team.

Discuss Sentrify
What to bring to the conversation
The protection scope
Endpoints, network boundaries and existing security tools.
The response model
Investigation, approvals and incident coordination responsibilities.
The evidence required
Vulnerability reporting, security briefings and internal review requirements.