What is the official website of Classical KUSC ?

The official website of Classical KUSC is http://www.kusc.org.

What is Classical KUSC's cybersecurity risk score?

Classical KUSC has an AI-generated cybersecurity risk score of 742 out of 1000, indicating a Moderate security posture according to Rankiteo's assessment.

How many security incidents has Classical KUSC experienced?

According to Rankiteo, Classical KUSC currently holds 0 security badges, indicating that no recognized compliance certifications are currently verified for the organization.

Has Classical KUSC been affected by any supply chain cyber incidents ?

According to Rankiteo, Classical KUSC has not been affected by any supply chain cyber incidents, and no incident IDs are currently listed for the organization.

Does Classical KUSC have SOC 2 Type 1 certification ?

According to Rankiteo, Classical KUSC is not certified under SOC 2 Type 1.

Does Classical KUSC have SOC 2 Type 2 certification ?

According to Rankiteo, Classical KUSC does not hold a SOC 2 Type 2 certification.

Does Classical KUSC comply with GDPR ?

According to Rankiteo, Classical KUSC is not listed as GDPR compliant.

Does Classical KUSC have PCI DSS certification ?

According to Rankiteo, Classical KUSC does not currently maintain PCI DSS compliance.

Does Classical KUSC comply with HIPAA ?

According to Rankiteo, Classical KUSC is not compliant with HIPAA regulations.

Does Classical KUSC have ISO 27001 certification ?

According to Rankiteo,Classical KUSC is not certified under ISO 27001, indicating the absence of a formally recognized information security management framework.

Which industry does Classical KUSC operate in ?

Classical KUSC operates primarily in the Musicians industry.

How many employees does Classical KUSC have ?

Classical KUSC employs approximately 23 people worldwide.

Does Classical KUSC own any subsidiaries ?

Classical KUSC presently has no subsidiaries across any sectors.

How many LinkedIn followers does Classical KUSC have ?

Classical KUSC's official LinkedIn profile has approximately 1,196 followers.

What is the NAICS classification code for Classical KUSC ?

Classical KUSC is classified under the NAICS code 71113, which corresponds to Musical Groups and Artists.

Does Classical KUSC have a Crunchbase profile ?

No, Classical KUSC does not have a profile on Crunchbase.

Does Classical KUSC have a LinkedIn profile ?

Yes, Classical KUSC maintains an official LinkedIn profile, which is actively utilized for branding and talent engagement, which can be accessed here: https://www.linkedin.com/company/kusc.

How many cybersecurity incidents has Classical KUSC experienced ?

As of September 17, 2026, Rankiteo reports that Classical KUSC has experienced 1 cybersecurity incidents.

How many peer or competitor companies does Classical KUSC have ?

Classical KUSC has an estimated 3,336 peer or competitor companies worldwide.

What types of cybersecurity incidents has Classical KUSC faced ?

Incident Types: The types of cybersecurity incidents that have occurred include Ransomware.

Badge your company to reduce your risk score and your cyber insurance costs!

Link verified badges to your company page to build trust with insurers and customers.

Apply now and get your badge!

Internal validation & live display

Insurers and partners see a safer profile

Faster underwriting decisions

Trusted by insurers. Chosen by leaders.

Proud contributor to the Society of Actuaries.

Classical KUSC

Boost Score +25 with badge (5 left)

742

/1000

Moderate

767

/1000

Fair

Classical KUSC Vendor Cyber Rating & Cyber Score

kusc.org

Add Your Compliance Badge

Classical KUSC is the largest and most listened to public radio and non-profit classical music station in the country. KUSC is dedicated to preserving classical music as a living art. Located in downtown Los Angeles, Classical KUSC uses digital transmission technology to broadcast commercial-free uninterrupted classical performances. The non-profit, listener-supported station has been broadcasting for over 60 years. The station is a broadcast service of the University of Southern California at 91.5(FM) in Los Angeles and Santa Clarita; 88.5 KPSC in Palm Springs; 91.1 KDSC in Thousand Oaks, 88.7 KQSC in Santa Barbara and 99.7 in Morro Bay/San Luis Obispo.

Classical KUSC

Classical KUSC CyberSecurity News & History

Past Incidents

Attack Types

Entity

Type

Severity

Impact

Seen

Blog Details

Supply Chain Source

Incident Details

View

Classical KUSC

Ransomware

100

4/2016

KUS549080425

Loading…

A.I.

Classical KUSC Company Scoring based on AI Models

Cyber Incidents Likelihood 3 - 6 - 9 months

Actual

Prediction

Incident Predictions locked

Access Monitoring Plan

A.I Risk Score Likelihood 3 - 6 - 9 months

Actual

Prediction A

Prediction B

Prediction C

Prediction D

A.I. Risk Score Predictions locked

Access Monitoring Plan

Loading…

Underwriter Stats for Classical KUSC

Incidents vs Musicians Industry Avg (This Year)

No incidents recorded for Classical KUSC in 2026.

Incidents vs All-Companies Average (This Year)

No incidents recorded for Classical KUSC in 2026.

Incident Types Classical KUSC vs Musicians Industry Avg (This Year)

No incidents recorded for Classical KUSC in 2026.

Incident History - Classical KUSC (X = Date, Y = Severity)

Loading…

SUBSIDIARY

Classical KUSC Subsidiaries

Parent Company

Classical KUSC

Musicians

Website: http://www.kusc.org

Company Size: 23

No subsidiary data available for this company.

Loading…

Classical KUSC Similar Companies

Yamaha Corporation

yamaha.com

Our history began in 1887 when Yamaha founder Torakusu Yamaha completed a repair job on a reed organ at a Japanese primary school. Perhaps no one thought at the time that this event would mark the beginning of 130-plus year history during which Yamaha would become a world-leading brand in musical instruments, other products, and services dear to the hearts of people everywhere. True to its slogan, “Sharing Passion & Performance,” the Yamaha Group helps enrich people’s lives day in and day out. Since our founding in 1887, we have offered the world a rich scope of products and services focused on sound and music. We want to create excitement and inspiration everywhere, joyfully highlighting music in life, education, and culture. We are deeply committed to creating customer value by offering products and services that draw on our reservoir of technology, know-how, and musical sensitivities. We have accumulated these values over our long history and are keen to address new challenges with a passion going beyond our customers’ expectations, always renewing our inspiration, and theirs. We are dedicated to engaging proactively with our customers to propose products and services that will stir their hearts over a lifetime. Looking ahead, we will be making every effort to ensure that we continue to be an “Indispensable, Brilliantly Individual Company,” always honouring long and close relationships with our customers.

Spotify

lifeatspotify.com

Our mission is to unlock the potential of human creativity—by giving a million creative artists the opportunity to live off their art and billions of fans the opportunity to enjoy and be inspired by it. Spotify transformed music listening forever when it launched in Sweden in 2008. Discover, manage and share over 70m tracks for free, or upgrade to Spotify Premium to access exclusive features including offline mode, improved sound quality, and an ad-free music listening experience. Today, Spotify is the most popular global audio streaming service with 365m users, including 165m subscribers across 178 markets. We are the largest driver of revenue to the music business today.

Loading…

NEWS

Classical KUSC CyberSecurity News

Latest updates, reports, and threat intel affecting the global network.

Loading…

CVE

Latest

Global CVEs (Not Company-Specific)

CVE-2026-65388

SUMMARY

A remote attacker who controls a container registry may be able to direct a client's token request to a host of the attacker's choice, and disclose the victim's registry credentials to that host. This vulnerability is addressed in containerization version 0.41.0.

Published

Date2026-09-16

Updated

Date2026-09-16

RISK INFORMATION (Score: )

Impact Score

Exploitability

REFERENCES

https://github.com/apple/containerization/security/advisories/GHSA-mx96-5vvg-x2mg

CVE-2026-61599

SUMMARY

djust provides Phoenix LiveView-style reactive server-side rendering for Django with Rust-powered performance. Prior to version 1.0.7, the djust live transport resolves the LiveView to mount from a client-supplied dotted path by calling `__import__(module_path, ...)`. The module is imported — running its top-level code (import side effects) — before the framework checks that the resolved object is a `LiveView` subclass and before any per-view authentication. The `LIVEVIEW_ALLOWED_MODULES` allowlist that should contain this is fail-open (`if allowed_modules:` — skipped when the setting is unset, the framework default) and uses loose `startswith` matching. An unauthenticated WebSocket client (the WS handshake does not require auth; per-view auth runs only after import + instantiate) can therefore send a `mount` / `live_redirect_mount` / `url_change` frame (or an SSE mount) with `view = "<any.importable.module>.AnyName"` and cause the server to import — and execute the top-level code of — any importable Python module by name. Version 1.0.7 fixes the issue with a fail-closed resolution gate (`djust._view_resolution.is_view_import_allowed`): a client view path resolves only if (a) its module is already loaded (`sys.modules` — so resolving runs no new code; URL-routed views loaded by URLconf at startup keep working with zero config) or (b) it matches `LIVEVIEW_ALLOWED_MODULES` on a module-segment boundary (explicit opt-in for lazily-imported views). The gate runs before `__import__` at all three sinks (+ defense-in-depth inside `_instantiate_view`). As a workaround, set `LIVEVIEW_ALLOWED_MODULES` to the narrow list of modules that contain your mountable LiveView classes. (Note: pre-patch the allowlist is `startswith`-matched and the import still precedes the subclass check, so this is mitigation, not a complete fix.)

Published

Date2026-09-16

Updated

Date2026-09-16

RISK INFORMATION (Score: )

cvss4

Base Score: 8.8

Complexity: LOW

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:L/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

Impact Score

Exploitability

REFERENCES

CVE-2026-61596

SUMMARY

djust provides Phoenix LiveView-style reactive server-side rendering for Django with Rust-powered performance. Prior to version 1.0.7, djust's per-object authorization (`get_object` + `has_object_permission`, ADR-017) was enforced on the WebSocket mount and event paths but not on three other render entry points: (a) the initial HTTP GET render, (b) SPA `url_change` navigation, and (c) `{% live_render %}` embedded child views. An authenticated user could therefore view (and on some paths act on) an object they are not authorized for by loading the page directly, navigating to it via SPA url-change, or composing it as an embedded child — a classic IDOR / broken object-level access control on object-scoped views. This is fixed in djust 1.0.7. All render entry points now route through a shared `enforce_object_permission` chokepoint: HTTP GET returns 403, `url_change` emits a `permission_denied` frame and skips the render, and `{% live_render %}` (eager + lazy) refuses the embed. Views without a custom `get_object` are unaffected (no-op). No reliable workaround short of upgrading. Do not expose object-scoped views through the HTTP-GET / url_change / live_render paths until patched.

Published

Date2026-09-16

Updated

Date2026-09-16

RISK INFORMATION (Score: 7.1)

cvss3

Base Score: 7.1

Complexity: LOW

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

Impact Score

4.2

Exploitability

2.8

REFERENCES

CVE-2026-61589

SUMMARY

djust provides Phoenix LiveView-style reactive server-side rendering for Django with Rust-powered performance. Prior to version 1.0.7, the WebSocket `handle_mount` and `ViewRuntime._build_request` rebuild an `HttpRequest` via `RequestFactory().get(...)` with no `HTTP_HOST`, so `request.get_host()` defaulted to `"testserver"` on the live path. Host/subdomain/domain `TenantResolver`s then misresolved the tenant — `None` on the live path while the HTTP path resolved correctly. With `STRICT_MODE=False` the tenant-scoped managers returned unscoped rows (cross-tenant disclosure); with the default they returned an empty queryset (broken tenancy). This is fixed in djust 1.0.7. The handshake Host is extracted from the ASGI scope, validated against `ALLOWED_HOSTS` (the same logic as the CSWSH Origin gate, parsed with Django's `split_domain_port` so malformed Hosts are rejected at the boundary), and propagated — with the TLS scheme — into the reconstructed request, so live-path tenant resolution matches HTTP exactly. There is no known workaround on the live path short of upgrading. Users are most exposed when combined with `STRICT_MODE=False`.

Published

Date2026-09-16

Updated

Date2026-09-16

RISK INFORMATION (Score: 6.3)

cvss3

Base Score: 6.3

Complexity: HIGH

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N

Impact Score

Exploitability

1.8

REFERENCES

CVE-2026-61588

SUMMARY

djust provides Phoenix LiveView-style reactive server-side rendering for Django with Rust-powered performance. Prior to version 1.0.7, when a Django `Model` instance is assigned to a public view attribute, djust serialized it to the client with no sensitive-field denylist — sending fields such as `password` (the hash), privilege flags (e.g. `is_staff` / `is_superuser`), tokens, and other PII to the browser. Because exposing model objects to templates is a normal djust pattern, this could leak credentials/PII without the developer realizing the full object crossed the wire. This is fixed in djust 1.0.7. Model serialization applies a secure-by-default sensitive-field denylist (password/hash/token/secret-style fields and known privilege flags are withheld) with an identity-subset fallback. As a workaround, keep `Model` instances on `_private` attributes and expose only the specific fields needed, until patched.

Published

Date2026-09-16

Updated

Date2026-09-16

RISK INFORMATION (Score: 6.5)

cvss3

Base Score: 6.5

Complexity: LOW

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Impact Score

3.6

Exploitability

2.8

REFERENCES

Loading…

API

Access Data Using Our API

Get company history

curl -i -X GET 'https://api.rankiteo.com/underwriter-getcompany-history?
linkedin_id=axa' -H 'apikey: YOUR_API_KEY_HERE'

Try It API Documentation Rapid

MEASURE

What Do We Measure ?

Incident

Finding

Grade

Digital Assets

Every week, Rankiteo analyzes billions of signals to give organizations a sharper, faster view of emerging risks. With deeper, more actionable intelligence at their fingertips, security teams can outpace threat actors, respond instantly to Zero-Day attacks, and dramatically shrink their risk exposure window.

These are some of the factors we use to calculate the overall score:

Network SecurityIdentify exposed access points, detect misconfigured SSL certificates, and uncover vulnerabilities across the network infrastructure.

SBOM (Software Bill of Materials)Gain visibility into the software components used within an organization to detect vulnerabilities, manage risk, and ensure supply chain security.

CMDB (Configuration Management Database)Monitor and manage all IT assets and their configurations to ensure accurate, real-time visibility across the company's technology environment.

Threat IntelligenceLeverage real-time insights on active threats, malware campaigns, and emerging vulnerabilities to proactively defend against evolving cyberattacks.

Rankiteo

By Rankiteo

★ ★ ★ ★ ★

View on G2.com

Rankiteo is a unified scoring and risk platform that analyzes billions of signals weekly to help organizations gain faster, more actionable insights into emerging threats. Empowering teams to outpace adversaries and reduce exposure.

View latest plans →View all security reports →

MILESTONEG

Users
Love Us

Loading…

Badge your company to reduce your risk score and your cyber insurance costs!

Trusted by insurers. Chosen by leaders.

Classical KUSC Vendor Cyber Rating & Cyber Score

Classical KUSC A.I CyberSecurity Scoring

Classical KUSC CyberSecurity News & History

Classical KUSC Company Scoring based on AI Models

Cyber Incidents Likelihood 3 - 6 - 9 months

Incident Predictions locked

A.I Risk Score Likelihood 3 - 6 - 9 months

A.I. Risk Score Predictions locked

Underwriter Stats for Classical KUSC

Incidents vs Musicians Industry Avg (This Year)

Incidents vs All-Companies Average (This Year)

Incident Types Classical KUSC vs Musicians Industry Avg (This Year)

Incident History - Classical KUSC (X = Date, Y = Severity)

Classical KUSC Subsidiaries

Parent Company

Classical KUSC

Classical KUSC Similar Companies

Yamaha Corporation

Spotify

Classical KUSC CyberSecurity News

Global CVEs (Not Company-Specific)

Access Data Using Our API

What Do We Measure ?

These are some of the factors we use to calculate the overall score:

Rankiteo

Classical KUSC CyberSecurity News & History

Classical KUSC Company Scoring based on AI Models

Cyber Incidents Likelihood 3 - 6 - 9 months

Incident Predictions locked

A.I Risk Score Likelihood 3 - 6 - 9 months

A.I. Risk Score Predictions locked

Underwriter Stats for Classical KUSC

Incidents vs Musicians Industry Avg (This Year)

Incidents vs All-Companies Average (This Year)

Incident Types Classical KUSC vs Musicians Industry Avg (This Year)

Incident History - Classical KUSC (X = Date, Y = Severity)

Classical KUSC Subsidiaries

Parent Company

Classical KUSC

Classical KUSC Similar Companies

Yamaha Corporation

Spotify

Classical KUSC CyberSecurity News

Global CVEs (Not Company-Specific)

Access Data Using Our API

What Do We Measure ?

These are some of the factors we use to calculate the overall score:

Rankiteo