Comparison Overview

Paracosm

VS

UKG

Paracosm

12 S Main Street Gainesville, Florida 32601, US
Last Update: 2025-05-06 (UTC)
Between 800 and 900

Strong

Paracosm develops mobile reality capture, progress monitoring, and visualization solutions to help construction teams build better, faster.

NAICS: 5112
NAICS Definition: Software Publishers
Employees: 11-50
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

UKG

None
Last Update: 2025-07-26 (UTC)

Strong

Between 800 and 900

At UKG, our purpose is people. As strong believers in the power of culture and belonging as the secret to success, we champion great workplaces and build lifelong partnerships with our customers to show whatโ€™s possible when businesses invest in their people. One of the worldโ€™s leading HCM cloud companies today, UKG and our Life-work Technology approach to HR, pay, time, and culture solutions for all people helps 80,000 organizations around the globe and across every industry anticipate and adapt to their employeesโ€™ needs beyond just work. To learn more, visit ukg.com. UKG Social Media Guidelines available at https://www.ukg.com/ukg-social-media-guidelines.

NAICS: 5112
NAICS Definition: Software Publishers
Employees: 15,440
Subsidiaries: 0
12-month incidents
0
Known data breaches
1
Attack type number
2

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/paracosm.jpeg
Paracosm
โ€”
ISO 27001
Not verified
โ€”
SOC 2
Not verified
โ€”
GDPR
No public badge
โ€”
PCI DSS
No public badge
https://images.rankiteo.com/companyimages/ukg.jpeg
UKG
โ€”
ISO 27001
Not verified
โ€”
SOC 2
Not verified
โ€”
GDPR
No public badge
โ€”
PCI DSS
No public badge
Compliance Summary
Paracosm
100%
Compliance Rate
0/4 Standards Verified
UKG
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Software Development Industry Average (This Year)

No incidents recorded for Paracosm in 2025.

Incidents vs Software Development Industry Average (This Year)

No incidents recorded for UKG in 2025.

Incident History โ€” Paracosm (X = Date, Y = Severity)

Paracosm cyber incidents detection timeline including parent company and subsidiaries

Incident History โ€” UKG (X = Date, Y = Severity)

UKG cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/paracosm.jpeg
Paracosm
Incidents

No Incident

https://images.rankiteo.com/companyimages/ukg.jpeg
UKG
Incidents

Date Detected: 6/2023
Type:Breach
Blog: Blog

Date Detected: 12/2021
Type:Ransomware
Blog: Blog

FAQ

Both Paracosm company and UKG company demonstrate a comparable AI risk posture, with strong governance and monitoring frameworks in place.

UKG company has historically faced a number of disclosed cyber incidents, whereas Paracosm company has not reported any.

In the current year, UKG company and Paracosm company have not reported any cyber incidents.

UKG company has confirmed experiencing a ransomware attack, while Paracosm company has not reported such incidents publicly.

UKG company has disclosed at least one data breach, while Paracosm company has not reported such incidents publicly.

Neither UKG company nor Paracosm company has reported experiencing targeted cyberattacks publicly.

Neither Paracosm company nor UKG company has reported experiencing or disclosing vulnerabilities publicly.

Neither Paracosm company nor UKG company has publicly disclosed detailed information about the number of their subsidiaries.

UKG company employs more people globally than Paracosm company, reflecting its scale as a Software Development.

Latest Global CVEs (Not Company-Specific)

Description

Quadient DS-700 iQ devices through 2025-09-30 might have a race condition during the quick clicking of (in order) the Question Mark button, the Help Button, the About button, and the Help Button, leading to a transition out of kiosk mode into local administrative access. NOTE: the reporter indicates that the "behavior was observed sporadically" during "limited time on the client site," making it not "possible to gain more information about the specific kiosk mode crashing issue," and the only conclusion was "there appears to be some form of race condition." Accordingly, there can be doubt that a reproducible cybersecurity vulnerability was identified; sporadic software crashes can also be caused by a hardware fault on a single device (for example, transient RAM errors). The reporter also describes a variety of other issues, including initial access via USB because of the absence of a "lock-pick resistant locking solution for the External Controller PC cabinet," which is not a cybersecurity vulnerability (section 4.1.5 of the CNA Operational Rules). Finally, it is unclear whether the device or OS configuration was inappropriate, given that the risks are typically limited to insider threats within the mail operations room of a large company.

Risk Information
cvss3
Base: 6.4
Severity: HIGH
CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Description

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. Versions between 2.1.0 and 2.14.19, 3.2.0-rc1, 3.1.0-rc1 through 3.1.7, and 3.0.0-rc1 through 3.0.18 contain a race condition in the repository credentials handler that can cause the Argo CD server to panic and crash when concurrent operations are performed on the same repository URL. The vulnerability is located in numerous repository related handlers in the util/db/repository_secrets.go file. A valid API token with repositories resource permissions (create, update, or delete actions) is required to trigger the race condition. This vulnerability causes the entire Argo CD server to crash and become unavailable. Attackers can repeatedly and continuously trigger the race condition to maintain a denial-of-service state, disrupting all GitOps operations. This issue is fixed in versions 2.14.20, 3.2.0-rc2, 3.1.8 and 3.0.19.

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

Stored cross-site scripting (XSS) vulnerabilities in Web Content translation in Liferay Portal 7.4.0 through 7.4.3.112, and older unsupported versions, and Liferay DXP 2023.Q4.0 through 2023.Q4.8, 2023.Q3.1 through 2023.Q3.10, 7.4 GA through update 92, and older unsupported versions allow remote attackers to inject arbitrary web script or HTML via any rich text field in a web content article.

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

Keysight Ixia Vision has an issue with hardcoded cryptographic material which may allow an attacker to intercept or decrypt payloads sent to the device via API calls or user authentication if the end user does not replace the TLS certificate that shipped with the device. Remediation is available in Version 6.9.1, released on September 23, 2025.

Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
cvss4
Base: 8.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/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

An Insecure Direct Object Reference (IDOR) in the /dashboard/notes endpoint of Syaqui Collegetivity v1.0.0 allows attackers to impersonate other users and perform arbitrary operations via a crafted POST request.