Comparison Overview

CITY RECORDS

VS

Being Single Magazine

CITY RECORDS

Svetog Nikole 52, Belgrade, Serbia, 11000, RS
Last Update: 2025-11-26
View Profile
Between 750 and 799
http://www.cityrecords.rs

Izdavačka kuća "City Records" osnovana je 1997. godine i od tada je institucija koja okuplja sva bitnija imena domaće muzičke scene. Otvorila put ka slavi mnogim, tada neafirmisanim, a sada veoma popularnim izvođačima (Željko Joksimović, Nataša Bekvalac, Ana Nikolić, Romana, OK band, Saša Kovačević...). “City Records” svojim stilom, savremenošću i kvalitetom diktira trendove u popularnoj muzici na ovim prostorima. "City Records" je počeo sa radom u avgustu 1997. Trenutno broji 16 stalno zaposlenih u direkciji, veleprodaji i proizvodnji. Na našim prostorima prvi su izdali muzički DVD i prvo strano licencno izdanje u saradnji sa muzičkim kućama BMG i SONY. "City Records" je od jula 2006. godina nosilac prestižnog Chambertrust pečata – znaka poverenja u poslovanju, koji je dobio od Privredne komore Beograda i WCN-a (Svetske komorske mreže). Jedan je od osnivača OFPS (Organizacija za kolektivno ostvarivanje prava proizvođača fonograma) koja se uspešno bori protiv piraterije kod nas. City Records je od 01.02.2012 proširio svoju delatnost pruzimanjem mašina za proizvodnju od strane Pink Digital Sistem-a u oblasti izrade i proizvodnje stampera-masteringa za CD,DVD 5 I DVD 9 . Željko Mitrović - osnivač i vlasnik Bane Stojanović - direktor Milica Mitrović - glavni i odgovorni urednik

NAICS: 511
NAICS Definition:
Employees: 29
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0
View Profile

Being Single Magazine

None
Last Update: 2025-11-21
Between 750 and 799
http://beingsinglemagonline.com/

Being Single Magazine , founded in 1982, began as a print publication. The mission of the magazine was to guide Singles in living their best life in their chosen lifestyle. Gaining worldwide acclaim over the years, we impacted the lives of tons of singles across the globe. We have recently made the complete switch from print to digital and hold tight to our purpose of providing the non-married with dating and lifestyle information to enhance and influence their lives and social decisions.

NAICS: 511
NAICS Definition: Publishing Industries (except Internet)
Employees: None
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/city-records.jpeg
CITY RECORDS
—
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/being-single-magazine.jpeg
Being Single Magazine
—
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
CITY RECORDS
100%
Compliance Rate
0/4 Standards Verified
Being Single Magazine
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Book and Periodical Publishing Industry Average (This Year)

No incidents recorded for CITY RECORDS in 2025.

Incidents vs Book and Periodical Publishing Industry Average (This Year)

No incidents recorded for Being Single Magazine in 2025.

Incident History — CITY RECORDS (X = Date, Y = Severity)

CITY RECORDS cyber incidents detection timeline including parent company and subsidiaries

Incident History — Being Single Magazine (X = Date, Y = Severity)

Being Single Magazine cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/city-records.jpeg
CITY RECORDS
Incidents

No Incident

https://images.rankiteo.com/companyimages/being-single-magazine.jpeg
Being Single Magazine
Incidents

No Incident

FAQ

Being Single Magazine company demonstrates a stronger AI Cybersecurity Score compared to CITY RECORDS company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Being Single Magazine company has disclosed a higher number of cyber incidents compared to CITY RECORDS company.

In the current year, Being Single Magazine company and CITY RECORDS company have not reported any cyber incidents.

Neither Being Single Magazine company nor CITY RECORDS company has reported experiencing a ransomware attack publicly.

Neither Being Single Magazine company nor CITY RECORDS company has reported experiencing a data breach publicly.

Neither Being Single Magazine company nor CITY RECORDS company has reported experiencing targeted cyberattacks publicly.

Neither CITY RECORDS company nor Being Single Magazine company has reported experiencing or disclosing vulnerabilities publicly.

Neither CITY RECORDS nor Being Single Magazine holds any compliance certifications.

Neither company holds any compliance certifications.

Neither CITY RECORDS company nor Being Single Magazine company has publicly disclosed detailed information about the number of their subsidiaries.

Neither CITY RECORDS nor Being Single Magazine holds SOC 2 Type 1 certification.

Neither CITY RECORDS nor Being Single Magazine holds SOC 2 Type 2 certification.

Neither CITY RECORDS nor Being Single Magazine holds ISO 27001 certification.

Neither CITY RECORDS nor Being Single Magazine holds PCI DSS certification.

Neither CITY RECORDS nor Being Single Magazine holds HIPAA certification.

Neither CITY RECORDS nor Being Single Magazine holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

ThingsBoard in versions prior to v4.2.1 allows an authenticated user to upload malicious SVG images via the "Image Gallery", leading to a Stored Cross-Site Scripting (XSS) vulnerability. The exploit can be triggered when any user accesses the public API endpoint of the malicious SVG images, or if the malicious images are embedded in an `iframe` element, during a widget creation, deployed to any page of the platform (e.g., dashboards), and accessed during normal operations. The vulnerability resides in the `ImageController`, which fails to restrict the execution of JavaScript code when an image is loaded by the user's browser. This vulnerability can lead to the execution of malicious code in the context of other users' sessions, potentially compromising their accounts and allowing unauthorized actions.

Published
Date
2025-11-27
Updated
Date
2025-11-27
Risk Information
cvss4
Base: 6.2
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:H/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
References
Description

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to to verify that the token used during the code exchange originates from the same authentication flow, which allows an authenticated user to perform account takeover via a specially crafted email address used when switching authentication methods and sending a request to the /users/login/sso/code-exchange endpoint. The vulnerability requires ExperimentalEnableAuthenticationTransfer to be enabled (default: enabled) and RequireEmailVerification to be disabled (default: disabled).

Published
Date
2025-11-27
Updated
Date
2025-11-27
Risk Information
cvss3
Base: 9.9
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
References
Description

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to sanitize team email addresses to be visible only to Team Admins, which allows any authenticated user to view team email addresses via the GET /api/v4/channels/{channel_id}/common_teams endpoint

Published
Date
2025-11-27
Updated
Date
2025-11-27
Risk Information
cvss3
Base: 4.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
References
Description

Exposure of email service credentials to users without administrative rights in Devolutions Server.This issue affects Devolutions Server: before 2025.2.21, before 2025.3.9.

Published
Date
2025-11-27
Updated
Date
2025-11-27
References
Description

Exposure of credentials in unintended requests in Devolutions Server.This issue affects Server: through 2025.2.20, through 2025.3.8.

Published
Date
2025-11-27
Updated
Date
2025-11-27
References