Comparison Overview

killanoodle

VS

Priest + Grace

killanoodle

undefined, Sydney, undefined, undefined, au
Last Update: 2025-12-01
Between 750 and 799

Killanoodle is a Sydney-based design agency specialising in art direction, brand identity and graphic design. Our design process encompasses both extensive research and intuition. We work closely with our clients to discover ideas and outcomes that are distinctive and successful. Through craft, experimentation and passion we develop beautiful campaigns, striking graphics, and memorable images.

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

Priest + Grace

45 MAIN ST, BROOKLYN, NY, 11201, US
Last Update: 2025-12-01

We are an award-winning design company. We create memorable solutions that increase revenue and brand awareness for our clients. Our experience on a vast array of projects gives us the flexibility to solve any design challenge. Basically, our design works. We’re not going to talk you to death. We listen, understand what you want to achieve, and get you there. We invent dynamic magazines that are helping to re-energize print, and lately, we’ve been devoting a good part of our time to creating mobile apps. We’ve partnered with Adobe, using their Digital Publishing Suite to program our apps. They’re an important part of your future and so are we.

NAICS: 54143
NAICS Definition: Graphic Design Services
Employees: 9
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/killanoodle.jpeg
killanoodle
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/priest-grace.jpeg
Priest + Grace
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
killanoodle
100%
Compliance Rate
0/4 Standards Verified
Priest + Grace
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Graphic Design Industry Average (This Year)

No incidents recorded for killanoodle in 2025.

Incidents vs Graphic Design Industry Average (This Year)

No incidents recorded for Priest + Grace in 2025.

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

killanoodle cyber incidents detection timeline including parent company and subsidiaries

Incident History — Priest + Grace (X = Date, Y = Severity)

Priest + Grace cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/killanoodle.jpeg
killanoodle
Incidents

No Incident

https://images.rankiteo.com/companyimages/priest-grace.jpeg
Priest + Grace
Incidents

No Incident

FAQ

Priest + Grace company demonstrates a stronger AI Cybersecurity Score compared to killanoodle company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Priest + Grace company has disclosed a higher number of cyber incidents compared to killanoodle company.

In the current year, Priest + Grace company and killanoodle company have not reported any cyber incidents.

Neither Priest + Grace company nor killanoodle company has reported experiencing a ransomware attack publicly.

Neither Priest + Grace company nor killanoodle company has reported experiencing a data breach publicly.

Neither Priest + Grace company nor killanoodle company has reported experiencing targeted cyberattacks publicly.

Neither killanoodle company nor Priest + Grace company has reported experiencing or disclosing vulnerabilities publicly.

Neither killanoodle nor Priest + Grace holds any compliance certifications.

Neither company holds any compliance certifications.

Neither killanoodle company nor Priest + Grace company has publicly disclosed detailed information about the number of their subsidiaries.

Priest + Grace company employs more people globally than killanoodle company, reflecting its scale as a Graphic Design.

Neither killanoodle nor Priest + Grace holds SOC 2 Type 1 certification.

Neither killanoodle nor Priest + Grace holds SOC 2 Type 2 certification.

Neither killanoodle nor Priest + Grace holds ISO 27001 certification.

Neither killanoodle nor Priest + Grace holds PCI DSS certification.

Neither killanoodle nor Priest + Grace holds HIPAA certification.

Neither killanoodle nor Priest + Grace holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

vLLM is an inference and serving engine for large language models (LLMs). Prior to 0.11.1, vllm has a critical remote code execution vector in a config class named Nemotron_Nano_VL_Config. When vllm loads a model config that contains an auto_map entry, the config class resolves that mapping with get_class_from_dynamic_module(...) and immediately instantiates the returned class. This fetches and executes Python from the remote repository referenced in the auto_map string. Crucially, this happens even when the caller explicitly sets trust_remote_code=False in vllm.transformers_utils.config.get_config. In practice, an attacker can publish a benign-looking frontend repo whose config.json points via auto_map to a separate malicious backend repo; loading the frontend will silently run the backend’s code on the victim host. This vulnerability is fixed in 0.11.1.

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

fastify-reply-from is a Fastify plugin to forward the current HTTP request to another server. Prior to 12.5.0, by crafting a malicious URL, an attacker could access routes that are not allowed, even though the reply.from is defined for specific routes in @fastify/reply-from. This vulnerability is fixed in 12.5.0.

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

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 21.0.2, 20.3.15, and 19.2.17, A Stored Cross-Site Scripting (XSS) vulnerability has been identified in the Angular Template Compiler. It occurs because the compiler's internal security schema is incomplete, allowing attackers to bypass Angular's built-in security sanitization. Specifically, the schema fails to classify certain URL-holding attributes (e.g., those that could contain javascript: URLs) as requiring strict URL security, enabling the injection of malicious scripts. This vulnerability is fixed in 21.0.2, 20.3.15, and 19.2.17.

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

Gin-vue-admin is a backstage management system based on vue and gin. In 2.8.6 and earlier, attackers can delete any file on the server at will, causing damage or unavailability of server resources. Attackers can control the 'FileMd5' parameter to delete any file and folder.

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

Portkey.ai Gateway is a blazing fast AI Gateway with integrated guardrails. Prior to 1.14.0, the gateway determined the destination baseURL by prioritizing the value in the x-portkey-custom-host request header. The proxy route then appends the client-specified path to perform an external fetch. This can be maliciously used by users for SSRF attacks. This vulnerability is fixed in 1.14.0.

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