Page cover

Commonwealth Bank

  • Completed a job simulation involving the role of a cybersecurity generalist, specializing in fraud detection and prevention for Commonwealth Bank's Cybersecurity team.

  • Developed skills in building data visualization dashboards using Splunk to uncover patterns and insights in historical customer data, aiding in fraud detection.

  • Demonstrated the ability to respond effectively to cybersecurity incidents, including notifying relevant teams, collecting information, containing and stopping attacks, and aiding in recovery efforts.

  • Enhanced security awareness expertise by designing infographics promoting best practices for secure password management, following Australian Cybersecurity Centre advice.

  • Acquired practical experience in penetration testing, assessing the security of web applications, identifying vulnerabilities, and providing recommendations for remediation to bolster cybersecurity defenses.

Task 1 - Data Analysis

  1. Imported “prepared_data” file into Splunk.

  2. File analysis using the “Interesting Fields” section in Splunk.

  3. Dashboard creation to include the following charts/tables:

    1. Count by Category, Fraudulent transactions, Age and Merchant.

      1. sourcetype="fraud_detection.csv" | top category

      2. sourcetype="fraud_detection.csv" | top fraud

      3. sourcetype="fraud_detection.csv" | top age

      4. sourcetype="fraud_detection.csv" | top merchant

    2. Fraud detected by Age, Category, Step (month) and Gender.

      1. sourcetype="fraud_detection.csv" fraud="1" | stats count values(fraud) by age

      2. sourcetype="fraud_detection.csv" fraud="1" | stats count values(fraud) by category

      3. sourcetype="fraud_detection.csv" fraud="1" | stats count values(fraud) by step

      4. sourcetype="fraud_detection.csv" fraud="1" | stats count values(fraud) by gender

  4. Provide responses to

    1. Which gender performed the most fraudulent activities and in what category?

      1. sourcetype="fraud_detection.csv" fraud="1" | stats count values(fraud) by category, gender

      2. Trellis > Use Trellis Layout > Split By gender

    2. Which age group performed the most fraudulent activities and to what merchant?

      1. sourcetype="fraud_detection.csv" fraud="1" | stats count values(fraud) by merchant, age

      2. Trellis > Use Trellis Layout > Split By age

  5. Exported dashboard as a PDF.

Task 2 - Incident Response

Resources

Study the links in the Resources to learn how to provide solutions to the following questions.

1. What kind of attack has happened and why do you think so?

This is a phishing attack that has potentially escalated into a ransomware attack:

  • Phishing: The email from "HR" was designed to trick employees into entering their credentials into a fake portal, which likely allowed the attacker to capture their login information.

  • Ransomware: The report of colleagues unable to open Word documents and file-shares suggests a malware infection. Phishing emails often serve as the entry point for ransomware to infiltrate systems, encrypt files, and block access.

2. As a cyber security analyst, what are the next steps to take? List all that apply.

  1. Isolate affected systems: Immediately isolate any compromised machines from the network to prevent the spread of ransomware or other malware.

  2. Identify the scope: Determine the extent of the attack by identifying who received the phishing email and whether any systems were successfully compromised.

  3. Reset compromised credentials: Instruct all affected employees to reset their login credentials, especially if they entered information on the fake website.

  4. Check for malware presence: Conduct a thorough scan of affected systems to check for any malicious software or ransomware.

  5. Activate incident response: Notify upper management and activate the organization's incident response team.

3. How would you contain, resolve and recover from this incident? List all answers that apply.

Containment:

  • Quarantine infected systems and networks.

  • Block access to external communication for potentially compromised systems.

  • Shut down unnecessary services and ensure that malicious emails are blocked at the server level.

Resolution:

  • Analyze the phishing emails and attachments for further clues on the malware.

  • Restore systems from backups, ensuring that backups themselves are free of malware.

  • Apply patches to known vulnerabilities in the systems.

Recovery:

  • Remove malware by cleaning infected systems using malware removal tools.

  • Restore files from backups, ensuring backups are recent and verified safe.

  • Monitor systems for abnormal activity to prevent further exploitation.

4. What activities should be performed post-incident?

  1. Incident report: Document the entire incident, including timeline, actions taken, and the outcome.

  2. Review and improve security measures: Conduct a review of current security practices and implement improvements such as:

    • Enhanced email filtering and anti-phishing tools.

    • Multi-factor authentication (MFA) for sensitive systems.

    • Employee security training on phishing and other cyber threats.

  3. Conduct a post-incident review: Analyze the attack's impact, the effectiveness of the response, and where improvements can be made.

  4. Monitor systems: Keep monitoring for any additional suspicious activity to ensure no further threats remain.

  5. Update disaster recovery plans: Adjust plans based on lessons learned to ensure faster, more effective responses in the future.

Task 3 - Penetration testing

  1. Go to HackThisSite and create an account.

  2. On the left-hand side, Click on the “Challenges” section and select “Basic” (or click here).

  3. Complete all levels from Basic Level 1 to 11.

  4. After completing all levels, document a Penetration Testing Report that includes an executive summary, scope of web application tested, vulnerability description and key findings for each level, as well as recommendations on how to better secure the web application.

  5. Additional resources are provided in the Resources for help, which will be especially useful if you have no prior experience with pentesting.

Resources:


Last updated