Comparison Overview

Tulane University Libraries

VS

Salt Lake County Library

Tulane University Libraries

7001 Freret Street, None, New Orleans, LA, US, 70118
Last Update: 2025-11-27
Between 700 and 749

Tulane University Libraries consist of four physical locations across two campuses in one of the most vibrant and diverse cities in North America. The Libraries serve Tulane’s nine schools and one undergraduate college with over 4.6 million books and physical items; 1.2 million eBooks; nearly 200,000 online journals; 900 databases; and distinctive collections that focus on the many facets of New Orleans’s music, history, and culture, including early jazz; regional history; literary culture; carnival; food and drink; and the architecture of the city and Gulf South region. The Libraries host the Tulane Digital Library and an institutional repository and publish several OpenAccess journals. Tulane’s Latin American Library (LAL) holds one of the most impressive collections in the world of materials on the history and culture of Central and South America and the Caribbean. The LAL also serves as the Secretariat for the Seminar on the Acquisition of Latin American Library Materials (SALALM), an international association of librarians, archivists, book dealers, book professionals, scholars, and students interested in collecting, preserving, and providing access to Latin American, Caribbean, Iberian, and Latinx information resources in all formats. Matas Library of the Health Sciences in downtown New Orleans serves students and faculty in the Schools of Medicine and of Public Health and Tropical Medicine as well as the Tulane National Primate Center in Covington, LA. The Tulane Libraries are made up of ca. 110 full-time staff and librarians. We are members of the Association of Research Libraries (ARL), the Association of Southeastern Research Libraries (ASERL), the Center for Research Libraries (CRL), the Coalition for Networked Information (CNI), HathiTrust, the Digital Library Federation (DLF), and other organizations. The Libraries’ values include a commitment to diversity, equity, and inclusion in our leadership and professional practice.

NAICS: 51912
NAICS Definition: Libraries and Archives
Employees: 46
Subsidiaries: 0
12-month incidents
0
Known data breaches
1
Attack type number
1

Salt Lake County Library

8030 S 1825 W, West Jordan , UT, 84088, US
Last Update: 2025-11-23
Between 750 and 799

The mission of Salt Lake County Library is to make a positive difference in the lives of our community by inspiring imagination, satisfying curiosity and providing a great place for everyone to visit. We provide spaces, resources and programs for self-guided learning, growth and community connections at community County Library branches and at the Library's Viridian Event Center located throughout the Salt Lake Valley and /or the Internet. The first Salt Lake County Library Board was established in 1938. One year later, in 1939, Salt Lake County Library Services began operations in two classrooms of the old Midvale School. More than 75 years later we have 18 libraries, two reading rooms and library services available in the Salt Lake County jail. Each year more than 4.5 million children, teens, adults and businesses visit our 18 Salt Lake County Libraries where thousands of free programs and millions of complimentary resources and materials are available to them. We are honored to remain an innovative community hub that provides equal access to information, technology and resources. Our online library, slcolibrary.org, provides library card holders the opportunity to manage their account, check out books, audiobooks, eaudiobooks, movies, television shows and music or access one of our many free databases – 24 hours a day, seven days a week. Library membership is free to Salt Lake County residents and continues to be an excellent return on investment for the community.

NAICS: 519
NAICS Definition:
Employees: 212
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/tulaneuniversityllibraries.jpeg
Tulane University Libraries
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/salt-lake-county-library.jpeg
Salt Lake County Library
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
Tulane University Libraries
100%
Compliance Rate
0/4 Standards Verified
Salt Lake County Library
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Libraries Industry Average (This Year)

No incidents recorded for Tulane University Libraries in 2025.

Incidents vs Libraries Industry Average (This Year)

No incidents recorded for Salt Lake County Library in 2025.

Incident History — Tulane University Libraries (X = Date, Y = Severity)

Tulane University Libraries cyber incidents detection timeline including parent company and subsidiaries

Incident History — Salt Lake County Library (X = Date, Y = Severity)

Salt Lake County Library cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/tulaneuniversityllibraries.jpeg
Tulane University Libraries
Incidents

Date Detected: 12/2023
Type:Breach
Attack Vector: Unauthorized acquisition of financial account numbers and credit/debit card numbers
Blog: Blog
https://images.rankiteo.com/companyimages/salt-lake-county-library.jpeg
Salt Lake County Library
Incidents

No Incident

FAQ

Salt Lake County Library company demonstrates a stronger AI Cybersecurity Score compared to Tulane University Libraries company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Tulane University Libraries company has historically faced a number of disclosed cyber incidents, whereas Salt Lake County Library company has not reported any.

In the current year, Salt Lake County Library company and Tulane University Libraries company have not reported any cyber incidents.

Neither Salt Lake County Library company nor Tulane University Libraries company has reported experiencing a ransomware attack publicly.

Tulane University Libraries company has disclosed at least one data breach, while the other Salt Lake County Library company has not reported such incidents publicly.

Neither Salt Lake County Library company nor Tulane University Libraries company has reported experiencing targeted cyberattacks publicly.

Neither Tulane University Libraries company nor Salt Lake County Library company has reported experiencing or disclosing vulnerabilities publicly.

Neither Tulane University Libraries nor Salt Lake County Library holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Tulane University Libraries company nor Salt Lake County Library company has publicly disclosed detailed information about the number of their subsidiaries.

Salt Lake County Library company employs more people globally than Tulane University Libraries company, reflecting its scale as a Libraries.

Neither Tulane University Libraries nor Salt Lake County Library holds SOC 2 Type 1 certification.

Neither Tulane University Libraries nor Salt Lake County Library holds SOC 2 Type 2 certification.

Neither Tulane University Libraries nor Salt Lake County Library holds ISO 27001 certification.

Neither Tulane University Libraries nor Salt Lake County Library holds PCI DSS certification.

Neither Tulane University Libraries nor Salt Lake County Library holds HIPAA certification.

Neither Tulane University Libraries nor Salt Lake County Library holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.16, 20.3.14, and 21.0.1, there is a XSRF token leakage via protocol-relative URLs in angular HTTP clients. The vulnerability is a Credential Leak by App Logic that leads to the unauthorized disclosure of the Cross-Site Request Forgery (XSRF) token to an attacker-controlled domain. Angular's HttpClient has a built-in XSRF protection mechanism that works by checking if a request URL starts with a protocol (http:// or https://) to determine if it is cross-origin. If the URL starts with protocol-relative URL (//), it is incorrectly treated as a same-origin request, and the XSRF token is automatically added to the X-XSRF-TOKEN header. This issue has been patched in versions 19.2.16, 20.3.14, and 21.0.1. A workaround for this issue involves avoiding using protocol-relative URLs (URLs starting with //) in HttpClient requests. All backend communication URLs should be hardcoded as relative paths (starting with a single /) or fully qualified, trusted absolute URLs.

Risk Information
cvss4
Base: 7.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/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

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Uncontrolled Recursion vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft deep ASN.1 structures that trigger unbounded recursive parsing. This leads to a Denial-of-Service (DoS) via stack exhaustion when parsing untrusted DER inputs. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 8.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/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

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Integer Overflow vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft ASN.1 structures containing OIDs with oversized arcs. These arcs may be decoded as smaller, trusted OIDs due to 32-bit bitwise truncation, enabling the bypass of downstream OID-based security decisions. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 6.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/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

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. Prior to versions 7.0.13 and 8.0.2, working with large buffers in Lua scripts can lead to a stack overflow. Users of Lua rules and output scripts may be affected when working with large buffers. This includes a rule passing a large buffer to a Lua script. This issue has been patched in versions 7.0.13 and 8.0.2. A workaround for this issue involves disabling Lua rules and output scripts, or making sure limits, such as stream.depth.reassembly and HTTP response body limits (response-body-limit), are set to less than half the stack size.

Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Description

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. In versions from 8.0.0 to before 8.0.2, a NULL dereference can occur when the entropy keyword is used in conjunction with base64_data. This issue has been patched in version 8.0.2. A workaround involves disabling rules that use entropy in conjunction with base64_data.

Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H