Ethics Team (#287)

Co-authored-by: Ben Stephens <ben.stephens@deakin.edu.au>
Co-authored-by: ben-AI-cybersec <142491786+ben-AI-cybersec@users.noreply.github.com>

Author: Elijahjudd5

.vscode/settings.json

@@ -0,0 +1,105 @@
+---
+sidebar_position: 2
+---
+
+ Redback Dummy Data Generator – Implementation Guide
+
+A Python-based tool designed to generate realistic dummy data across multiple file formats for testing the Redback Asset Assessment Tool (AAT). The generated files include a mixture of public and synthetic sensitive information to simulate real-world data repositories.
+
+## Features
+
+- Supports multiple file types: CSV, JSON, TXT, DOCX, and PDF
+
+- Sensitivity levels: Low, Medium, High, Mixed
+
+- Randomised file contents with realistic structure
+
+- Console UI for interactive use
+
+- Modular class-based architecture (DummyDataGenerator)
+
+- Error handling for PDF generation edge cases
+
+---
+
+## Setup Instructions
+
+1. Clone the Repository
+
+- git clone https://github.com/Redback-Operations/redback-ethics.git
+- cd redback-ethics/dummy_data_generator
+
+![Step 1 – Clone the Repository](./Photos/DumbyData1.png)
+
+This image shows the README file for the “Redback Dummy Data Generator” project, providing an overview of its features and detailed setup instructions, including cloning the repository, setting up a virtual environment, installing packages, and running the generator via a Python script.
+
+
+
+
+2. Navigate to the Project Folder
+
+- cd path/to/redback-ethics/dummy_data_generator
+
+![Step 2 – Navigate to the Project Folder](./Photos/DumbyData2.png)
+
+This image demonstrates how to clone the redback-ethics GitHub repository and navigate into the dummy_data_generator directory to begin setting up the project.
+
+
+
+3. Create and Activate a Virtual Environment
+
+- python3 -m venv .venv
+- source .venv/bin/activate
+
+![Step 3 – Create and Activate a Virtual Environment](./Photos/DumbyData3.png)
+
+- On Windows: .venv\Scripts\activate
+
+This image shows the creation and activation of a Python virtual environment using python3 -m venv .venv and source .venv/bin/activate, preparing an isolated workspace for the project.
+
+
+
+4. Install Required Packages
+
+- pip install -r requirements.txt
+
+![Step 4 – Install Required Packages](./Photos/DumbyData4.png)
+
+This image shows the installation of required Python packages using pip install -r requirements.txt, ensuring all dependencies for the project are set up in the virtual environment.
+
+
+5. Run the Generator
+
+- python main.py
+
+![Step 5 – Run the Generator](./Photos/DumbyData5.png)
+
+The generator will launch a console UI that prompts you to choose:
+
+- Output directory
+
+- Number of files
+
+- Sensitivity level
+
+- File types to generate
+
+This image shows the execution of python main.py, which launches the Redback Dummy Data Generator’s console interface, prompting the user to specify a directory to save the generated synthetic test files.
+
+---
+
+
+## Output
+
+The generated synthetic test files (e.g. .csv, .json, .txt, .pdf, .docx) will be saved in the directory you specified. These are designed to reflect realistic structures and sensitivity distributions.
+
+-  Notes
+
+Activate your virtual environment each time before running the generator (source .venv/bin/activate)
+
+You can extend or modify the generation logic by editing main.py or extending the DummyDataGenerator class
+
+If you add new packages, don’t forget to update requirements.txt
+
+For troubleshooting, enhancements, or support, contact the Redback Ethics team or open an issue in the GitHub repository.
+

docs/cybersecurity/Ethics Team/Asset Assessment Project/Implementation of Dummy Data Generator.md

@@ -0,0 +1,99 @@
+---
+sidebar_position: 1
+---
+# Project Overview
+
+## Asset Assessment 
+
+- **Project Name:** Redback Asset Assessment  
+- **Purpose:**  
+  Introduce stakeholders and new developers to the Redback Asset Assessment, its goals, scope, the problem it solves, and its classification system for sensitive data.
+
+---
+
+## Problem Statement
+
+Before detailing the goals and structure of this project, it’s essential to define the core issue that the Redback Asset Assessment is designed to address:
+
+> Sensitive data breaches remain one of the most common and damaging threats to organizations.
+
+Such breaches can result in:
+- Identity theft,
+- Customer harm,
+- Legal and regulatory penalties,
+- Loss of trust and reputation.
+
+Common causes include:
+- Data stored without proper classification,
+- Information retained beyond legal timeframes,
+- Exposure of data during development or system integration,
+- Lack of encryption or access control.
+
+---
+
+## Project Goals
+
+The **Redback Asset Assessment** is designed to proactively combat these issues by automating the **classification** and **flagging** of sensitive data. This enables guided responses and automated actions, ensuring compliance with modern privacy standards.
+
+This project aims to help Redback:
+- Detect exposure risks early in the development lifecycle.
+- Classify sensitive data by urgency, legal impact, and business sensitivity.
+- Comply with key data privacy standards (e.g., **APP 11**, **Privacy Act 1988**).
+- Automate DevOps-driven mitigation workflows for compliance enforcement.
+
+---
+
+## Scope
+
+The tool scans:
+- **Code repositories**
+- **Documents**
+- **Databases**
+
+It locates **text** and **file-based sensitive data**, classifying it by:
+- **Data Type:** PII, PHI, NPI, etc.
+- **Storage Format:** JSON, TXT, MP4, etc.
+- **Lifecycle Status:** Retained vs. Expired
+- **Risk Level:** Low, Medium, High
+
+**Integration targets** include CI/CD pipelines, file systems, and enterprise systems, providing early detection and containment of privacy risks.
+
+---
+
+## Key Features
+
+- **Data Classification:** Supports types like PII, PHI, NPI, biometric, and more.
+- **Risk Levels:** Flags data by sensitivity level (Low/Medium/High) and recommends controls.
+- **DevOps Integration:** CI/CD pipelines, developer tools, SIEMs, etc.
+- **Compliance Monitoring:** Detects expired, exposed, or misclassified data.
+
+---
+
+## Target Users
+
+| Role              | Use Case                                          |
+|-------------------|--------------------------------------------------|
+| Development Teams | Prevent data leaks in code and builds            |
+| Security Analysts | Proactively identify data breach risks           |
+| Compliance Officers | Validate regulatory compliance and flag issues |
+
+---
+
+## Example Use Cases
+
+- Preventing sensitive data from being pushed to public repositories.
+- Detecting unencrypted medical or financial records.
+- Automatically deleting records beyond their retention period.
+- Alerting when real production data is used in test environments.
+
+---
+
+## Summary
+
+The **Redback Asset Assessment** revolutionizes data protection by making data sensitivity detection:
+- **Automatic**
+- **Proactive**
+- **Enforceable**
+
+It is designed for **seamless integration** with existing company workflows to reduce data breach risks and ensure compliance as the company scales and evolves.
+

docs/cybersecurity/Ethics Team/Asset Assessment Project/Photos/DumbyData1.png

@@ -0,0 +1,8 @@
+{
+    "label": "Asset Assessment Project",
+    "position": 2,
+    "link": {
+      "type": "generated-index",
+      "description": "Documents relating to the Asset Assessment Project."
+    }
+  }

docs/cybersecurity/Ethics Team/Asset Assessment Project/Photos/DumbyData2.png

@@ -0,0 +1,86 @@
+---
+sidebar_position: 1
+---
+# Project Overview
+
+## Cross-Team Legal Advice
+
+## Purpose
+
+Inform Redback Operation team members from all projects about the legal requirements related to the work they are undertaking, as well as provide unofficial legal advice regarding whether or not they are acting in line with said requirements.
+
+---
+
+## Problem Statement
+
+A lack of awareness of the relevant legal requirements by members of Redback Operations results in a greater risk of data being mishandled and misconduct within the team's work.
+
+This lack of awareness could result in:
+
+- Breaches of Privacy laws  
+- Breaches of user’s rights  
+- Increased risk of negligence  
+- Extreme damage to reputation  
+
+Common causes include:
+
+- Lack of legal knowledge  
+- General lack of law background  
+- Lack of real-world experience  
+
+---
+
+## Project Goals
+
+The Cross-Team Legal Advice project is designed to:
+
+- Educate members of Redback Operations
+- Provide unofficial legal advice to teams on their compliance with relevant legal requirements
+- Inform members about legal obligations and how to be more compliant
+
+The project aims to help Redback:
+
+- Comply with relevant legal requirements, including but not limited to:
+  - The *Privacy Act 1988 (Cth)*
+  - The *Australian Consumer Law* (Schedule 2 of the *Competition and Consumer Act 2010 (Cth)*)
+- Ensure members are aware of certain legal requirements
+
+---
+
+## Scope
+
+**Tools Used:**
+
+- **Google Forms:** Multiple choice questions regarding legal issues and optional short answer fields for additional legal questions
+- **Google Sheets:** Accessed by Cross-Team Legal Advice members to log responses from the form
+- **Google Docs:** Used to store and manage the questions for the form
+- **FAQ Document:** (To be created in Semester 2) Will contain frequently asked questions and common legal issues, and will be continuously updated
+
+---
+
+## Key Features
+
+- **Google Forms:** Used by Redback team members to seek legal advice
+- **Google Sheets:** Used by Cross-Team Legal Advice members to track form responses
+- **FAQ Document (Semester 2):** Lists frequent or relevant legal questions/issues and provides guidance; will be regularly updated
+
+---
+
+## Target Users
+
+| Role                       | Use Case                                            |
+|---------------------------|-----------------------------------------------------|
+| All Redback Operations team members | Seek legal advice regarding the work they are undertaking |
+
+---
+
+## Example Use Cases
+
+- A member of another team wants to ensure compliance with the Privacy Act
+- A member of another team has a question about the Australian Consumer Law
+
+---
+
+## Summary
+
+The Cross-Team Legal Advice project serves as both a compliance aid and an educational tool for the Redback Operations team. It is designed to improve legal awareness and reduce the risk of misconduct by ensuring that unofficial legal guidance is delivered effectively and efficiently across teams.