Comparison Overview

Another Axiom

VS

Keywords Studios

Another Axiom

None
Last Update: 2025-12-11
Between 700 and 749

Another Axiom is the development team for Gorilla Tag - With over 10 million downloads on the Meta Quest and PC VR platforms. Our passion is building Diegetic Virtual Realities. Instead of treating our world like a video game, we are building Gorilla Tag to make it feel like it’s a plausible, alternate space that could exist if the rules of reality were just a little bit different. People come away from our world with real dreams and memories of having been there with their friends. We are a flat organization that believes that everyone contributes to our products in their own way - That everyone should be encouraged to explore and participate in all aspects of game development with their own unique point-of-view to help us build a diverse product.

NAICS: 51126
NAICS Definition: Software Publishers
Employees: 74
Subsidiaries: 0
12-month incidents
0
Known data breaches
1
Attack type number
1

Keywords Studios

Whelan House, South County Business Park, Leopardstown, Dublin, Ireland, IE, 18
Last Update: 2025-12-15

🎮🎬 We help make video games, films, and fan favourites you’ve probably played, watched, or heard. We work behind the scenes with game developers, publishers, and entertainment companies to bring their ideas to life and keep them running smoothly. From game development and art production to audio services, localization, game testing, community support, and marketing, we’re the partner you call when you need extra hands (or brains). We are 13,000 people worldwide. Tech-savvy, AI-aware, and deeply invested in R&D. We’re adaptable, collaborative, and used to plugging into diverse teams and pipelines. Many of us grew up with games, animation, and film. We’re fans first, and that shows in how we work: with care, respect, accessibility, and safety in mind. Whether it’s building innovative experiences, meeting tight deadlines, or preserving creative vision across every language and culture, our services and proprietary tools integrate seamlessly with your team at any stage of the product life cycle. We don’t always make the headlines, but we help others get there. Among our clients: Tencent Games, Microsoft, Ubisoft, Supercell, Bandai Namco, Netflix, Amazon... #ImagineMore

NAICS: 51126
NAICS Definition: Software Publishers
Employees: 11,763
Subsidiaries: 33
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/another-axiom.jpeg
Another Axiom
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/keywordsstudios.jpeg
Keywords Studios
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
Another Axiom
100%
Compliance Rate
0/4 Standards Verified
Keywords Studios
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Computer Games Industry Average (This Year)

No incidents recorded for Another Axiom in 2025.

Incidents vs Computer Games Industry Average (This Year)

No incidents recorded for Keywords Studios in 2025.

Incident History — Another Axiom (X = Date, Y = Severity)

Another Axiom cyber incidents detection timeline including parent company and subsidiaries

Incident History — Keywords Studios (X = Date, Y = Severity)

Keywords Studios cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/another-axiom.jpeg
Another Axiom
Incidents

Date Detected: 12/2024
Type:Breach
Attack Vector: VPN usage
Motivation: Gain unfair advantage in the game
Blog: Blog
https://images.rankiteo.com/companyimages/keywordsstudios.jpeg
Keywords Studios
Incidents

No Incident

FAQ

Keywords Studios company demonstrates a stronger AI Cybersecurity Score compared to Another Axiom company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Another Axiom company has historically faced a number of disclosed cyber incidents, whereas Keywords Studios company has not reported any.

In the current year, Keywords Studios company and Another Axiom company have not reported any cyber incidents.

Neither Keywords Studios company nor Another Axiom company has reported experiencing a ransomware attack publicly.

Another Axiom company has disclosed at least one data breach, while the other Keywords Studios company has not reported such incidents publicly.

Neither Keywords Studios company nor Another Axiom company has reported experiencing targeted cyberattacks publicly.

Neither Another Axiom company nor Keywords Studios company has reported experiencing or disclosing vulnerabilities publicly.

Neither Another Axiom nor Keywords Studios holds any compliance certifications.

Neither company holds any compliance certifications.

Keywords Studios company has more subsidiaries worldwide compared to Another Axiom company.

Keywords Studios company employs more people globally than Another Axiom company, reflecting its scale as a Computer Games.

Neither Another Axiom nor Keywords Studios holds SOC 2 Type 1 certification.

Neither Another Axiom nor Keywords Studios holds SOC 2 Type 2 certification.

Neither Another Axiom nor Keywords Studios holds ISO 27001 certification.

Neither Another Axiom nor Keywords Studios holds PCI DSS certification.

Neither Another Axiom nor Keywords Studios holds HIPAA certification.

Neither Another Axiom nor Keywords Studios holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Zerobyte is a backup automation tool Zerobyte versions prior to 0.18.5 and 0.19.0 contain an authentication bypass vulnerability where authentication middleware is not properly applied to API endpoints. This results in certain API endpoints being accessible without valid session credentials. This is dangerous for those who have exposed Zerobyte to be used outside of their internal network. A fix has been applied in both version 0.19.0 and 0.18.5. If immediate upgrade is not possible, restrict network access to the Zerobyte instance to trusted networks only using firewall rules or network segmentation. This is only a temporary mitigation; upgrading is strongly recommended.

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

Open Source Point of Sale (opensourcepos) is a web based point of sale application written in PHP using CodeIgniter framework. Starting in version 3.4.0 and prior to version 3.4.2, a Cross-Site Request Forgery (CSRF) vulnerability exists in the application's filter configuration. The CSRF protection mechanism was **explicitly disabled**, allowing the application to process state-changing requests (POST) without verifying a valid CSRF token. An unauthenticated remote attacker can exploit this by hosting a malicious web page. If a logged-in administrator visits this page, their browser is forced to send unauthorized requests to the application. A successful exploit allows the attacker to silently create a new Administrator account with full privileges, leading to a complete takeover of the system and loss of confidentiality, integrity, and availability. The vulnerability has been patched in version 3.4.2. The fix re-enables the CSRF filter in `app/Config/Filters.php` and resolves associated AJAX race conditions by adjusting token regeneration settings. As a workaround, administrators can manually re-enable the CSRF filter in `app/Config/Filters.php` by uncommenting the protection line. However, this is not recommended without applying the full patch, as it may cause functionality breakage in the Sales module due to token synchronization issues.

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

Zed, a code editor, has an aribtrary code execution vulnerability in versions prior to 0.218.2-pre. The Zed IDE loads Model Context Protocol (MCP) configurations from the `settings.json` file located within a project’s `.zed` subdirectory. A malicious MCP configuration can contain arbitrary shell commands that run on the host system with the privileges of the user running the IDE. This can be triggered automatically without any user interaction besides opening the project in the IDE. Version 0.218.2-pre fixes the issue by implementing worktree trust mechanism. As a workaround, users should carefully review the contents of project settings files (`./zed/settings.json`) before opening new projects in Zed.

Risk Information
cvss3
Base: 7.7
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Description

Zed, a code editor, has an aribtrary code execution vulnerability in versions prior to 0.218.2-pre. The Zed IDE loads Language Server Protocol (LSP) configurations from the `settings.json` file located within a project’s `.zed` subdirectory. A malicious LSP configuration can contain arbitrary shell commands that run on the host system with the privileges of the user running the IDE. This can be triggered when a user opens project file for which there is an LSP entry. A concerted effort by an attacker to seed a project settings file (`./zed/settings.json`) with malicious language server configurations could result in arbitrary code execution with the user's privileges if the user opens the project in Zed without reviewing the contents. Version 0.218.2-pre fixes the issue by implementing worktree trust mechanism. As a workaround, users should carefully review the contents of project settings files (`./zed/settings.json`) before opening new projects in Zed.

Risk Information
cvss3
Base: 7.7
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Description

Storybook is a frontend workshop for building user interface components and pages in isolation. A vulnerability present starting in versions 7.0.0 and prior to versions 7.6.21, 8.6.15, 9.1.17, and 10.1.10 relates to Storybook’s handling of environment variables defined in a `.env` file, which could, in specific circumstances, lead to those variables being unexpectedly bundled into the artifacts created by the `storybook build` command. When a built Storybook is published to the web, the bundle’s source is viewable, thus potentially exposing those variables to anyone with access. For a project to potentially be vulnerable to this issue, it must build the Storybook (i.e. run `storybook build` directly or indirectly) in a directory that contains a `.env` file (including variants like `.env.local`) and publish the built Storybook to the web. Storybooks built without a `.env` file at build time are not affected, including common CI-based builds where secrets are provided via platform environment variables rather than `.env` files. Storybook runtime environments (i.e. `storybook dev`) are not affected. Deployed applications that share a repo with your Storybook are not affected. Users should upgrade their Storybook—on both their local machines and CI environment—to version .6.21, 8.6.15, 9.1.17, or 10.1.10 as soon as possible. Maintainers additionally recommend that users audit for any sensitive secrets provided via `.env` files and rotate those keys. Some projects may have been relying on the undocumented behavior at the heart of this issue and will need to change how they reference environment variables after this update. If a project can no longer read necessary environmental variable values, either prefix the variables with `STORYBOOK_` or use the `env` property in Storybook’s configuration to manually specify values. In either case, do not include sensitive secrets as they will be included in the built bundle.

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