Comparison Overview

Settify

VS

Lexgo

Settify

11/459 Little Collins Street, Melbourne, VIC, 3000, AU
Last Update: 2025-11-28
Between 700 and 749

Settify is a global Legal Tech company with headquarters based in Melbourne, Australia. We provide law firms with technology that enables clients to get started online. Clients engage with interactive, conversational online systems, helping them to understand where they stand, the issues they'll face and how their lawyers can assist. Our systems use Artificial Intelligence and Expert systems to intelligently seek all of the client's key background information, which is summarised into a brief for their lawyers. Launched in 2017, Settify has been adopted by hundreds of firms around Australia, New Zealand, the United Kingdom, and Canada. It has helped tens of thousands of clients to engage with their lawyers, whose legal concerns total in the hundreds of billions of dollars. Settify has received multiple awards, for innovation, marketing, and technology. We believe that technology will improve the power, efficiency and effectiveness of legal services. Our core philosophy however, is that the relationship of trust between lawyers and clients will always be paramount. We use technology to make the law more human.

NAICS: 541
NAICS Definition:
Employees: 18
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Lexgo

Callao 2911, Las Condes, Santiago Metropolitan Region, CL, 7550293
Last Update: 2025-11-29
Between 700 and 749

Lexgo offers legal advise and represents hundreds of companies in the Americas. Our clients trust us for the creation of new branches, the legal administration of their companies, international hiring and tax compliance. Our service exceeds the expected user experience in the industry by focusing on constant communication, speedy delivery and customer success.

NAICS: 5411
NAICS Definition: Legal Services
Employees: 19
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/settify.jpeg
Settify
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/lexgohq.jpeg
Lexgo
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
Settify
100%
Compliance Rate
0/4 Standards Verified
Lexgo
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Legal Services Industry Average (This Year)

No incidents recorded for Settify in 2025.

Incidents vs Legal Services Industry Average (This Year)

No incidents recorded for Lexgo in 2025.

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

Settify cyber incidents detection timeline including parent company and subsidiaries

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

Lexgo cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/settify.jpeg
Settify
Incidents

No Incident

https://images.rankiteo.com/companyimages/lexgohq.jpeg
Lexgo
Incidents

No Incident

FAQ

Both Settify company and Lexgo company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, Lexgo company has disclosed a higher number of cyber incidents compared to Settify company.

In the current year, Lexgo company and Settify company have not reported any cyber incidents.

Neither Lexgo company nor Settify company has reported experiencing a ransomware attack publicly.

Neither Lexgo company nor Settify company has reported experiencing a data breach publicly.

Neither Lexgo company nor Settify company has reported experiencing targeted cyberattacks publicly.

Neither Settify company nor Lexgo company has reported experiencing or disclosing vulnerabilities publicly.

Neither Settify nor Lexgo holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Settify company nor Lexgo company has publicly disclosed detailed information about the number of their subsidiaries.

Lexgo company employs more people globally than Settify company, reflecting its scale as a Legal Services.

Neither Settify nor Lexgo holds SOC 2 Type 1 certification.

Neither Settify nor Lexgo holds SOC 2 Type 2 certification.

Neither Settify nor Lexgo holds ISO 27001 certification.

Neither Settify nor Lexgo holds PCI DSS certification.

Neither Settify nor Lexgo holds HIPAA certification.

Neither Settify nor Lexgo holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

A vulnerability was determined in motogadget mo.lock Ignition Lock up to 20251125. Affected by this vulnerability is an unknown functionality of the component NFC Handler. Executing manipulation can lead to use of hard-coded cryptographic key . The physical device can be targeted for the attack. A high complexity level is associated with this attack. The exploitation appears to be difficult. The vendor was contacted early about this disclosure but did not respond in any way.

Risk Information
cvss2
Base: 1.2
Severity: HIGH
AV:L/AC:H/Au:N/C:P/I:N/A:N
cvss3
Base: 2.0
Severity: HIGH
CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
cvss4
Base: 1.0
Severity: HIGH
CVSS:4.0/AV:P/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P/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

OrangeHRM is a comprehensive human resource management (HRM) system. From version 5.0 to 5.7, the interview attachment retrieval endpoint in the Recruitment module serves files based solely on an authenticated session and user-supplied identifiers, without verifying whether the requester has permission to access the associated interview record. Because the server does not perform any recruitment-level authorization checks, an ESS-level user with no access to recruitment workflows can directly request interview attachment URLs and receive the corresponding files. This exposes confidential interview documents—including candidate CVs, evaluations, and supporting files—to unauthorized users. The issue arises from relying on predictable object identifiers and session presence rather than validating the user’s association with the relevant recruitment process. This issue has been patched in version 5.8.

Risk Information
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/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

OrangeHRM is a comprehensive human resource management (HRM) system. From version 5.0 to 5.7, the application’s recruitment attachment retrieval endpoint does not enforce the required authorization checks before serving candidate files. Even users restricted to ESS-level access, who have no permission to view the Recruitment module, can directly access candidate attachment URLs. When an authenticated request is made to the attachment endpoint, the system validates the session but does not confirm that the requesting user has the necessary recruitment permissions. As a result, any authenticated user can download CVs and other uploaded documents for arbitrary candidates by issuing direct requests to the attachment endpoint, leading to unauthorized exposure of sensitive applicant data. This issue has been patched in version 5.8.

Risk Information
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/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

OrangeHRM is a comprehensive human resource management (HRM) system. From version 5.0 to 5.7, the application does not invalidate existing sessions when a user is disabled or when a password change occurs, allowing active session cookies to remain valid indefinitely. As a result, a disabled user, or an attacker using a compromised account, can continue to access protected pages and perform operations as long as a prior session remains active. Because the server performs no session revocation or session-store cleanup during these critical state changes, disabling an account or updating credentials has no effect on already-established sessions. This makes administrative disable actions ineffective and allows unauthorized users to retain full access even after an account is closed or a password is reset, exposing the system to prolonged unauthorized use and significantly increasing the impact of account takeover scenarios. This issue has been patched in version 5.8.

Risk Information
cvss4
Base: 8.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/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

OrangeHRM is a comprehensive human resource management (HRM) system. From version 5.0 to 5.7, the password reset workflow does not enforce that the username submitted in the final reset request matches the account for which the reset process was originally initiated. After obtaining a valid reset link for any account they can receive email for, an attacker can alter the username parameter in the final reset request to target a different user. Because the system accepts the supplied username without verification, the attacker can set a new password for any chosen account, including privileged accounts, resulting in full account takeover. This issue has been patched in version 5.8.

Risk Information
cvss4
Base: 8.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/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