Datasets:

Canstralian
/

Purple-Team-Cybersecurity-Dataset

@@ -7,124 +7,69 @@ size_categories:
 - 10K<n<100K
 ---
-# Purple Team Cybersecurity Dataset
-<!-- Hugging Face Metadata -->
-<!-- language: other -->
-<!-- license: mit -->
-<!-- datasets: canstralian/Purple-Team-Cybersecurity-Dataset -->
-<!-- Badges -->
-[![Build Status](https://img.shields.io/github/actions/workflow/status/canstralian/Purple-Team-Cybersecurity-Dataset/ci.yml)](https://github.com/canstralian/Purple-Team-Cybersecurity-Dataset/actions)
-[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
-## Dataset Card for Purple Team Cybersecurity Dataset
-**Dataset Summary**
-The Purple Team Cybersecurity Dataset is a comprehensive collection of events that amalgamates Red Team (attack) and Blue Team (defense) data. This dataset is designed to facilitate research and development in cybersecurity, particularly in understanding and analyzing the interplay between offensive and defensive strategies. It includes standardized fields such as timestamps, IP addresses, MITRE ATT&CK IDs, tool names, and event descriptions, providing a balanced perspective of both attack and defense scenarios.
-### Dataset Details
-**Dataset Description**
-This dataset was curated by combining existing Red Team and Blue Team datasets, normalizing and standardizing the data to ensure consistency. Each event is labeled as either “Attack” or “Defense” and is mapped to the corresponding MITRE ATT&CK tactics. The dataset aims to support cybersecurity research by providing a balanced and comprehensive view of both offensive and defensive events.
-- Curated by: Canstralian
-- Language(s) (NLP): Not Applicable
-- License: MIT License
-Dataset Sources
-- Repository: [https://github.com/canstralian/Purple-Team-Cybersecurity-Dataset](https://github.com/canstralian/Purple-Team-Cybersecurity-Dataset)
-- Paper: [More Information Needed (Optional)]
-Uses
-Direct Use
-This dataset is intended for use in cybersecurity research, including but not limited to:
-- Analyzing attack and defense patterns
-- Developing and testing intrusion detection systems
-- Training machine learning models for threat detection
-Out-of-Scope Use
-The dataset is not suitable for:
-   • Real-time threat monitoring in production environments
-   • Any application involving sensitive or personally identifiable information
 Dataset Structure
-The dataset comprises events with the following fields:
-   • Timestamp: ISO 8601 formatted date and time
-   • Source_IP: Validated source IP address
-   • Destination_IP: Validated destination IP address
-   • MITRE_ATT&CK_ID: Standardized MITRE ATT&CK technique ID
-   • Tool_Name: Standardized name of the tool used
-   • Event_Description: Detailed description of the event
-   • Event_Type: Label indicating “Attack” or “Defense”
-   • MITRE_Tactic: Mapped MITRE ATT&CK tactic
-Dataset Creation
-Curation Rationale
-The dataset was created to provide a balanced and comprehensive resource for cybersecurity professionals and researchers, enabling the study of both attack and defense mechanisms within a unified framework.
-Source Data
-Data Collection and Processing
-Data was collected from existing Red Team and Blue Team datasets, followed by normalization and standardization processes to ensure consistency across fields. Events were labeled and mapped to MITRE ATT&CK tactics to facilitate structured analysis.
-Who are the source data producers?
-The original data was produced by various cybersecurity teams and organizations engaged in offensive and defensive security operations.
-Annotations
-Annotation process
-Events were labeled as “Attack” or “Defense” based on their origin and nature. Each event was mapped to the corresponding MITRE ATT&CK tactic using a predefined mapping.
-Who are the annotators?
-The annotation was performed by cybersecurity experts with experience in both offensive and defensive operations.
-Personal and Sensitive Information
-The dataset does not contain any personal or sensitive information. All IP addresses have been validated to ensure they do not correspond to real-world entities.
-Bias, Risks, and Limitations
-While efforts have been made to balance the dataset, there may still be inherent biases due to the nature of the source data. Users should be aware of these potential biases and exercise caution when applying the dataset to different contexts.
-Recommendations
-Users should be made aware of the risks, biases, and limitations of the dataset. More information needed for further recommendations.
 Citation
-BibTeX:
-[More Information Needed]
-APA:
-[More Information Needed]
-Glossary
-   • MITRE ATT&CK: A globally accessible knowledge base of adversary tactics and techniques based on real-world observations.
-More Information
-[More Information Needed]
-Dataset Card Authors
-**Author**: Canstralian
-- **GitHub**: [https://github.com/canstralian](https://github.com/canstralian)
-- **Hugging Face**: [https://huggingface.co/canstralian](https://huggingface.co/canstralian)
-Dataset Card Contact
-**Contact Information**: [Your Contact Information (email or other contact)]

 - 10K<n<100K
 ---
+Dataset Card for Purple Team Cybersecurity Dataset
+Dataset Summary
+The Purple Team Cybersecurity Dataset is a synthetic collection designed to simulate collaborative cybersecurity exercises, integrating offensive (Red Team) and defensive (Blue Team) strategies. It encompasses detailed records of attack events, defense responses, system logs, network traffic, and performance metrics. This dataset serves as a valuable resource for training, analysis, and enhancing organizational security postures.
 Dataset Structure
+The dataset is organized into the following primary components:
+	1.	Attack Events (Red Team)
+      •   event_id (INT): Unique identifier for each attack event.
+      •   timestamp (DATETIME): Date and time of the attack event.
+      •   attack_technique (STRING): MITRE ATT&CK technique used.
+      •   attack_category (STRING): Category of attack (e.g., Initial Access, Execution).
+      •   target_system (STRING): System or application targeted.
+      •   success_status (BOOLEAN): Indicates whether the attack was successful.
+	2.	Defense Responses (Blue Team)
+      •   response_id (INT): Unique identifier for each defense response.
+      •   event_id (INT): Foreign key linking to the attack event.
+      •   detection_time (DATETIME): Timestamp when the attack was detected.
+      •   response_time (DATETIME): Timestamp when the response was initiated.
+      •   detection_method (STRING): Method of detection (e.g., SIEM, IDS).
+      •   response_action (STRING): Action taken to mitigate the attack.
+      •   effectiveness (INT): Effectiveness score (1-10) of the response.
+	3.	System Logs
+      •   log_id (INT): Unique identifier for each log entry.
+      •   event_id (INT): Foreign key linking to the attack event.
+      •   timestamp (DATETIME): Date and time of the log entry.
+      •   log_source (STRING): Source of the log (e.g., Windows Event, Syslog).
+      •   log_type (STRING): Type of log (e.g., Security, Application).
+      •   log_message (TEXT): Full content of the log message.
+	4.	Network Traffic
+      •   traffic_id (INT): Unique identifier for each traffic record.
+      •   event_id (INT): Foreign key linking to the attack event.
+      •   timestamp (DATETIME): Date and time of the network traffic.
+      •   source_ip (STRING): Source IP address.
+      •   destination_ip (STRING): Destination IP address.
+      •   protocol (STRING): Network protocol used.
+      •   port (INT): Port number.
+      •   payload_size (INT): Size of the data payload in bytes.
+	5.	Performance Metrics
+      •   metric_id (INT): Unique identifier for each metric entry.
+      •   event_id (INT): Foreign key linking to the attack event.
+      •   detection_time_seconds (INT): Time taken to detect the attack in seconds.
+      •   response_time_seconds (INT): Time taken to respond to the attack in seconds.
+      •   false_positive_rate (FLOAT): Rate of false positives in detection.
+      •   missed_detection_rate (FLOAT): Rate of attacks not detected.
+Intended Uses
+This dataset is intended for:
+   •   Training: Developing and refining cybersecurity defense and response strategies.
+   •   Analysis: Studying attack patterns and evaluating defense mechanisms.
+   •   Simulation: Creating realistic scenarios for cybersecurity drills and exercises.
+Source and Licensing
+This dataset is hosted on Hugging Face by Canstralian. For licensing information, please refer to the repository’s README.md file.
 Citation
+If you utilize this dataset in your research or projects, please provide appropriate credit to the creators as specified in the repository.
+For further guidance on creating dataset cards, you can refer to the Hugging Face documentation:
+   •   Create a dataset card
+   •   Dataset Cards