Ravn Alaska Company Cyber Security Posture

ravnalaska.com

For decades, our airlines have been connecting some of the Last Frontierโ€™s most famous destinations, including Anchorage, Fairbanks, Bethel, Cordova, Homer, Valdez, Kenai, Kodiak and beyond. Ravn Alaska proudly offers scheduled service to more than 100 communities throughout the state. Our team of professionals on the ground and in the air has the history and experience to offer the highest level of customer satisfaction today โ€” and for the future. We offer service for passenger groups and odd-sized cargo up to 6,000 pounds, and have charter authority for anywhere in our great state, Canada and the Lower 48. Visit Ravn Alaska on the web at www.flyravn.com for flight schedules and more. #ravnalaska #alaskanspirit #aviation

Ravn Alaska Company Details

Linkedin ID:

ravn-alaska

Employees number:

221 employees

Number of followers:

6416

NAICS:

481

Industry Type:

Airlines and Aviation

Homepage:

ravnalaska.com

IP Addresses:

Scan still pending

Company ID:

RAV_4321009

Scan Status:

In-progress

AI scoreRavn Alaska Risk Score (AI oriented)

Between 900 and 1000

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

globalscoreRavn Alaska Global Score
blurone
Ailogo

Ravn Alaska 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 900 and 1000

Ravn Alaska Company Cyber Security News & History

Past Incidents
1
Attack Types
1
EntityTypeSeverityImpactSeenUrl IDDetailsView
Ravn AlaskaCyber Attack60212/2019RAV2571523Link
Rankiteo Explanation :
Attack limited on finance or reputation

Description: At least a dozen RavnAir flights in Alaska were canceled following what the company described as a malicious cyber attack on its computer network. The cancellations hit at the peak of holiday travel in Alaska, with schools out and many families traveling in the state or Outside. The company said in a written statement that the cyber attack forced them to disconnect their Dash 8 maintenance system and its back-up. It wasnโ€™t immediately clear which routes had been canceled.

Ravn Alaska Company Subsidiaries

SubsidiaryImage

For decades, our airlines have been connecting some of the Last Frontierโ€™s most famous destinations, including Anchorage, Fairbanks, Bethel, Cordova, Homer, Valdez, Kenai, Kodiak and beyond. Ravn Alaska proudly offers scheduled service to more than 100 communities throughout the state. Our team of professionals on the ground and in the air has the history and experience to offer the highest level of customer satisfaction today โ€” and for the future. We offer service for passenger groups and odd-sized cargo up to 6,000 pounds, and have charter authority for anywhere in our great state, Canada and the Lower 48. Visit Ravn Alaska on the web at www.flyravn.com for flight schedules and more. #ravnalaska #alaskanspirit #aviation

Loading...

Access Data Using Our API

SubsidiaryImage

Get company history

curl -i -X GET 'https://api.rankiteo.com/underwriter-getcompany-history?linkedin_id=ravn-alaska' -H 'apikey: YOUR_API_KEY_HERE'
newsone

Ravn Alaska Cyber Security News

2019-12-21T08:00:00.000Z
UPDATE: Cyber attack on RavnAir forces cancellation of Alaska Dash 8 service

RavnAir Group says a cyber attack has forced the company to cancel Ravn Air Alaska Dash 8 flights Saturday, with additional cancellationsย ...

2019-12-23T08:00:00.000Z
More RavnAir flights canceled after cyber attack

RavnAir continued to cancel some flights Monday, three days after what the company described as a malicious cyber attack on its computerย ...

2020-01-14T08:00:00.000Z
Impact of Cyber Attacks on RavnAir More Damaging Than First Thought; Flights May Be Grounded for a Month

The impact of cyber attacks is often greater than initial evaluations indicate. The mid-December cyber attack on RavnAir Group forced atย ...

2019-12-21T08:00:00.000Z
RavnAir Group Experiences Cyber Attack On Dash 8 Aircraft; Unalaska Flights Impacted

RavnAir Group announced today it experienced a "malicious cyber attack" on the company's IT network on Friday, impacting travel to and fromย ...

2018-10-04T07:00:00.000Z
Ravn Air Group to Buy Rival PenAir Out of Bankruptcy

An affiliate of Alaskan regional airline Ravn Air Group Inc. won a bankruptcy auction for rival PenAir with a $12.3 million offer.

2019-12-30T08:00:00.000Z
Travel Continues To Be Impacted After RavnAir Group Experiences Cyber Attack On Dash 8 Aircraft

Ravn announced it experienced a "malicious cyber attack" on the company's IT network on Dec. 20, impacting travel around the state. The attackย ...

similarCompanies

Ravn Alaska Similar Companies

GOL Linhas Aรฉreas

Somos a maior Companhia Aรฉrea do Paรญs e estamos entre as que mais crescem no mundo. A nossa histรณria comeรงou em 2001 e, desde entรฃo, somos responsรกveis por inovar o mercado da aviaรงรฃo no Brasil. Tudo isso graรงas ร  dedicaรงรฃo do nosso Time para garantir o nosso Valor nรบmero 1, a Seguranรงa, entregand

Aeromexico

Grupo Aeromexico, S.A.B. de C.V. is a holding company whose subsidiaries are engaged in commercial aviation and the promotion of passenger loyalty programs in Mexico. Aeromexico, Mexicoโ€™s global airline, operates more than 600 daily flights and has its main hub in Terminal 2 of the Mexico City Inter

KLM Royal Dutch Airlines

Welcome to our LinkedIn page! KLM was founded in 1919 and is the oldest airline in the world. With a vast network of European and intercontinental destinations, KLM can offer direct flights to major cities and economic centres all over the world. Through our LinkedIn account, we make sure you are

Servisair

Servisair is a leading global provider of aviation ground services delivering an integrated range of handling solutions across 128 locations. We form part of the Derichebourg Group, which also has divisions in Corporate and Environmental Services, collectively employing 47,000 staff throughout 30

Etihad

Marhaba! Welcome to Etihad Airways. We are proud to be the national airline of the UAE, flying to Abu Dhabi or onwards to over 70 global destinations. Our passion is to help people reach unmissable places, where theyโ€™ll make unforgettable memories. Our aim is to provide our passengers with unbeata

British Airways

As a global airline and the UKโ€™s flag carrier, British Airways has been flying its customers to where they need to be for more than 100 years. The airline connects Britain with the world and the world with Britain, operating one of the most extensive international scheduled airline route networks to

faq

Frequently Asked Questions (FAQ) on Cybersecurity Incidents

Ravn Alaska CyberSecurity History Information

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

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

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 For decades, our airlines have been connecting some of the Last Frontierโ€™s most famous destinations, including Anchorage, Fairbanks, Bethel, Cordova, Homer, Valdez, Kenai, Kodiak and beyond. Ravn Alaska proudly offers scheduled service to more than 100 communities throughout the state. Our team of professionals on the ground and in the air has the history and experience to offer the highest level of customer satisfaction today โ€” and for the future. We offer service for passenger groups and odd-sized cargo up to 6,000 pounds, and have charter authority for anywhere in our great state, Canada and the Lower 48. Visit Ravn Alaska on the web at www.flyravn.com for flight schedules and more. #ravnalaska #alaskanspirit #aviation.

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