Comparison Overview

Twin Cities Gay Men's Chorus

VS

Minnesota Boychoir

Twin Cities Gay Men's Chorus

528 Hennepin Avenue, Minneapolis, Minnesota, 55403, US
Last Update: 2025-12-17
Between 750 and 799

Now celebrating its 38th year, Twin Cities Gay Men’s Chorus (TCGMC) is a non-profit 501(c)(3) volunteer community chorus whose mission is Gay Men Building Community Through Music. Twin Cities Gay Men’s Chorus seeks to provide its members with rewarding musical experiences and to promote social exchange. As an organization that celebrates diversity and uses music as a way to transform, educate and heal, the Chorus works towards the elimination of homophobia and intolerance through community outreach. With over 170 singing members, TCGMC and its two small ensembles, the Chamber Singers and OutLoud!, produce and present a full concert season every year. The Chorus performs its concert series at Ted Mann Concert Hall in Minneapolis and is also featured at a number of other special appearances and outreach programs (schools, churches, universities, festivals) locally, throughout the Midwest and the nation. TCGMC provides its members with rewarding musical performance experiences that celebrate diversity and use music as a way to transform, educate and heal. The Chorus promotes social justice and the elimination of homophobia and intolerance through our regular season of performances and community outreach performances across Minnesota and the Upper Midwest. Our strategic vision is to be a dynamic choral leader, changing lives through the performance of significant music.

NAICS: 7111
NAICS Definition: Performing Arts Companies
Employees: 9
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Minnesota Boychoir

75 West 5th Street, Suite 411, Saint Paul, Minnesota, 55102-1414, US
Last Update: 2025-12-17
Between 750 and 799

Mission Statement: The Minnesota Boychoir challenges boys and young men from many backgrounds to the highest standards of choral music, nurtures the development of exceptional character, and inspires and benefits the community. Founded in 1962, the Minnesota Boychoir is the oldest boy choir in the Minneapolis/Saint Paul metropolitan area. The Boychoir’s reputation for excellence has brought invitations from local and national music conventions, as well as sporting events and touring Broadway companies. The choir’s schedule includes national and international tours, thrilling audiences in over a dozen states and on five continents. In 2007 to celebrate the Boychoir's 45th Anniversary, the boys headlined the World Voices Australia International Choral Festival at Sydney’s famed Opera House. Our 50th Anniversary Season began by touring to Milan, Venice, Florence and Rome, Italy in June 2011, featuring a performance for Mass in Saint Peter’s Basilica at the Vatican and culminated with solo performances at Orchestra Hall in Minneapolis and the State Capitol. The Minnesota Boychoir trains young men to be outstanding musicians and strives to help them develop a sense of poise and self-confidence through education and performance. A choirboy is challenged to sing well, stand tall, stay on schedule, take pride in his appearance, respect those in charge and tap into the best part of whom he is and what he can accomplish. The Minnesota Boychoir challenges boys and young men from many backgrounds to the highest standards of choral music, nurtures the development of exceptional character, and inspires and benefits the community.

NAICS: 7111
NAICS Definition: Performing Arts Companies
Employees: 7
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/twin-cities-gay-men's-chorus.jpeg
Twin Cities Gay Men's Chorus
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/minnesota-boychoir.jpeg
Minnesota Boychoir
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
Twin Cities Gay Men's Chorus
100%
Compliance Rate
0/4 Standards Verified
Minnesota Boychoir
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Performing Arts Industry Average (This Year)

No incidents recorded for Twin Cities Gay Men's Chorus in 2025.

Incidents vs Performing Arts Industry Average (This Year)

No incidents recorded for Minnesota Boychoir in 2025.

Incident History — Twin Cities Gay Men's Chorus (X = Date, Y = Severity)

Twin Cities Gay Men's Chorus cyber incidents detection timeline including parent company and subsidiaries

Incident History — Minnesota Boychoir (X = Date, Y = Severity)

Minnesota Boychoir cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/twin-cities-gay-men's-chorus.jpeg
Twin Cities Gay Men's Chorus
Incidents

No Incident

https://images.rankiteo.com/companyimages/minnesota-boychoir.jpeg
Minnesota Boychoir
Incidents

No Incident

FAQ

Minnesota Boychoir company demonstrates a stronger AI Cybersecurity Score compared to Twin Cities Gay Men's Chorus company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Minnesota Boychoir company has disclosed a higher number of cyber incidents compared to Twin Cities Gay Men's Chorus company.

In the current year, Minnesota Boychoir company and Twin Cities Gay Men's Chorus company have not reported any cyber incidents.

Neither Minnesota Boychoir company nor Twin Cities Gay Men's Chorus company has reported experiencing a ransomware attack publicly.

Neither Minnesota Boychoir company nor Twin Cities Gay Men's Chorus company has reported experiencing a data breach publicly.

Neither Minnesota Boychoir company nor Twin Cities Gay Men's Chorus company has reported experiencing targeted cyberattacks publicly.

Neither Twin Cities Gay Men's Chorus company nor Minnesota Boychoir company has reported experiencing or disclosing vulnerabilities publicly.

Neither Twin Cities Gay Men's Chorus nor Minnesota Boychoir holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Twin Cities Gay Men's Chorus company nor Minnesota Boychoir company has publicly disclosed detailed information about the number of their subsidiaries.

Twin Cities Gay Men's Chorus company employs more people globally than Minnesota Boychoir company, reflecting its scale as a Performing Arts.

Neither Twin Cities Gay Men's Chorus nor Minnesota Boychoir holds SOC 2 Type 1 certification.

Neither Twin Cities Gay Men's Chorus nor Minnesota Boychoir holds SOC 2 Type 2 certification.

Neither Twin Cities Gay Men's Chorus nor Minnesota Boychoir holds ISO 27001 certification.

Neither Twin Cities Gay Men's Chorus nor Minnesota Boychoir holds PCI DSS certification.

Neither Twin Cities Gay Men's Chorus nor Minnesota Boychoir holds HIPAA certification.

Neither Twin Cities Gay Men's Chorus nor Minnesota Boychoir 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