Comparison Overview

Simon Fraser University

VS

Northwestern University

Simon Fraser University

8888 University Drive, Burnaby, BC, CA, V5A 1S6
Last Update: 2025-11-22
Between 750 and 799

As Canada’s engaged university, SFU works with communities, organizations and partners to create, share and embrace knowledge that improves life and generates real change. We deliver a world-class education with lifelong value that shapes change-makers, visionaries and problem-solvers. We connect research and innovation to entrepreneurship and industry to deliver sustainable, relevant solutions to today’s problems. With campuses in British Columbia’s three largest cities – Vancouver, Burnaby and Surrey – SFU has eight faculties that deliver 193 undergraduate degree programs and 127 graduate degree programs to more than 35,000 students. The university now boasts more than 160,000 alumni residing in 143 countries.

NAICS: 6113
NAICS Definition: Colleges, Universities, and Professional Schools
Employees: 7,539
Subsidiaries: 3
12-month incidents
0
Known data breaches
1
Attack type number
1

Northwestern University

633 Clark St, Evanston, IL, 60208, US
Last Update: 2025-11-25
Between 800 and 849

Northwestern is one of the nation’s premier research universities, combining innovative teaching and pioneering research in a highly collaborative, multidisciplinary, and diverse environment. Northwestern provides both students and faculty exceptional opportunities for intellectual, personal, and professional growth in beautiful settings, with two campuses located on Lake Michigan: a 240-acre campus in Evanston, minutes north of Chicago, and a 25-acre campus in downtown Chicago. A third campus in Doha, Qatar was founded in 2008. For more information visit http://www.northwestern.edu

NAICS: 6113
NAICS Definition: Colleges, Universities, and Professional Schools
Employees: 16,756
Subsidiaries: 18
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/simon-fraser-university.jpeg
Simon Fraser University
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/northwestern-university.jpeg
Northwestern University
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
Simon Fraser University
100%
Compliance Rate
0/4 Standards Verified
Northwestern University
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Higher Education Industry Average (This Year)

No incidents recorded for Simon Fraser University in 2025.

Incidents vs Higher Education Industry Average (This Year)

No incidents recorded for Northwestern University in 2025.

Incident History — Simon Fraser University (X = Date, Y = Severity)

Simon Fraser University cyber incidents detection timeline including parent company and subsidiaries

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

Northwestern University cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/simon-fraser-university.jpeg
Simon Fraser University
Incidents

Date Detected: 6/2019
Type:Breach
Blog: Blog
https://images.rankiteo.com/companyimages/northwestern-university.jpeg
Northwestern University
Incidents

No Incident

FAQ

Northwestern University company demonstrates a stronger AI Cybersecurity Score compared to Simon Fraser University company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Simon Fraser University company has historically faced a number of disclosed cyber incidents, whereas Northwestern University company has not reported any.

In the current year, Northwestern University company and Simon Fraser University company have not reported any cyber incidents.

Neither Northwestern University company nor Simon Fraser University company has reported experiencing a ransomware attack publicly.

Simon Fraser University company has disclosed at least one data breach, while the other Northwestern University company has not reported such incidents publicly.

Neither Northwestern University company nor Simon Fraser University company has reported experiencing targeted cyberattacks publicly.

Neither Simon Fraser University company nor Northwestern University company has reported experiencing or disclosing vulnerabilities publicly.

Neither Simon Fraser University nor Northwestern University holds any compliance certifications.

Neither company holds any compliance certifications.

Northwestern University company has more subsidiaries worldwide compared to Simon Fraser University company.

Northwestern University company employs more people globally than Simon Fraser University company, reflecting its scale as a Higher Education.

Neither Simon Fraser University nor Northwestern University holds SOC 2 Type 1 certification.

Neither Simon Fraser University nor Northwestern University holds SOC 2 Type 2 certification.

Neither Simon Fraser University nor Northwestern University holds ISO 27001 certification.

Neither Simon Fraser University nor Northwestern University holds PCI DSS certification.

Neither Simon Fraser University nor Northwestern University holds HIPAA certification.

Neither Simon Fraser University nor Northwestern University 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