Comparison Overview
SegurPro

SegurPro
Av. Ermano Marchetti, 1435, São Paulo, 05038-001, BR
Last Update: 03/04/2026
A SegurPro é o próximo passo em segurança privada. Uma empresa que conta com uma equipe de 30 mil profissionais de alto nível aliada à tecnologia de ponta e que já nasce com a expertise de mais de 40 anos de experiência herdada do Grupo Prosegur. Somos mais que uma empr...

Securitas Nederland
De Corridor 3a, Breukelen, Utrecht, NL, 3621
Last Update: 01/04/2026
Door de juiste inzet van mens, kennis en techniek vinden we de ideale ‘veiligheidsbalans’ voor iedere situatie. Dat begint altijd met heel goed luisteren om zo te doorgronden wat de specifieke omstandigheden en wensen van de klant zijn. Vervolgens groeien we samen naar ...
Compliance Ranges Comparison

SegurPro







Securitas Nederland






Benchmark & Cyber Underwriting Signals
Incidents vs Security and Investigations Industry Avg (This Year)
No incidents recorded for SegurPro in 2026.
Incidents vs Security and Investigations Industry Avg (This Year)
No incidents recorded for Securitas Nederland in 2026.
Incident History - SegurPro (X = Date, Y = Severity)
SegurPro cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Securitas Nederland (X = Date, Y = Severity)
Securitas Nederland cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

SegurPro

Securitas Nederland
FAQ
Latest Global CVEs
Buffer Overflow vulnerability in Systerel S2OPC 1.7.3 allows a remote attacker to cause a denial of service via the Alarm/Conditions wrapper when processing PublishResponse EventNotificationList data
- https://github.com/gff-cw/information/issues/18
- https://github.com/systerel/S2OPC/blob/S2OPC_Toolkit_1.7.3/src/ClientServer/address_space/sopc_event_manager.c
- https://github.com/systerel/S2OPC/blob/S2OPC_Toolkit_1.7.3/src/ClientServer/frontend/client_wrapper/alarm_conditions/libs2opc_client_alarm_conditions.c
- https://github.com/systerel/S2OPC/blob/S2OPC_Toolkit_1.7.3/src/ClientServer/frontend/client_wrapper/internal/state_machine.c
- https://gitlab.com/systerel/S2OPC/-/work_items/1781
Buffer Overflow vulnerability in Systerel S2OPC 1.7.3 allows a remote attacker to cause a denial of service via the LockedStaMac_ProcessMsg_DeleteMonitoredItemsResponse and SOPC_StaMac_NewDeleteMonitoredItems in the client wrapper DeleteMonitoredItems path
- https://github.com/gff-cw/information/issues/16
- https://github.com/systerel/S2OPC/blob/master/samples/ClientServer/client_wrapper/examples/subscribe.c
- https://github.com/systerel/S2OPC/blob/master/src/ClientServer/frontend/client_wrapper/internal/state_machine.c
- https://gitlab.com/systerel/S2OPC/-/work_items/1780
In open62541 1.5.5, a server-side use-after-free exists in the local MonitoredItem callback path. The issue occurs when UA_Subscription_localPublish continues to use the current UA_Notification after a callback invokes UA_Server_deleteMonitoredItem for the current local MonitoredItem. This allows a remote attacker to cause a denial of service.
H5Z__filter_nbit in H5Znbit.c in HDF5 through 2.3.0 dereferences cd_values[0] through cd_values[4] without validating that cd_values is non-NULL or that cd_nelmts is at least 5, the fixed size of the filter's header. This allows attackers to cause a denial of service via a crafted HDF5 file that stores the N-Bit filter pipeline message with zero client-data values, opened and read via H5Dread, e.g. by the h5ls or h5repack tools.
H5O__layout_decode in H5Olayout.c in HDF5 through 2.3.0 does not validate that a chunked dataset's stored chunk-layout dimensionality matches its dataspace rank when an existing dataset is opened, whereas this check is performed only at dataset-creation time. This allows attackers to cause a denial of service (divide-by-zero and application crash in H5S__hyper_iter_get_seq_list in src/H5Shyper.c) via a crafted HDF5 file with mismatched chunk/dataspace ranks that is opened and read via H5Dopen2 and H5Dread, e.g. by the h5repack tool.