Comparison Overview

G4S

VS

ORIONSECURE

G4S

6th Floor, London, SW1H 0DB, GB
Last Update: 2025-11-21
Between 800 and 849

G4S is a leading security and facility services company that provides proactive security services and cutting-edge smart technology to deliver tailored, integrated security solutions that allow clients to focus on their core business. Through a global workforce of approximately 800,000 people, we leverage best practices in communities all over the world. With revenues at approximately $20 billion, we are supported by efficient processes and systems that can only come with scale to help deliver our promise locally: keeping people safe so our communities can thrive. For more information on G4S, visit www.g4s.com.

NAICS: 5616
NAICS Definition: Investigation and Security Services
Employees: 113,216
Subsidiaries: 3
12-month incidents
0
Known data breaches
0
Attack type number
0

ORIONSECURE

5-E, 1st Floor, Jungi House, Street No. 5 Shahpur Jat, New Delhi 110049, IN
Last Update: 2025-11-24
Between 750 and 799

At ORIONSECURE, we are a leading provider of both Traditional and New-Age Security Services. ORIONSECURE is the flagship & holding company of the larger ORION Group. At ORION we protect and support your people, premises and assets through our end to end solutions for : - Security Services - Facility Management Services - Investigation & Intelligence Services - Research & Consulting Service - Skill & Training Division Established in 2005, The Orion Group has operations across all states of India, Middle East, Africa and Europe. Headquartered in New Delhi, India, It is a professionally run enterprise that is led by Senior Business & Operations Leaders from across industry. ORIONSECURE has sustained high growth YOY for the part the past 3 years and has grown to be one of the most trusted and respected names in the industry.

NAICS: 5616
NAICS Definition: Investigation and Security Services
Employees: 10,001
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/g4s.jpeg
G4S
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
https://images.rankiteo.com/companyimages/orionsecure.jpeg
ORIONSECURE
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
Compliance Summary
G4S
100%
Compliance Rate
0/4 Standards Verified
ORIONSECURE
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Security and Investigations Industry Average (This Year)

No incidents recorded for G4S in 2025.

Incidents vs Security and Investigations Industry Average (This Year)

No incidents recorded for ORIONSECURE in 2025.

Incident History — G4S (X = Date, Y = Severity)

G4S cyber incidents detection timeline including parent company and subsidiaries

Incident History — ORIONSECURE (X = Date, Y = Severity)

ORIONSECURE cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/g4s.jpeg
G4S
Incidents

No Incident

https://images.rankiteo.com/companyimages/orionsecure.jpeg
ORIONSECURE
Incidents

No Incident

FAQ

G4S company demonstrates a stronger AI Cybersecurity Score compared to ORIONSECURE company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, ORIONSECURE company has disclosed a higher number of cyber incidents compared to G4S company.

In the current year, ORIONSECURE company and G4S company have not reported any cyber incidents.

Neither ORIONSECURE company nor G4S company has reported experiencing a ransomware attack publicly.

Neither ORIONSECURE company nor G4S company has reported experiencing a data breach publicly.

Neither ORIONSECURE company nor G4S company has reported experiencing targeted cyberattacks publicly.

Neither G4S company nor ORIONSECURE company has reported experiencing or disclosing vulnerabilities publicly.

Neither G4S nor ORIONSECURE holds any compliance certifications.

Neither company holds any compliance certifications.

G4S company has more subsidiaries worldwide compared to ORIONSECURE company.

G4S company employs more people globally than ORIONSECURE company, reflecting its scale as a Security and Investigations.

Neither G4S nor ORIONSECURE holds SOC 2 Type 1 certification.

Neither G4S nor ORIONSECURE holds SOC 2 Type 2 certification.

Neither G4S nor ORIONSECURE holds ISO 27001 certification.

Neither G4S nor ORIONSECURE holds PCI DSS certification.

Neither G4S nor ORIONSECURE holds HIPAA certification.

Neither G4S nor ORIONSECURE holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.16, 20.3.14, and 21.0.1, there is a XSRF token leakage via protocol-relative URLs in angular HTTP clients. The vulnerability is a Credential Leak by App Logic that leads to the unauthorized disclosure of the Cross-Site Request Forgery (XSRF) token to an attacker-controlled domain. Angular's HttpClient has a built-in XSRF protection mechanism that works by checking if a request URL starts with a protocol (http:// or https://) to determine if it is cross-origin. If the URL starts with protocol-relative URL (//), it is incorrectly treated as a same-origin request, and the XSRF token is automatically added to the X-XSRF-TOKEN header. This issue has been patched in versions 19.2.16, 20.3.14, and 21.0.1. A workaround for this issue involves avoiding using protocol-relative URLs (URLs starting with //) in HttpClient requests. All backend communication URLs should be hardcoded as relative paths (starting with a single /) or fully qualified, trusted absolute URLs.

Risk Information
cvss4
Base: 7.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Uncontrolled Recursion vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft deep ASN.1 structures that trigger unbounded recursive parsing. This leads to a Denial-of-Service (DoS) via stack exhaustion when parsing untrusted DER inputs. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 8.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Integer Overflow vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft ASN.1 structures containing OIDs with oversized arcs. These arcs may be decoded as smaller, trusted OIDs due to 32-bit bitwise truncation, enabling the bypass of downstream OID-based security decisions. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 6.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. Prior to versions 7.0.13 and 8.0.2, working with large buffers in Lua scripts can lead to a stack overflow. Users of Lua rules and output scripts may be affected when working with large buffers. This includes a rule passing a large buffer to a Lua script. This issue has been patched in versions 7.0.13 and 8.0.2. A workaround for this issue involves disabling Lua rules and output scripts, or making sure limits, such as stream.depth.reassembly and HTTP response body limits (response-body-limit), are set to less than half the stack size.

Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Description

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. In versions from 8.0.0 to before 8.0.2, a NULL dereference can occur when the entropy keyword is used in conjunction with base64_data. This issue has been patched in version 8.0.2. A workaround involves disabling rules that use entropy in conjunction with base64_data.

Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H