Comparison Overview

Aschehoug

VS

Lippincott NursingCenter

Aschehoug

Sehestedsgt. 3, Oslo, 0102, NO
Last Update: 2025-11-21
Between 750 and 799

Aschehoug forlag gir lesere, lærere og elever litterære opplevelser og kunnskap gjennom bøkene og læremidlene våre. Vi opplyser, utfordrer og underholder, enten du liker å lese, lytte eller utforske digitalt. Gode lese- og læreopplevelser er nøkkelen til å forstå verden og oss selv. Derfor satser vi på nye stemmer og formater, et litterært mangfold og et rikt læringsunivers. Vi skal være en garantist for ytringsfrihet, som er en forutsetning for demokratiet og at samfunnet stadig utvikler seg. Aschehoug ble grunnlagt i 1872. Forlaget Oktober og Universitetsforlaget inngår i forlagskonsernet, som også eier deler av Norli, De norske Bokklubbene og Lydbokforlaget. Mads Nygaard er konsernsjef og forlegger. Vi holder til på Sehesteds plass, sentralt i Oslo.

NAICS: 511
NAICS Definition: Publishing Industries (except Internet)
Employees: 300
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Lippincott NursingCenter

Two Commerce Square, 2001 Market Street, Philadelphia, PA, 19103, US
Last Update: 2025-11-27
Between 750 and 799

Created by nurses, for nurses, Lippincott® NursingCenter®, from Wolters Kluwer Health, is the premier destination site for your clinical and professional informational needs. We are committed to providing credible, current, authoritative, evidence-based resources to help you in your practice. Lippincott® Nursing Center® is powered by more than 70 of our leading peer-reviewed nursing journals, including the American Journal of Nursing, Nursing2021, Nursing Management, The Nurse Practitioner, and many more specialty Lippincott® journals and books. Follow Wolters Kluwer Health https://www.linkedin.com/company/wolters-kluwer-health/.

NAICS: 511
NAICS Definition: Publishing Industries (except Internet)
Employees: 93
Subsidiaries: 1
12-month incidents
0
Known data breaches
1
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/aschehoug.jpeg
Aschehoug
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/lippincott-s-nursingcenter-com.jpeg
Lippincott NursingCenter
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
Aschehoug
100%
Compliance Rate
0/4 Standards Verified
Lippincott NursingCenter
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 Aschehoug in 2025.

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

No incidents recorded for Lippincott NursingCenter in 2025.

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

Aschehoug cyber incidents detection timeline including parent company and subsidiaries

Incident History — Lippincott NursingCenter (X = Date, Y = Severity)

Lippincott NursingCenter cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/aschehoug.jpeg
Aschehoug
Incidents

No Incident

https://images.rankiteo.com/companyimages/lippincott-s-nursingcenter-com.jpeg
Lippincott NursingCenter
Incidents

Date Detected: 4/2025
Type:Breach
Blog: Blog

FAQ

Aschehoug company demonstrates a stronger AI Cybersecurity Score compared to Lippincott NursingCenter company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Lippincott NursingCenter company has historically faced a number of disclosed cyber incidents, whereas Aschehoug company has not reported any.

In the current year, Lippincott NursingCenter company has reported more cyber incidents than Aschehoug company.

Neither Lippincott NursingCenter company nor Aschehoug company has reported experiencing a ransomware attack publicly.

Lippincott NursingCenter company has disclosed at least one data breach, while Aschehoug company has not reported such incidents publicly.

Neither Lippincott NursingCenter company nor Aschehoug company has reported experiencing targeted cyberattacks publicly.

Neither Aschehoug company nor Lippincott NursingCenter company has reported experiencing or disclosing vulnerabilities publicly.

Neither Aschehoug nor Lippincott NursingCenter holds any compliance certifications.

Neither company holds any compliance certifications.

Lippincott NursingCenter company has more subsidiaries worldwide compared to Aschehoug company.

Aschehoug company employs more people globally than Lippincott NursingCenter company, reflecting its scale as a Book and Periodical Publishing.

Neither Aschehoug nor Lippincott NursingCenter holds SOC 2 Type 1 certification.

Neither Aschehoug nor Lippincott NursingCenter holds SOC 2 Type 2 certification.

Neither Aschehoug nor Lippincott NursingCenter holds ISO 27001 certification.

Neither Aschehoug nor Lippincott NursingCenter holds PCI DSS certification.

Neither Aschehoug nor Lippincott NursingCenter holds HIPAA certification.

Neither Aschehoug nor Lippincott NursingCenter 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.

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
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).

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
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

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
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.

Description

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