Comparison Overview

Ishii Design

VS

Semius

Ishii Design

721 North 1890 West, #37b, Provo, Utah 84601, US
Last Update: 2025-12-02
Between 750 and 799

Ishii Design is a graphic design company that was founded by Daniel Ishii in 1979 during an era of pasteup, mechanical pens, t-squares and triangles. The focus of the company has remained the same during it's lifetime -- "Build relationships with those passionate about building their business and help them succeed." We find that business owners and sales professionals are the most passionate employees of their respective businesses and thus the most inspiring. Each designer at Ishii Design has at least 20 years of design experience. Over the years, we have been give the opportunity to work with hundreds of professionals and have learned a great deal in the process. We implement everything we know into each and every project.

NAICS: 54143
NAICS Definition: Graphic Design Services
Employees: 4
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Semius

None
Last Update: 2025-12-03
Between 750 and 799

Somos un Estudio de Diseño Web y Gráfico. Nos dedicamos a crear valor para las empresas que quieran entrar en el mercado digital. Especializados en Diseño Web, Identidad y Marketing Digital. Semius está conformado por un grupo de jóvenes profesionales apasionados por su trabajo. Trabajamos día a día para diseñar planes estratégicos de comunicación pensados para cada uno de nuestros clientes. Amamos lo que hacemos.

NAICS: 541
NAICS Definition:
Employees: 1
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/ishii-design.jpeg
Ishii Design
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/semius.jpeg
Semius
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
Ishii Design
100%
Compliance Rate
0/4 Standards Verified
Semius
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Graphic Design Industry Average (This Year)

No incidents recorded for Ishii Design in 2025.

Incidents vs Graphic Design Industry Average (This Year)

No incidents recorded for Semius in 2025.

Incident History — Ishii Design (X = Date, Y = Severity)

Ishii Design cyber incidents detection timeline including parent company and subsidiaries

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

Semius cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/ishii-design.jpeg
Ishii Design
Incidents

No Incident

https://images.rankiteo.com/companyimages/semius.jpeg
Semius
Incidents

No Incident

FAQ

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

Historically, Semius company has disclosed a higher number of cyber incidents compared to Ishii Design company.

In the current year, Semius company and Ishii Design company have not reported any cyber incidents.

Neither Semius company nor Ishii Design company has reported experiencing a ransomware attack publicly.

Neither Semius company nor Ishii Design company has reported experiencing a data breach publicly.

Neither Semius company nor Ishii Design company has reported experiencing targeted cyberattacks publicly.

Neither Ishii Design company nor Semius company has reported experiencing or disclosing vulnerabilities publicly.

Neither Ishii Design nor Semius holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Ishii Design company nor Semius company has publicly disclosed detailed information about the number of their subsidiaries.

Ishii Design company employs more people globally than Semius company, reflecting its scale as a Graphic Design.

Neither Ishii Design nor Semius holds SOC 2 Type 1 certification.

Neither Ishii Design nor Semius holds SOC 2 Type 2 certification.

Neither Ishii Design nor Semius holds ISO 27001 certification.

Neither Ishii Design nor Semius holds PCI DSS certification.

Neither Ishii Design nor Semius holds HIPAA certification.

Neither Ishii Design nor Semius 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