Neighbourly.co.nz Breach Incident Score: Analysis & Impact (NEI1767441726)

In this Rankiteo incident briefing, we review the Neighbourly.co.nz breach identified under incident ID NEI1767441726.

The analysis begins with a detailed overview of Neighbourly.co.nz's information like the linkedin page: https://www.linkedin.com/company/neighbourly-co-nz, the number of followers: 0, the industry type: Online Audio and Video Media and the number of employees: 823 employees

After the initial compromise, the video explains how Rankiteo's incident engine converts technical details into a normalized incident score. The incident score before the incident was 834 and after the incident was 808 with a difference of -26 which is could be a good indicator of the severity and impact of the incident.

In the next step of the video, we will analyze in more details the incident and the impact it had on Neighbourly.co.nz and their customers.

Neighbourly recently reported "Neighbourly Data Breach", a noteworthy cybersecurity incident.

Unauthorised access to certain categories of data held by Neighbourly, including registered users’ names, email addresses, GPS coordinates, public forum posts, private member communications, publicly advertised events, and business addresses.

The disruption is felt across the environment, affecting Neighbourly platform, and exposing Registered users’ names, email addresses, GPS coordinates, public forum posts, private member communications, publicly advertised events, business addresses.

In response, moved swiftly to contain the threat with measures like Breach quickly contained, and began remediation that includes Issue addressed; platform restored and secured, while recovery efforts such as Website and services fully operational continue, and stakeholders are being briefed through Public apology, user advisories, and updates during investigation.

The case underscores how Completed, teams are taking away lessons such as Need for more robust processes to prevent future breaches; importance of user awareness and security measures like two-factor authentication, and recommending next steps like Enable two-factor authentication where available, Remain alert to phishing attempts (unusual calls, emails, or texts) and Avoid clicking links in emails; type web addresses directly, with advisories going out to stakeholders covering Advisories issued to staff and members on security best practices.

Finally, we try to match the incident with the MITRE ATT&CK framework to see if there is any correlation between the incident and the MITRE ATT&CK framework.

The MITRE ATT&CK framework is a knowledge base of techniques and sub-techniques that are used to describe the tactics and procedures of cyber adversaries. It is a powerful tool for understanding the threat landscape and for developing effective defense strategies.

Rankiteo's analysis has identified several MITRE ATT&CK tactics and techniques associated with this incident, each with varying levels of confidence based on available evidence. Under the Initial Access tactic, the analysis identified Valid Accounts (T1078) with moderate to high confidence (70%), with evidence including unauthorised access to certain categories of data, and vulnerability leading to the breach has been addressed and Exploit Public-Facing Application (T1190) with moderate confidence (60%), with evidence including neighbourly platform affected, and issue addressed; platform secured. Under the Credential Access tactic, the analysis identified Unsecured Credentials (T1552) with moderate confidence (50%), supported by evidence indicating passwords were not accessed (implies other credentials may have been). Under the Collection tactic, the analysis identified Data from Information Repositories (T1213) with high confidence (90%), supported by evidence indicating names, email addresses, GPS coordinates, private member communications accessed. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with moderate to high confidence (80%), with evidence including unauthorised access to sensitive user information, and data breach involving exposure of PII and Transfer Data to Cloud Account (T1537) with moderate confidence (50%), supported by evidence indicating no direct evidence, but common in breaches of this nature. Under the Impact tactic, the analysis identified Data Destruction (T1485) with lower confidence (30%), supported by evidence indicating no evidence of data destruction, but included due to breach impact, Data Encrypted for Impact (T1486) with lower confidence (10%), supported by evidence indicating no evidence of ransomware or encryption, and Data Manipulation: Stored Data Manipulation (T1565.001) with lower confidence (40%), supported by evidence indicating potential misuse of stolen data (court injunction sought). These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.