The Lion Brewery Company Cyber Security Posture
lionbrewery.comThe Lion Brewery was built in 1905 as the Luzerne County Brewing Company. We brew the Lionshead and Stegmaier beers, Lionshead Root Beer, and in the past have brewed Gibbons beer and various other brands. In addition to our brands, the brewery serves the industry as a contract brewer and has brewing, keg, bottling and canning capabilities, a 75,000 sq ft. warehouse and a 400 barrel kettle. The Brewery operates the bottling line 24 hours a day, 5 days per week and the brew house and can line 24 hours per day, 7 days per week. Since 2010, the brewery has invested over $20 million into the brewery, which also includes a new can line, bottle filler, and keg filler, and in May of 2017, added a new high speed labeler with paper and pressure sensitive label capabilities and a split deck pasteurizer that can run with or without pasteurization.
LB Company Details
thelionbrewery
80 employees
425
none
Food & Beverages
lionbrewery.com
Scan still pending
THE_8624575
In-progress
LB Risk Score (AI oriented)Between 200 and 800
This score is AI-generated and less favored by cyber insurers, who prefer the TPRM score.
LB Global Score.png)
The Lion Brewery Company Scoring based on AI Models
| Model Name | Date | Description | Current Score Difference | Score |
|---|---|---|---|---|
| AVERAGE-Industry | 03-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 200 and 800 |
The Lion Brewery Company Cyber Security News & History
| Entity | Type | Severity | Impact | Seen | Url ID | Details | View |
|---|---|---|---|---|---|---|---|
| The Lion Brewery | Ransomware | 85 | 2 | 06/2020 | THE0285123 | Link | |
Rankiteo Explanation : Attack limited on finance or reputationDescription: Lion experienced a ransomware attack. The hackers seized control of data or systems and then demanded a ransom that often runs to millions. The brewing giant and bar owner took systems offline as a precaution which affected both manufacturing and customer orders. Supplies ran low at a number of outlets. | |||||||
The Lion Brewery Company Subsidiaries
The Lion Brewery was built in 1905 as the Luzerne County Brewing Company. We brew the Lionshead and Stegmaier beers, Lionshead Root Beer, and in the past have brewed Gibbons beer and various other brands. In addition to our brands, the brewery serves the industry as a contract brewer and has brewing, keg, bottling and canning capabilities, a 75,000 sq ft. warehouse and a 400 barrel kettle. The Brewery operates the bottling line 24 hours a day, 5 days per week and the brew house and can line 24 hours per day, 7 days per week. Since 2010, the brewery has invested over $20 million into the brewery, which also includes a new can line, bottle filler, and keg filler, and in May of 2017, added a new high speed labeler with paper and pressure sensitive label capabilities and a split deck pasteurizer that can run with or without pasteurization.
Access Data Using Our API
Get company history
Rapid.png)
LB Cyber Security News
Pandemic or not, cyber risk still a big threat for breweries
From the initial shutdowns, to limited capacity and sanitation requirements, COVID-19 has created challenges for breweries nationwide.
Lion Brewery reinforces data security and integrity with ISO 27001:2022
Lion Brewery (Ceylon) PLC was accredited with the internationally recognised standard – ISO 27001:2022 certification.
Lion serves up stronger data security to keep its supply chain moving
Lion's partnership with Microsoft has enabled the company to strengthen its data governance and information security capabilities in key areas ...
Hackers post evidence they have beer giant Lion's confidential files
The hackers that attacked the Australian beverage giant are threatening to auction or publish sensitive information on the dark web unless ...
Cyberattack Forces Brewery Shutdown at Molson Coors
Molson Coors says said a cyberattack attack has caused delays and disruptions to parts of the business handling brewery operations, ...
Don't pay the ransom, mate. Don't even fix a price, say Australia's cyber security bods
Most online attacks could be easily avoided by following basic cyber security advice, Australia's national cyber security bureau has said.
Party poopers: Cyber attack at Lion brewery disrupts supply of beer
Thoughtless cyber-criminals put Kiwis' access to beer at risk on the first day of level 1, and the threat continues.
Ransomware attack shuts down Kirin’s Lion Co breweries
Kirin's Australian brewing unit, Lion Co, has warned of beer shortages after a cyber attack halted production at its breweries. June 12, 2020.
Molson Coors says cyberattack disrupted beer brewing
Molson Coors confirmed in a regulatory filing on Thursday that it suffered a cyberattack that disrupted its beer production, and it may not be out of the woods ...
LB Similar Companies
Levy Restaurants
Discover the Levy Difference Passion is a great gift, and we have a lot of gifted people. Our contagious enthusiasm stimulates minds, engages senses and touches hearts. Each guest is greeted with a warm welcome, served with pride and extended a heartfelt invitation to return. Experience legendary
Bon Preu S.A.U.
El Grup Bon Preu és una empresa catalana referent en el sector de l’alimentació, compromesa amb els ciutadans i el territori. El seu propòsit és facilitar el dia a dia dels seus clients, oferint serveis bàsics i quotidians en l’alimentació amb Bonpreu i Esclat i BonpreuEsclat online, car
Cacau Show
We are passionate for chocolate. We can translate it into the quality of our products, and the way we make them become true. Everything we create has a handcrafted aspect, a human touch. That is because, for Cacau Show, each chocolate is a caress expression, a real moment of happiness. For us, ch
Restaurant Associates
Restaurant Associates is a chef-driven hospitality company known for elevating culinary and brand experiences for our clients and guests across the country. Our lines of business include restaurants, workplace, higher education, cultural centers, and event catering. Our teams are built on our cul
Parmalat Group
The Parmalat Group is a food-industry group with a multinational strategy that seeks to increase the well-being of consumers throughout the world. The ultimate purpose of the Group is to create value for its shareholders while adhering to ethical principles of business conduct, to perform a useful s
Frequently Asked Questions (FAQ) on Cybersecurity Incidents
LB CyberSecurity History Information
Total Incidents: According to Rankiteo, LB 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 The Lion Brewery was built in 1905 as the Luzerne County Brewing Company. We brew the Lionshead and Stegmaier beers, Lionshead Root Beer, and in the past have brewed Gibbons beer and various other brands. In addition to our brands, the brewery serves the industry as a contract brewer and has brewing, keg, bottling and canning capabilities, a 75,000 sq ft. warehouse and a 400 barrel kettle. The Brewery operates the bottling line 24 hours a day, 5 days per week and the brew house and can line 24 hours per day, 7 days per week. Since 2010, the brewery has invested over $20 million into the brewery, which also includes a new can line, bottle filler, and keg filler, and in May of 2017, added a new high speed labeler with paper and pressure sensitive label capabilities and a split deck pasteurizer that can run with or without pasteurization..
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
Incident 1: Ransomware Attack
Regulations Violated: {Regulations_Violated}
Fines Imposed: {Fines_Imposed}
Legal Actions: {Legal_Actions}
Regulatory Notifications: {Regulatory_Notifications}
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
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?
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:
Identify exposed access points, detect misconfigured SSL certificates, and uncover vulnerabilities across the network infrastructure.
Gain visibility into the software components used within an organization to detect vulnerabilities, manage risk, and ensure supply chain security.
Monitor and manage all IT assets and their configurations to ensure accurate, real-time visibility across the company's technology environment.
Leverage real-time insights on active threats, malware campaigns, and emerging vulnerabilities to proactively defend against evolving cyberattacks.
