Comparison Overview

St Martin-in-the-Fields, London

VS

Bayside Historical Society

St Martin-in-the-Fields, London

5 St Martin's Place, London, England, WC2N 4JH, GB
Last Update: 2025-12-01

St Martin-in-the-Fields is an iconic church located in the heart of London on Trafalgar Square. Every year we welcome over 1 million people to worship, reflect, relax, meet, eat and drink, enjoy music and the arts and the rich cultural offer of our organisation. We are place for everyone, everywhere, every day. St Martin’s is a unique institution in which faith, cultural, charitable and commercial initiatives combine to serve our community. St Martin-in-the-Fields Ltd is our social enterprise responsible for running our unique Crypt Cafe, Gallery, Courtyard Kiosk, Shop, Corporate Events, Private Dining, Retail Spaces and for programming over 300 concerts, exhibitions and pop-up activities each year! Do visit our website for information on what’s on and how you can hire our unique spaces. The profits from the social enterprise are fed back into the church in support of its operation, its work with local community and in supporting those experiencing homelessness. St Martin’s is an incredible place to work. Here we live our values, our employees are free to be themselves, to arrive for work every day safe in the knowledge that their individuality and uniqueness is part of what makes this a great place to work. If you are interested in knowing more, why not come and visit us for a bite to eat, to see a show or take some quiet reflection in one of our public spaces. If you are a values driven, passionate person, looking to make a difference to our local community and have a global impact on issues such as social change, homelessness and refugee support, why not check out our vacancies page, there may just your next dream job waiting for you here!

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

Bayside Historical Society

208 Totten Avenue, Bayside, NY, 11359, US
Last Update: 2025-12-01

Bayside Historical Society was founded in 1964 to collect, preserve, and disseminate information concerning the history of Bayside and its adjacent communities; advocate for the preservation and protection of its most historic structures and distinctive neighborhoods through the landmarking process; and strive to develop a broad constituency of like-minded preservation and educational organizations to protect the historic integrity of our communities and collections.

NAICS: 712
NAICS Definition:
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/st-martin-in-the-fields-london.jpeg
St Martin-in-the-Fields, London
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/bayside-historical-society.jpeg
Bayside Historical Society
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
St Martin-in-the-Fields, London
100%
Compliance Rate
0/4 Standards Verified
Bayside Historical Society
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Museums, Historical Sites, and Zoos Industry Average (This Year)

No incidents recorded for St Martin-in-the-Fields, London in 2025.

Incidents vs Museums, Historical Sites, and Zoos Industry Average (This Year)

No incidents recorded for Bayside Historical Society in 2025.

Incident History — St Martin-in-the-Fields, London (X = Date, Y = Severity)

St Martin-in-the-Fields, London cyber incidents detection timeline including parent company and subsidiaries

Incident History — Bayside Historical Society (X = Date, Y = Severity)

Bayside Historical Society cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/st-martin-in-the-fields-london.jpeg
St Martin-in-the-Fields, London
Incidents

No Incident

https://images.rankiteo.com/companyimages/bayside-historical-society.jpeg
Bayside Historical Society
Incidents

No Incident

FAQ

Bayside Historical Society company demonstrates a stronger AI Cybersecurity Score compared to St Martin-in-the-Fields, London company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Bayside Historical Society company has disclosed a higher number of cyber incidents compared to St Martin-in-the-Fields, London company.

In the current year, Bayside Historical Society company and St Martin-in-the-Fields, London company have not reported any cyber incidents.

Neither Bayside Historical Society company nor St Martin-in-the-Fields, London company has reported experiencing a ransomware attack publicly.

Neither Bayside Historical Society company nor St Martin-in-the-Fields, London company has reported experiencing a data breach publicly.

Neither Bayside Historical Society company nor St Martin-in-the-Fields, London company has reported experiencing targeted cyberattacks publicly.

Neither St Martin-in-the-Fields, London company nor Bayside Historical Society company has reported experiencing or disclosing vulnerabilities publicly.

Neither St Martin-in-the-Fields, London nor Bayside Historical Society holds any compliance certifications.

Neither company holds any compliance certifications.

Neither St Martin-in-the-Fields, London company nor Bayside Historical Society company has publicly disclosed detailed information about the number of their subsidiaries.

St Martin-in-the-Fields, London company employs more people globally than Bayside Historical Society company, reflecting its scale as a Museums, Historical Sites, and Zoos.

Neither St Martin-in-the-Fields, London nor Bayside Historical Society holds SOC 2 Type 1 certification.

Neither St Martin-in-the-Fields, London nor Bayside Historical Society holds SOC 2 Type 2 certification.

Neither St Martin-in-the-Fields, London nor Bayside Historical Society holds ISO 27001 certification.

Neither St Martin-in-the-Fields, London nor Bayside Historical Society holds PCI DSS certification.

Neither St Martin-in-the-Fields, London nor Bayside Historical Society holds HIPAA certification.

Neither St Martin-in-the-Fields, London nor Bayside Historical Society 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