First Financial Credit Union Company Cyber Security Posture
ffnm.orgFirst Financial Credit Union was formed in 1937 by ten members of the telephone company here in New Mexico. In the early 80s, the breakup of the Bell System occurred. With the breakup came a period of downsizing in the state. At this point, First Financial chose to pursue additional fields of membership so as to not be impacted by the changes in its environment. Since that time, the credit union has grown to serve the employees of 200 companies. Anyone who is interested in joining a credit union can join First Financial Credit Union. Send us an e-mail or give us a call at (505) 766-5600 (or 1-800-342-8298) and find out how you can become a member today.
FFCU Company Details
first-financial-credit-union
199 employees
1449.0
522
Banking
ffnm.org
Scan still pending
FIR_1347549
In-progress
FFCU Risk Score (AI oriented)Between 800 and 900
This score is AI-generated and less favored by cyber insurers, who prefer the TPRM score.
FFCU Global Score.png)
First Financial Credit Union 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 800 and 900 |
First Financial Credit Union Company Cyber Security News & History
| Entity | Type | Severity | Impact | Seen | Url ID | Details | View |
|---|---|---|---|---|---|---|---|
| First Financial Credit Union | Breach | 100 | 5 | 05/2022 | FIR14326522 | Link | |
Rankiteo Explanation : Attack threatening the organization's existenceDescription: First Financial Credit Union suffered a data breach incident after an unauthorized party accessed some of portions of the FFCU computer network. The compromised information included membersโ names, addresses, Social Security numbers, driverโs license numbers, government ID numbers, bank account information and credit card information. FFCU investigated the incident with third-party experts and notified the impacted individuals. | |||||||
First Financial Credit Union Company Subsidiaries
First Financial Credit Union was formed in 1937 by ten members of the telephone company here in New Mexico. In the early 80s, the breakup of the Bell System occurred. With the breakup came a period of downsizing in the state. At this point, First Financial chose to pursue additional fields of membership so as to not be impacted by the changes in its environment. Since that time, the credit union has grown to serve the employees of 200 companies. Anyone who is interested in joining a credit union can join First Financial Credit Union. Send us an e-mail or give us a call at (505) 766-5600 (or 1-800-342-8298) and find out how you can become a member today.
Access Data Using Our API
Get company history
Rapid.png)
FFCU Cyber Security News
Hackers Hit Nebraskaโs Liberty First Credit Union
The $478 million Liberty First Credit Union in Lincoln, Neb., reported a data breach that may have affected 52,496 persons.
Power Financial Credit Union Stands Strong Against Rising Cybersecurity Threats and is Leading an Effort to Educate Its Community During Cybersecurity Awareness Month
In 2023, reports of financial fraud and cybercrime surged, with nearly 75% of banks reporting a rise in cyberattacks. Cyberattacks happen everyย ...
SchoolsFirst, Californiaโs biggest credit union, looks to next-generation growth
Organization: SchoolsFirst Federal Credit Union has more than 30 billion in assets and serves 1.4 million school employees and their families.
Massive data breach at federal credit union exposes 240K members
SRP Federal Credit Union, a South Carolina-based financial institution, had a major data breach impacting more than 240,000 people.
Financial regulatory agencies are sunsetting a tool to assess cyber risks
The Federal Financial Institutions Examination Council revealed last month that the Cybersecurity Assessment Tool will go dark Aug. 31, 2025, aย ...
Identity Theft and Credit Card Fraud Statistics for 2025
Identity theft rises in 2025: 365,758 cases of identity theft were reported in the first quarter of 2025, up over 70,000 from the previousย ...
12 Best Online Banks of 2025
NerdWallet's picks include banks, nonbank financial institutions and one credit union with strong overall ratings and mobile features.
Historical Timeline
Review a historic timeline nothing the history of credit unions and the evoluation of the financial and regulatory system they operate in.
Cybersecurity Expert Shares Tips for Dublin-Based Patelco Credit Union Customers After Ransomware Attack
A cybersecurity expert gives practical advice for folks affected by the data breach at one of the Bay Area's largest credit unions.
FFCU Similar Companies
Bank Pekao S.A.
Bank Pekao S.A. powstaล w 1929 roku. Obecnie jesteลmy jednฤ z najwiฤkszych instytucji finansowych w regionie Europy ลrodkowo-Wschodniej i drugim, pod wzglฤdem wielkoลci bankiem w Polsce z ok. 230 mld zล aktywรณw. Dziฤki znaczฤ cej sieci oddziaลรณw obsลugujemy ponad 5,7 mln klientรณw. Jako wiodฤ cy bank k
Kotak Mahindra Bank
About Kotak Mahindra Group: Established in 1985, the Kotak Mahindra Group is one of Indiaโs leading financial services conglomerates. In February 2003, Kotak Mahindra Finance Ltd. (KMFL), the Groupโs flagship company, received a banking license from the Reserve Bank of India (RBI). With this, KMF
Central Bank of Nigeria
The mandate of the Central Bank of Nigeria (CBN) is derived from the 1958 Act of Parliament, as amended in 1991, 1993,1997,1998,1999 and 2007. The CBN Act of 2007 of the Federal Republic of Nigeria charges the Bank with the overall control and administration of the monetary and financial sector pol
U.S. Bank
At U.S. Bank, we help millions of clients achieve their goals with a balance of best-in-class technology and human expertise tailored to individual needs. As the fifth-largest commercial bank in the United States, weโve built a reputation for strength and stability across a diversified mix of busine
ANZ
ANZ has a proud heritage of more than 180 years. Our purpose is to shape a world where people and communities thrive. That is why we strive to create a balanced, sustainable economy in which everyone can take part and build a better life. We employ more than 50,000 people and have our global headq
ABN AMRO Bank N.V.
Welkom op het LinkedIn-account van ABN AMRO. We staan 24/7 klaar om jouw vragen te beantwoorden. Onze taak is altijd om de klant te ondersteunen op het moment dat het er echt op aankomt. Dat is onze verantwoordelijkheid. Dat maakt ons relevant. En wat er vandaag de dag toe doet voor de klant is de
Frequently Asked Questions (FAQ) on Cybersecurity Incidents
FFCU CyberSecurity History Information
Total Incidents: According to Rankiteo, FFCU has faced 1 incidents in the past.
Incident Types: The types of cybersecurity incidents that have occurred include ['Breach'].
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 First Financial Credit Union was formed in 1937 by ten members of the telephone company here in New Mexico. In the early 80s, the breakup of the Bell System occurred. With the breakup came a period of downsizing in the state. At this point, First Financial chose to pursue additional fields of membership so as to not be impacted by the changes in its environment. Since that time, the credit union has grown to serve the employees of 200 companies. Anyone who is interested in joining a credit union can join First Financial Credit Union. Send us an e-mail or give us a call at (505) 766-5600 (or 1-800-342-8298) and find out how you can become a member today..
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.
