Keck Medicine of USC Company Cyber Security Posture

keckmedicine.org

Keck Medicine of USC is the University of Southern Californiaโ€™s medical enterprise, one of only two university-based medical systems in the Los Angeles area. Keck Medicine combines academic excellence, world-class research and state-of-the-art facilities to provide highly specialized care for some of the most acute patients in the country. Its internationally renowned physicians and scientists provide world-class patient care at Keck Hospital of USC, USC Norris Cancer Hospital, USC Verdugo Hills Hospital, USC Arcadia Hospital and more than 100 unique clinics in Los Angeles, Orange, Kern, Tulare and Ventura counties. Keck Medical Center of USC, which includes Keck Hospital and USC Norris Cancer Hospital, is among the top 50 hospitals in the country in 10 specialties, as well as among the top six hospitals in California and top three hospitals in metro Los Angeles, according to the U.S. News & World Report 2023-24 Best Hospitals rankings.

KMU Company Details

Linkedin ID:

keck-medicine-of-usc

Employees number:

4711 employees

Number of followers:

53284.0

NAICS:

62

Industry Type:

Hospitals and Health Care

Homepage:

keckmedicine.org

IP Addresses:

Scan still pending

Company ID:

KEC_3998812

Scan Status:

In-progress

AI scoreKMU Risk Score (AI oriented)

Between 800 and 900

This score is AI-generated and less favored by cyber insurers, who prefer the TPRM score.

Ailogo

Keck Medicine of USC Company Scoring based on AI Models

Model NameDateDescriptionCurrent Score DifferenceScore
AVERAGE-Industry03-12-2025

This score represents the average cybersecurity rating of companies already scanned within the same industry. It provides a benchmark to compare an individual company's security posture against its industry peers.

N/A

Between 800 and 900

Keck Medicine of USC Company Cyber Security News & History

Past Incidents
1
Attack Types
1
EntityTypeSeverityImpactSeenUrl IDDetailsView
Keck Medicine of USCRansomware85308/2016KEC11119622Link
Rankiteo Explanation :
Attack with significant impact with internal employee data leaks

Description: Keck Medical Center of USC suffered a ransomware attack, two servers were hacked that contained internal documents. The compromised information included demographic information, date of birth, health information including treatment and diagnosis, and in some cases, Social Security numbers. Other files in the encrypted folders contained medical record numbers, date of service, insurance information, and CPT codes, but no patient names. Keck investigated the incident and restored the files within a few days and did not pay any ransom.

Keck Medicine of USC Company Subsidiaries

SubsidiaryImage

Keck Medicine of USC is the University of Southern Californiaโ€™s medical enterprise, one of only two university-based medical systems in the Los Angeles area. Keck Medicine combines academic excellence, world-class research and state-of-the-art facilities to provide highly specialized care for some of the most acute patients in the country. Its internationally renowned physicians and scientists provide world-class patient care at Keck Hospital of USC, USC Norris Cancer Hospital, USC Verdugo Hills Hospital, USC Arcadia Hospital and more than 100 unique clinics in Los Angeles, Orange, Kern, Tulare and Ventura counties. Keck Medical Center of USC, which includes Keck Hospital and USC Norris Cancer Hospital, is among the top 50 hospitals in the country in 10 specialties, as well as among the top six hospitals in California and top three hospitals in metro Los Angeles, according to the U.S. News & World Report 2023-24 Best Hospitals rankings.

Loading...

Access Data Using Our API

SubsidiaryImage

Get company history

curl -i -X GET 'https://api.rankiteo.com/underwriter-getcompany-history?linkedin_id=keck-medicine-of-usc' -H 'apikey: YOUR_API_KEY_HERE'
newsone

KMU Cyber Security News

2025-05-28T18:11:57.000Z
Keck Medicine of USC students support communities hit by LA wildfires

When the Eaton and Palisades wildfires devastated areas of Los Angeles County earlier this year, they sparked a swift response from students at Keck Schoolย ...

2024-09-03T07:00:00.000Z
Bargaining, contract fights heat up across health systems

Thousands of healthcare workers nationwide are negotiating for new contracts, and staff at some facilities are preparing for the possibilityย ...

2017-11-02T07:00:00.000Z
GO-Biz Launches Cyber-Health IT Advisory Board with USC Center for Body Computing

The USC Center for Body Computing will lead the advisory board with its founder and executive director, Leslie Saxon, MD, serving as chair. Theย ...

2022-10-03T07:00:00.000Z
Eleven New Faculty Join USCโ€™s Department of Computer Science

Filip Ilievski joined USC as a research assistant professor of computer science in August 2022. He is also a research lead at the Center onย ...

2020-10-15T07:00:00.000Z
Patient engagement enables โ€˜immenseโ€™ revenue savings for Keck Medicine of USC

Keck Medicine of USC, a health system based in Los Angeles, had experienced a few years of dramatic growth in both patient volume andย ...

2023-09-28T07:00:00.000Z
MedCity Moves Podcast: Recent Hires, Layoffs & an Interview with Chris Allen, CFO at Keck Medicine of USC

The MedCity Moves Podcast (Opens in a new window) is back with another episode. We discuss some of the executive appointments occurring inย ...

2019-06-21T07:00:00.000Z
Are Spicy Foods Bad For Your Stomach?

Are spicy foods bad for your stomach? originally appeared on Quora: the place to gain and share knowledge, empowering people to learn fromย ...

2023-09-27T18:31:51.000Z
How health IT's leading innovators are using AI now, and where they see it going

AI can make maternal ultrasonography more accessible, accurate and efficient. That could completely change the landscape for perinatal care and greatly improveย ...

2019-03-19T07:00:00.000Z
USC delegation meets with lawmakers in Washington, D.C.

USC interim President Wanda M. Austin and provost Michael Quick led a delegation of trustees and administrators to Washington, DC, last week to advocate for aย ...

similarCompanies

KMU Similar Companies

Help at Home

In our 45+ year history, Help at Home has provided care for individuals, helping them to remain independent and able to live their best lives in their own homes. Our clients have always been like family. As the leading national provider of high-quality, relationship-based home care for seniors and p

University Hospitals Bristol and Weston NHS Foundation Trust

We are University Hospitals Bristol and Weston NHS Foundation Trust (UHBW). One of the largest acute Trusts in the country, bringing together a combined workforce of over 13,000 staff and over 100 different clinical services across 10 different sites, serving a core population of more than 500,000 p

Unilabs

We are one of Europeโ€šร„รดs leading suppliers of clinical laboratory testing and medical diagnostic imaging services to private and public healthcare providers, local governments, insurance companies, pharmaceutical companies and the general public. We operate laboratory and medical diagnostic imaging

IHH HEALTHCARE MALAYSIA

IHH Healthcare Malaysia is one of the largest private healthcare providers in Malaysia, with approximately 3,000 beds. Our healthcare network comprises 11 Pantai Hospitals, four Gleneagles Hospitals, Prince Court Medical Centre and Timberland Medical Centre, and is complemented by ancillary service

Aster DM Healthcare

From a single medical centre to a performance-driven healthcare enterprise spread across more than 366 medical establishments, including 34 hospitals, 131 clinics and 502 pharmacies in 7 countries and growing, Aster DM Healthcare has transitioned into being the leading healthcare authority across th

Brigham and Women's Hospital

Boston's Brigham and Women's Hospital (BWH) is an international leader in virtually every area of medicine and has been the site of pioneering breakthroughs that have improved lives around the world. A major teaching hospital of Harvard Medical School, BWH has a legacy of excellence that continues t

faq

Frequently Asked Questions (FAQ) on Cybersecurity Incidents

KMU CyberSecurity History Information

Total Incidents: According to Rankiteo, KMU has faced 1 incidents in the past.

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

Total Financial Loss: The total financial loss from these incidents is estimated to be {total_financial_loss}.

Cybersecurity Posture: The company's overall cybersecurity posture is described as Keck Medicine of USC is the University of Southern Californiaโ€™s medical enterprise, one of only two university-based medical systems in the Los Angeles area. Keck Medicine combines academic excellence, world-class research and state-of-the-art facilities to provide highly specialized care for some of the most acute patients in the country. Its internationally renowned physicians and scientists provide world-class patient care at Keck Hospital of USC, USC Norris Cancer Hospital, USC Verdugo Hills Hospital, USC Arcadia Hospital and more than 100 unique clinics in Los Angeles, Orange, Kern, Tulare and Ventura counties. Keck Medical Center of USC, which includes Keck Hospital and USC Norris Cancer Hospital, is among the top 50 hospitals in the country in 10 specialties, as well as among the top six hospitals in California and top three hospitals in metro Los Angeles, according to the U.S. News & World Report 2023-24 Best Hospitals rankings..

Detection and Response: The company detects and responds to cybersecurity incidents through {description_of_detection_and_response_process}.

Incident Details

Incident 1: Ransomware Attack

Title: {Incident_Title}

Description: {Brief_description_of_the_incident}

Date Detected: {Detection_Date}

Date Publicly Disclosed: {Disclosure_Date}

Date Resolved: {Resolution_Date}

Type: {Type_of_Attack}

Attack Vector: {Attack_Vector}

Vulnerability Exploited: {Vulnerability}

Threat Actor: {Threat_Actor}

Motivation: {Motivation}

Incident 2: Data Breach

Title: {Incident_Title}

Description: {Brief_description_of_the_incident}

Date Detected: {Detection_Date}

Date Publicly Disclosed: {Disclosure_Date}

Date Resolved: {Resolution_Date}

Type: {Type_of_Attack}

Attack Vector: {Attack_Vector}

Vulnerability Exploited: {Vulnerability}

Threat Actor: {Threat_Actor}

Motivation: {Motivation}

Common Attack Types: As of now, the company has not encountered any reported incidents involving common cyberattacks.

Identification of Attack Vectors: The company identifies the attack vectors used in incidents through {description_of_identification_process}.

Impact of the Incidents

Incident 1: Ransomware Attack

Financial Loss: {Financial_Loss}

Data Compromised: {Data_Compromised}

Systems Affected: {Systems_Affected}

Downtime: {Downtime}

Operational Impact: {Operational_Impact}

Conversion Rate Impact: {Conversion_Rate_Impact}

Revenue Loss: {Revenue_Loss}

Customer Complaints: {Customer_Complaints}

Brand Reputation Impact: {Brand_Reputation_Impact}

Legal Liabilities: {Legal_Liabilities}

Identity Theft Risk: {Identity_Theft_Risk}

Payment Information Risk: {Payment_Information_Risk}

Incident 2: Data Breach

Financial Loss: {Financial_Loss}

Data Compromised: {Data_Compromised}

Systems Affected: {Systems_Affected}

Downtime: {Downtime}

Operational Impact: {Operational_Impact}

Conversion Rate Impact: {Conversion_Rate_Impact}

Revenue Loss: {Revenue_Loss}

Customer Complaints: {Customer_Complaints}

Brand Reputation Impact: {Brand_Reputation_Impact}

Legal Liabilities: {Legal_Liabilities}

Identity Theft Risk: {Identity_Theft_Risk}

Payment Information Risk: {Payment_Information_Risk}

Average Financial Loss: The average financial loss per incident is {average_financial_loss}.

Commonly Compromised Data Types: The types of data most commonly compromised in incidents are {list_of_commonly_compromised_data_types}.

Incident 1: Ransomware Attack

Entity Name: {Entity_Name}

Entity Type: {Entity_Type}

Industry: {Industry}

Location: {Location}

Size: {Size}

Customers Affected: {Customers_Affected}

Incident 2: Data Breach

Entity Name: {Entity_Name}

Entity Type: {Entity_Type}

Industry: {Industry}

Location: {Location}

Size: {Size}

Customers Affected: {Customers_Affected}

Response to the Incidents

Incident 1: Ransomware Attack

Incident Response Plan Activated: {Yes/No}

Third Party Assistance: {Yes/No}

Law Enforcement Notified: {Yes/No}

Containment Measures: {Containment_Measures}

Remediation Measures: {Remediation_Measures}

Recovery Measures: {Recovery_Measures}

Communication Strategy: {Communication_Strategy}

Adaptive Behavioral WAF: {Adaptive_Behavioral_WAF}

On-Demand Scrubbing Services: {On_Demand_Scrubbing_Services}

Network Segmentation: {Network_Segmentation}

Enhanced Monitoring: {Enhanced_Monitoring}

Incident 2: Data Breach

Incident Response Plan Activated: {Yes/No}

Third Party Assistance: {Yes/No}

Law Enforcement Notified: {Yes/No}

Containment Measures: {Containment_Measures}

Remediation Measures: {Remediation_Measures}

Recovery Measures: {Recovery_Measures}

Communication Strategy: {Communication_Strategy}

Adaptive Behavioral WAF: {Adaptive_Behavioral_WAF}

On-Demand Scrubbing Services: {On_Demand_Scrubbing_Services}

Network Segmentation: {Network_Segmentation}

Enhanced Monitoring: {Enhanced_Monitoring}

Incident Response Plan: The company's incident response plan is described as {description_of_incident_response_plan}.

Third-Party Assistance: The company involves third-party assistance in incident response through {description_of_third_party_involvement}.

Data Breach Information

Incident 2: Data Breach

Type of Data Compromised: {Type_of_Data}

Number of Records Exposed: {Number_of_Records}

Sensitivity of Data: {Sensitivity_of_Data}

Data Exfiltration: {Yes/No}

Data Encryption: {Yes/No}

File Types Exposed: {File_Types}

Personally Identifiable Information: {Yes/No}

Prevention of Data Exfiltration: The company takes the following measures to prevent data exfiltration: {description_of_prevention_measures}.

Handling of PII Incidents: The company handles incidents involving personally identifiable information (PII) through {description_of_handling_process}.

Ransomware Information

Incident 1: Ransomware Attack

Ransom Demanded: {Ransom_Amount}

Ransom Paid: {Ransom_Paid}

Ransomware Strain: {Ransomware_Strain}

Data Encryption: {Yes/No}

Data Exfiltration: {Yes/No}

Ransom Payment Policy: The company's policy on paying ransoms in ransomware incidents is described as {description_of_ransom_payment_policy}.

Data Recovery from Ransomware: The company recovers data encrypted by ransomware through {description_of_data_recovery_process}.

Regulatory Compliance

Ransomware Logo

Incident 1: Ransomware Attack

Regulations Violated: {Regulations_Violated}

Fines Imposed: {Fines_Imposed}

Legal Actions: {Legal_Actions}

Regulatory Notifications: {Regulatory_Notifications}

Data Breach Logo

Incident 2: Data Breach

Regulations Violated: {Regulations_Violated}

Fines Imposed: {Fines_Imposed}

Legal Actions: {Legal_Actions}

Regulatory Notifications: {Regulatory_Notifications}

Regulatory Frameworks: The company complies with the following regulatory frameworks regarding cybersecurity: {list_of_regulatory_frameworks}.

Ensuring Regulatory Compliance: The company ensures compliance with regulatory requirements through {description_of_compliance_measures}.

Lessons Learned and Recommendations

Incident 1: Ransomware Attack

Lessons Learned: {Lessons_Learned}

Incident 2: Data Breach

Lessons Learned: {Lessons_Learned}

Incident 1: Ransomware Attack

Recommendations: {Recommendations}

Incident 2: Data Breach

Recommendations: {Recommendations}

Key Lessons Learned: The key lessons learned from past incidents are {list_of_key_lessons_learned}.

Implemented Recommendations: The company has implemented the following recommendations to improve cybersecurity: {list_of_implemented_recommendations}.

References

Incident 1: Ransomware Attack

Source: {Source}

URL: {URL}

Date Accessed: {Date_Accessed}

Incident 2: Data Breach

Source: {Source}

URL: {URL}

Date Accessed: {Date_Accessed}

Additional Resources: Stakeholders can find additional resources on cybersecurity best practices at {list_of_additional_resources}.

Investigation Status

Incident 1: Ransomware Attack

Investigation Status: {Investigation_Status}

Incident 2: Data Breach

Investigation Status: {Investigation_Status}

Communication of Investigation Status: The company communicates the status of incident investigations to stakeholders through {description_of_communication_process}.

Stakeholder and Customer Advisories

Incident 1: Ransomware Attack

Stakeholder Advisories: {Stakeholder_Advisories}

Customer Advisories: {Customer_Advisories}


Incident 2: Data Breach

Stakeholder Advisories: {Stakeholder_Advisories}

Customer Advisories: {Customer_Advisories}

Advisories Provided: The company provides the following advisories to stakeholders and customers following an incident: {description_of_advisories_provided}.

Initial Access Broker

Incident 1: Ransomware Attack

Entry Point: {Entry_Point}

Reconnaissance Period: {Reconnaissance_Period}

Backdoors Established: {Backdoors_Established}

High Value Targets: {High_Value_Targets}

Data Sold on Dark Web: {Yes/No}

Incident 2: Data Breach

Entry Point: {Entry_Point}

Reconnaissance Period: {Reconnaissance_Period}

Backdoors Established: {Backdoors_Established}

High Value Targets: {High_Value_Targets}

Data Sold on Dark Web: {Yes/No}

Monitoring and Mitigation of Initial Access Brokers: The company monitors and mitigates the activities of initial access brokers through {description_of_monitoring_and_mitigation_measures}.

Post-Incident Analysis

Incident 1: Ransomware Attack

Root Causes: {Root_Causes}

Corrective Actions: {Corrective_Actions}

Incident 2: Data Breach

Root Causes: {Root_Causes}

Corrective Actions: {Corrective_Actions}

Post-Incident Analysis Process: The company's process for conducting post-incident analysis is described as {description_of_post_incident_analysis_process}.

Corrective Actions Taken: The company has taken the following corrective actions based on post-incident analysis: {list_of_corrective_actions_taken}.

Additional Questions

General Information

Ransom Payment History: The company has {paid/not_paid} ransoms in the past.

Last Ransom Demanded: The amount of the last ransom demanded was {last_ransom_amount}.

Last Attacking Group: The attacking group in the last incident was {last_attacking_group}.

Incident Details

Most Recent Incident Detected: The most recent incident detected was on {most_recent_incident_detected_date}.

Most Recent Incident Publicly Disclosed: The most recent incident publicly disclosed was on {most_recent_incident_publicly_disclosed_date}.

Most Recent Incident Resolved: The most recent incident resolved was on {most_recent_incident_resolved_date}.

Impact of the Incidents

Highest Financial Loss: The highest financial loss from an incident was {highest_financial_loss}.

Most Significant Data Compromised: The most significant data compromised in an incident was {most_significant_data_compromised}.

Most Significant System Affected: The most significant system affected in an incident was {most_significant_system_affected}.

Response to the Incidents

Third-Party Assistance in Most Recent Incident: The third-party assistance involved in the most recent incident was {third_party_assistance_in_most_recent_incident}.

Containment Measures in Most Recent Incident: The containment measures taken in the most recent incident were {containment_measures_in_most_recent_incident}.

Data Breach Information

Most Sensitive Data Compromised: The most sensitive data compromised in a breach was {most_sensitive_data_compromised}.

Number of Records Exposed: The number of records exposed in the most significant breach was {number_of_records_exposed}.

Ransomware Information

Highest Ransom Demanded: The highest ransom demanded in a ransomware incident was {highest_ransom_demanded}.

Highest Ransom Paid: The highest ransom paid in a ransomware incident was {highest_ransom_paid}.

Regulatory Compliance

Highest Fine Imposed: The highest fine imposed for a regulatory violation was {highest_fine_imposed}.

Most Significant Legal Action: The most significant legal action taken for a regulatory violation was {most_significant_legal_action}.

Lessons Learned and Recommendations

Most Significant Lesson Learned: The most significant lesson learned from past incidents was {most_significant_lesson_learned}.

Most Significant Recommendation Implemented: The most significant recommendation implemented to improve cybersecurity was {most_significant_recommendation_implemented}.

References

Most Recent Source: The most recent source of information about an incident is {most_recent_source}.

Most Recent URL for Additional Resources: The most recent URL for additional resources on cybersecurity best practices is {most_recent_url}.

Investigation Status

Current Status of Most Recent Investigation: The current status of the most recent investigation is {current_status_of_most_recent_investigation}.

Stakeholder and Customer Advisories

Most Recent Stakeholder Advisory: The most recent stakeholder advisory issued was {most_recent_stakeholder_advisory}.

Most Recent Customer Advisory: The most recent customer advisory issued was {most_recent_customer_advisory}.

Initial Access Broker

Most Recent Entry Point: The most recent entry point used by an initial access broker was {most_recent_entry_point}.

Most Recent Reconnaissance Period: The most recent reconnaissance period for an incident was {most_recent_reconnaissance_period}.

Post-Incident Analysis

Most Significant Root Cause: The most significant root cause identified in post-incident analysis was {most_significant_root_cause}.

Most Significant Corrective Action: The most significant corrective action taken based on post-incident analysis was {most_significant_corrective_action}.

What Do We Measure?

revertimgrevertimgrevertimgrevertimg
Incident
revertimgrevertimgrevertimgrevertimg
Finding
revertimgrevertimgrevertimgrevertimg
Grade
revertimgrevertimgrevertimgrevertimg
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 Security

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

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

Top LeftTop RightBottom LeftBottom Right
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.
Users Love Us Badge