diff --git a/docs/company-policy/Business Continuity Plan.md b/docs/company-policy/Business Continuity Plan.md index 26ba213d3..375268ebc 100644 --- a/docs/company-policy/Business Continuity Plan.md +++ b/docs/company-policy/Business Continuity Plan.md @@ -201,3 +201,4 @@ _For detailed views on recovery of assets and operations after minimal operation **For viewing the tables in the Appendix, please download the PDF file of the Business Continuity Plan that will be found in the PDF Downloads Page in Policies.** + diff --git a/docs/company-policy/Disaster Recovery Policy.mdx b/docs/company-policy/Disaster Recovery Policy.mdx index 2c9dd837f..b5ece694c 100644 --- a/docs/company-policy/Disaster Recovery Policy.mdx +++ b/docs/company-policy/Disaster Recovery Policy.mdx @@ -381,4 +381,4 @@ To view the original tables, styles and structure, as well as the Risk Matrix. P type="application/pdf" width="100%" height="800px" -/> \ No newline at end of file +/> diff --git a/docs/company-policy/ISMS/DLP-data-classification-update.md b/docs/company-policy/ISMS/DLP-data-classification-update.md index 15f635fb0..d59d533af 100644 --- a/docs/company-policy/ISMS/DLP-data-classification-update.md +++ b/docs/company-policy/ISMS/DLP-data-classification-update.md @@ -64,3 +64,4 @@ Policy enforcement ensures that all DLP and Data Classification policies are fol ## Conclusion By adhering to the DLP and Data Classification policies outlined in this document, the safety and integrity of Redback Operations’ data can be ensured. Regular audits should be conducted to review the effectiveness of these policies and adapt them to emerging technologies and potential risks. + diff --git a/docs/company-policy/ISMS/User-Awareness-Training.md b/docs/company-policy/ISMS/User-Awareness-Training.md index 14fa10e32..3512b049a 100644 --- a/docs/company-policy/ISMS/User-Awareness-Training.md +++ b/docs/company-policy/ISMS/User-Awareness-Training.md @@ -113,4 +113,4 @@ This policy will be reviewed: - Annually. - After any major cybersecurity incident. - Upon changes to legislation or best practices. -The IT Security Team and Compliance Officers are responsible for reviewing and updating the policy content. \ No newline at end of file +The IT Security Team and Compliance Officers are responsible for reviewing and updating the policy content. diff --git a/docs/company-policy/ISMS/cloud-security.mdx b/docs/company-policy/ISMS/cloud-security.mdx index 9dd72098b..8b8556bb0 100644 --- a/docs/company-policy/ISMS/cloud-security.mdx +++ b/docs/company-policy/ISMS/cloud-security.mdx @@ -196,3 +196,4 @@ Controls map to NIST CSF functions—Identify (asset inventory, roles), Protect - [Azure Security Documentation](https://learn.microsoft.com/en-us/azure/security/) - [Google Cloud Security Best Practices](https://cloud.google.com/security/best-practices) - [OWASP Top Ten](https://owasp.org/www-project-top-ten/) + diff --git a/docs/company-policy/ISMS/cryptography.md b/docs/company-policy/ISMS/cryptography.md index 148427089..ebd72854a 100644 --- a/docs/company-policy/ISMS/cryptography.md +++ b/docs/company-policy/ISMS/cryptography.md @@ -454,3 +454,4 @@ The encryption policy will be reviewed at least bi-annually to assess its effect - Update training and awareness programs to reflect changes in the policy and emerging threats. The commitment to continuous improvement through training, awareness, and regular policy reviews is essential for maintaining the security and integrity of sensitive information within Redback Operations. + diff --git a/docs/company-policy/ISMS/cyber-security-metrics.md b/docs/company-policy/ISMS/cyber-security-metrics.md index c609098c2..eb0823bc6 100644 --- a/docs/company-policy/ISMS/cyber-security-metrics.md +++ b/docs/company-policy/ISMS/cyber-security-metrics.md @@ -47,3 +47,4 @@ Below are the 7 metrics listed in the ISMS in more detail - How is access to sensitive data and systems controlled and monitored, and how is privilege escalation prevented? - Are all accounts secured with Muli-Factor Authentication (MFA)? - Do we have a password policy addressing common malpractices, such as password recycling and weak passwords? + diff --git a/docs/company-policy/ISMS/dlp-data-classification.md b/docs/company-policy/ISMS/dlp-data-classification.md index db623e2c0..0f067bdaf 100644 --- a/docs/company-policy/ISMS/dlp-data-classification.md +++ b/docs/company-policy/ISMS/dlp-data-classification.md @@ -111,3 +111,4 @@ Moreover, regular audits can take place to assess how effective the policies reg ## Conclusion To conclude, if all DLP and Data Classification policies that are listed in this document are always adhered to, the safety and integrity of data collected and stored by Redback Operations is guaranteed. Though regular audits should take place to actively review all policies being followed, to counteract emerging technologies and potential risks that may threaten our data. + diff --git a/docs/company-policy/ISMS/easm.md b/docs/company-policy/ISMS/easm.md index e742d1aa6..1b24b6105 100644 --- a/docs/company-policy/ISMS/easm.md +++ b/docs/company-policy/ISMS/easm.md @@ -572,3 +572,4 @@ Strict access protocols for visitors are enforced, including escorted access, vi **Physical Device Security** Cable locks, secure enclosures, and other physical restraints are used to prevent unauthorized removal of devices. + diff --git a/docs/company-policy/ISMS/endpoint.md b/docs/company-policy/ISMS/endpoint.md index e69c41d1b..8ba41968e 100644 --- a/docs/company-policy/ISMS/endpoint.md +++ b/docs/company-policy/ISMS/endpoint.md @@ -156,3 +156,4 @@ Failure to comply with this policy may result in: ## Review and Maintenance This policy will be reviewed every 6 months or upon significant changes to Redback’s operational model or security posture. Updates will be developed under version control and published on the Redback Documentation site. + diff --git a/docs/company-policy/ISMS/gap-analysis.md b/docs/company-policy/ISMS/gap-analysis.md index 7e795526a..56d144a66 100644 --- a/docs/company-policy/ISMS/gap-analysis.md +++ b/docs/company-policy/ISMS/gap-analysis.md @@ -223,3 +223,4 @@ This gap analysis report underscores the urgent need for a comprehensive review   + diff --git a/docs/company-policy/ISMS/isms.md b/docs/company-policy/ISMS/isms.md index 9248c83c4..a950d44e0 100644 --- a/docs/company-policy/ISMS/isms.md +++ b/docs/company-policy/ISMS/isms.md @@ -262,3 +262,4 @@ This section contains links to supplementary policies affiliated with Redback Op [User Awareness Training](https://redback-operations.github.io/redback-documentation/docs/company-policy/ISMS/User-Awareness-Training) [Review of ISMS](https://redback-operations.github.io/redback-documentation/docs/company-policy/Policy%20Reviews/isms-review) + diff --git a/docs/company-policy/ISMS/monitoring-log-analytics.mdx b/docs/company-policy/ISMS/monitoring-log-analytics.mdx index d7ffaf0e8..1ff91f937 100644 --- a/docs/company-policy/ISMS/monitoring-log-analytics.mdx +++ b/docs/company-policy/ISMS/monitoring-log-analytics.mdx @@ -540,3 +540,4 @@ Detailed records of all review meetings, discussions, decisions made, and the re - Audit records must be maintained for a minimum of 24 months. [def]: # + diff --git a/docs/company-policy/ISMS/security-safeguards.mdx b/docs/company-policy/ISMS/security-safeguards.mdx index 7d82bed56..8b9830675 100644 --- a/docs/company-policy/ISMS/security-safeguards.mdx +++ b/docs/company-policy/ISMS/security-safeguards.mdx @@ -93,3 +93,4 @@ These recommendations should be prioritized in the ISMS implementation plan (see - [7] Khan, A. (2024). NIST CSF PR.AC-7: Users, Devices, and Other Assets are Authenticated. Available at: https://grc-docs.com/blogs/nist-csf-framework-categories/nist-csf-pr-ac-7-users-devices-and-other-assets-are-authenticated - [8] Convesio. (2024). The Impact of GDPR on Biometric Data. Available at: https://convesio.com/knowledgebase/article/the-impact-of-gdpr-on-biometric-data-what-you-need-to-know/ - Redback Operations ISMS Guide, Cryptography Policy, Data Classification & DLP Policy, Endpoint Security Policy + diff --git a/docs/company-policy/ISMS/server-security.mdx b/docs/company-policy/ISMS/server-security.mdx index c375d67b8..efbc1fd9c 100644 --- a/docs/company-policy/ISMS/server-security.mdx +++ b/docs/company-policy/ISMS/server-security.mdx @@ -934,3 +934,4 @@ Once changes are approved, the updated policy is communicated to all stakeholder https://www.cyber.gov.au/resources-business-and-government/essential-cyber-security/ism/cyber-security-guidelines/guidelines-system-hardening (Australian Signals Directorate, Guidelines for System Hardening, May 12 2024) + diff --git a/docs/company-policy/Policy Reviews/isms-review.md b/docs/company-policy/Policy Reviews/isms-review.md index b7ed146c9..7aba9514b 100644 --- a/docs/company-policy/Policy Reviews/isms-review.md +++ b/docs/company-policy/Policy Reviews/isms-review.md @@ -280,4 +280,4 @@ Mislabelled as Section 11.1. Needs to be renamed to 10.2 to be in line with ISO ## Summary -The current policy is on the right track to being ISO/IEC 27001 certified. However, there are some sections that either don’t exist or require more detail to be compliant. The overall requirement structure was mostly adhered to, but all the later sections have the wrong numbering structure and as such made it difficult to keep track of each requirement. As mentioned throughout this review, Section 12 is supposed to have links to other policies that are referenced in the policy but there are no links present currently. This needs to be addressed. There also needs to be policies created for some of the assets mentioned in the scope (those are listed in its respective section). \ No newline at end of file +The current policy is on the right track to being ISO/IEC 27001 certified. However, there are some sections that either don’t exist or require more detail to be compliant. The overall requirement structure was mostly adhered to, but all the later sections have the wrong numbering structure and as such made it difficult to keep track of each requirement. As mentioned throughout this review, Section 12 is supposed to have links to other policies that are referenced in the policy but there are no links present currently. This needs to be addressed. There also needs to be policies created for some of the assets mentioned in the scope (those are listed in its respective section). diff --git a/docs/company-policy/application control policy.md b/docs/company-policy/application control policy.md index c7595a999..34529a05e 100644 --- a/docs/company-policy/application control policy.md +++ b/docs/company-policy/application control policy.md @@ -137,3 +137,4 @@ This Application Control Policy is designed to ensure that Redback Operations ma For additional guidelines and best practices, refer to the following resources: ["Australian Signals Directorate, Guidelines for System Hardening, May 12, 2024"](https://www.cyber.gov.au/resources-business-and-government/essential-cyber-security/ism/cyber-security-guidelines/guidelines-system-hardening) + diff --git a/docs/company-policy/clean desk policy.md b/docs/company-policy/clean desk policy.md index 938a2e0a2..8cd93e6bd 100644 --- a/docs/company-policy/clean desk policy.md +++ b/docs/company-policy/clean desk policy.md @@ -127,3 +127,4 @@ This Clean Desk and Digital Workspace Policy provides a comprehensive framework For additional guidelines and best practices, refer to the following resources: ["Australian Signals Directorate, Guidelines for System Hardening, May 12, 2024"](https://www.cyber.gov.au/resources-business-and-government/essential-cyber-security/ism/cyber-security-guidelines/guidelines-system-hardening) + diff --git a/docs/company-policy/data-analytics-framework.md b/docs/company-policy/data-analytics-framework.md index edde4f536..9cbb9c394 100644 --- a/docs/company-policy/data-analytics-framework.md +++ b/docs/company-policy/data-analytics-framework.md @@ -291,3 +291,4 @@ The framework acts as a blueprint for consistency and efficiency in handling dat 2. **Updating Models and Systems** Regularly update predictive models and systems. + diff --git a/docs/cybersecurity/Archive/guidelines/project-1.md b/docs/cybersecurity/Archive/guidelines/project-1.md index f9876f7e6..24ca8bd70 100644 --- a/docs/cybersecurity/Archive/guidelines/project-1.md +++ b/docs/cybersecurity/Archive/guidelines/project-1.md @@ -371,4 +371,4 @@ Appropriate encryption methods should be implemented through Transport Layer Security (TLS) or Secure Socket Layer (SSL certificates). Authorisation methods and access permissions should be implemented to ensure only authorised users or devices can access certain data. This can be done through access control lists (ACLs) -or role-based access control (RBAC). \ No newline at end of file +or role-based access control (RBAC). diff --git a/docs/cybersecurity/Archive/guidelines/project-3.md b/docs/cybersecurity/Archive/guidelines/project-3.md index fd27a69b7..20207d42c 100644 --- a/docs/cybersecurity/Archive/guidelines/project-3.md +++ b/docs/cybersecurity/Archive/guidelines/project-3.md @@ -416,4 +416,4 @@ must undertake an assessment where there has been a data loss or unauthorised access to or disclosure of personal information. - The company must notify the OAIC where the incident is likely to result in harm to an -individual. \ No newline at end of file +individual. diff --git a/docs/cybersecurity/Blue Team/Introduction to Blue Team.md b/docs/cybersecurity/Blue Team/Introduction to Blue Team.md index 16b2ed9b6..a7d2b46e2 100644 --- a/docs/cybersecurity/Blue Team/Introduction to Blue Team.md +++ b/docs/cybersecurity/Blue Team/Introduction to Blue Team.md @@ -53,3 +53,4 @@ After you've read through these sections, have a think about what you'd like to + diff --git a/docs/cybersecurity/Blue Team/Onboarding/Docker Containers.md b/docs/cybersecurity/Blue Team/Onboarding/Docker Containers.md index c9ab1c791..9e09b23a4 100644 --- a/docs/cybersecurity/Blue Team/Onboarding/Docker Containers.md +++ b/docs/cybersecurity/Blue Team/Onboarding/Docker Containers.md @@ -76,4 +76,4 @@ When you make any changes to this compose file, the process for restarting the c ## 3. Further Reading - [Docker](https://docs.docker.com/) -- [Data Warehouse Docker Guide](https://redback-operations.github.io/redback-documentation/docs/data-warehousing/Instructional%20Documents/VM%20Guide/#the-vm-and-docker) \ No newline at end of file +- [Data Warehouse Docker Guide](https://redback-operations.github.io/redback-documentation/docs/data-warehousing/Instructional%20Documents/VM%20Guide/#the-vm-and-docker) diff --git a/docs/cybersecurity/Blue Team/Onboarding/Wazuh Architecture.md b/docs/cybersecurity/Blue Team/Onboarding/Wazuh Architecture.md index 3b1698923..133fa941d 100644 --- a/docs/cybersecurity/Blue Team/Onboarding/Wazuh Architecture.md +++ b/docs/cybersecurity/Blue Team/Onboarding/Wazuh Architecture.md @@ -81,3 +81,4 @@ This is an example of how an alert would look like on the dashboard. + diff --git a/docs/cybersecurity/Blue Team/Onboarding/Wazuh Background/Choosing-Both-Suricata-and-Wazuh.md b/docs/cybersecurity/Blue Team/Onboarding/Wazuh Background/Choosing-Both-Suricata-and-Wazuh.md deleted file mode 100644 index 8648dc81c..000000000 --- a/docs/cybersecurity/Blue Team/Onboarding/Wazuh Background/Choosing-Both-Suricata-and-Wazuh.md +++ /dev/null @@ -1,70 +0,0 @@ ---- -sidebar_position: 5 ---- - -:::info - **Last Edited:** 19 May 2024. **Author:** Tushar Sharma, Pranav Sharma **Version:** 3.0. -::: - -# Choosing Both Suricata and Wazuh: Understanding Their Unique Qualities - -## Introduction - -Redback Operations focuses on developing cutting-edge connected fitness devices. It requires the paramount importance of protecting user data and ensuring the integrity of the products. To enhance the security of the software systems within Redback Operations. We have implemented both Wazuh and Suricata on our virtual machine (VM) which will handle all the software project and data. This initiative is proactive approach to cybersecurity which aims to mitigate risks, ensure compliance, and enhance the safety, reliability, and peace of mind associated with our connected fitness technology. This document provides an overview of the need for implementing both Wazuh and Suricata, the strategic reasons behind their deployment, and the benefits they offer in terms of security, compliance, scalability, and operational efficiency. - - -## Why We Implemented Both Wazuh and Suricata? - -### 1. Enhanced Security Posture - -Wazuh is a Security Information and Event Management (SIEM) solution which focuses on collecting and analysing logs and events from hosts, applications, and network devices for security monitoring and threat detection [1]. Whereas Suricata is a Network Intrusion Detection System (NIDS) that focuses on inspecting network traffic and packets to detect threats like intrusions, DDoS attacks, and suspicious network activities. By combining these two solutions, we can achieve comprehensive security coverage, by combining both solutions. - -### 2. Scalability and Flexibility - -Both Wazuh and Suricata are designed to scale with our growing infrastructure. Wazuh can handle log and event monitoring across multiple endpoints, while Suricata efficiently processes high-speed network traffic. This ensures that our security measures remain effective as our operations expand, without the need for frequent upgrades or replacements. - -### 3. Improved Operational Efficiency - -Centralizing security monitoring with Wazuh and leveraging Suricata's network detection capabilities streamlines our security operations. This reduces the workload on security teams and project handlers, enabling efficient threat detection and response. - -### 4. Comprehensive Security Monitoring - -Implementing both solutions helps to providing comprehensive security monitoring and threat detection capabilities. Wazuh aids in monitoring host activities, file integrity, and security configurations, while Suricata helps identify external threats and monitor overall network health. - - -## Why we didn’t Implemented Only One Solution - -Implementing only one solution, whether Wazuh or Suricata, would expose significant security risks and operational challenges. As Relying solely on one solution would create critical security gaps [1]. For example, relying solely on Wazuh for host-based monitoring might overlook network-level threats, while depending exclusively on Suricata for network detection might miss insights into system-level activities and events. This fragmented approach leaves us vulnerable to various cyber threats, compromising our ability to maintain compliance with regulatory requirements and reducing operational efficiency. - -Implementing only one solution that may not provide the necessary breadth and depth of coverage to meet these requirements effectively. For instance, while Wazuh's robust monitoring capabilities help us meet regulatory standards by providing detailed insights into host-level activities and events, Suricata's network-based detection capabilities are equally crucial for identifying and mitigating threats that originate from external sources or traverse our network [1]. - -A single solution may lack the scalability and flexibility needed to adapt to the ongoing projects that are growing. Wazuh and Suricata are designed to scale seamlessly, offering flexibility in deployment and management across various environments. It ensures that our security measures remain robust and effective in the face of evolving threats. -Additionally, adopting a multi-layered security approach enhances our ability to detect and respond to sophisticated cyber threats effectively. Combining the capabilities of Wazuh and Suricata allows us to correlate security events and incidents across different layers of our infrastructure, providing a more comprehensive view of our security landscape. - - -## Difference between Wazuah and Suricata - - -| | **Wazuh** | **Suricata** | -|-------------|-----------|--------------| -| 1. | Wazuh is a Security Information and Event Management (SIEM) solution. | It is Network-based Intrusion Detection System (NIDS). | -| 2. | It collects and analyses logs and events from hosts, applications, and network devices for security monitoring and threat detection. | It inspects network traffic and packets to detect threats like intrusions, DDoS attacks, and suspicious network activities. | -| 3. | It provides a comprehensive security monitoring platform. | It focuses solely on network-based threat detection. | -| 4. | It utilises the system resources to log traffic inspection such as CPU, memory. | It primary utilises the network resources such as bandwidth and latency for traffic inspection. | -| 5 | It helps in regulatory compliance by monitoring host activities, file integrity and security configurations. | It aids in identifying external threats and monitoring the overall network health. | -| 6.| [Deploying Wazuh](https://redback-operations.github.io/redback-documentation/docs/cybersecurity/research/ids-and-wazuh/deploying-wazuh) | [Intrusion Detection System](https://redback-operations.github.io/redback-documentation/docs/cybersecurity/research/ids-and-wazuh/intrusion-detection-system) | - - -## Conclusion - -The deployment of Wazuh as a Security Information and Event Management (SIEM) solution and Suricata as a Network Intrusion Detection System (NIDS) on our virtual machine (VM) significantly enhances Redback Operations' cybersecurity posture. The integration of Wazuh and Suricata creates a multi-layered security approach, ensures the protection from a wide range of cyber threats. By combining the capabilities of a SIEM and a NIDS, we demonstrate our commitment to providing a secure and reliable environment. - - -## Reference - - -[1] I. O. Odike, “Responding to network attacks with Suricata and Wazuh XDR,” Wazuh, 11 November 2022. [Online]. Available: https://wazuh.com/blog/responding-to-network-attacks-with-suricata-and-wazuh-xdr/. - -[2] M. Stromann, “Suricata vs Wazuh,” LiveEnterprise, 06 August 2023. [Online]. Available: https://www.liventerprise.org/compare/Suricata_vs_Wazuh/. - - diff --git a/docs/cybersecurity/Blue Team/Onboarding/Wazuh Background/Installing Wazuh/Wazuh Agent Integration.pdf b/docs/cybersecurity/Blue Team/Onboarding/Wazuh Background/Installing Wazuh/Wazuh Agent Integration.pdf deleted file mode 100644 index 5fd5a6e72..000000000 Binary files a/docs/cybersecurity/Blue Team/Onboarding/Wazuh Background/Installing Wazuh/Wazuh Agent Integration.pdf and /dev/null differ diff --git a/docs/cybersecurity/Blue Team/Onboarding/Wazuh Background/Installing Wazuh/deploying-wazuh.mdx b/docs/cybersecurity/Blue Team/Onboarding/Wazuh Background/Installing Wazuh/deploying-wazuh.mdx index 8d688dca7..c7e94ba31 100644 --- a/docs/cybersecurity/Blue Team/Onboarding/Wazuh Background/Installing Wazuh/deploying-wazuh.mdx +++ b/docs/cybersecurity/Blue Team/Onboarding/Wazuh Background/Installing Wazuh/deploying-wazuh.mdx @@ -10,3 +10,4 @@ sidebar_position: 2 width="100%" height="800px" /> + diff --git a/docs/cybersecurity/Blue Team/Onboarding/Wazuh Background/Installing Wazuh/wazuh-implementation-guide.mdx b/docs/cybersecurity/Blue Team/Onboarding/Wazuh Background/Installing Wazuh/wazuh-implementation-guide.mdx index 4246335e7..415a76901 100644 --- a/docs/cybersecurity/Blue Team/Onboarding/Wazuh Background/Installing Wazuh/wazuh-implementation-guide.mdx +++ b/docs/cybersecurity/Blue Team/Onboarding/Wazuh Background/Installing Wazuh/wazuh-implementation-guide.mdx @@ -9,4 +9,4 @@ sidebar_position: 1 type="application/pdf" width="100%" height="800px" -/> \ No newline at end of file +/> diff --git a/docs/cybersecurity/Blue Team/Onboarding/Wazuh Background/intrusion-detection-system.mdx b/docs/cybersecurity/Blue Team/Onboarding/Wazuh Background/intrusion-detection-system.mdx index 33fbd7f82..82fc9f81e 100644 --- a/docs/cybersecurity/Blue Team/Onboarding/Wazuh Background/intrusion-detection-system.mdx +++ b/docs/cybersecurity/Blue Team/Onboarding/Wazuh Background/intrusion-detection-system.mdx @@ -9,4 +9,4 @@ sidebar_position: 3 type="application/pdf" width="100%" height="800px" -/> \ No newline at end of file +/> diff --git a/docs/cybersecurity/Blue Team/Onboarding/Wazuh Background/wazuh-documentation.md b/docs/cybersecurity/Blue Team/Onboarding/Wazuh Background/wazuh-documentation.md deleted file mode 100644 index 1c193b66f..000000000 --- a/docs/cybersecurity/Blue Team/Onboarding/Wazuh Background/wazuh-documentation.md +++ /dev/null @@ -1,81 +0,0 @@ ---- -sidebar_position: 6 ---- - -# Wazuh Documentation - -Documentation of the Wazuh open-source security platform: - -:::Info -Author: **Lachlan Harrison**, **31/08/2024** -::: - -## Section 1 - Capabilities of Wazuh - -Wazuh is an open source and completely free security platform which can be utilized for many features and learning which will be discussed in this documentation. The tool itself is accessible via this link: https://wazuh.com/ - -When we utilize the Wazuh platform, every user that interacts with the platform is presented with many opportunities to learn various concepts ranging from hacking methods to security methods to strengthen your systems and protect yourself from any attacker in which may discover the various vulnerabilities and exploit them for their own gains. These are all a threat in the modern world and thus we have adopted to utilizing Wazuh to assist in detecting these threats and mitigating them as soon as possible to reduce the liklihood of a compromise or enumeration agaisnt members of the company. - -When we mention these systems, they are referred to as Agents in which we can deploy various agents across the platform. The tool itself as well allows for further analysis into your agents across the dashboard in which the user can also discover various information about their agent, various configurations and standards to improve their security with this platform. - -- We can also allow for Wazuh to send security alerts to our devices via a chosen method which can range from platforms like Slack to our own Emails. This tool is referred to as a SIEM tool (Security, Information and Event Management) which all of these elements are showcased in Wazuh’s interface. SIEM categorised tools are very important in Cyber Security elements as they are efficient with providing the appropriate analysis, detailed information, security recommendations and also real-time events that are occurring within our linked agents. - -- Wazuh utilizes a simplistic method of analyzing our agents and due to this, the platform itself only requires a Linux server along with another machine to monitor the output of the tool which includes another computer. Many Linux servers are supported with Wazuh including various popular services such as Ubuntu and Debain. The implementation of this tool is also relatively easy and has already been discussed on another one of our documents. - -- The open-sourced tool as stated before provides users with a unique learning experience in which there is plenty of learning opportunities to grow and develop their knowledge in how to keep their devices safer from discovered vulnerabilities as well as providing users with knowledge of potential risks and how they can be mitigated to prevent enumeration, exploitation and compromises. This allows for users to become more cyber safe, reinforces their agent’s defences against cyber attacks and provides users with the knowledge to prevent these cases in the future. - -- Wazuh’s system requirements are quite slim even if utilizing a Virutal machine, this creates for easier access to reach more users as well as easier performance on the machine. These include a minimum requirement of 2GB of RAM along with 2 CPU cores whereas the recommended requirements aim for 4GB of RAM and 8 CPU cores allowing for a better performance and smoother experience when analyzing agents. - -Wazuh provides a lot of analysis opportunities for users to discover while utilizing the platform along with users to learn various concepts and potential vulnerabilities within their linked agents. - - - -## Section 2 - What can we learn from Wazuh? - -- The platform informs the user of any security configurations that need to be implemented to further enhance their security on the linked agent/s. These security configurations are also referred to as misconfigurations in which some of these the user may not intentionally select as it may have been from a previous user or default settings. Wazuh provides methods into configuring these misconfigurations properly along with what the misconfiguration actually is. - -- Wazuh focuses on vulnerabilities a lot as it is the source of many cyber attacks and the platform explains these vulnerabilities, categorises them into severity of the vulnerability and also how we can mitigate some of these vulnerabilities so that the user cannot be discovered by an attacker via enumeration/social engineering tactics which can further lead to a potential compromise. A list of common vulnerabilities is accessible which can make the user more aware of the risk of enumeration and exploitation which can be mitigated by the user and prevent attackers from performing their reconnaissance on the targeted agent. - -- Wazuh explores various threats in which malware is another area explored in which the interface is able to gather the type of malware being executed within the machine should the agent be compromised along with the severity of the malware. Other threats explored include brute-force attacks which can occur at any time in which Wazuh is able to alert the user that an attack is occurring and allows for the user to respond accordingly. This involves blocking the attacking IP address where the attack is being traced to which allows for proper incident response to the situation. With constant evolving cyber threats growing every day, Wazuh adapts to this with constant updates to its cyber attacks and is able to detect various new attacks within the linked agents. - -- The MITRE ATT&CK framework is a major implementation within Wazuh as it is an important framework to learn and understand so that users can become aware of the various categories of attacks and what each of these attacks are. Detected vulnerabilities within an agent also provide for MITRE techniques to be classified and sorted with the associated vulnerability which each technique has a unique tag and allows for the user to learn about the associated attack method which is linked to the vulnerability. For example, a brute force technique is categorised into the Credential Access category with a unique ID of T1110. - -- Other elements that Wazuh can analyse and inform us about is any changes within the Windows registry (if agent is windows) as well as any directory and file. These can range from changes to Windows registry keys including modifications, deleting and creating key values. Wazuh also analyses changes to a file and directory including adding, deleting and editing these files and directories. - -- Wazuh provides insight into various compliance standards in a matter for users to follow which includes but are not limited to up to date updates, constant securing of devices which may involve MFA (Multi-Factor Authentication) and mitigating discovered vulnerabilities. - -- The platform also displays to the user a Secure Configuration Assessment (SCA) which is able to inform users of why they need to follow certain actions to reduce the risk of being compromised and further keep themselves protected. The score given in the assessment further entails the user to perform various actions to achieve a higher score in their SCA which may involve for example installing certain software onto the associated agent. These are also considered misconfigurations which also utilize MITRE technique tags to classify them and the tool also informs the user with how they can check for these various misconfigurations and what they are. - -- Intel provided on various security events is extremely critical for incident response and for developing a safer agent and reduce the risk of enumeration and compromise. The intel Wazuh provides includes authentication failures/success, top alerts as well as providing an entire list of security alerts for the associated agent in which we can obtain in the interface. - -The tool provides so much information for the user and assists in becoming more secure with their agents as well as constant monitoring for any new changes needed to mitigate vulnerabilities that are discovered and any abnormal behaviour detected in which the user is able to respond accordingly. - - - -## Section 3 - Why Wazuh? Why do we need this tool? - -Since implementing Wazuh into Redback Operations, Wazuh provides many reasons as to why this tool should be utilized including various elements that provide an opportunity for the user to develop their own cyber safe environment. - -1. **Security Awareness** – Wazuh provides users knowledge of potential vulnerabilities and also how to mitigate these vulnerabilities to reduce the risk of a compromise or enumeration by an attacker by providing detailed information and solutions to make the user more aware of what is happening and why this is a risk. - -2. **Incident Response** – The platform allows for active response to real events occurring on their linked agents including various attacks and file changes to at which the user can act upon these incidents and take the necessary steps required to mitigate these attacks and risks. - -3. **Securing of Devices** – With the constant evolution of Cyber threats, Wazuh adapts and informs the user of these new threats by creating awareness of new exploits/vulnerabilities discovered within an agent and how to mitigate these risks hence why this tool provides a great opportunity for users to further secure their devices by adjusting configurations and making appropriate changes to mitigate the security alerts that are being detected. - -4. **Safety** – The tool itself protects user’s machines by providing adequate information to the user as to how to improve their safety and security to protect themselves from foreign attacks/interference which in turn creates ease of access for company members to continue their work on their projects knowing that the agent they are utilizing has its security enhanced due to the correct configurations and implementations utilized within the agent. - -5. **Accessibility** – Having a relatively easy to understand User Interface (UI), many users can easily navigate Wazuh’s dashboard to locate their agents and analyse the discovered elements. This creates an easy and also safe method of learning of what is being displayed to the user which for example, various vulnerabilities along with their MITRE techniques utilized to exploit this vulnerability and solutions to mitigate these vulnerabilities. - -6. **Compliance** – Wazuh provides members the opportunity to be compliant with various standards that are followed throughout many companies including but not limited to MFA and minimalized password sharing. Through this, users can become more cyber safe and also by following these standards, users can also create a more cyber safe environment for their companies. - -### Conclusion: -As a free open-sourced platform, Wazuh provides plenty of information and opportunities for members to learn about various cyber security principles, concepts and risks in which every one can learn how to mitigate and also utilize the platform in a positive manor to assist in protecting themselves from the evolving world of cyber threats and attacks. - -From easy implementation, low requirements and plenty of concepts that can be learnt, this platform is an extremely important asset to utilize in further enhancing a cyber safe environment to reduce the risk of exploitation, enumeration and compromise of a linked agent while also having various areas to develop our understanding of cyber security principles including but not limited to, Incident Response, Security awareness and safety. - -### Extra Resources: - -- MITRE ATT&CK Framework: https://attack.mitre.org/ -- Security Awareness Training Modules: https://classroom.google.com/c/NzAzMjgwOTI3MDIw?cjc=ppfbboc -- Link to Wazuh Video Documentation: https://youtu.be/g82PwIFLYYc?si=4pZzpdajIvHrIKlg -- Also check out the Wazuh PowerPoint documentation below for a more visual approach! diff --git a/docs/cybersecurity/Blue Team/Onboarding/Wazuh Background/wazuh-powerpoint.mdx b/docs/cybersecurity/Blue Team/Onboarding/Wazuh Background/wazuh-powerpoint.mdx index 8e5ae9860..5c6228ff4 100644 --- a/docs/cybersecurity/Blue Team/Onboarding/Wazuh Background/wazuh-powerpoint.mdx +++ b/docs/cybersecurity/Blue Team/Onboarding/Wazuh Background/wazuh-powerpoint.mdx @@ -16,3 +16,4 @@ Author: **Lachlan Harrison**, **17/09/2024** width="100%" height="800px" /> + diff --git a/docs/cybersecurity/Blue Team/Onboarding/installing wazuh.md b/docs/cybersecurity/Blue Team/Onboarding/installing wazuh.md index c32e63d61..8b60121a4 100644 --- a/docs/cybersecurity/Blue Team/Onboarding/installing wazuh.md +++ b/docs/cybersecurity/Blue Team/Onboarding/installing wazuh.md @@ -106,3 +106,4 @@ You should see Wazuh Manager, Wazuh Indexer, and Wazuh Dashboard all showing as ## Reference https://documentation.wazuh.com/current/deployment-options/docker/wazuh-container.html#single-node-stack + diff --git a/docs/cybersecurity/Blue Team/Onboarding/wazuh-background.md b/docs/cybersecurity/Blue Team/Onboarding/wazuh-background.md index 1f65758f2..01c5c5bd9 100644 --- a/docs/cybersecurity/Blue Team/Onboarding/wazuh-background.md +++ b/docs/cybersecurity/Blue Team/Onboarding/wazuh-background.md @@ -84,3 +84,4 @@ For example: This is not required for Wazuh access but may be needed for backend tasks. + diff --git a/docs/cybersecurity/Blue Team/Production/Email Infrastructure/Email-Infra-Security.md b/docs/cybersecurity/Blue Team/Production/Email Infrastructure/Email-Infra-Security.md index 87007f345..efeb8bd7d 100644 --- a/docs/cybersecurity/Blue Team/Production/Email Infrastructure/Email-Infra-Security.md +++ b/docs/cybersecurity/Blue Team/Production/Email Infrastructure/Email-Infra-Security.md @@ -247,3 +247,4 @@ The establishment of a robust, scalable, and secure email infrastructure enables - [Microsoft: Data Loss Prevention (DLP)](https://www.microsoft.com/en-au/security/business/security-101/what-is-data-loss-prevention-dlp) --- + diff --git a/docs/cybersecurity/Blue Team/Production/Email Infrastructure/phase1.md b/docs/cybersecurity/Blue Team/Production/Email Infrastructure/phase1.md index 97d1f13be..8a8580817 100644 --- a/docs/cybersecurity/Blue Team/Production/Email Infrastructure/phase1.md +++ b/docs/cybersecurity/Blue Team/Production/Email Infrastructure/phase1.md @@ -102,3 +102,4 @@ Create an initial email account (e.g., `adm-redbackops@redbackops.com`) as part - [Unlock or lock my domain - GoDaddy](https://www.godaddy.com/en-au/help/unlock-or-lock-my-domain-410) - [Microsoft 365 Developer Program Overview](https://learn.microsoft.com/en-us/office/developer-program/microsoft-365-developer-program) - [Get started with Microsoft 365 Developer Program](https://learn.microsoft.com/en-us/office/developer-program/microsoft-365-developer-program-get-started) + diff --git a/docs/cybersecurity/Blue Team/Production/Email Infrastructure/phase2.md b/docs/cybersecurity/Blue Team/Production/Email Infrastructure/phase2.md index e7c893fb2..2f58cc955 100644 --- a/docs/cybersecurity/Blue Team/Production/Email Infrastructure/phase2.md +++ b/docs/cybersecurity/Blue Team/Production/Email Infrastructure/phase2.md @@ -107,4 +107,4 @@ Ensure the following DNS records are published in the DNS of the domain: ## References - [MXToolbox](https://mxtoolbox.com/) - [Microsoft Admin Center](https://admin.microsoft.com/) -- [GoDaddy DNS Management](https://dcc.godaddy.com/) \ No newline at end of file +- [GoDaddy DNS Management](https://dcc.godaddy.com/) diff --git a/docs/cybersecurity/Blue Team/Production/Email Infrastructure/phase3.md b/docs/cybersecurity/Blue Team/Production/Email Infrastructure/phase3.md index d0f37b637..f5ef2afac 100644 --- a/docs/cybersecurity/Blue Team/Production/Email Infrastructure/phase3.md +++ b/docs/cybersecurity/Blue Team/Production/Email Infrastructure/phase3.md @@ -158,3 +158,4 @@ Perform a spoofing test using online tools such as [DMARCTester](https://www.dma - [PowerDMARC - All About SPF, DKIM, and DMARC](https://powerdmarc.com/all-about-spf-dkim-dmarc/) - [Microsoft Hosted Apps (MHA)](https://mha.azurewebsites.net/) - [DMARC Tester](https://www.dmarctester.com/) + diff --git a/docs/cybersecurity/Blue Team/Production/Email Infrastructure/phase4.md b/docs/cybersecurity/Blue Team/Production/Email Infrastructure/phase4.md index 1b46cf9de..50839349c 100644 --- a/docs/cybersecurity/Blue Team/Production/Email Infrastructure/phase4.md +++ b/docs/cybersecurity/Blue Team/Production/Email Infrastructure/phase4.md @@ -101,4 +101,4 @@ Before implementing the controls, the following PowerShell setup steps were impl ## References - [Microsoft Admin Center](https://admin.microsoft.com/) - [CIS Benchmark – Microsoft 365](https://www.cisecurity.org/benchmark/microsoft_365) -- [Redback Cyber GitHub Repo - Additional CIS Security Controls - Email & Collaboration.ps1](https://github.com/Redback-Operations/redback-cyber/blob/main/T3_2024/Email%20Infrastructure%20%26%20Security/Additional%20CIS%20Security%20Controls%20-%20Email%20%26%20Collaboration.ps1) \ No newline at end of file +- [Redback Cyber GitHub Repo - Additional CIS Security Controls - Email & Collaboration.ps1](https://github.com/Redback-Operations/redback-cyber/blob/main/T3_2024/Email%20Infrastructure%20%26%20Security/Additional%20CIS%20Security%20Controls%20-%20Email%20%26%20Collaboration.ps1) diff --git a/docs/cybersecurity/Blue Team/Production/Email Infrastructure/phase5.md b/docs/cybersecurity/Blue Team/Production/Email Infrastructure/phase5.md index 57b516cf4..7e55a6962 100644 --- a/docs/cybersecurity/Blue Team/Production/Email Infrastructure/phase5.md +++ b/docs/cybersecurity/Blue Team/Production/Email Infrastructure/phase5.md @@ -236,3 +236,4 @@ However, based on the screenshot above, it can be validated that MTA-STS was app - [PowerShell Script – MFA Enforcement](https://github.com/Redback-Operations/redback-cyber/blob/main/T1_2025/Email%20Infrastructure%20%26%20Security/Set-MFAEnforcement-AllUsers-Phase5.ps1) - [PowerShell Script – Mailflow & Audit Controls](https://github.com/Redback-Operations/redback-cyber/blob/main/T1_2025/Email%20Infrastructure%20%26%20Security/Set-MailflowSecurity-AuditControls-Phase5.ps1) + diff --git a/docs/cybersecurity/Blue Team/Production/Nginx and ModSecurity/About Nginx and ModSecurity.md b/docs/cybersecurity/Blue Team/Production/Nginx and ModSecurity/About Nginx and ModSecurity.md index e57c7b0dc..c9dd213a0 100644 --- a/docs/cybersecurity/Blue Team/Production/Nginx and ModSecurity/About Nginx and ModSecurity.md +++ b/docs/cybersecurity/Blue Team/Production/Nginx and ModSecurity/About Nginx and ModSecurity.md @@ -58,3 +58,4 @@ Finally, once the reverse proxy has been deployed and tested, ideally people sho In T2 2025, given the scope of this project, efforts were directed towards installing Nginx and ModSecurity, enabling logging, and testing web apps used across the Cyber Security and Data Warehouse teams. Please refer to the next document for more information. + diff --git a/docs/cybersecurity/Blue Team/Production/Nginx and ModSecurity/Nginx + ModSecurity Setup.md b/docs/cybersecurity/Blue Team/Production/Nginx and ModSecurity/Nginx + ModSecurity Setup.md index 4bd77842e..3dbd4234f 100644 --- a/docs/cybersecurity/Blue Team/Production/Nginx and ModSecurity/Nginx + ModSecurity Setup.md +++ b/docs/cybersecurity/Blue Team/Production/Nginx and ModSecurity/Nginx + ModSecurity Setup.md @@ -171,3 +171,4 @@ This guide only briefly covered the current setup. To further understand all the Also, to get a better understanding of Nginx, refer to the official documentation: http://nginx.org/en/docs/ Additionally, to get an understanding of what's been tested so far, review the next doc in this series. + diff --git a/docs/cybersecurity/Blue Team/Production/Nginx and ModSecurity/Nginx Testing.md b/docs/cybersecurity/Blue Team/Production/Nginx and ModSecurity/Nginx Testing.md index dc56ff63a..3c66cf7cf 100644 --- a/docs/cybersecurity/Blue Team/Production/Nginx and ModSecurity/Nginx Testing.md +++ b/docs/cybersecurity/Blue Team/Production/Nginx and ModSecurity/Nginx Testing.md @@ -82,3 +82,4 @@ One thing that has been tested is manually replacing the locations of resources ![Dremio config](img-proxy/dremio.png) + diff --git a/docs/cybersecurity/Blue Team/Production/Wazuh/Backups and Upgrades/wazuh-agent-upgrade-guide.md b/docs/cybersecurity/Blue Team/Production/Wazuh/Backups and Upgrades/wazuh-agent-upgrade-guide.md index ff3eb6d8c..7ca8c791c 100644 --- a/docs/cybersecurity/Blue Team/Production/Wazuh/Backups and Upgrades/wazuh-agent-upgrade-guide.md +++ b/docs/cybersecurity/Blue Team/Production/Wazuh/Backups and Upgrades/wazuh-agent-upgrade-guide.md @@ -135,3 +135,4 @@ After the upgrade, disable the Wazuh repository to avoid undesired upgrades and ## Reference - https://documentation.wazuh.com/current/upgrade-guide/wazuh-agent/linux.html + diff --git a/docs/cybersecurity/Blue Team/Production/Wazuh/Backups and Upgrades/wazuh-backup-redeploy.md b/docs/cybersecurity/Blue Team/Production/Wazuh/Backups and Upgrades/wazuh-backup-redeploy.md index fdf004e60..e580e4312 100644 --- a/docs/cybersecurity/Blue Team/Production/Wazuh/Backups and Upgrades/wazuh-backup-redeploy.md +++ b/docs/cybersecurity/Blue Team/Production/Wazuh/Backups and Upgrades/wazuh-backup-redeploy.md @@ -282,3 +282,4 @@ sidebar_position: 8 docker ps ``` ![Wazuh Backup Redeploy](./img-backup-redeploy/18_wazuh_bkup_redeploy.jpg) + diff --git a/docs/cybersecurity/Blue Team/Production/Wazuh/Backups and Upgrades/wazuh-docker-upgrade-guide.md b/docs/cybersecurity/Blue Team/Production/Wazuh/Backups and Upgrades/wazuh-docker-upgrade-guide.md index 193580ed7..9fd94c246 100644 --- a/docs/cybersecurity/Blue Team/Production/Wazuh/Backups and Upgrades/wazuh-docker-upgrade-guide.md +++ b/docs/cybersecurity/Blue Team/Production/Wazuh/Backups and Upgrades/wazuh-docker-upgrade-guide.md @@ -187,4 +187,4 @@ docker compose up -d ## References - https://documentation.wazuh.com/current/deployment-options/docker/upgrading-wazuh-docker.html -- https://documentation.wazuh.com/current/release-notes/index.html \ No newline at end of file +- https://documentation.wazuh.com/current/release-notes/index.html diff --git a/docs/cybersecurity/Blue Team/Production/Wazuh/Enhancements/ClamAV-Integration.md b/docs/cybersecurity/Blue Team/Production/Wazuh/Enhancements/ClamAV-Integration.md index 94a48ed22..b7a719ec7 100644 --- a/docs/cybersecurity/Blue Team/Production/Wazuh/Enhancements/ClamAV-Integration.md +++ b/docs/cybersecurity/Blue Team/Production/Wazuh/Enhancements/ClamAV-Integration.md @@ -157,4 +157,4 @@ Moreover, during this task, YARA and ClamAV integration was explored. However, i - [Installing ClamAV via Docker](https://docs.clamav.net/manual/Installing/Docker.html) - [ClamAV scanning options](https://docs.clamav.net/manual/Usage/Scanning.html) - [Syslog Docker driver](https://docs.docker.com/engine/logging/drivers/syslog/) -- [Adding custom decoders](https://documentation.wazuh.com/current/user-manual/ruleset/decoders/custom.html) \ No newline at end of file +- [Adding custom decoders](https://documentation.wazuh.com/current/user-manual/ruleset/decoders/custom.html) diff --git a/docs/cybersecurity/Blue Team/Production/Wazuh/Enhancements/Suricata.md b/docs/cybersecurity/Blue Team/Production/Wazuh/Enhancements/Suricata.md index ecc6a6dea..cbfdfa8b9 100644 --- a/docs/cybersecurity/Blue Team/Production/Wazuh/Enhancements/Suricata.md +++ b/docs/cybersecurity/Blue Team/Production/Wazuh/Enhancements/Suricata.md @@ -90,3 +90,4 @@ Once set up, you should see alerts on the dashboard for network-related activity - [Suricata docs](https://docs.suricata.io/en/latest/) - [Logrotate guide](https://betterstack.com/community/guides/logging/how-to-manage-log-files-with-logrotate-on-ubuntu-20-04/) + diff --git a/docs/cybersecurity/Blue Team/Production/Wazuh/Enhancements/VirusTotal-Integration.md b/docs/cybersecurity/Blue Team/Production/Wazuh/Enhancements/VirusTotal-Integration.md index a8f8a21cd..4a76e14b0 100644 --- a/docs/cybersecurity/Blue Team/Production/Wazuh/Enhancements/VirusTotal-Integration.md +++ b/docs/cybersecurity/Blue Team/Production/Wazuh/Enhancements/VirusTotal-Integration.md @@ -103,3 +103,4 @@ Finally, the Public API is forbidden to be used in a commercial setting. Hence, ## 4. References - [VirusTotal Integration Wazuh Guide](https://documentation.wazuh.com/current/user-manual/capabilities/malware-detection/virus-total-integration.html) - [EICAR](https://www.eicar.org/download-anti-malware-testfile/) + diff --git a/docs/cybersecurity/Blue Team/Production/Wazuh/Enhancements/wazuh-docker-runtime-monitoring.md b/docs/cybersecurity/Blue Team/Production/Wazuh/Enhancements/wazuh-docker-runtime-monitoring.md index dfbbadb65..f708fac6b 100644 --- a/docs/cybersecurity/Blue Team/Production/Wazuh/Enhancements/wazuh-docker-runtime-monitoring.md +++ b/docs/cybersecurity/Blue Team/Production/Wazuh/Enhancements/wazuh-docker-runtime-monitoring.md @@ -224,4 +224,4 @@ curl -XGET "http://redback.it.deakin.edu.au:8082/users/?id=SELECT+*+FROM+users" ## References - https://documentation.wazuh.com/current/user-manual/capabilities/container-security/use-cases.html -- https://wazuh.com/blog/docker-container-security-monitoring-with-wazuh/ \ No newline at end of file +- https://wazuh.com/blog/docker-container-security-monitoring-with-wazuh/ diff --git a/docs/cybersecurity/Blue Team/Production/Wazuh/Enhancements/wazuh-sso-rbac.md b/docs/cybersecurity/Blue Team/Production/Wazuh/Enhancements/wazuh-sso-rbac.md index c2e98fc2b..747a605f5 100644 --- a/docs/cybersecurity/Blue Team/Production/Wazuh/Enhancements/wazuh-sso-rbac.md +++ b/docs/cybersecurity/Blue Team/Production/Wazuh/Enhancements/wazuh-sso-rbac.md @@ -281,4 +281,4 @@ With this configuration, Wazuh is securely integrated with Microsoft Entra ID us ## References -- https://documentation.wazuh.com/current/user-manual/user-administration/single-sign-on/administrator/microsoft-entra-id.html#wazuh-dashboard-configuration \ No newline at end of file +- https://documentation.wazuh.com/current/user-manual/user-administration/single-sign-on/administrator/microsoft-entra-id.html#wazuh-dashboard-configuration diff --git a/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/End to End Validation.md b/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/End to End Validation.md index 423b0fc7f..fad2f9f4e 100644 --- a/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/End to End Validation.md +++ b/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/End to End Validation.md @@ -270,3 +270,4 @@ This project demonstrates the feasibility of building a SOAR pipeline entirely w The project successfully validated an end-to-end SOAR workflow across detection, enrichment, orchestration, automation, and response. Despite using only free/community editions, the stack demonstrated the capabilities required for modern SOCs. This marks the closure of the project - proving that a functioning SOAR pipeline can be achieved with open-source tools, and providing a foundation for future enhancements (e.g., scaling, machine learning-based correlation, or additional analyzers). + diff --git a/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Introduction.md b/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Introduction.md index c8b5efeb6..0e7f37dbc 100644 --- a/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Introduction.md +++ b/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Introduction.md @@ -102,3 +102,4 @@ The aim of this project was to build a fully integrated Automated Threat Hunting - End-to-end SOAR capabilities with TheHive and Cortex for automated case handling. - Custom behavioural detection rules tailored to common attack techniques. - Full automation of threat detection, enrichment, and triage. + diff --git a/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Phase 1 - Core Setup and Wazuh Deployment.md b/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Phase 1 - Core Setup and Wazuh Deployment.md index 4faad342e..a5858d307 100644 --- a/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Phase 1 - Core Setup and Wazuh Deployment.md +++ b/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Phase 1 - Core Setup and Wazuh Deployment.md @@ -634,3 +634,4 @@ Once everything is set up and connected, we can check the connection status betw + diff --git "a/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Phase 2 -Network Threat Detection Integration \342\200\223 Suricata + Wazuh.md" "b/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Phase 2 -Network Threat Detection Integration \342\200\223 Suricata + Wazuh.md" index d809eb05e..34efbc304 100644 --- "a/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Phase 2 -Network Threat Detection Integration \342\200\223 Suricata + Wazuh.md" +++ "b/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Phase 2 -Network Threat Detection Integration \342\200\223 Suricata + Wazuh.md" @@ -388,3 +388,4 @@ For users who still don’t see alerts even after applying rules and generating + diff --git a/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Phase 3 - MISP Threat Intelligence Platform Deployment.md b/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Phase 3 - MISP Threat Intelligence Platform Deployment.md index 3e198c097..96bfd9525 100644 --- a/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Phase 3 - MISP Threat Intelligence Platform Deployment.md +++ b/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Phase 3 - MISP Threat Intelligence Platform Deployment.md @@ -259,3 +259,4 @@ By successfully completing this step, you validate that your MISP deployment is + diff --git "a/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Phase 4 - Wazuh\342\200\223MISP Automation and Alert Enrichment.md" "b/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Phase 4 - Wazuh\342\200\223MISP Automation and Alert Enrichment.md" index 9347e4f61..f46170f7f 100644 --- "a/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Phase 4 - Wazuh\342\200\223MISP Automation and Alert Enrichment.md" +++ "b/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Phase 4 - Wazuh\342\200\223MISP Automation and Alert Enrichment.md" @@ -39,3 +39,4 @@ As a result, the enriched alert is no longer simply a record of a local system e This transition marks the start of true automation. From this point onward, the system is capable of continuously monitoring inbound events, automatically correlating them with real-time threat intelligence from MISP, and escalating alerts based on confirmed matches - all without the need for manual review or scripting. This creates a continuous feedback loop in which Wazuh functions not just as a detection engine, but as an intelligence-aware analyst capable of filtering noise and surfacing high-confidence threats. The successful enrichment demonstrated in the previous screenshot confirms that this process is now occurring automatically. Users can validate this visually by accessing the Wazuh Dashboard and searching for rule IDs such as 100622, or by filtering alerts using tags like misp_alert, threat_intel, or custom_correlated. Selecting any of these alerts reveals a detailed JSON view, where the embedded MISP context, including the event ID, category, type, and value, can be reviewed in full, verifying the seamless integration of external intelligence with local detection. + diff --git a/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Phase 5 - SOAR Deployment-The Hive and Cortex.md b/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Phase 5 - SOAR Deployment-The Hive and Cortex.md index 3973540e9..dfa73aa2f 100644 --- a/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Phase 5 - SOAR Deployment-The Hive and Cortex.md +++ b/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Phase 5 - SOAR Deployment-The Hive and Cortex.md @@ -174,3 +174,4 @@ Once configured, these analyzers can be invoked manually by analysts or automati Working with **TheHive** will be continued in a later phase where we will explore how to use it effectively for case management, incident triage, and collaborative analysis. TheHive is an open-source Security Incident Response Platform (SIRP) designed to help security teams handle alerts, manage investigations, and collaborate on security incidents in a structured and auditable manner. It allows the creation of detailed cases from alerts generated by external systems such as Wazuh, MISP, or Cortex. Each case can include tasks, observables, and linked events, making it ideal for documenting forensic analysis, tracking investigation progress, and standardising incident response procedures across teams. By integrating it with Cortex, TheHive becomes capable of enriching observables automatically, running analyzers, and orchestrating responses, all within a single unified platform that enhances operational efficiency and threat-handling maturity. ::: + diff --git a/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Phase 6 - Behavioural Rules and Testing.md b/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Phase 6 - Behavioural Rules and Testing.md index 8c4def65c..b20ece637 100644 --- a/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Phase 6 - Behavioural Rules and Testing.md +++ b/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Phase 6 - Behavioural Rules and Testing.md @@ -129,3 +129,4 @@ This configuration raises the threshold for triggering the rule and lowers its a With noise suppression and enrichment functioning, your Wazuh-based threat detection pipeline becomes significantly more efficient, contextual, and actionable. + diff --git a/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Phase 7 - Wazuh & The Hive Integration.md b/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Phase 7 - Wazuh & The Hive Integration.md index 131e97ef7..6bfae5332 100644 --- a/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Phase 7 - Wazuh & The Hive Integration.md +++ b/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Phase 7 - Wazuh & The Hive Integration.md @@ -330,4 +330,4 @@ From a strategic perspective, this integration lays the groundwork for more adva 6. **API & Automation**: Extend TheHive with scripts, connectors, and integrations with other tools. -7. **Audit & Accountability**: Maintain a clear record of who did what and when for compliance. \ No newline at end of file +7. **Audit & Accountability**: Maintain a clear record of who did what and when for compliance. diff --git a/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Phase 8 - Cortex Observables.md b/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Phase 8 - Cortex Observables.md index f118417b5..d5661c9d4 100644 --- a/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Phase 8 - Cortex Observables.md +++ b/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Phase 8 - Cortex Observables.md @@ -37,3 +37,4 @@ After analyzer jobs complete, click the observable to view detailed reports. Rep ![Report View](img\Viewing_Report.png) Analysis_of_a_report.png ![Report Analysis View](img\Analysis_of_a_report.png) + diff --git a/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Phase 9 - Cortex Automation.md b/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Phase 9 - Cortex Automation.md index 9eb36d806..e981c0841 100644 --- a/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Phase 9 - Cortex Automation.md +++ b/docs/cybersecurity/Blue Team/Research/Automated Threat Hunting/Phase 9 - Cortex Automation.md @@ -199,4 +199,4 @@ This flow enables both manual Cortex analyzer execution and autorun for IP obser ![Automating Multiple run-1](img\automating_multiple_run_1.png) ![Automating Multiple run-2](img\automating_multiple_run_2.png) -::: \ No newline at end of file +::: diff --git a/docs/cybersecurity/Blue Team/Research/CVE Threat Automation/CVE Threat Automation.md b/docs/cybersecurity/Blue Team/Research/CVE Threat Automation/CVE Threat Automation.md index 501df11d1..57dec6bc1 100644 --- a/docs/cybersecurity/Blue Team/Research/CVE Threat Automation/CVE Threat Automation.md +++ b/docs/cybersecurity/Blue Team/Research/CVE Threat Automation/CVE Threat Automation.md @@ -231,3 +231,4 @@ By integrating MISP, Python automation, and Wazuh, we: The framework serves as a blueprint for scalable cybersecurity operations and continues to evolve with advanced threat intelligence integrations. --- + diff --git a/docs/cybersecurity/Blue Team/Research/Cowrie/Cowrie-Honeypot-Implementation-Guide.md b/docs/cybersecurity/Blue Team/Research/Cowrie/Cowrie-Honeypot-Implementation-Guide.md index 4ce43d68d..9edb6841d 100644 --- a/docs/cybersecurity/Blue Team/Research/Cowrie/Cowrie-Honeypot-Implementation-Guide.md +++ b/docs/cybersecurity/Blue Team/Research/Cowrie/Cowrie-Honeypot-Implementation-Guide.md @@ -800,4 +800,4 @@ This methodical technique guarantees that the honeypot is kept up to date, depen ## Conclusion -This manual offers a thorough, step-by-step procedure for setting up and evaluating a Cowrie honeypot. The screenshots and logs that are linked show real-world uses. These procedures can be repeated by future staff members to successfully set up and maintain secure honeypots. \ No newline at end of file +This manual offers a thorough, step-by-step procedure for setting up and evaluating a Cowrie honeypot. The screenshots and logs that are linked show real-world uses. These procedures can be repeated by future staff members to successfully set up and maintain secure honeypots. diff --git a/docs/cybersecurity/Blue Team/Research/ELF Stack/elf-stack-geoip.md b/docs/cybersecurity/Blue Team/Research/ELF Stack/elf-stack-geoip.md index 41ea40c83..558e3c2f5 100644 --- a/docs/cybersecurity/Blue Team/Research/ELF Stack/elf-stack-geoip.md +++ b/docs/cybersecurity/Blue Team/Research/ELF Stack/elf-stack-geoip.md @@ -316,3 +316,4 @@ Then select the data views that you want (that have the logs) and that should lo + diff --git a/docs/cybersecurity/research/Feasibility Study On Hayabusa.md b/docs/cybersecurity/Blue Team/Research/Feasibility Study On Hayabusa.md similarity index 99% rename from docs/cybersecurity/research/Feasibility Study On Hayabusa.md rename to docs/cybersecurity/Blue Team/Research/Feasibility Study On Hayabusa.md index f5772422e..b9de2d48b 100644 --- a/docs/cybersecurity/research/Feasibility Study On Hayabusa.md +++ b/docs/cybersecurity/Blue Team/Research/Feasibility Study On Hayabusa.md @@ -7,7 +7,7 @@ sidebar_position: 20 :::info **Last Edited:** 15 September 2024. **Authors:** Devika Sivakumar **Version:** 1.0. -[PDF template here](docs\Feasibility-Study-Hayabusa.pdf) +> **Note:** PDF removed during cleanup. ::: ## 1. Objectives @@ -79,4 +79,5 @@ For Redback’s Cybersecurity Team, having Hayabusa integrated into Wazuh’s wo Overall, integrating Hayabusa into the cybersecurity infrastructure is a feasible and beneficial step toward strengthening the company's ability to respond to and investigate security incidents, ensuring the integrity and security of Redback Operations' projects. -**Appendix:** Playbook Maintenance and Review The integration of Hayabusa into Wazuh should be reviewed bi-annually. This review will ensure that all configurations are optimized, and that the tool remains aligned with Redback’s growing infrastructure. Training should also be updated annually, ensuring all Cybersecurity Team members can leverage Hayabusa effectively in incident response and forensic workflows. \ No newline at end of file +**Appendix:** Playbook Maintenance and Review The integration of Hayabusa into Wazuh should be reviewed bi-annually. This review will ensure that all configurations are optimized, and that the tool remains aligned with Redback’s growing infrastructure. Training should also be updated annually, ensuring all Cybersecurity Team members can leverage Hayabusa effectively in incident response and forensic workflows. + diff --git a/docs/cybersecurity/research/Feasibility Study on OpenCTI Template.md b/docs/cybersecurity/Blue Team/Research/Feasibility Study on OpenCTI Template.md similarity index 98% rename from docs/cybersecurity/research/Feasibility Study on OpenCTI Template.md rename to docs/cybersecurity/Blue Team/Research/Feasibility Study on OpenCTI Template.md index 8dd03039c..27c7342ce 100644 --- a/docs/cybersecurity/research/Feasibility Study on OpenCTI Template.md +++ b/docs/cybersecurity/Blue Team/Research/Feasibility Study on OpenCTI Template.md @@ -9,7 +9,7 @@ Feasibility Study on Implementing OpenCTI Template (Guide) :::info **Last Edited:** 12 May 2024. **Authors:** Devika Sivakumar **Version:** 1.0. -[PDF template here](docs\Feasibility-Study-on-OpenCTI-Template.pdf) +> **Note:** PDF removed during cleanup. ::: ## 1. Introduction @@ -84,3 +84,5 @@ Feasibility Study on Implementing OpenCTI Template (Guide) This outline provides a structured approach to conducting a feasibility study on implementing OpenCTI within an organization. Each section can be further elaborated with detailed analysis and findings based on the specific context and requirements of the organization. + + diff --git a/docs/cybersecurity/Blue Team/Research/Graylog Setup/Graylog and Logstash Comparative Analysis.md b/docs/cybersecurity/Blue Team/Research/Graylog Setup/Graylog and Logstash Comparative Analysis.md index 673a36046..90e426b01 100644 --- a/docs/cybersecurity/Blue Team/Research/Graylog Setup/Graylog and Logstash Comparative Analysis.md +++ b/docs/cybersecurity/Blue Team/Research/Graylog Setup/Graylog and Logstash Comparative Analysis.md @@ -91,4 +91,4 @@ Graylog offers a more opinionated, streamlined experience ideal for many logging - Elastic. (2023). Logstash Documentation. Elastic. Retrieved from https://www.elastic.co/logstash - Graylog. (2023). Graylog Documentation. Retrieved https://go2docs.graylog.org/ -- Faruk Ozelll. (2024). Log Management: Graylog vs ELK — Which One is Right for You? Medium. Retrieved from https://medium.com/@faruk.ozelll/log-management-graylog-vs-elk-which-one-is-right-for-you-a6d42c924218 \ No newline at end of file +- Faruk Ozelll. (2024). Log Management: Graylog vs ELK — Which One is Right for You? Medium. Retrieved from https://medium.com/@faruk.ozelll/log-management-graylog-vs-elk-which-one-is-right-for-you-a6d42c924218 diff --git a/docs/cybersecurity/Blue Team/Research/Graylog Setup/Graylog setup with TLS.md b/docs/cybersecurity/Blue Team/Research/Graylog Setup/Graylog setup with TLS.md index b4153f943..e42ddd104 100644 --- a/docs/cybersecurity/Blue Team/Research/Graylog Setup/Graylog setup with TLS.md +++ b/docs/cybersecurity/Blue Team/Research/Graylog Setup/Graylog setup with TLS.md @@ -192,3 +192,4 @@ elasticsearch_password = allowfullscreen> + diff --git a/docs/cybersecurity/Blue Team/Research/MISP/Automating_feeds_on_MISP.md b/docs/cybersecurity/Blue Team/Research/MISP/Automating_feeds_on_MISP.md index e595cad19..49f17f6e7 100644 --- a/docs/cybersecurity/Blue Team/Research/MISP/Automating_feeds_on_MISP.md +++ b/docs/cybersecurity/Blue Team/Research/MISP/Automating_feeds_on_MISP.md @@ -81,3 +81,4 @@ _sudo usermod -aG docker $USER_ ## 1.4 Conclusion MISP is a powerful platform for managing and sharing threat intelligence. By automating feed updates and leveraging its API, you can integrate it into your security operations for enriched threat detection and response. + diff --git a/docs/cybersecurity/Blue Team/Research/MISP/MISP_Setup_Guide.md b/docs/cybersecurity/Blue Team/Research/MISP/MISP_Setup_Guide.md index 70ed4640b..4a5b65255 100644 --- a/docs/cybersecurity/Blue Team/Research/MISP/MISP_Setup_Guide.md +++ b/docs/cybersecurity/Blue Team/Research/MISP/MISP_Setup_Guide.md @@ -72,3 +72,4 @@ sidebar_position: 1 ### Glance on MISP Dashboard [![Glance on MISP Dashboard](http://img.youtube.com/vi/9ZVIKV3WlHI/0.jpg)](https://youtu.be/9ZVIKV3WlHI) + diff --git a/docs/cybersecurity/Blue Team/Research/Pi-Hole/QEMU-RaspberryPi-Simulation-Pi-hole.md b/docs/cybersecurity/Blue Team/Research/Pi-Hole/QEMU-RaspberryPi-Simulation-Pi-hole.md index 8beb5c04a..783930323 100644 --- a/docs/cybersecurity/Blue Team/Research/Pi-Hole/QEMU-RaspberryPi-Simulation-Pi-hole.md +++ b/docs/cybersecurity/Blue Team/Research/Pi-Hole/QEMU-RaspberryPi-Simulation-Pi-hole.md @@ -315,3 +315,4 @@ By following these steps, a comprehensive and reliable setup for the QEMU Raspbe 3. CyberSec Research Lab (2024). *Enhancing Network Security through DNS*. Available at: [https://cyberseclab.org/dns-security](https://cyberseclab.org/dns-security) (Accessed: 24 November 2024). 4. Tech with Tim (2024). *QEMU Raspberry Pi Setup and Testing*. Available at: [https://youtu.be/cE21YjuaB6o?si=8vUHWSPezyhhIGxN](https://youtu.be/cE21YjuaB6o?si=8vUHWSPezyhhIGxN) (Accessed: 24 November 2024). 5. Firebog (2024). *Blocklists for Pi-hole*. Available at: [https://firebog.net/](https://firebog.net/) (Accessed: 24 November 2024). + diff --git a/docs/cybersecurity/Blue Team/Research/Pi-Hole/pi-research.md b/docs/cybersecurity/Blue Team/Research/Pi-Hole/pi-research.md index 953bca3e5..693dfba75 100644 --- a/docs/cybersecurity/Blue Team/Research/Pi-Hole/pi-research.md +++ b/docs/cybersecurity/Blue Team/Research/Pi-Hole/pi-research.md @@ -55,3 +55,4 @@ Pi-hole offers several advantages to enhance your online experience by blocking here you can see pihole has already started blocking some of the domains that are blacklisted. In conclusion, Pi-hole is a cost-effective, efficient, and easy-to-manage solution that provides comprehensive ad-blocking, privacy protection, and faster internet browsing for all devices on your network. + diff --git a/docs/cybersecurity/Blue Team/Research/Pi-Hole/pihole-setup.md b/docs/cybersecurity/Blue Team/Research/Pi-Hole/pihole-setup.md index 85e10b9e7..3f7c7ad77 100644 --- a/docs/cybersecurity/Blue Team/Research/Pi-Hole/pihole-setup.md +++ b/docs/cybersecurity/Blue Team/Research/Pi-Hole/pihole-setup.md @@ -154,3 +154,4 @@ After doing this, go to update gravity and click update this will update the add + diff --git a/docs/cybersecurity/research/SIEM-research.md b/docs/cybersecurity/Blue Team/Research/SIEM-research.md similarity index 99% rename from docs/cybersecurity/research/SIEM-research.md rename to docs/cybersecurity/Blue Team/Research/SIEM-research.md index e87c4004e..b7bb9ec27 100644 --- a/docs/cybersecurity/research/SIEM-research.md +++ b/docs/cybersecurity/Blue Team/Research/SIEM-research.md @@ -80,4 +80,4 @@ Google SIEM system is a great security tool the company will significantly benef - Mokalled, H., Catelli, R., Casola, V., Debertol, D., Meda, E., & Zunino, R. (2020). The Guidelines to Adopt an Applicable SIEM Solution. Journal of Information Security, 11(01), 46–70. https://doi.org/10.4236/jis.2020.111003 -- Caldeira, H. (2021). Security Information and Event Management (SIEM) Implementation Recommendations to Enhance Network Security - ProQuest. Www.proquest.com. https://www.proquest.com/openview/9e4526ef3c8c179fc9128f72132a9eee/1?pq-origsite=gscholar&cbl=18750&diss=y \ No newline at end of file +- Caldeira, H. (2021). Security Information and Event Management (SIEM) Implementation Recommendations to Enhance Network Security - ProQuest. Www.proquest.com. https://www.proquest.com/openview/9e4526ef3c8c179fc9128f72132a9eee/1?pq-origsite=gscholar&cbl=18750&diss=y diff --git a/docs/cybersecurity/research/Threat Intelligence.md b/docs/cybersecurity/Blue Team/Research/Threat Intelligence.md similarity index 96% rename from docs/cybersecurity/research/Threat Intelligence.md rename to docs/cybersecurity/Blue Team/Research/Threat Intelligence.md index 79c97a515..25755b939 100644 --- a/docs/cybersecurity/research/Threat Intelligence.md +++ b/docs/cybersecurity/Blue Team/Research/Threat Intelligence.md @@ -44,11 +44,11 @@ Considering them to be the threats to **Redback Organization**, and being the th ![](img\ti-2.png) -![](img\ti-3.png.jpg) +![](img\ti-3.png) -![](img\ti-4.png.jpg) +![](img\ti-4.png) -![](img\ti-5.png.jpg) +![](img\ti-5.png) After getting some latest search results, I will begin with collecting **IOCs** and share them afterward with the team to block them. @@ -73,24 +73,24 @@ Let's begin hunting some IOCs using **FOFA**, **Validin**, and **VirusTotal**: The IOC `mxuconlinegame[.]com` is used to collect more IOCs relevant to it. 1. Search IOC on **FOFA**. -![](img\ti-6.png.jpg) +![](img\ti-6.png) 2. Analyze the information that can be used to hunt more IOCs as shown in Figure 7. -![](img\ti-7.png.jpg) +![](img\ti-7.png) 3. Create a query of the common patterns to search for more relevant IOCs. The goal is to filter out until the most prominent results are acquired. -![](img\ti-8.png.jpg) +![](img\ti-8.png) 4. Collect the results and analyze them further on **VirusTotal** and **Qianxin**. The following are the newly hunted IOCs: - `patch-manger[.]com` - `ferrinonlinemuseum[.]com` - `82.221.136.1` - `82.221.136.47` -![](img\ti-9.png.jpg) +![](img\ti-9.png) 5. Search further about the identified IOCs. -![](img\ti-10.png.jpg) -![](img\ti-11.png.jpg) +![](img\ti-10.png) +![](img\ti-11.png) After analyzing further, it was concluded that these IPs and domains belong to **APT Bitter**, and they are acting as **C2 Servers**. @@ -115,4 +115,5 @@ There are further tools and platforms that are collectively used for threat inte - [FOFA](https://en.fofa.info) -- [VirusTotal](https://www.virustotal.com) \ No newline at end of file +- [VirusTotal](https://www.virustotal.com) + diff --git a/docs/cybersecurity/Blue Team/Research/Wazuh - MISP Integration/Wazuh - MISP Integration.md b/docs/cybersecurity/Blue Team/Research/Wazuh - MISP Integration/Wazuh - MISP Integration.md index 801cc943c..bdb5327ab 100644 --- a/docs/cybersecurity/Blue Team/Research/Wazuh - MISP Integration/Wazuh - MISP Integration.md +++ b/docs/cybersecurity/Blue Team/Research/Wazuh - MISP Integration/Wazuh - MISP Integration.md @@ -452,3 +452,4 @@ allowfullscreen> + diff --git a/docs/cybersecurity/research/google-compute-engine.md b/docs/cybersecurity/Blue Team/Research/google-compute-engine.md similarity index 99% rename from docs/cybersecurity/research/google-compute-engine.md rename to docs/cybersecurity/Blue Team/Research/google-compute-engine.md index 06cb4bb8f..5911aabb0 100644 --- a/docs/cybersecurity/research/google-compute-engine.md +++ b/docs/cybersecurity/Blue Team/Research/google-compute-engine.md @@ -218,3 +218,4 @@ go to “Manage nodes and clouds”->”Configure Clouds”->”Advanced…”, [3] Jagrat, “Jenkins build jobs - how to create and trigger build jobs in Jenkins?,” TOOLSQA, 11-Dec-2022. [Online]. Available: https://www.toolsqa.com/jenkins/jenkins-build-jobs/. [Accessed: 11-Dec-2022]. [4] “Using Jenkins for distributed builds on Compute engine | cloud architecture center | google cloud,” Google. [Online]. Available: https://cloud.google.com/architecture/using-jenkins-for-distributed-builds-on-compute-engine. [Accessed: 11-Dec-2022]. + diff --git a/docs/cybersecurity/research/img/LAN.PNG b/docs/cybersecurity/Blue Team/Research/img/LAN.PNG similarity index 100% rename from docs/cybersecurity/research/img/LAN.PNG rename to docs/cybersecurity/Blue Team/Research/img/LAN.PNG diff --git a/docs/cybersecurity/research/img/action.PNG b/docs/cybersecurity/Blue Team/Research/img/action.PNG similarity index 100% rename from docs/cybersecurity/research/img/action.PNG rename to docs/cybersecurity/Blue Team/Research/img/action.PNG diff --git a/docs/cybersecurity/research/img/chronical.png b/docs/cybersecurity/Blue Team/Research/img/chronical.png similarity index 100% rename from docs/cybersecurity/research/img/chronical.png rename to docs/cybersecurity/Blue Team/Research/img/chronical.png diff --git a/docs/cybersecurity/research/img/compute-error.png b/docs/cybersecurity/Blue Team/Research/img/compute-error.png similarity index 100% rename from docs/cybersecurity/research/img/compute-error.png rename to docs/cybersecurity/Blue Team/Research/img/compute-error.png diff --git a/docs/cybersecurity/research/img/compute-output.png b/docs/cybersecurity/Blue Team/Research/img/compute-output.png similarity index 100% rename from docs/cybersecurity/research/img/compute-output.png rename to docs/cybersecurity/Blue Team/Research/img/compute-output.png diff --git a/docs/cybersecurity/research/img/compute-plugin.png b/docs/cybersecurity/Blue Team/Research/img/compute-plugin.png similarity index 100% rename from docs/cybersecurity/research/img/compute-plugin.png rename to docs/cybersecurity/Blue Team/Research/img/compute-plugin.png diff --git a/docs/cybersecurity/research/img/compute-troubleshoot.png b/docs/cybersecurity/Blue Team/Research/img/compute-troubleshoot.png similarity index 100% rename from docs/cybersecurity/research/img/compute-troubleshoot.png rename to docs/cybersecurity/Blue Team/Research/img/compute-troubleshoot.png diff --git a/docs/cybersecurity/research/img/google-chronical.png b/docs/cybersecurity/Blue Team/Research/img/google-chronical.png similarity index 100% rename from docs/cybersecurity/research/img/google-chronical.png rename to docs/cybersecurity/Blue Team/Research/img/google-chronical.png diff --git a/docs/cybersecurity/research/img/iam-service.png b/docs/cybersecurity/Blue Team/Research/img/iam-service.png similarity index 100% rename from docs/cybersecurity/research/img/iam-service.png rename to docs/cybersecurity/Blue Team/Research/img/iam-service.png diff --git a/docs/cybersecurity/research/img/ids.PNG b/docs/cybersecurity/Blue Team/Research/img/ids.PNG similarity index 100% rename from docs/cybersecurity/research/img/ids.PNG rename to docs/cybersecurity/Blue Team/Research/img/ids.PNG diff --git a/docs/cybersecurity/research/img/kea.PNG b/docs/cybersecurity/Blue Team/Research/img/kea.PNG similarity index 100% rename from docs/cybersecurity/research/img/kea.PNG rename to docs/cybersecurity/Blue Team/Research/img/kea.PNG diff --git a/docs/cybersecurity/research/img/login-pf.PNG b/docs/cybersecurity/Blue Team/Research/img/login-pf.PNG similarity index 100% rename from docs/cybersecurity/research/img/login-pf.PNG rename to docs/cybersecurity/Blue Team/Research/img/login-pf.PNG diff --git a/docs/cybersecurity/research/img/name-os.PNG b/docs/cybersecurity/Blue Team/Research/img/name-os.PNG similarity index 100% rename from docs/cybersecurity/research/img/name-os.PNG rename to docs/cybersecurity/Blue Team/Research/img/name-os.PNG diff --git a/docs/cybersecurity/research/img/net-disc.PNG b/docs/cybersecurity/Blue Team/Research/img/net-disc.PNG similarity index 100% rename from docs/cybersecurity/research/img/net-disc.PNG rename to docs/cybersecurity/Blue Team/Research/img/net-disc.PNG diff --git a/docs/cybersecurity/research/img/new-install.PNG b/docs/cybersecurity/Blue Team/Research/img/new-install.PNG similarity index 100% rename from docs/cybersecurity/research/img/new-install.PNG rename to docs/cybersecurity/Blue Team/Research/img/new-install.PNG diff --git a/docs/cybersecurity/research/img/pfsense-home.PNG b/docs/cybersecurity/Blue Team/Research/img/pfsense-home.PNG similarity index 100% rename from docs/cybersecurity/research/img/pfsense-home.PNG rename to docs/cybersecurity/Blue Team/Research/img/pfsense-home.PNG diff --git a/docs/cybersecurity/research/img/putty.PNG b/docs/cybersecurity/Blue Team/Research/img/putty.PNG similarity index 100% rename from docs/cybersecurity/research/img/putty.PNG rename to docs/cybersecurity/Blue Team/Research/img/putty.PNG diff --git a/docs/cybersecurity/research/img/siem-1.png b/docs/cybersecurity/Blue Team/Research/img/siem-1.png similarity index 100% rename from docs/cybersecurity/research/img/siem-1.png rename to docs/cybersecurity/Blue Team/Research/img/siem-1.png diff --git a/docs/cybersecurity/research/img/siem-2.png b/docs/cybersecurity/Blue Team/Research/img/siem-2.png similarity index 100% rename from docs/cybersecurity/research/img/siem-2.png rename to docs/cybersecurity/Blue Team/Research/img/siem-2.png diff --git a/docs/cybersecurity/research/img/siem.png b/docs/cybersecurity/Blue Team/Research/img/siem.png similarity index 100% rename from docs/cybersecurity/research/img/siem.png rename to docs/cybersecurity/Blue Team/Research/img/siem.png diff --git a/docs/cybersecurity/research/img/ssh.PNG b/docs/cybersecurity/Blue Team/Research/img/ssh.PNG similarity index 100% rename from docs/cybersecurity/research/img/ssh.PNG rename to docs/cybersecurity/Blue Team/Research/img/ssh.PNG diff --git a/docs/cybersecurity/research/img/ti-1.png b/docs/cybersecurity/Blue Team/Research/img/ti-1.png similarity index 100% rename from docs/cybersecurity/research/img/ti-1.png rename to docs/cybersecurity/Blue Team/Research/img/ti-1.png diff --git a/docs/cybersecurity/research/img/ti-10.png.jpg b/docs/cybersecurity/Blue Team/Research/img/ti-10.png similarity index 100% rename from docs/cybersecurity/research/img/ti-10.png.jpg rename to docs/cybersecurity/Blue Team/Research/img/ti-10.png diff --git a/docs/cybersecurity/research/img/ti-11.png.jpg b/docs/cybersecurity/Blue Team/Research/img/ti-11.png similarity index 100% rename from docs/cybersecurity/research/img/ti-11.png.jpg rename to docs/cybersecurity/Blue Team/Research/img/ti-11.png diff --git a/docs/cybersecurity/research/img/ti-2.png b/docs/cybersecurity/Blue Team/Research/img/ti-2.png similarity index 100% rename from docs/cybersecurity/research/img/ti-2.png rename to docs/cybersecurity/Blue Team/Research/img/ti-2.png diff --git a/docs/cybersecurity/research/img/ti-3.png.jpg b/docs/cybersecurity/Blue Team/Research/img/ti-3.png similarity index 100% rename from docs/cybersecurity/research/img/ti-3.png.jpg rename to docs/cybersecurity/Blue Team/Research/img/ti-3.png diff --git a/docs/cybersecurity/research/img/ti-4.png.jpg b/docs/cybersecurity/Blue Team/Research/img/ti-4.png similarity index 100% rename from docs/cybersecurity/research/img/ti-4.png.jpg rename to docs/cybersecurity/Blue Team/Research/img/ti-4.png diff --git a/docs/cybersecurity/research/img/ti-5.png.jpg b/docs/cybersecurity/Blue Team/Research/img/ti-5.png similarity index 100% rename from docs/cybersecurity/research/img/ti-5.png.jpg rename to docs/cybersecurity/Blue Team/Research/img/ti-5.png diff --git a/docs/cybersecurity/research/img/ti-6.png.jpg b/docs/cybersecurity/Blue Team/Research/img/ti-6.png similarity index 100% rename from docs/cybersecurity/research/img/ti-6.png.jpg rename to docs/cybersecurity/Blue Team/Research/img/ti-6.png diff --git a/docs/cybersecurity/research/img/ti-7.png.jpg b/docs/cybersecurity/Blue Team/Research/img/ti-7.png similarity index 100% rename from docs/cybersecurity/research/img/ti-7.png.jpg rename to docs/cybersecurity/Blue Team/Research/img/ti-7.png diff --git a/docs/cybersecurity/research/img/ti-8.png.jpg b/docs/cybersecurity/Blue Team/Research/img/ti-8.png similarity index 100% rename from docs/cybersecurity/research/img/ti-8.png.jpg rename to docs/cybersecurity/Blue Team/Research/img/ti-8.png diff --git a/docs/cybersecurity/research/img/ti-9.png.jpg b/docs/cybersecurity/Blue Team/Research/img/ti-9.png similarity index 100% rename from docs/cybersecurity/research/img/ti-9.png.jpg rename to docs/cybersecurity/Blue Team/Research/img/ti-9.png diff --git a/docs/cybersecurity/research/img/tpm-application.png b/docs/cybersecurity/Blue Team/Research/img/tpm-application.png similarity index 100% rename from docs/cybersecurity/research/img/tpm-application.png rename to docs/cybersecurity/Blue Team/Research/img/tpm-application.png diff --git a/docs/cybersecurity/research/img/virtual.PNG b/docs/cybersecurity/Blue Team/Research/img/virtual.PNG similarity index 100% rename from docs/cybersecurity/research/img/virtual.PNG rename to docs/cybersecurity/Blue Team/Research/img/virtual.PNG diff --git a/docs/cybersecurity/research/img/wizard.PNG b/docs/cybersecurity/Blue Team/Research/img/wizard.PNG similarity index 100% rename from docs/cybersecurity/research/img/wizard.PNG rename to docs/cybersecurity/Blue Team/Research/img/wizard.PNG diff --git a/docs/cybersecurity/research/img/zfs-conf.PNG b/docs/cybersecurity/Blue Team/Research/img/zfs-conf.PNG similarity index 100% rename from docs/cybersecurity/research/img/zfs-conf.PNG rename to docs/cybersecurity/Blue Team/Research/img/zfs-conf.PNG diff --git a/docs/cybersecurity/research/pFsense-configuration.md b/docs/cybersecurity/Blue Team/Research/pFsense-configuration.md similarity index 99% rename from docs/cybersecurity/research/pFsense-configuration.md rename to docs/cybersecurity/Blue Team/Research/pFsense-configuration.md index f5dc95b0b..2c4fb307a 100644 --- a/docs/cybersecurity/research/pFsense-configuration.md +++ b/docs/cybersecurity/Blue Team/Research/pFsense-configuration.md @@ -140,3 +140,4 @@ As shown in the **Blocked** tab we have blocked pings by snort after using ping: 6. Once the settings have been applied, scroll down and click save. If done correctly, there should not be any errors preventing you from saving. 7. Now check for connectivity with your LDAP, to do that stay in the user manager tab and navigate to **settings** 8. Select your LDAP server in the **Authentication Server** drop down box. scroll down and select **Save & Test**, if successful, you should see you have made connection to your LDAP. + diff --git a/docs/cybersecurity/research/pFsense-install-guide.md b/docs/cybersecurity/Blue Team/Research/pFsense-install-guide.md similarity index 99% rename from docs/cybersecurity/research/pFsense-install-guide.md rename to docs/cybersecurity/Blue Team/Research/pFsense-install-guide.md index 68cd6fc57..16da41809 100644 --- a/docs/cybersecurity/research/pFsense-install-guide.md +++ b/docs/cybersecurity/Blue Team/Research/pFsense-install-guide.md @@ -141,4 +141,4 @@ vm_fault: page read error, pid 1 (init) ``` If you are facing other issues that are not here, you can find more troubleshooting guides using NetGate Docs: -[Netgate Docs](https://docs.netgate.com/pfsense/en/latest/troubleshooting/index.html) \ No newline at end of file +[Netgate Docs](https://docs.netgate.com/pfsense/en/latest/troubleshooting/index.html) diff --git a/docs/cybersecurity/research/siems-google-chronical.md b/docs/cybersecurity/Blue Team/Research/siems-google-chronical.md similarity index 99% rename from docs/cybersecurity/research/siems-google-chronical.md rename to docs/cybersecurity/Blue Team/Research/siems-google-chronical.md index fa3fa334f..8e15f22f7 100644 --- a/docs/cybersecurity/research/siems-google-chronical.md +++ b/docs/cybersecurity/Blue Team/Research/siems-google-chronical.md @@ -80,3 +80,4 @@ In conclusion, SIEMs can be extremely beneficial to safeguard and monitor the se [6] Google Cloud (n.d.). Log in to Chronicle [Website]. Available: URL https://cloud.google.com/chronicle/docs/log-in-to-ui [7] LOGPOINT (n.d.). What is SIEM? A complete guide to Security Information and Event Management [Website]. Available: URL https://www.logpoint.com/en/understand/what-is-siem/ + diff --git a/docs/cybersecurity/research/tpm-research.md b/docs/cybersecurity/Blue Team/Research/tpm-research.md similarity index 99% rename from docs/cybersecurity/research/tpm-research.md rename to docs/cybersecurity/Blue Team/Research/tpm-research.md index 0f9d29636..2bed2da59 100644 --- a/docs/cybersecurity/research/tpm-research.md +++ b/docs/cybersecurity/Blue Team/Research/tpm-research.md @@ -233,3 +233,4 @@ To mitigate these few known issues, we have made some recommendations for Redbac [39] "LUKS on Raspberry Pi", LUKS-on-Raspberry-Pi, 2021. [Online]. Available: https://rr-developer.github.io/LUKS-on-Raspberry-Pi/. [Accessed: 20- Aug- 2022] [40] "Raspbian Stretch Luks Encrypt [solved] - Raspberry Pi Forums", Forums.raspberrypi.com, 2018. [Online]. Available: https://forums.raspberrypi.com/viewtopic.php?t=219867. [Accessed: 20- Aug- 2022] + diff --git a/docs/cybersecurity/research/virtual-private-cloud.md b/docs/cybersecurity/Blue Team/Research/virtual-private-cloud.md similarity index 99% rename from docs/cybersecurity/research/virtual-private-cloud.md rename to docs/cybersecurity/Blue Team/Research/virtual-private-cloud.md index e25105476..af7bd5ae8 100644 --- a/docs/cybersecurity/research/virtual-private-cloud.md +++ b/docs/cybersecurity/Blue Team/Research/virtual-private-cloud.md @@ -102,3 +102,4 @@ https://www.ringcentral.com/gb/en/blog/definitions/virtual-private-cloud/ https://www.cloudflare.com/learning/network-layer/what-is-a-subnet/ https://www.accessagility.com/blog/benefits-of-subnetting#:~:text=Subnetting%20is%20the%20practice%20of,control%2C%20and%20improving%20network%20security. https://www.youtube.com/watch?v=ujXr0i5EoHE&ab_channel=CloudAcademy + diff --git a/docs/cybersecurity/Ethics Team/Asset Assessment Project/Implementation of Dummy Data Generator.md b/docs/cybersecurity/Ethics Team/Asset Assessment Project/Implementation of Dummy Data Generator.md index d48866277..fa80cfd7c 100644 --- a/docs/cybersecurity/Ethics Team/Asset Assessment Project/Implementation of Dummy Data Generator.md +++ b/docs/cybersecurity/Ethics Team/Asset Assessment Project/Implementation of Dummy Data Generator.md @@ -103,3 +103,4 @@ 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. + diff --git a/docs/cybersecurity/Ethics Team/Asset Assessment Project/Project Overview.md b/docs/cybersecurity/Ethics Team/Asset Assessment Project/Project Overview.md index e918d0f59..86ad55f02 100644 --- a/docs/cybersecurity/Ethics Team/Asset Assessment Project/Project Overview.md +++ b/docs/cybersecurity/Ethics Team/Asset Assessment Project/Project Overview.md @@ -97,3 +97,4 @@ The **Redback Asset Assessment** revolutionizes data protection by making data s It is designed for **seamless integration** with existing company workflows to reduce data breach risks and ensure compliance as the company scales and evolves. + diff --git a/docs/cybersecurity/Ethics Team/Cross-Team Legal Advice/Project Overview.md b/docs/cybersecurity/Ethics Team/Cross-Team Legal Advice/Project Overview.md index a4636fd99..5803bf26d 100644 --- a/docs/cybersecurity/Ethics Team/Cross-Team Legal Advice/Project Overview.md +++ b/docs/cybersecurity/Ethics Team/Cross-Team Legal Advice/Project Overview.md @@ -83,4 +83,4 @@ The project aims to help Redback: ## 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. \ No newline at end of file +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. diff --git a/docs/cybersecurity/GRC Team/CI-CD-Implementation/Implementation Guide.md b/docs/cybersecurity/GRC Team/CI-CD-Implementation/Implementation Guide.md index 1de52a955..7c3afddea 100644 --- a/docs/cybersecurity/GRC Team/CI-CD-Implementation/Implementation Guide.md +++ b/docs/cybersecurity/GRC Team/CI-CD-Implementation/Implementation Guide.md @@ -182,3 +182,4 @@ Verifying the pipeline execution ensures that the CI/CD process is functioning a ### References - Docker 2024. Docker Documentation. Available at: [https://docs.docker.com/](https://docs.docker.com/). + diff --git a/docs/cybersecurity/GRC Team/CI-CD-Implementation/Implementation Proof.md b/docs/cybersecurity/GRC Team/CI-CD-Implementation/Implementation Proof.md index 123603727..ec96e1622 100644 --- a/docs/cybersecurity/GRC Team/CI-CD-Implementation/Implementation Proof.md +++ b/docs/cybersecurity/GRC Team/CI-CD-Implementation/Implementation Proof.md @@ -133,3 +133,4 @@ In this screenshot, the user retrieves the Jenkins initial admin password using ## Ready to Build and Run ![Figure 16](./img/Pi16.png) + diff --git a/docs/cybersecurity/GRC Team/Essential 8-Proposal/Essential 8_Proposal.md b/docs/cybersecurity/GRC Team/Essential 8-Proposal/Essential 8_Proposal.md index cb43aa3e1..f506a53f6 100644 --- a/docs/cybersecurity/GRC Team/Essential 8-Proposal/Essential 8_Proposal.md +++ b/docs/cybersecurity/GRC Team/Essential 8-Proposal/Essential 8_Proposal.md @@ -197,3 +197,4 @@ By implementing these targeted Essential 8 strategies and moving towards Maturit - Increased cyber-awareness and disciplined security practices across the team Cybersecurity doesn’t have to be complicated to make a big impact. By building these simple, practical habits into our day-to-day work, Redback is setting itself up for a safer, more resilient future. + diff --git a/docs/cybersecurity/GRC Team/GRC-Team-Audits/Athlete Wearable Technology Project 1.md b/docs/cybersecurity/GRC Team/GRC-Team-Audits/Athlete Wearable Technology Project 1.md index fcb0cd2a5..f75f1fe13 100644 --- a/docs/cybersecurity/GRC Team/GRC-Team-Audits/Athlete Wearable Technology Project 1.md +++ b/docs/cybersecurity/GRC Team/GRC-Team-Audits/Athlete Wearable Technology Project 1.md @@ -93,3 +93,4 @@ The audit gave significant insights into the Athlete Wearable Technology project - **User Awareness Training:** While initial training was implemented, the team did not review the Cybersecurity Awareness Training document. It will be vital for team members to be trained on the policies and procedures. Overall, the project displays compliance in some areas, but the existing lack of data collecting has slowed down the development of more complete security standards. As the project progresses, resolving the identified gaps and recommendations will be critical to improving the integrity and security of the Athlete Wearable Technology Project. + diff --git a/docs/cybersecurity/GRC Team/GRC-Team-Audits/Athlete Wearable Technology Project.md b/docs/cybersecurity/GRC Team/GRC-Team-Audits/Athlete Wearable Technology Project.md index 40f901824..ac254c427 100644 --- a/docs/cybersecurity/GRC Team/GRC-Team-Audits/Athlete Wearable Technology Project.md +++ b/docs/cybersecurity/GRC Team/GRC-Team-Audits/Athlete Wearable Technology Project.md @@ -95,3 +95,4 @@ The audit gave significant insights into the Athlete Wearable Technology project - **User Awareness Training:** While initial training was implemented, the team did not review the Cybersecurity Awareness Training document. It will be vital for team members to be trained on the policies and procedures. Overall, the project displays compliance in some areas, but the existing lack of data collecting has slowed down the development of more complete security standards. As the project progresses, resolving the identified gaps and recommendations will be critical to improving the integrity and security of the Athlete Wearable Technology Project. + diff --git a/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit Templates/annual-audit-checklist.md b/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit Templates/annual-audit-checklist.md index 61681ac00..8769c4d2e 100644 --- a/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit Templates/annual-audit-checklist.md +++ b/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit Templates/annual-audit-checklist.md @@ -81,3 +81,4 @@ - **Notes:** > _Add notes here during audit._ + diff --git a/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit Templates/as-needed-audit-checklist.md b/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit Templates/as-needed-audit-checklist.md index 3bf34287f..22577dd4e 100644 --- a/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit Templates/as-needed-audit-checklist.md +++ b/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit Templates/as-needed-audit-checklist.md @@ -81,3 +81,4 @@ - **Notes:** > _Add notes here during audit._ + diff --git a/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit Templates/audit-template.md b/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit Templates/audit-template.md index 6e571d612..ca5fc5a3f 100644 --- a/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit Templates/audit-template.md +++ b/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit Templates/audit-template.md @@ -64,4 +64,4 @@ The structure for the General Audit Points section should be used. After the audit has been completed, a report needs to be formed. The structure of this report can be sourced from existing reports, though the video link below includes a tutorial on how to conduct the audit and formulate an audit report. -**Link:** https://youtu.be/FvGHO3ixBo8 \ No newline at end of file +**Link:** https://youtu.be/FvGHO3ixBo8 diff --git a/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit Templates/bi-annual-audit-checklist.md b/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit Templates/bi-annual-audit-checklist.md index f73fceab4..440abe16d 100644 --- a/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit Templates/bi-annual-audit-checklist.md +++ b/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit Templates/bi-annual-audit-checklist.md @@ -29,3 +29,4 @@ - **Notes:** > _Add notes here during audit._ + diff --git a/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit Templates/daily-audit-checklist.md b/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit Templates/daily-audit-checklist.md index eef603f11..79510f5bc 100644 --- a/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit Templates/daily-audit-checklist.md +++ b/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit Templates/daily-audit-checklist.md @@ -105,3 +105,4 @@ - **Notes:** > _Add notes here during audit._ + diff --git a/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit Templates/fortnightly-audit-checklist.md b/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit Templates/fortnightly-audit-checklist.md index d385be4ed..372332925 100644 --- a/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit Templates/fortnightly-audit-checklist.md +++ b/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit Templates/fortnightly-audit-checklist.md @@ -103,3 +103,4 @@ - **Notes:** > _Add notes here during audit._ + diff --git a/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit Templates/monthly-audit-checklist.md b/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit Templates/monthly-audit-checklist.md index a4d5b0da7..d4b551356 100644 --- a/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit Templates/monthly-audit-checklist.md +++ b/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit Templates/monthly-audit-checklist.md @@ -277,3 +277,4 @@ - **Notes:** > _Add notes here during audit._ + diff --git a/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit Templates/quarterly-audit-checklist.md b/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit Templates/quarterly-audit-checklist.md index 589d0c8c8..323a7690e 100644 --- a/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit Templates/quarterly-audit-checklist.md +++ b/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit Templates/quarterly-audit-checklist.md @@ -468,3 +468,4 @@ > _Add notes here during audit._ + diff --git a/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit Templates/weekly-audit-checklist.md b/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit Templates/weekly-audit-checklist.md index 77d26fb3a..f5ba561b0 100644 --- a/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit Templates/weekly-audit-checklist.md +++ b/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit Templates/weekly-audit-checklist.md @@ -129,3 +129,4 @@ - **Notes:** > _Add notes here during audit._ + diff --git a/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit _Policy/Redback_Operations_Audit_Policy.md b/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit _Policy/Redback_Operations_Audit_Policy.md index 74ce7bc46..3e9cbf46b 100644 --- a/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit _Policy/Redback_Operations_Audit_Policy.md +++ b/docs/cybersecurity/GRC Team/GRC-Team-Audits/Audit _Policy/Redback_Operations_Audit_Policy.md @@ -271,3 +271,4 @@ All sanctions are logged in the Audit Register. **Cybersecurity GRC Team** 📄 [Redback Documentation](https://redback-operations.github.io/redback-documentation/) + diff --git a/docs/cybersecurity/GRC Team/GRC-Team-Audits/Data-Warehousing-Audit.md b/docs/cybersecurity/GRC Team/GRC-Team-Audits/Data-Warehousing-Audit.md index b91921aa5..4ba8999f2 100644 --- a/docs/cybersecurity/GRC Team/GRC-Team-Audits/Data-Warehousing-Audit.md +++ b/docs/cybersecurity/GRC Team/GRC-Team-Audits/Data-Warehousing-Audit.md @@ -184,3 +184,4 @@ Finally, referring to the general governance points, there should be regular ris After the audit, a few more questions were asked to gain a better understanding of the direction that the Data Warehousing team aims to take. Kaylin ended by saying that he and his team “want to have governance and the correct security in place to be an elite team, and an elite project”. He wants their service to be a “self-service for employees”, and to have cloud storage and access to make it easier to “provide a service to the rest of the projects as somewhere that they can store and access their data”. + diff --git a/docs/cybersecurity/GRC Team/GRC-Team-Audits/Essential 8 Assesment/Assessment Report/Essential 8 ML1 Data Warehouse Team.md b/docs/cybersecurity/GRC Team/GRC-Team-Audits/Essential 8 Assesment/Assessment Report/Essential 8 ML1 Data Warehouse Team.md index ea94075c9..dd9a50759 100644 --- a/docs/cybersecurity/GRC Team/GRC-Team-Audits/Essential 8 Assesment/Assessment Report/Essential 8 ML1 Data Warehouse Team.md +++ b/docs/cybersecurity/GRC Team/GRC-Team-Audits/Essential 8 Assesment/Assessment Report/Essential 8 ML1 Data Warehouse Team.md @@ -134,3 +134,4 @@ We acknowledge the support and contributions of the following entities and commu - **Traditional Owners of the Land** – We pay our respects to the Wadawurrung people, the Traditional Custodians of the land on which we study and work, and honour their enduring connection to land, waters, and culture. --- + diff --git a/docs/cybersecurity/GRC Team/GRC-Team-Audits/Essential 8 Assesment/Assessment Report/Redback_E8_ML1_Data_Warehousing_Checklist.md b/docs/cybersecurity/GRC Team/GRC-Team-Audits/Essential 8 Assesment/Assessment Report/Redback_E8_ML1_Data_Warehousing_Checklist.md index 1e348c222..cb605165f 100644 --- a/docs/cybersecurity/GRC Team/GRC-Team-Audits/Essential 8 Assesment/Assessment Report/Redback_E8_ML1_Data_Warehousing_Checklist.md +++ b/docs/cybersecurity/GRC Team/GRC-Team-Audits/Essential 8 Assesment/Assessment Report/Redback_E8_ML1_Data_Warehousing_Checklist.md @@ -167,3 +167,4 @@ sidebar_position: 1 | Patch Operating Systems | ML1-PO | ML1-PO-08 | ISM-1691 | Workstation and server OS patches are applied within one month of release. | Match scan output with patch application dates; check backlog or exceptions. | Patch cycle report, dashboard exports. | WSUS, Linux YUM/APT Logs | ⛔ Not Applicable | Not applicable – No monthly OS patching is handled by Redback Operations. This is managed by Deakin’s system administrators. | \\share\redback-evidence\ML1-PO-sample.pdf | 2025-05-17 00:00:00 | Shreyas Vivek/Daezel Goyal | | Patch Operating Systems | ML1-PO | ML1-PO-09 | ISM-1691 | No OS vulnerabilities older than one month exist in any production environment. | Run full authenticated vulnerability scan and compare to patch registry. | Vulnerability scan logs, remediation reports. | Qualys, Nessus | ⛔ Not Applicable | Not applicable – No scan reports or CVE compliance data are generated or reviewed by the Redback team. | \\share\redback-evidence\ML1-PO-sample.pdf | 2025-05-17 00:00:00 | Shreyas Vivek/Daezel Goyal | | Patch Operating Systems | ML1-PO | ML1-PO-10 | ISM-1905 | Unsupported operating systems are replaced or removed from the environment. | Compare list of active systems with vendor lifecycle documentation. | System inventory, vendor EOL documentation. | CMDB, OS Scan Tools | ⚠️ Partially Implemented | Partially implemented – The current VM is running a supported Ubuntu LTS version. However, there is no formal tracking or decommissioning process managed by Redback. OS lifecycle is assumed to be monitored by Deakin IT. | \\share\redback-evidence\ML1-PO-sample.pdf | 2025-05-17 00:00:00 | Shreyas Vivek/Daezel Goyal | + diff --git a/docs/cybersecurity/GRC Team/GRC-Team-Audits/Essential 8 Assesment/Master Checklist/Redback_E8_ML1_Assessment_Checklist.md b/docs/cybersecurity/GRC Team/GRC-Team-Audits/Essential 8 Assesment/Master Checklist/Redback_E8_ML1_Assessment_Checklist.md index 86391af24..be02ed5a9 100644 --- a/docs/cybersecurity/GRC Team/GRC-Team-Audits/Essential 8 Assesment/Master Checklist/Redback_E8_ML1_Assessment_Checklist.md +++ b/docs/cybersecurity/GRC Team/GRC-Team-Audits/Essential 8 Assesment/Master Checklist/Redback_E8_ML1_Assessment_Checklist.md @@ -166,3 +166,4 @@ sidebar_position: 1 | Patch Operating Systems | ML1-PO | ML1-PO-08 | ISM-1691 | Workstation and server OS patches are applied within one month of release. | Match scan output with patch application dates; check backlog or exceptions. | Patch cycle report, dashboard exports. | WSUS, Linux YUM/APT Logs | DevSecOps | Monthly | All systems patched within 30-day window. No exceptions pending. | nan | | Patch Operating Systems | ML1-PO | ML1-PO-09 | ISM-1691 | No OS vulnerabilities older than one month exist in any production environment. | Run full authenticated vulnerability scan and compare to patch registry. | Vulnerability scan logs, remediation reports. | Qualys, Nessus | DevSecOps | Monthly | Scan logs confirm 0 critical vulnerabilities 30 days. | nan | | Patch Operating Systems | ML1-PO | ML1-PO-10 | ISM-1905 | Unsupported operating systems are replaced or removed from the environment. | Compare list of active systems with vendor lifecycle documentation. | System inventory, vendor EOL documentation. | CMDB, OS Scan Tools | DevSecOps | Quarterly | Legacy Windows 2012 decommissioned. CMDB updated. | nan | + diff --git a/docs/cybersecurity/GRC Team/GRC-Team-Audits/Player-Tracking-Audit.md b/docs/cybersecurity/GRC Team/GRC-Team-Audits/Player-Tracking-Audit.md index d8e55afe1..aefc0245c 100644 --- a/docs/cybersecurity/GRC Team/GRC-Team-Audits/Player-Tracking-Audit.md +++ b/docs/cybersecurity/GRC Team/GRC-Team-Audits/Player-Tracking-Audit.md @@ -463,4 +463,4 @@ Many of the non-compliant audit points are due to a lack of knowledge or awarene A prospective idea that Vincent and I discussed was assigning a member of the cyber security team to each specific project for a trimester, this way that team member could work with the projects to build awareness and understanding of these policies, uplift their cyber security posture and deliver on many of the recommendations provided by the cyber audits the GRC team has completed this trimester. -Overall, the experience of completing this audit has been highly rewarding from both the perspective of the GRC/Cyber Security Team and the individual projects outside of this. I feel it has helped build awareness of the ever increasing risks of cyber security, and the strong emphasis that should be placed on ensuring compliance with the companies cyber security policies and frameworks, across all projects and teams within Redback Operations. I hope the results of these audits are built upon in future trimesters and can act as a gap analysis for future cyber security team members to uplift compliance within the projects. \ No newline at end of file +Overall, the experience of completing this audit has been highly rewarding from both the perspective of the GRC/Cyber Security Team and the individual projects outside of this. I feel it has helped build awareness of the ever increasing risks of cyber security, and the strong emphasis that should be placed on ensuring compliance with the companies cyber security policies and frameworks, across all projects and teams within Redback Operations. I hope the results of these audits are built upon in future trimesters and can act as a gap analysis for future cyber security team members to uplift compliance within the projects. diff --git a/docs/cybersecurity/GRC Team/GRC-Team-Audits/Vr-Sun-Cycle-Audit.md b/docs/cybersecurity/GRC Team/GRC-Team-Audits/Vr-Sun-Cycle-Audit.md index 351e0663f..ed1a3685f 100644 --- a/docs/cybersecurity/GRC Team/GRC-Team-Audits/Vr-Sun-Cycle-Audit.md +++ b/docs/cybersecurity/GRC Team/GRC-Team-Audits/Vr-Sun-Cycle-Audit.md @@ -150,3 +150,4 @@ Overall, the team has been quite successful with the development of their projec - Implement encryption and data protection as the project evolves. - Conduct mandatory User Awareness Training for team members. - Develop a risk management and incident response plan. + diff --git a/docs/cybersecurity/GRC Team/GRC-Team-Audits/audit-report-project-2.md b/docs/cybersecurity/GRC Team/GRC-Team-Audits/audit-report-project-2.md index 1b3a7d93b..f6b273d14 100644 --- a/docs/cybersecurity/GRC Team/GRC-Team-Audits/audit-report-project-2.md +++ b/docs/cybersecurity/GRC Team/GRC-Team-Audits/audit-report-project-2.md @@ -147,4 +147,4 @@ The first and most important step is for all team members to familiarize themsel --- ## Conclusion -The audit of Project 2: Elderly Wearable Technology revealed key gaps in compliance with Redback’s ISMS policies, primarily due to a lack of awareness across both the Data Warehousing and project teams. Ensuring that all team members read and follow the ISMS policies is crucial for improving security practices. With the recommended actions in place, the project can move forward securely, aligned with company standards, and ensuring the protection of data and overall success. \ No newline at end of file +The audit of Project 2: Elderly Wearable Technology revealed key gaps in compliance with Redback’s ISMS policies, primarily due to a lack of awareness across both the Data Warehousing and project teams. Ensuring that all team members read and follow the ISMS policies is crucial for improving security practices. With the recommended actions in place, the project can move forward securely, aligned with company standards, and ensuring the protection of data and overall success. diff --git a/docs/cybersecurity/GRC Team/ISMS-Policy-Implementation-Plans/Active_Directory_Windows_Hardening_Guide.md b/docs/cybersecurity/GRC Team/ISMS-Policy-Implementation-Plans/Active_Directory_Windows_Hardening_Guide.md index c57cf165b..648ed87b7 100644 --- a/docs/cybersecurity/GRC Team/ISMS-Policy-Implementation-Plans/Active_Directory_Windows_Hardening_Guide.md +++ b/docs/cybersecurity/GRC Team/ISMS-Policy-Implementation-Plans/Active_Directory_Windows_Hardening_Guide.md @@ -1302,3 +1302,4 @@ AD replication status should be monitored frequently so that issues do not get u | Bluetooth Service | Disabled | | + diff --git a/docs/cybersecurity/GRC Team/ISMS-Policy-Implementation-Plans/Cryptography-Deployment-Plan.md b/docs/cybersecurity/GRC Team/ISMS-Policy-Implementation-Plans/Cryptography-Deployment-Plan.md index 9f429f8c7..f942868d7 100644 --- a/docs/cybersecurity/GRC Team/ISMS-Policy-Implementation-Plans/Cryptography-Deployment-Plan.md +++ b/docs/cybersecurity/GRC Team/ISMS-Policy-Implementation-Plans/Cryptography-Deployment-Plan.md @@ -54,3 +54,4 @@ As more data is collected by each team, the bigger encryption software the compa --- This deployment plan provides a structured approach to introducing cryptographic tools into Redback Operations, ensuring secure data handling and compliance with industry standards. + diff --git a/docs/cybersecurity/GRC Team/ISMS-Policy-Implementation-Plans/Cryptography-Implementation-Plan.md b/docs/cybersecurity/GRC Team/ISMS-Policy-Implementation-Plans/Cryptography-Implementation-Plan.md index 5e175ab8e..bf8ce13e6 100644 --- a/docs/cybersecurity/GRC Team/ISMS-Policy-Implementation-Plans/Cryptography-Implementation-Plan.md +++ b/docs/cybersecurity/GRC Team/ISMS-Policy-Implementation-Plans/Cryptography-Implementation-Plan.md @@ -82,3 +82,4 @@ sidebar_label: Cryptography Implementation Plan 2024 - [VeraCrypt](https://sourceforge.net/projects/veracrypt/) - [AxCrypt Pricing](https://axcrypt.net/pricing/) - [NordLocker](https://nordlocker.com) + diff --git a/docs/cybersecurity/GRC Team/ISMS-Policy-Implementation-Plans/Implementation plan for Monitoring & Log Analytics.md b/docs/cybersecurity/GRC Team/ISMS-Policy-Implementation-Plans/Implementation plan for Monitoring & Log Analytics.md index bb3c2ca42..aa442b62c 100644 --- a/docs/cybersecurity/GRC Team/ISMS-Policy-Implementation-Plans/Implementation plan for Monitoring & Log Analytics.md +++ b/docs/cybersecurity/GRC Team/ISMS-Policy-Implementation-Plans/Implementation plan for Monitoring & Log Analytics.md @@ -60,3 +60,4 @@ To develop an easy way to implement a cost-effective deployment plan for our Mon - Leanne Mitton, L.M. (2023). Regulatory Compliance 101: What You Need To Know. Splunk Blogs. [Splunk Blog](https://www.splunk.com/en_us/blog/learn/regulatory-compliance.html) - Mezmo. (2024). MONITORING AND LOGGING REQUIREMENTS FOR COMPLIANCE. Regulatory Compliance. [Mezmo](https://www.mezmo.com/learn-observability/monitoring-and-logging-requirements-for-compliance) - Rafal Kuc, R.K. (2023). 15 Best Log Analysis Tools & Log Analyzers of 2024 (Paid, Free & Open Source). Sematext. [Sematext Blog](https://sematext.com/blog/log-analysis-tools/) + diff --git a/docs/cybersecurity/GRC Team/ISMS-Policy-Implementation-Plans/Monitoring & Log Analytics.md b/docs/cybersecurity/GRC Team/ISMS-Policy-Implementation-Plans/Monitoring & Log Analytics.md index 5d4ed9004..9db27dd91 100644 --- a/docs/cybersecurity/GRC Team/ISMS-Policy-Implementation-Plans/Monitoring & Log Analytics.md +++ b/docs/cybersecurity/GRC Team/ISMS-Policy-Implementation-Plans/Monitoring & Log Analytics.md @@ -62,3 +62,4 @@ To develop an easy way to implement a cost-effective deployment plan for our Mon - Leanne Mitton, L.M. (2023). Regulatory Compliance 101: What You Need To Know. Splunk Blogs. [Splunk Blog](https://www.splunk.com/en_us/blog/learn/regulatory-compliance.html) - Mezmo. (2024). MONITORING AND LOGGING REQUIREMENTS FOR COMPLIANCE. Regulatory Compliance. [Mezmo](https://www.mezmo.com/learn-observability/monitoring-and-logging-requirements-for-compliance) - Rafal Kuc, R.K. (2023). 15 Best Log Analysis Tools & Log Analyzers of 2024 (Paid, Free & Open Source). Sematext. [Sematext Blog](https://sematext.com/blog/log-analysis-tools/) + diff --git a/docs/cybersecurity/GRC Team/ISMS-Policy-Implementation-Plans/dlp-data-classification.md b/docs/cybersecurity/GRC Team/ISMS-Policy-Implementation-Plans/dlp-data-classification.md index 67318331d..3b6d1265c 100644 --- a/docs/cybersecurity/GRC Team/ISMS-Policy-Implementation-Plans/dlp-data-classification.md +++ b/docs/cybersecurity/GRC Team/ISMS-Policy-Implementation-Plans/dlp-data-classification.md @@ -95,3 +95,4 @@ To conclude, the implementation of our Data Loss Prevention and Data Classificat This plan should be regularly reviewed and audited to ensure compliance in all areas (this audit can be done every quarter). The overall compliance and implementation of this plan is pivotal for the security and protection of data within Redback Operations. + diff --git a/docs/cybersecurity/GRC Team/ISMS-Policy-Implementation-Plans/dp-endpoint-security.md b/docs/cybersecurity/GRC Team/ISMS-Policy-Implementation-Plans/dp-endpoint-security.md index 8b3ee8e48..d9f55e7b4 100644 --- a/docs/cybersecurity/GRC Team/ISMS-Policy-Implementation-Plans/dp-endpoint-security.md +++ b/docs/cybersecurity/GRC Team/ISMS-Policy-Implementation-Plans/dp-endpoint-security.md @@ -41,4 +41,4 @@ This General Deployment Plan outlines the key steps for implementing endpoint se | Implement minor adjustments based on feedback. | Week 3 | Week 3 | Open | | | Continue refining and updating security protocols as needed. | Week 4 | Week 4 | Open | | | Finalize improvements based on feedback from stakeholders. | Week 5 | Week 5 | Open | | -| Maintain ongoing review cycles and introduce new tools. | Week 6-12 | Week 12 | Open | | \ No newline at end of file +| Maintain ongoing review cycles and introduce new tools. | Week 6-12 | Week 12 | Open | | diff --git a/docs/cybersecurity/GRC Team/ISMS-Policy-Implementation-Plans/ip-endpoint-security.md b/docs/cybersecurity/GRC Team/ISMS-Policy-Implementation-Plans/ip-endpoint-security.md index 7eedd91a5..dede3c64f 100644 --- a/docs/cybersecurity/GRC Team/ISMS-Policy-Implementation-Plans/ip-endpoint-security.md +++ b/docs/cybersecurity/GRC Team/ISMS-Policy-Implementation-Plans/ip-endpoint-security.md @@ -161,3 +161,4 @@ Feedback from users and stakeholders will be gathered through various channels, ### Improvement To ensure continuous improvement, we will implement a structured process for regularly updating and enhancing our security measures. This process will incorporate the latest industry best practices and adapt to emerging threats. By staying informed about the latest security trends and technologies, we will maintain a robust and up-to-date security posture, introducing new tools and technologies as necessary to protect against evolving risks. + diff --git a/docs/cybersecurity/GRC Team/ISMS-Policy-Implementation-Plans/server-security-implementation-plan.md b/docs/cybersecurity/GRC Team/ISMS-Policy-Implementation-Plans/server-security-implementation-plan.md index b6d08b904..d337eb12c 100644 --- a/docs/cybersecurity/GRC Team/ISMS-Policy-Implementation-Plans/server-security-implementation-plan.md +++ b/docs/cybersecurity/GRC Team/ISMS-Policy-Implementation-Plans/server-security-implementation-plan.md @@ -182,4 +182,4 @@ We feel this is achievable by splitting up relevant tasks between the Security t In conclusion, if the company decides to proceed with this plan we feel we have created a cost-effective and easy to implement implementation strategy that will see Redback Operations comply with the Server Security policy within a short-medium term. -Once all deployment strategies are followed, the security team should complete a compliance analysis to determine compliance with the policy. \ No newline at end of file +Once all deployment strategies are followed, the security team should complete a compliance analysis to determine compliance with the policy. diff --git a/docs/cybersecurity/Blue Team/Research/Awareness-Training/Module 10.pdf b/docs/cybersecurity/GRC/Research/Awareness-Training/Module 10.pdf similarity index 100% rename from docs/cybersecurity/Blue Team/Research/Awareness-Training/Module 10.pdf rename to docs/cybersecurity/GRC/Research/Awareness-Training/Module 10.pdf diff --git a/docs/cybersecurity/Blue Team/Research/Awareness-Training/Module 11.pdf b/docs/cybersecurity/GRC/Research/Awareness-Training/Module 11.pdf similarity index 100% rename from docs/cybersecurity/Blue Team/Research/Awareness-Training/Module 11.pdf rename to docs/cybersecurity/GRC/Research/Awareness-Training/Module 11.pdf diff --git a/docs/cybersecurity/Blue Team/Research/Awareness-Training/Module 12.pdf b/docs/cybersecurity/GRC/Research/Awareness-Training/Module 12.pdf similarity index 100% rename from docs/cybersecurity/Blue Team/Research/Awareness-Training/Module 12.pdf rename to docs/cybersecurity/GRC/Research/Awareness-Training/Module 12.pdf diff --git a/docs/cybersecurity/Blue Team/Research/Awareness-Training/Module-9.pdf b/docs/cybersecurity/GRC/Research/Awareness-Training/Module-9.pdf similarity index 100% rename from docs/cybersecurity/Blue Team/Research/Awareness-Training/Module-9.pdf rename to docs/cybersecurity/GRC/Research/Awareness-Training/Module-9.pdf diff --git a/docs/cybersecurity/Blue Team/Research/Awareness-Training/Subject_Guide.md b/docs/cybersecurity/GRC/Research/Awareness-Training/Subject_Guide.md similarity index 99% rename from docs/cybersecurity/Blue Team/Research/Awareness-Training/Subject_Guide.md rename to docs/cybersecurity/GRC/Research/Awareness-Training/Subject_Guide.md index c4e3cbab4..8a00a5d9f 100644 --- a/docs/cybersecurity/Blue Team/Research/Awareness-Training/Subject_Guide.md +++ b/docs/cybersecurity/GRC/Research/Awareness-Training/Subject_Guide.md @@ -109,3 +109,4 @@ Training Link – Training is hosted on Google classroom and can completed by [c Australian Cyber Security Centre. (2024). Guidelines for personnel security (June 2024). Australian Government.
https://www.cyber.gov.au/sites/default/files/2024-06/08.%20ISM%20-%20Guidelines%20for%20Personnel%20Security%20%28June%202024%29.pdf Australian Cyber Security Centre. (n.d.). Learn the basics. Australian Government.
https://www.cyber.gov.au/learn-basics + diff --git a/docs/cybersecurity/Blue Team/Research/Awareness-Training/User-Awareness-GAP-Analysis.md b/docs/cybersecurity/GRC/Research/Awareness-Training/User-Awareness-GAP-Analysis.md similarity index 99% rename from docs/cybersecurity/Blue Team/Research/Awareness-Training/User-Awareness-GAP-Analysis.md rename to docs/cybersecurity/GRC/Research/Awareness-Training/User-Awareness-GAP-Analysis.md index d1035ff35..397a42218 100644 --- a/docs/cybersecurity/Blue Team/Research/Awareness-Training/User-Awareness-GAP-Analysis.md +++ b/docs/cybersecurity/GRC/Research/Awareness-Training/User-Awareness-GAP-Analysis.md @@ -149,3 +149,4 @@ Given the solid baseline knowledge of all employees, it is recommended to create - Watch out for threats These topics should form six modules, with each ASD/ACSC topic providing the core content for a module. Additional, more specific content (likely from other ACSC webpages) will also need to be included in each module to ensure the Security Awareness Training is current and applicable to Redback Operations. + diff --git a/docs/cybersecurity/Blue Team/Research/Awareness-Training/User-Awareness-Training.md b/docs/cybersecurity/GRC/Research/Awareness-Training/User-Awareness-Training.md similarity index 99% rename from docs/cybersecurity/Blue Team/Research/Awareness-Training/User-Awareness-Training.md rename to docs/cybersecurity/GRC/Research/Awareness-Training/User-Awareness-Training.md index a9bb2fb9c..d89fc88f5 100644 --- a/docs/cybersecurity/Blue Team/Research/Awareness-Training/User-Awareness-Training.md +++ b/docs/cybersecurity/GRC/Research/Awareness-Training/User-Awareness-Training.md @@ -156,3 +156,4 @@ In cybersecurity, this means protecting sensitive data, ensuring transparency, a - **Compliance** – Follow all Redback Operations policies and procedures. --- + diff --git a/docs/cybersecurity/Blue Team/Research/Awareness-Training/_category_.json b/docs/cybersecurity/GRC/Research/Awareness-Training/_category_.json similarity index 100% rename from docs/cybersecurity/Blue Team/Research/Awareness-Training/_category_.json rename to docs/cybersecurity/GRC/Research/Awareness-Training/_category_.json diff --git a/docs/cybersecurity/Blue Team/Research/Awareness-Training/img/GAP-Q1.png b/docs/cybersecurity/GRC/Research/Awareness-Training/img/GAP-Q1.png similarity index 100% rename from docs/cybersecurity/Blue Team/Research/Awareness-Training/img/GAP-Q1.png rename to docs/cybersecurity/GRC/Research/Awareness-Training/img/GAP-Q1.png diff --git a/docs/cybersecurity/Blue Team/Research/Awareness-Training/img/GAP-Q2.png b/docs/cybersecurity/GRC/Research/Awareness-Training/img/GAP-Q2.png similarity index 100% rename from docs/cybersecurity/Blue Team/Research/Awareness-Training/img/GAP-Q2.png rename to docs/cybersecurity/GRC/Research/Awareness-Training/img/GAP-Q2.png diff --git a/docs/cybersecurity/Blue Team/Research/Awareness-Training/img/GAP-Q3.png b/docs/cybersecurity/GRC/Research/Awareness-Training/img/GAP-Q3.png similarity index 100% rename from docs/cybersecurity/Blue Team/Research/Awareness-Training/img/GAP-Q3.png rename to docs/cybersecurity/GRC/Research/Awareness-Training/img/GAP-Q3.png diff --git a/docs/cybersecurity/Blue Team/Research/Awareness-Training/img/GAP-Q4.png b/docs/cybersecurity/GRC/Research/Awareness-Training/img/GAP-Q4.png similarity index 100% rename from docs/cybersecurity/Blue Team/Research/Awareness-Training/img/GAP-Q4.png rename to docs/cybersecurity/GRC/Research/Awareness-Training/img/GAP-Q4.png diff --git a/docs/cybersecurity/Blue Team/Research/Awareness-Training/img/GAP-Q5.png b/docs/cybersecurity/GRC/Research/Awareness-Training/img/GAP-Q5.png similarity index 100% rename from docs/cybersecurity/Blue Team/Research/Awareness-Training/img/GAP-Q5.png rename to docs/cybersecurity/GRC/Research/Awareness-Training/img/GAP-Q5.png diff --git a/docs/cybersecurity/Blue Team/Research/Awareness-Training/img/GAP-Q6.png b/docs/cybersecurity/GRC/Research/Awareness-Training/img/GAP-Q6.png similarity index 100% rename from docs/cybersecurity/Blue Team/Research/Awareness-Training/img/GAP-Q6.png rename to docs/cybersecurity/GRC/Research/Awareness-Training/img/GAP-Q6.png diff --git a/docs/cybersecurity/Blue Team/Research/Awareness-Training/img/GAP-Q7.png b/docs/cybersecurity/GRC/Research/Awareness-Training/img/GAP-Q7.png similarity index 100% rename from docs/cybersecurity/Blue Team/Research/Awareness-Training/img/GAP-Q7.png rename to docs/cybersecurity/GRC/Research/Awareness-Training/img/GAP-Q7.png diff --git a/docs/cybersecurity/Blue Team/Research/Awareness-Training/img/GAP-Q8.png b/docs/cybersecurity/GRC/Research/Awareness-Training/img/GAP-Q8.png similarity index 100% rename from docs/cybersecurity/Blue Team/Research/Awareness-Training/img/GAP-Q8.png rename to docs/cybersecurity/GRC/Research/Awareness-Training/img/GAP-Q8.png diff --git a/docs/cybersecurity/Blue Team/Research/Awareness-Training/img/GAP-Q9.png b/docs/cybersecurity/GRC/Research/Awareness-Training/img/GAP-Q9.png similarity index 100% rename from docs/cybersecurity/Blue Team/Research/Awareness-Training/img/GAP-Q9.png rename to docs/cybersecurity/GRC/Research/Awareness-Training/img/GAP-Q9.png diff --git a/docs/cybersecurity/research/Servicesnow/Servicesnow.md b/docs/cybersecurity/GRC/Research/Servicesnow/Servicesnow.md similarity index 99% rename from docs/cybersecurity/research/Servicesnow/Servicesnow.md rename to docs/cybersecurity/GRC/Research/Servicesnow/Servicesnow.md index 24fade71d..0988736ed 100644 --- a/docs/cybersecurity/research/Servicesnow/Servicesnow.md +++ b/docs/cybersecurity/GRC/Research/Servicesnow/Servicesnow.md @@ -92,3 +92,4 @@ ServiceNow offers a comprehensive suite of features that can significantly enhan - Smith, J. (2022). *Comprehensive IT Service Management Solution*. Retrieved from [ServiceNow Docs](https://docs.servicenow.com/). - Thompson, L. (2023). *ServiceNow: Enhancing IT Operations with AI and Automation*. Retrieved from [Capterra](https://www.capterra.com/p/172402/ServiceNow/). - Wilson, P. (2023). *Case Study: Enhancing Self-Service with ServiceNow Knowledge Management*. Retrieved from [ServiceNow Customers](https://www.servicenow.com/company/customers.html). + diff --git a/docs/cybersecurity/research/Servicesnow/_category_.json b/docs/cybersecurity/GRC/Research/Servicesnow/_category_.json similarity index 100% rename from docs/cybersecurity/research/Servicesnow/_category_.json rename to docs/cybersecurity/GRC/Research/Servicesnow/_category_.json diff --git a/docs/cybersecurity/research/Servicesnow/img/sn1.jpg b/docs/cybersecurity/GRC/Research/Servicesnow/img/sn1.jpg similarity index 100% rename from docs/cybersecurity/research/Servicesnow/img/sn1.jpg rename to docs/cybersecurity/GRC/Research/Servicesnow/img/sn1.jpg diff --git a/docs/cybersecurity/research/Servicesnow/img/sn2.png b/docs/cybersecurity/GRC/Research/Servicesnow/img/sn2.png similarity index 100% rename from docs/cybersecurity/research/Servicesnow/img/sn2.png rename to docs/cybersecurity/GRC/Research/Servicesnow/img/sn2.png diff --git a/docs/cybersecurity/Infrastrcture Team/Semester Updates/Core Services.md b/docs/cybersecurity/Infrastrcture Team/Semester Updates/Core Services.md index 3d5c1830c..ff0cd61b8 100644 --- a/docs/cybersecurity/Infrastrcture Team/Semester Updates/Core Services.md +++ b/docs/cybersecurity/Infrastrcture Team/Semester Updates/Core Services.md @@ -94,4 +94,4 @@ Upgrading Docker will restart the engine. Any containers without a restart polic ### OS Upgrade -The VM was upgraded to Ubuntu 22.04 LTS during the last week of the semester. The end of life is April 2027. Before upgrading ask the Deakin IT team for a new snapshot and have each project lead test their applications before deleting the snapshot - unless the snapshot can be kept. \ No newline at end of file +The VM was upgraded to Ubuntu 22.04 LTS during the last week of the semester. The end of life is April 2027. Before upgrading ask the Deakin IT team for a new snapshot and have each project lead test their applications before deleting the snapshot - unless the snapshot can be kept. diff --git a/docs/cybersecurity/Infrastrcture Team/Ubuntu Server/LDAP Configuration.md b/docs/cybersecurity/Infrastrcture Team/Ubuntu Server/LDAP Configuration.md index f96ed6f23..0be06404a 100644 --- a/docs/cybersecurity/Infrastrcture Team/Ubuntu Server/LDAP Configuration.md +++ b/docs/cybersecurity/Infrastrcture Team/Ubuntu Server/LDAP Configuration.md @@ -107,3 +107,4 @@ sudo ldapadd -x -D cn=admin,dc=redbackops,dc=org,dc=au -W -f add_entries.ldif ```bash ldapsearch -x -LLL -b dc=redbackops,dc=org,dc=au `uid=jdoe` ``` + diff --git a/docs/cybersecurity/Infrastrcture Team/Ubuntu Server/LDAP Ubuntu Server Handover.md b/docs/cybersecurity/Infrastrcture Team/Ubuntu Server/LDAP Ubuntu Server Handover.md index 480b1a1c2..01297f14c 100644 --- a/docs/cybersecurity/Infrastrcture Team/Ubuntu Server/LDAP Ubuntu Server Handover.md +++ b/docs/cybersecurity/Infrastrcture Team/Ubuntu Server/LDAP Ubuntu Server Handover.md @@ -71,3 +71,4 @@ The following have both been written in Markdown and should be available in the - [LDAP vs. Kerberos](https://www.geeksforgeeks.org/difference-between-ldap-and-kerberos/) - [IBM LDAP utilities](https://www.ibm.com/docs/en/zos/2.5.0?topic=utilities-ldapmodify-ldapadd) - [LDAP over SSL](https://www.server-world.info/en/note?os=Ubuntu_22.04&p=openldap&f=4) + diff --git a/docs/cybersecurity/Infrastrcture Team/Ubuntu Server/Optional Services.md b/docs/cybersecurity/Infrastrcture Team/Ubuntu Server/Optional Services.md index 3aca9bca0..c2678adb5 100644 --- a/docs/cybersecurity/Infrastrcture Team/Ubuntu Server/Optional Services.md +++ b/docs/cybersecurity/Infrastrcture Team/Ubuntu Server/Optional Services.md @@ -81,3 +81,4 @@ The **`netstat`** command displays active connections, routing tables, interface sudo netstat -tuln | grep :389 ``` This output confirms that **port 389** is open and listening for both IPv4 and IPv6 traffic, validating that the LDAP service is available and functional. + diff --git a/docs/cybersecurity/RED TEAM/backend-pentest/pentest-info.md b/docs/cybersecurity/RED TEAM/backend-pentest/pentest-info.md index 23abb1655..63c44a46b 100644 --- a/docs/cybersecurity/RED TEAM/backend-pentest/pentest-info.md +++ b/docs/cybersecurity/RED TEAM/backend-pentest/pentest-info.md @@ -331,4 +331,4 @@ Expected Result: Intrusion detection systems should detect and alert on simulate - Aircrack-ng- Category: Password cracking -- Kismet- Category: Packet sniffer \ No newline at end of file +- Kismet- Category: Packet sniffer diff --git a/docs/cybersecurity/RED TEAM/backend-pentest/project-8-backend.md b/docs/cybersecurity/RED TEAM/backend-pentest/project-8-backend.md index 3fe8af569..01ab8e2e5 100644 --- a/docs/cybersecurity/RED TEAM/backend-pentest/project-8-backend.md +++ b/docs/cybersecurity/RED TEAM/backend-pentest/project-8-backend.md @@ -43,4 +43,4 @@ web browser. - Explore different pages by navigating to Signup, Login, Home, Navigate through these pages to explore the functionality. -- Please ask team lead for credentials. \ No newline at end of file +- Please ask team lead for credentials. diff --git a/docs/cybersecurity/RED TEAM/backend-pentest/setup-pentest.md b/docs/cybersecurity/RED TEAM/backend-pentest/setup-pentest.md index b0c08e95f..64bb45223 100644 --- a/docs/cybersecurity/RED TEAM/backend-pentest/setup-pentest.md +++ b/docs/cybersecurity/RED TEAM/backend-pentest/setup-pentest.md @@ -63,4 +63,4 @@ URLs and whatnot - Reboot the virtual machine to ensure all changes take effect. -- Open a terminal and run sudo apt update && sudo apt upgrade to update Kali Linux \ No newline at end of file +- Open a terminal and run sudo apt update && sudo apt upgrade to update Kali Linux diff --git a/docs/cybersecurity/RED TEAM/backend-pentest/system-report.md b/docs/cybersecurity/RED TEAM/backend-pentest/system-report.md index 9a01cad7d..6450439f7 100644 --- a/docs/cybersecurity/RED TEAM/backend-pentest/system-report.md +++ b/docs/cybersecurity/RED TEAM/backend-pentest/system-report.md @@ -98,4 +98,4 @@ maintenance. The backend system embodies a foundational framework proficient in catering to essential user- related functionalities and interactions. However, pivotal enhancements in password security mechanisms, input validation strategies, and comprehensive documentation are paramount to fortify -the system's robustness, security posture, and overall reliability \ No newline at end of file +the system's robustness, security posture, and overall reliability diff --git a/docs/cybersecurity/RED TEAM/usecases/Enumeration.md b/docs/cybersecurity/RED TEAM/usecases/Enumeration.md index 1c4da6716..63bee3419 100644 --- a/docs/cybersecurity/RED TEAM/usecases/Enumeration.md +++ b/docs/cybersecurity/RED TEAM/usecases/Enumeration.md @@ -184,3 +184,4 @@ To conclude, the process involved setting up and interacting with a MongoDB inst ### Conclusion: To conclude, implementing the recommended remediation steps will significantly reduce the risk of exploitation and improve the system’s resilience to cyber threats. By prioritizing the high and critical vulnerabilities, Redback Operations can take a proactive approach to securing its infrastructure and maintaining the integrity and confidentiality of its network communications. + diff --git a/docs/cybersecurity/RED TEAM/usecases/GapAnalysisM.md b/docs/cybersecurity/RED TEAM/usecases/GapAnalysisM.md index b57b62c5f..7badc8e07 100644 --- a/docs/cybersecurity/RED TEAM/usecases/GapAnalysisM.md +++ b/docs/cybersecurity/RED TEAM/usecases/GapAnalysisM.md @@ -32,4 +32,4 @@ Last year, Redback Operations addressed various security issues such as unauthor - **Gap**: Redback Operations has not conducted phishing simulations or employee awareness training regularly. This leaves the organization vulnerable to email-based phishing attacks. - **Suggestion**: Conduct regular phishing awareness training and deploy email filtering tools to block malicious emails before they reach users. -By addressing gaps in MQTT authentication, Slowloris DoS vulnerabilities, weak SSL/TLS configurations, HTTP verb tampering, and the lack of phishing simulations, Redback Operations will significantly strengthen its overall security. \ No newline at end of file +By addressing gaps in MQTT authentication, Slowloris DoS vulnerabilities, weak SSL/TLS configurations, HTTP verb tampering, and the lack of phishing simulations, Redback Operations will significantly strengthen its overall security. diff --git a/docs/cybersecurity/RED TEAM/usecases/PenTestMQTT.md b/docs/cybersecurity/RED TEAM/usecases/PenTestMQTT.md index 867f151bd..768619ce7 100644 --- a/docs/cybersecurity/RED TEAM/usecases/PenTestMQTT.md +++ b/docs/cybersecurity/RED TEAM/usecases/PenTestMQTT.md @@ -252,3 +252,4 @@ The broker at 10.137.0.149 is actively listening on port 1883 as indicated by th ### Conclusion: In conclusion, penetration testing is a critical cybersecurity practice for identifying and addressing vulnerabilities in systems, networks, and applications before they can be exploited. Understanding the security of an MQTT broker is essential, as it can be a target for attacks, making strong security practices like penetration testing important to maintain secure operations. + diff --git a/docs/cybersecurity/RED TEAM/usecases/PhishingVps.md b/docs/cybersecurity/RED TEAM/usecases/PhishingVps.md index 2e9faa55a..e0d6290e6 100644 --- a/docs/cybersecurity/RED TEAM/usecases/PhishingVps.md +++ b/docs/cybersecurity/RED TEAM/usecases/PhishingVps.md @@ -142,3 +142,4 @@ For the landing page, click "Import Site" on the top and enter the link address ![gp10](img/gp10.png) Unfortunately, the email phishing attempt using GoPhish was unsuccessful. Despite testing the campaign with three students' email addresses, the emails were consistently flagged, and the domain was marked as a phishing site. As a result, the phishing emails never reached the intended recipients, failing to bypass security filters. + diff --git a/docs/cybersecurity/RED TEAM/usecases/SETPhishing.md b/docs/cybersecurity/RED TEAM/usecases/SETPhishing.md index 0258611f6..9d9c7fc08 100644 --- a/docs/cybersecurity/RED TEAM/usecases/SETPhishing.md +++ b/docs/cybersecurity/RED TEAM/usecases/SETPhishing.md @@ -136,4 +136,4 @@ I used Kali Linux to run the SET for generating the phishing email and creating ## Conclusion: This demonstration effectively showcased the process of conducting a phishing attack in a controlled environment using the Social Engineering Toolkit (SET). By sending phishing emails and cloning legitimate login pages, I simulated a scenario where sensitive credentials were captured. Although some phishing emails were blocked due to spam filters, this highlighted the importance of email filtering systems. -Additionally, the successful credential harvesting in a local network environment emphasizes how phishing attacks can be executed. The failure of the phishing link on the host machine underlines the importance of correct network configurations during testing. To mitigate such risks, organizations should implement multi-factor authentication (MFA), conduct regular user awareness training, use strong spam filters, and employ network monitoring tools to detect suspicious activity. These measures are essential to defending against phishing attacks and minimizing their impact. \ No newline at end of file +Additionally, the successful credential harvesting in a local network environment emphasizes how phishing attacks can be executed. The failure of the phishing link on the host machine underlines the importance of correct network configurations during testing. To mitigate such risks, organizations should implement multi-factor authentication (MFA), conduct regular user awareness training, use strong spam filters, and employ network monitoring tools to detect suspicious activity. These measures are essential to defending against phishing attacks and minimizing their impact. diff --git a/docs/cybersecurity/RED TEAM/usecases/pdf.md b/docs/cybersecurity/RED TEAM/usecases/pdf.md index ace58d932..3d513dbcc 100644 --- a/docs/cybersecurity/RED TEAM/usecases/pdf.md +++ b/docs/cybersecurity/RED TEAM/usecases/pdf.md @@ -16,3 +16,4 @@ Find below the documents referenced in the Usecases page. - [Data Theft Incident Response Usecase](docs\Data-Theft-Red-Team-Usecase.pdf) - [Malware Outbreak Incident Response Usecase](docs\Malware-Outbreak-Red-Team-Usecase.pdf) - [Virus Outbreak Incident Response Usecase](docs\Virus-Outbreak-Red-Team-Usecase.pdf) + diff --git a/docs/cybersecurity/RED TEAM/usecases/pentest.md b/docs/cybersecurity/RED TEAM/usecases/pentest.md index fbd8bf236..fb1b002d6 100644 --- a/docs/cybersecurity/RED TEAM/usecases/pentest.md +++ b/docs/cybersecurity/RED TEAM/usecases/pentest.md @@ -688,3 +688,4 @@ Addressing these recommendations promptly, while conducting regular security ass - **OpenVAS**: Utilized for thorough vulnerability scanning and assessments. + diff --git a/docs/cybersecurity/RED TEAM/usecases/phishing.md b/docs/cybersecurity/RED TEAM/usecases/phishing.md index 871cf6afb..1deb038a9 100644 --- a/docs/cybersecurity/RED TEAM/usecases/phishing.md +++ b/docs/cybersecurity/RED TEAM/usecases/phishing.md @@ -184,3 +184,4 @@ Creating a Sending Profile in GoPhish After completing the setup above. Now click on campaign and start a new one. Use the profiles already created and launch a campaign. After launching, the profiles should receive the email with phishing link: ![picture13](img/Picture13.jpg) + diff --git a/docs/cybersecurity/research/2fa-bypass.md b/docs/cybersecurity/Red Team/Research/2fa-bypass.md similarity index 99% rename from docs/cybersecurity/research/2fa-bypass.md rename to docs/cybersecurity/Red Team/Research/2fa-bypass.md index 5dff4cbde..edad7657a 100644 --- a/docs/cybersecurity/research/2fa-bypass.md +++ b/docs/cybersecurity/Red Team/Research/2fa-bypass.md @@ -188,4 +188,4 @@ https://breakdev.org/evilginx-advanced-phishing-with-two-factor-authentication-b https://medium.com/@OWN_team/analysis-and-detection-of-mitm-phishing-attacks-bypassing-2fa- o365-use-case-cf0ffdae9cae -https://blog.netwrix.com/2022/11/29/bypassing-mfa-with-pass-the-cookie-attack/ \ No newline at end of file +https://blog.netwrix.com/2022/11/29/bypassing-mfa-with-pass-the-cookie-attack/ diff --git a/docs/cybersecurity/research/authenticate-features.md b/docs/cybersecurity/Red Team/Research/authenticate-features.md similarity index 99% rename from docs/cybersecurity/research/authenticate-features.md rename to docs/cybersecurity/Red Team/Research/authenticate-features.md index bd34cc496..13d47d035 100644 --- a/docs/cybersecurity/research/authenticate-features.md +++ b/docs/cybersecurity/Red Team/Research/authenticate-features.md @@ -50,4 +50,4 @@ encryption to meet your individual data security requirements. MongoDB Atlas mak 3. Client-rest encryption 4. Rotation of encryption keys -Each method is discussed in the report to showcase key features, recommendations or limitations for the final decision. The report concludes with the flowchart of all the encryption methods for th field data. Moreover, demonstrates the procedures to enable authentication and encryption of all the user data and company data. \ No newline at end of file +Each method is discussed in the report to showcase key features, recommendations or limitations for the final decision. The report concludes with the flowchart of all the encryption methods for th field data. Moreover, demonstrates the procedures to enable authentication and encryption of all the user data and company data. diff --git a/docs/cybersecurity/research/flutter-security.md b/docs/cybersecurity/Red Team/Research/flutter-security.md similarity index 99% rename from docs/cybersecurity/research/flutter-security.md rename to docs/cybersecurity/Red Team/Research/flutter-security.md index 498d62569..c0b5f62c6 100644 --- a/docs/cybersecurity/research/flutter-security.md +++ b/docs/cybersecurity/Red Team/Research/flutter-security.md @@ -32,3 +32,4 @@ Please note, that I will create a presentation to elaborate further, and I will [3] appmire.be (n.d). flutter_jailbreak_detection 1.8.0 [Website]. Available: flutter_jailbreak_detection: https://pub.dev/packages/flutter_jailbreak_detection [4] Codeplayon (2021, December. 2). How to secure flutter application code [Website]. Available: https://www.codeplayon.com/2021/12/how-to-secure-flutter-application-code/ + diff --git a/docs/cybersecurity/research/img/2fa-auth.jpg b/docs/cybersecurity/Red Team/Research/img/2fa-auth.jpg similarity index 100% rename from docs/cybersecurity/research/img/2fa-auth.jpg rename to docs/cybersecurity/Red Team/Research/img/2fa-auth.jpg diff --git a/docs/cybersecurity/research/img/2fa-graph.jpg b/docs/cybersecurity/Red Team/Research/img/2fa-graph.jpg similarity index 100% rename from docs/cybersecurity/research/img/2fa-graph.jpg rename to docs/cybersecurity/Red Team/Research/img/2fa-graph.jpg diff --git a/docs/cybersecurity/research/img/2fa-passthrough.jpg b/docs/cybersecurity/Red Team/Research/img/2fa-passthrough.jpg similarity index 100% rename from docs/cybersecurity/research/img/2fa-passthrough.jpg rename to docs/cybersecurity/Red Team/Research/img/2fa-passthrough.jpg diff --git a/docs/cybersecurity/research/img/2fa-tokens.jpg b/docs/cybersecurity/Red Team/Research/img/2fa-tokens.jpg similarity index 100% rename from docs/cybersecurity/research/img/2fa-tokens.jpg rename to docs/cybersecurity/Red Team/Research/img/2fa-tokens.jpg diff --git a/docs/cybersecurity/research/img/authenticate-tls.jpg b/docs/cybersecurity/Red Team/Research/img/authenticate-tls.jpg similarity index 100% rename from docs/cybersecurity/research/img/authenticate-tls.jpg rename to docs/cybersecurity/Red Team/Research/img/authenticate-tls.jpg diff --git a/docs/cybersecurity/research/two-factor-authentication.md b/docs/cybersecurity/Red Team/Research/two-factor-authentication.md similarity index 99% rename from docs/cybersecurity/research/two-factor-authentication.md rename to docs/cybersecurity/Red Team/Research/two-factor-authentication.md index 3a27f399b..8ced6cc26 100644 --- a/docs/cybersecurity/research/two-factor-authentication.md +++ b/docs/cybersecurity/Red Team/Research/two-factor-authentication.md @@ -141,4 +141,4 @@ function Loginverification (emailad, code, req, res, failUrl) { }) }) } -``` \ No newline at end of file +``` diff --git a/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Azure DevOps Comparative Assessment.md b/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Azure DevOps Comparative Assessment.md index 4ea2d72f4..de9f44fd2 100644 --- a/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Azure DevOps Comparative Assessment.md +++ b/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Azure DevOps Comparative Assessment.md @@ -209,3 +209,4 @@ Following the above investigation, it is recommended that we move to the Azure D * Azure DevOps is strong in all areas, whereas there are limitations with the Atlassian product suite. * Azure DevOps will be far easier for access control as mentors can control access easily through Deakin M365 IAM control. * Opens the door to utilising Azure for cloud requirements over Google (GCP) providing further integration still throughout the company’s tooling. + diff --git a/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Azure DevOps Quick Start Guide.md b/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Azure DevOps Quick Start Guide.md index e18bddcc8..704d7dd0d 100644 --- a/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Azure DevOps Quick Start Guide.md +++ b/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Azure DevOps Quick Start Guide.md @@ -171,3 +171,4 @@ Here are some items you may want to consider moving into Azure DevOps in T1 2025 - Ensure your board is updated and items are moved through the swim lanes accurately reflecting progress. - Update Welcome Wiki with any knew information that may be required following your own contribution to Azure DevOps. - You may even want to update this quick start guide for the next cohort to get started quickly in the platform. + diff --git a/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Best Practice & Usage Guidelines.mdx b/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Best Practice & Usage Guidelines.mdx index ef08d5c3b..de3e4b71f 100644 --- a/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Best Practice & Usage Guidelines.mdx +++ b/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Best Practice & Usage Guidelines.mdx @@ -109,4 +109,4 @@ Queries and dashboards in Azure Boards provide tools for monitoring team perform ![Queries and Dashboards](/img/azure-boards-images/6-6-image.png) -
\ No newline at end of file +
diff --git a/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Conclusion.mdx b/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Conclusion.mdx index 52890fe76..64c35540b 100644 --- a/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Conclusion.mdx +++ b/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Conclusion.mdx @@ -65,4 +65,4 @@ With features like custom boards, sprints, work item templates, and integrations By integrating best practices in task management, reporting, and sprint execution, this solution is expected to lead to increased efficiency, reduced operational risk, and improved collaboration between teams. The successful deployment of this design ensures that the Redback's Cyber Security Team is equipped to handle its responsibilities while maintaining the flexibility to evolve alongside the organization's needs. -
\ No newline at end of file +
diff --git a/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Cyber Security Team Use Cases & Examples.mdx b/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Cyber Security Team Use Cases & Examples.mdx index ef002b487..01a9bc5ec 100644 --- a/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Cyber Security Team Use Cases & Examples.mdx +++ b/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Cyber Security Team Use Cases & Examples.mdx @@ -243,4 +243,4 @@ The GRC Team will work closely with other teams, such as Infrastructure and SecD A compliance audit is scheduled and documented as a work item in Azure Boards. The audit is conducted, and any findings are logged as separate work items, with details on the required corrective actions. The GRC Team collaborates with the relevant teams to ensure that all compliance issues are addressed, tracking the progress of these efforts in Azure Boards. -
\ No newline at end of file +
diff --git a/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Glossary.mdx b/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Glossary.mdx index 82a351d6e..133198c0f 100644 --- a/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Glossary.mdx +++ b/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Glossary.mdx @@ -121,4 +121,4 @@ Provided in this section is a glossary of all relevant terms and object definiti - **Dashboard**\ A visual interface in Azure Boards that displays key metrics, such as task completion rates, sprint progress, or incident response status. Dashboards are customizable for different teams and stakeholders. -
\ No newline at end of file +
diff --git a/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Introduction & High Level Summary.mdx b/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Introduction & High Level Summary.mdx index 14fe7058d..552db810d 100644 --- a/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Introduction & High Level Summary.mdx +++ b/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Introduction & High Level Summary.mdx @@ -233,4 +233,4 @@ Sprints and iterations will be used by each team to plan and execute work within Sprints will be an integral part of each team's workflow, helping them manage their work efficiently and deliver results within the required timeframe. -
\ No newline at end of file +
diff --git a/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Risk Assessment.mdx b/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Risk Assessment.mdx index 0bae590d4..b5555597d 100644 --- a/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Risk Assessment.mdx +++ b/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Risk Assessment.mdx @@ -101,4 +101,4 @@ The following tables outline potential risks associated with the implementation | Over-Complication of Workflows | Workflows may become overly complicated, making it difficult for team members to follow processes efficiently. | Regularly review and simplify workflows based on feedback. Ensure workflows are aligned with team needs and operational goals. | Implement a feedback loop to continuously gather input from users and make adjustments. Use pilot testing before implementing major workflow changes. | | Training and Onboarding Delays | New team members may require additional time and resources for training, delaying their ability to contribute. | Establish a proactive onboarding process with comprehensive training. Provide ongoing support and mentorship. | Allow for extended onboarding periods in project planning. Assign mentors to new team members to accelerate their learning and integration into the team. | -
\ No newline at end of file +
diff --git a/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Setup Guide & Implementation Plan.mdx b/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Setup Guide & Implementation Plan.mdx index 80daca862..e3d71bb6d 100644 --- a/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Setup Guide & Implementation Plan.mdx +++ b/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Setup Guide & Implementation Plan.mdx @@ -297,4 +297,4 @@ While this implementation plan is designed for the Redback Cyber Security team, - Regularly evaluate the use of Azure Boards to identify areas for improvement, such as optimizing task prioritization or enhancing dashboard functionality. -
\ No newline at end of file +
diff --git a/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Solution Architecture.mdx b/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Solution Architecture.mdx index 1ee705913..96604a6af 100644 --- a/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Solution Architecture.mdx +++ b/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Solution Architecture.mdx @@ -141,4 +141,4 @@ All data within Azure Boards will be protected by encryption, both at rest and i Azure Boards will be configured to provide audit logs that track all significant actions, such as the creation or modification of work items, changes to access permissions, and integration with external tools. These logs will be used to ensure compliance with internal and regulatory requirements. -
\ No newline at end of file +
diff --git a/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Technical Use Guide.mdx b/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Technical Use Guide.mdx index bf9b6bb19..5f178389d 100755 --- a/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Technical Use Guide.mdx +++ b/docs/cybersecurity/SecDevOps Team/Azure Boards Project Management/Technical Use Guide.mdx @@ -152,4 +152,4 @@ is returned. More detail is included in the video demonstration. #### _Query To Select PR's_ ![no-scroll-dashboard-view](/img/azure-boards-images/tech-use-guide/pr_view_query.png) -
\ No newline at end of file +
diff --git a/docs/cybersecurity/SecDevOps Team/Coding Best Practices/Introduction.md b/docs/cybersecurity/SecDevOps Team/Coding Best Practices/Introduction.md index e4b42a0ed..147e3fd6f 100644 --- a/docs/cybersecurity/SecDevOps Team/Coding Best Practices/Introduction.md +++ b/docs/cybersecurity/SecDevOps Team/Coding Best Practices/Introduction.md @@ -22,3 +22,4 @@ The module is constructed with a number of sections including: - **Section 2:** CODING BEST PRACTICES - **Section 3:** CODE REVIEWING - **Section 4:** QUIZ + diff --git a/docs/cybersecurity/SecDevOps Team/Coding Best Practices/Section1.md b/docs/cybersecurity/SecDevOps Team/Coding Best Practices/Section1.md index d658a145c..c4a6cd250 100644 --- a/docs/cybersecurity/SecDevOps Team/Coding Best Practices/Section1.md +++ b/docs/cybersecurity/SecDevOps Team/Coding Best Practices/Section1.md @@ -109,3 +109,4 @@ function update-title('title') ``` + diff --git a/docs/cybersecurity/SecDevOps Team/Coding Best Practices/Section2.md b/docs/cybersecurity/SecDevOps Team/Coding Best Practices/Section2.md index 135778d34..3ad484785 100644 --- a/docs/cybersecurity/SecDevOps Team/Coding Best Practices/Section2.md +++ b/docs/cybersecurity/SecDevOps Team/Coding Best Practices/Section2.md @@ -215,3 +215,4 @@ This is a simple measure that we can implement although it still can sometimes s We should save our code daily for large projects but even for smaller files, something as simple as ***‘Ctrl+S’*** (on Windows) to save our file always ensures we are keeping our progress so that if one of these unprecedented scenarios occur, we can be confident that when we return, we can pick up our work where we left it off without fear of losing what we have worked on. Autosave can be viable but don’t always rely on it also. Manual saving after all is the key to achieving this best practice method. Always remember to keep saving your work throughout the duration of modification, don't leave it until the end of your session to save and exit!! + diff --git a/docs/cybersecurity/SecDevOps Team/Coding Best Practices/Section3.md b/docs/cybersecurity/SecDevOps Team/Coding Best Practices/Section3.md index e4a14cd66..6f2f93d7c 100644 --- a/docs/cybersecurity/SecDevOps Team/Coding Best Practices/Section3.md +++ b/docs/cybersecurity/SecDevOps Team/Coding Best Practices/Section3.md @@ -18,3 +18,4 @@ We will then point out what needed to be refactored and why for the coding examp *A few bonus points of addition in which we can also add from the video in which was not initially discussed includes the implementation of a Try-Catch exception handling. And also the header for the file to assist in indentifying the creator of the file along with its modifications.* The ability to review your own work saves a lot of time for everyone as it is essentially like the first line of defence. You are trying to catch anything that you can see before it is then processed for another individual to also review. You may not always be able to find everything although, finding something is better than nothing. (Sometimes there may also just be genuinely nothing to find!) + diff --git a/docs/cybersecurity/SecDevOps Team/Coding Best Practices/Section4.md b/docs/cybersecurity/SecDevOps Team/Coding Best Practices/Section4.md index bb824169a..95f9d4dcd 100644 --- a/docs/cybersecurity/SecDevOps Team/Coding Best Practices/Section4.md +++ b/docs/cybersecurity/SecDevOps Team/Coding Best Practices/Section4.md @@ -14,3 +14,4 @@ To access the quiz for this module, a link will be provided. Test what you have **Quiz Link:** https://forms.gle/aLqL6Y2oxEvkMM7Z8 After completing the quiz you have successfully completed this module about Coding Best Practices, thank you for your time and hopefully you have learnt a few new skills to apply when developing future programs! + diff --git a/docs/cybersecurity/SecDevOps Team/azure/azure-proposal.md b/docs/cybersecurity/SecDevOps Team/azure/azure-proposal.md index fb5afdf91..b89003aa6 100644 --- a/docs/cybersecurity/SecDevOps Team/azure/azure-proposal.md +++ b/docs/cybersecurity/SecDevOps Team/azure/azure-proposal.md @@ -140,4 +140,4 @@ an approximate cost of 1204 AUD per month. Despite the slight cost increase Azure will have over Google Cloud, the increase justifies the various efficiencies and ease of use the company will get from quick sign ins to access provisioning and resource control, which would make Azure a far more viable option than -Google Cloud. \ No newline at end of file +Google Cloud. diff --git a/docs/cybersecurity/SecDevOps Team/secure-code/Bandit_Documentation.md b/docs/cybersecurity/SecDevOps Team/secure-code/Bandit_Documentation.md index d16a2fa41..6b2384dcc 100644 --- a/docs/cybersecurity/SecDevOps Team/secure-code/Bandit_Documentation.md +++ b/docs/cybersecurity/SecDevOps Team/secure-code/Bandit_Documentation.md @@ -253,3 +253,4 @@ Enhanced reporting with trend analysis and historical comparisons ## Conclusion Our journey with Bandit, from a simple scanning script to a comprehensive security analysis tool, has significantly enhanced Redback Operations' security review process. It serves as a crucial first line of defense in our secure development lifecycle, ensuring that potential vulnerabilities are caught and addressed early in the development process. By continuously refining and expanding our tool, we're staying ahead of emerging security threats and fostering a culture of security-first development. + diff --git a/docs/cybersecurity/SecDevOps Team/secure-code/Dependency-Scanner-Report.md b/docs/cybersecurity/SecDevOps Team/secure-code/Dependency-Scanner-Report.md index 8a2c521ba..3d9393e58 100644 --- a/docs/cybersecurity/SecDevOps Team/secure-code/Dependency-Scanner-Report.md +++ b/docs/cybersecurity/SecDevOps Team/secure-code/Dependency-Scanner-Report.md @@ -29,3 +29,4 @@ The full report and vulnerability spreadsheet can be found in the Redback Sharep - Consider configuring the scanner to block pull requests if **critical or high severity vulnerabilities** are detected. - Future reviews should incorporate both dependency and container scanning. - Project teams should be supported with remediation guidance and patching strategies. + diff --git a/docs/cybersecurity/SecDevOps Team/secure-code/Dependency-Scanner.md b/docs/cybersecurity/SecDevOps Team/secure-code/Dependency-Scanner.md index 481808886..bff0119ec 100644 --- a/docs/cybersecurity/SecDevOps Team/secure-code/Dependency-Scanner.md +++ b/docs/cybersecurity/SecDevOps Team/secure-code/Dependency-Scanner.md @@ -79,4 +79,4 @@ This job scans only the files changed in the pull request for vulnerabilities an ### Trivy PR Check Results - Vulnerabilities found in the files changed in the PR will trigger a review comment on the PR. The comment will include information about the severity of each vulnerability. -- HIGH and CRITICAL vulnerabilities will be marked as errors by Reviewdog. This can be configured to block the PR from being merged if desired, however that functionality has been disabled in this initial implementation. \ No newline at end of file +- HIGH and CRITICAL vulnerabilities will be marked as errors by Reviewdog. This can be configured to block the PR from being merged if desired, however that functionality has been disabled in this initial implementation. diff --git a/docs/cybersecurity/SecDevOps Team/secure-code/OWASP-Top-10-review.md b/docs/cybersecurity/SecDevOps Team/secure-code/OWASP-Top-10-review.md index 880274356..b0dc06263 100644 --- a/docs/cybersecurity/SecDevOps Team/secure-code/OWASP-Top-10-review.md +++ b/docs/cybersecurity/SecDevOps Team/secure-code/OWASP-Top-10-review.md @@ -176,3 +176,4 @@ This vulnerability occurs when a web application fetches a remote resource witho OWASP (Open Worldwide Application Security Project) 2024, OWASP Top Ten Project, viewed 7 December 2024, https://owasp.org/www-project-top-ten/. + diff --git a/docs/cybersecurity/SecDevOps Team/secure-code/TLSPlan.md b/docs/cybersecurity/SecDevOps Team/secure-code/TLSPlan.md index 8263bbb3c..f50c10b07 100644 --- a/docs/cybersecurity/SecDevOps Team/secure-code/TLSPlan.md +++ b/docs/cybersecurity/SecDevOps Team/secure-code/TLSPlan.md @@ -700,3 +700,4 @@ with the legitimate machine. - Monitor, maintain, and manage certificates. - Update documentation and provide training. - Review and implement improvements. + diff --git a/docs/cybersecurity/SecDevOps Team/secure-code/TLS_Proof_of_Concept_plus_automation.md b/docs/cybersecurity/SecDevOps Team/secure-code/TLS_Proof_of_Concept_plus_automation.md index 48c92ee28..2f1271a18 100644 --- a/docs/cybersecurity/SecDevOps Team/secure-code/TLS_Proof_of_Concept_plus_automation.md +++ b/docs/cybersecurity/SecDevOps Team/secure-code/TLS_Proof_of_Concept_plus_automation.md @@ -324,3 +324,4 @@ Not only does this provide a validated process for future TLS deployments but al This PoC has resulted in the successful testing of the Certbot – Let's Encrypt TLS solution as applied to our test MQTT broker, with the successful renewal of the deployed certificate. All this is also captured in an easy to run script which will deploy a Mosquitto broker with TLS. + diff --git a/docs/cybersecurity/SecDevOps Team/secure-code/adjusting-mac.md b/docs/cybersecurity/SecDevOps Team/secure-code/adjusting-mac.md index f1e9601bc..77a6a4c72 100644 --- a/docs/cybersecurity/SecDevOps Team/secure-code/adjusting-mac.md +++ b/docs/cybersecurity/SecDevOps Team/secure-code/adjusting-mac.md @@ -33,4 +33,4 @@ import hashlib Although with these changes reversing to get the original MAC address still isn’t possible, it is still the most plausible method. For that to happen we would have to convert the hashes into encryption, -which in itself is riskier \ No newline at end of file +which in itself is riskier diff --git a/docs/cybersecurity/SecDevOps Team/secure-code/flutter-best-practice.md b/docs/cybersecurity/SecDevOps Team/secure-code/flutter-best-practice.md index ab311638c..898a993ee 100644 --- a/docs/cybersecurity/SecDevOps Team/secure-code/flutter-best-practice.md +++ b/docs/cybersecurity/SecDevOps Team/secure-code/flutter-best-practice.md @@ -141,3 +141,4 @@ access ### Obfuscation https://paulmburu.hashnode.dev/securing-a-flutter-app + diff --git a/docs/cybersecurity/SecDevOps Team/secure-code/project-1-MQTT.md b/docs/cybersecurity/SecDevOps Team/secure-code/project-1-MQTT.md index bbb4ce063..4d025eb76 100644 --- a/docs/cybersecurity/SecDevOps Team/secure-code/project-1-MQTT.md +++ b/docs/cybersecurity/SecDevOps Team/secure-code/project-1-MQTT.md @@ -25,4 +25,4 @@ Code Adjustments and Project 1 Collabs ## Sample Codes for Receiving and Sending Through the MQTT -![MQTT Sample](img\mqtt-sample.png) \ No newline at end of file +![MQTT Sample](img\mqtt-sample.png) diff --git a/docs/cybersecurity/SecDevOps Team/secure-code/project1-mqtt-secure-code-review.md b/docs/cybersecurity/SecDevOps Team/secure-code/project1-mqtt-secure-code-review.md index 307683016..c2f12f52d 100644 --- a/docs/cybersecurity/SecDevOps Team/secure-code/project1-mqtt-secure-code-review.md +++ b/docs/cybersecurity/SecDevOps Team/secure-code/project1-mqtt-secure-code-review.md @@ -155,3 +155,4 @@ def main(): if __name__ == "__main__": main() ``` + diff --git a/docs/cybersecurity/SecDevOps Team/secure-code/secure-code-review-methodologies.md b/docs/cybersecurity/SecDevOps Team/secure-code/secure-code-review-methodologies.md index 5e308f49a..6027482b0 100644 --- a/docs/cybersecurity/SecDevOps Team/secure-code/secure-code-review-methodologies.md +++ b/docs/cybersecurity/SecDevOps Team/secure-code/secure-code-review-methodologies.md @@ -172,3 +172,4 @@ There are some common patterns or coding practices that often lead to security v [2] The Cloud Native Experts, “What Is Secure Code Review? Process, Tools, and Best Practices,” 5 November 2023. [Online]. Available: https://www.aquasec.com/cloud-native-academy/devsecops/secure-code-review/. [3] J. Mlakar, “InfoSec Design Principles – 8 Security Principles To Implement,” MlakarTechTalk, 16 April 2019. [Online]. Available: https://www.mlakartechtalk.com/infosec-design-principles-8-security-principles-to-implement/. + diff --git a/docs/cybersecurity/research/CI-CD_Dhairya/_category_.json b/docs/cybersecurity/SecDevOps/Research/CI-CD_Dhairya/_category_.json similarity index 100% rename from docs/cybersecurity/research/CI-CD_Dhairya/_category_.json rename to docs/cybersecurity/SecDevOps/Research/CI-CD_Dhairya/_category_.json diff --git a/docs/cybersecurity/research/CI-CD_Dhairya/best-practices.mdx b/docs/cybersecurity/SecDevOps/Research/CI-CD_Dhairya/best-practices.mdx similarity index 98% rename from docs/cybersecurity/research/CI-CD_Dhairya/best-practices.mdx rename to docs/cybersecurity/SecDevOps/Research/CI-CD_Dhairya/best-practices.mdx index 0b8f5f519..a74bedd76 100644 --- a/docs/cybersecurity/research/CI-CD_Dhairya/best-practices.mdx +++ b/docs/cybersecurity/SecDevOps/Research/CI-CD_Dhairya/best-practices.mdx @@ -10,4 +10,4 @@ PDF Guide type="application/pdf" width="100%" height="800px" -/> \ No newline at end of file +/> diff --git a/docs/cybersecurity/research/CI-CD_Dhairya/on-prem.mdx b/docs/cybersecurity/SecDevOps/Research/CI-CD_Dhairya/on-prem.mdx similarity index 98% rename from docs/cybersecurity/research/CI-CD_Dhairya/on-prem.mdx rename to docs/cybersecurity/SecDevOps/Research/CI-CD_Dhairya/on-prem.mdx index e7a26b677..a10c7ac67 100644 --- a/docs/cybersecurity/research/CI-CD_Dhairya/on-prem.mdx +++ b/docs/cybersecurity/SecDevOps/Research/CI-CD_Dhairya/on-prem.mdx @@ -10,4 +10,4 @@ PDF Guide type="application/pdf" width="100%" height="800px" -/> \ No newline at end of file +/> diff --git a/docs/cybersecurity/research/CI-CD_Dhairya/setting-up.mdx b/docs/cybersecurity/SecDevOps/Research/CI-CD_Dhairya/setting-up.mdx similarity index 98% rename from docs/cybersecurity/research/CI-CD_Dhairya/setting-up.mdx rename to docs/cybersecurity/SecDevOps/Research/CI-CD_Dhairya/setting-up.mdx index 8416183ab..1ce8b3cc9 100644 --- a/docs/cybersecurity/research/CI-CD_Dhairya/setting-up.mdx +++ b/docs/cybersecurity/SecDevOps/Research/CI-CD_Dhairya/setting-up.mdx @@ -10,4 +10,4 @@ PDF Guide type="application/pdf" width="100%" height="800px" -/> \ No newline at end of file +/> diff --git a/docs/cybersecurity/research/CI-CD_Dhairya/troubleshoot.mdx b/docs/cybersecurity/SecDevOps/Research/CI-CD_Dhairya/troubleshoot.mdx similarity index 98% rename from docs/cybersecurity/research/CI-CD_Dhairya/troubleshoot.mdx rename to docs/cybersecurity/SecDevOps/Research/CI-CD_Dhairya/troubleshoot.mdx index d8bc541bb..6e08767c8 100644 --- a/docs/cybersecurity/research/CI-CD_Dhairya/troubleshoot.mdx +++ b/docs/cybersecurity/SecDevOps/Research/CI-CD_Dhairya/troubleshoot.mdx @@ -10,4 +10,4 @@ PDF Guide type="application/pdf" width="100%" height="800px" -/> \ No newline at end of file +/> diff --git a/docs/cybersecurity/research/img/jenkins-architecture.png b/docs/cybersecurity/SecDevOps/Research/img/jenkins-architecture.png similarity index 100% rename from docs/cybersecurity/research/img/jenkins-architecture.png rename to docs/cybersecurity/SecDevOps/Research/img/jenkins-architecture.png diff --git a/docs/cybersecurity/research/img/jenkins-cve.png b/docs/cybersecurity/SecDevOps/Research/img/jenkins-cve.png similarity index 100% rename from docs/cybersecurity/research/img/jenkins-cve.png rename to docs/cybersecurity/SecDevOps/Research/img/jenkins-cve.png diff --git a/docs/cybersecurity/research/img/jenkins-cycle.png b/docs/cybersecurity/SecDevOps/Research/img/jenkins-cycle.png similarity index 100% rename from docs/cybersecurity/research/img/jenkins-cycle.png rename to docs/cybersecurity/SecDevOps/Research/img/jenkins-cycle.png diff --git a/docs/cybersecurity/research/img/jenkins-perms.png b/docs/cybersecurity/SecDevOps/Research/img/jenkins-perms.png similarity index 100% rename from docs/cybersecurity/research/img/jenkins-perms.png rename to docs/cybersecurity/SecDevOps/Research/img/jenkins-perms.png diff --git a/docs/cybersecurity/research/img/nth-check.png b/docs/cybersecurity/SecDevOps/Research/img/nth-check.png similarity index 100% rename from docs/cybersecurity/research/img/nth-check.png rename to docs/cybersecurity/SecDevOps/Research/img/nth-check.png diff --git a/docs/cybersecurity/research/jenkins-and-snyk.md b/docs/cybersecurity/SecDevOps/Research/jenkins-and-snyk.md similarity index 99% rename from docs/cybersecurity/research/jenkins-and-snyk.md rename to docs/cybersecurity/SecDevOps/Research/jenkins-and-snyk.md index 4a0a80d51..aeb818577 100644 --- a/docs/cybersecurity/research/jenkins-and-snyk.md +++ b/docs/cybersecurity/SecDevOps/Research/jenkins-and-snyk.md @@ -71,3 +71,4 @@ The Jenkins integrated with Snyk is very convenient for developers to discover s [3] Saurabh, “What is Jenkins?: Jenkins for continuous integration,” Edureka, 15-Nov-2022. [Online]. Available: https://www.edureka.co/blog/what-is-jenkins/. [Accessed: 22-Nov-2022]. [4] “SNYK code - supported languages and Frameworks,” Snyk Code - Supported languages and frameworks - Snyk User Docs. [Online]. Available: https://docs.snyk.io/products/snyk-code/snyk-code-language-and-framework-support. [Accessed: 22-Nov-2022]. + diff --git a/docs/cybersecurity/research/jenkins-security.md b/docs/cybersecurity/SecDevOps/Research/jenkins-security.md similarity index 99% rename from docs/cybersecurity/research/jenkins-security.md rename to docs/cybersecurity/SecDevOps/Research/jenkins-security.md index 3e5881af4..ecd1a4548 100644 --- a/docs/cybersecurity/research/jenkins-security.md +++ b/docs/cybersecurity/SecDevOps/Research/jenkins-security.md @@ -114,4 +114,4 @@ An open-source automation tool called Jenkins is free to use and comes with buil - A. Ilgayev, “Jenkins security best practices,” Cycode, 24-Aug-2022. [Online]. Available: https://cycode.com/blog/jenkins-security-best-practices/. [Accessed: 23-Nov-2022]. -- Jenkins Plugin for Fortify SCA (v 19.2). YouTube, 2019. [Online video]. Available: https://www.youtube.com/watch?v=9R6FZQu_jGc. [Accessed: 23-Nov-2022]. \ No newline at end of file +- Jenkins Plugin for Fortify SCA (v 19.2). YouTube, 2019. [Online video]. Available: https://www.youtube.com/watch?v=9R6FZQu_jGc. [Accessed: 23-Nov-2022]. diff --git a/docs/cybersecurity/research/sonarqube/SonarQube-local-setup.mdx b/docs/cybersecurity/SecDevOps/Research/sonarqube/SonarQube-local-setup.mdx similarity index 99% rename from docs/cybersecurity/research/sonarqube/SonarQube-local-setup.mdx rename to docs/cybersecurity/SecDevOps/Research/sonarqube/SonarQube-local-setup.mdx index 6adee0a1c..8c424d918 100644 --- a/docs/cybersecurity/research/sonarqube/SonarQube-local-setup.mdx +++ b/docs/cybersecurity/SecDevOps/Research/sonarqube/SonarQube-local-setup.mdx @@ -13,3 +13,4 @@ Author : Ashan Ruwanpathiranage width="100%" height="800px" /> + diff --git a/docs/cybersecurity/research/sonarqube/_category_.json b/docs/cybersecurity/SecDevOps/Research/sonarqube/_category_.json similarity index 100% rename from docs/cybersecurity/research/sonarqube/_category_.json rename to docs/cybersecurity/SecDevOps/Research/sonarqube/_category_.json diff --git a/docs/cybersecurity/research/sonarqube/sonarqube-azure-cloud-host.md b/docs/cybersecurity/SecDevOps/Research/sonarqube/sonarqube-azure-cloud-host.md similarity index 99% rename from docs/cybersecurity/research/sonarqube/sonarqube-azure-cloud-host.md rename to docs/cybersecurity/SecDevOps/Research/sonarqube/sonarqube-azure-cloud-host.md index 4d2fab6a9..169787ddf 100644 --- a/docs/cybersecurity/research/sonarqube/sonarqube-azure-cloud-host.md +++ b/docs/cybersecurity/SecDevOps/Research/sonarqube/sonarqube-azure-cloud-host.md @@ -137,3 +137,4 @@ Now to go to browser --> http://SonarQube_public_dns_name:9000/ By following these steps, you can successfully integrate SonarQube with GitHub to enhance your code quality and maintainability practices. + diff --git a/docs/cybersecurity/research/sonarqube/sonarqube-github-intergration.md b/docs/cybersecurity/SecDevOps/Research/sonarqube/sonarqube-github-intergration.md similarity index 99% rename from docs/cybersecurity/research/sonarqube/sonarqube-github-intergration.md rename to docs/cybersecurity/SecDevOps/Research/sonarqube/sonarqube-github-intergration.md index c03fe85b2..9678267e1 100644 --- a/docs/cybersecurity/research/sonarqube/sonarqube-github-intergration.md +++ b/docs/cybersecurity/SecDevOps/Research/sonarqube/sonarqube-github-intergration.md @@ -140,3 +140,4 @@ This guide provides detailed steps to integrate SonarQube with GitHub. It assume --- By following these steps, you can successfully integrate SonarQube with GitHub to enhance your code quality and maintainability practices. + diff --git a/docs/cybersecurity/research/Efficient and Effective Way of Analyzing TTPs of Malware.md b/docs/cybersecurity/research/Efficient and Effective Way of Analyzing TTPs of Malware.md index d4bf23287..2ea531baf 100644 --- a/docs/cybersecurity/research/Efficient and Effective Way of Analyzing TTPs of Malware.md +++ b/docs/cybersecurity/research/Efficient and Effective Way of Analyzing TTPs of Malware.md @@ -67,3 +67,4 @@ Overall, the blue team can use this method to analyze TTPs of many malwares in l - [Malware Bazaar - APT Bitter Signatures](https://bazaar.abuse.ch/browse/signature/Bitter/) - [VirusTotal](https://www.virustotal.com) + diff --git a/docs/cybersecurity/research/additional-pieces.md b/docs/cybersecurity/research/additional-pieces.md index 1f3228d3b..8a4f7c1be 100644 --- a/docs/cybersecurity/research/additional-pieces.md +++ b/docs/cybersecurity/research/additional-pieces.md @@ -6,6 +6,8 @@ sidebar_position: 99 For those that are a bit too long, or pending conversion -- [Web Application Security](additional-pieces\Web-Application-Security.pdf) -- [GCP Infrastructure Security](additional-pieces\GCP-Infrastructure-Security.pdf) -- [IoT Security](additional-pieces\IoT-Security.pdf) \ No newline at end of file +- Web Application Security *(removed)* +- GCP Infrastructure Security *(removed)* +- IoT Security *(removed)* + + diff --git a/docs/cybersecurity/research/additional-pieces/GCP-Infrastructure-Security.pdf b/docs/cybersecurity/research/additional-pieces/GCP-Infrastructure-Security.pdf deleted file mode 100644 index d61c30568..000000000 Binary files a/docs/cybersecurity/research/additional-pieces/GCP-Infrastructure-Security.pdf and /dev/null differ diff --git a/docs/cybersecurity/research/additional-pieces/IoT-Security.pdf b/docs/cybersecurity/research/additional-pieces/IoT-Security.pdf deleted file mode 100644 index a0e669246..000000000 Binary files a/docs/cybersecurity/research/additional-pieces/IoT-Security.pdf and /dev/null differ diff --git a/docs/cybersecurity/research/additional-pieces/Web-Application-Security.pdf b/docs/cybersecurity/research/additional-pieces/Web-Application-Security.pdf deleted file mode 100644 index 4ec03c2e1..000000000 Binary files a/docs/cybersecurity/research/additional-pieces/Web-Application-Security.pdf and /dev/null differ diff --git a/docs/cybersecurity/research/docs/Feasibility-Study-Hayabusa.pdf b/docs/cybersecurity/research/docs/Feasibility-Study-Hayabusa.pdf deleted file mode 100644 index 8ff945f28..000000000 Binary files a/docs/cybersecurity/research/docs/Feasibility-Study-Hayabusa.pdf and /dev/null differ diff --git a/docs/cybersecurity/research/docs/Feasibility-Study-on-OpenCTI-Template.pdf b/docs/cybersecurity/research/docs/Feasibility-Study-on-OpenCTI-Template.pdf deleted file mode 100644 index f4c72a86b..000000000 Binary files a/docs/cybersecurity/research/docs/Feasibility-Study-on-OpenCTI-Template.pdf and /dev/null differ diff --git a/docs/cybersecurity/research/docs/Feasibility-Study-on-OpenCTI.pdf b/docs/cybersecurity/research/docs/Feasibility-Study-on-OpenCTI.pdf deleted file mode 100644 index 309bb8b54..000000000 Binary files a/docs/cybersecurity/research/docs/Feasibility-Study-on-OpenCTI.pdf and /dev/null differ diff --git a/docs/cybersecurity/research/feasibility study on OpenCTI.md b/docs/cybersecurity/research/feasibility study on OpenCTI.md index 7cbe2c105..1663de2aa 100644 --- a/docs/cybersecurity/research/feasibility study on OpenCTI.md +++ b/docs/cybersecurity/research/feasibility study on OpenCTI.md @@ -135,3 +135,4 @@ To determine whether OpenCTI can effectively support and enhance the threat inte - Summary of Findings: The conclusion will reflect the suitability of OpenCTI for deployment within the existing VM environment. Emphasize that this approach maximizes the use of current resources while still providing the desired enhancements to threat intelligence capabilities. - Recommendations: Recommend moving forward with OpenCTI, with an implementation plan that includes careful testing and optimization within the VM environment. - Next Steps: The next steps will include working with the university’s IT team to ensure the VMs are properly configured for OpenCTI and planning for a pilot phase to test the deployment in this environment. + diff --git a/docs/cybersecurity/research/major-areas-response.md b/docs/cybersecurity/research/major-areas-response.md deleted file mode 100644 index f72da18dd..000000000 --- a/docs/cybersecurity/research/major-areas-response.md +++ /dev/null @@ -1,63 +0,0 @@ ---- -sidebar_position: 11 ---- -# How We Can Monitor Major Areas -In response to major areas review - -:::info -**Author:** Jamison Begley -::: - -## Cloud Infrastructure - -To maintain the integrity of cloud infrastructure, all machines and accounts must be password protected, alongside the implementation of 2-Factor Authentication. Not only does this apply a second layer of security to the cloud infrastructure, but log-in attempts can be monitored and logged through the 2FA implementation, ensuring that the company can be made aware in the event of an infrastructural breach in the cloud department. This allows for quick responsiveness in the event of an emergency, thus working to protect sensitive information and network storage. - -## Application Performance - -A major way to monitor application performance is through user feedback and reviews. Only a user can provide a gauge as to whether the performance needs to be worked on and improved, and what specifically needs to be improved on. An active strive for positive user reviews can help aid this, by swiftly responding to negative and constructive user reviews to provide an adequate experience. - -Aside from reviews, load testing can be done on the applications to test for internal performance limitations and scalability issues where server-side upgrades may need to take place if necessary. - -Though ultimately, application performance can be monitored through the implementation of technical monitoring metrics, such as response time, error rates and total-resource usage. Application Performance Measurement (APM) solutions much be explored for an in-depth analysis of application performance. - -## Resource Usage and Cost - -To monitor resource usage, tools such as Datadog or Grafana can be utilized to monitor CPU usage, memory usage, disk activity and network traffic. This information can be used to dictate whether certain areas of operation are under heavy load, and appropriate measures can be taken to come to a solution. - -Moreover, to monitor resource costs, budgeting practices must take place to ensure that our resources expenses are managed effectively. To do this, a cost-usage matrix should be created to assess whether it is worthwhile spending a certain amount of money on a resource that we may barely use. By doing so, we can cut out unnecessary resource costs, therefore optimizing our budget allocation. - -## Security and Compliance - -Not only do we need to adhere to industry standards, but regular checks on full compliance policies need to take place to ensure that these standards are adhered to. This can be monitored through regular risk assessments based on an already defined risk matrix, documenting and reporting any changes and how they were assessed/put in place. All relevant employees must be briefed and trained so they are aware of all security and compliance measures, so they are not compromised at any time. Though these compliance policies and contingency plans must be easily accessible for all staff members in the event of a compliance breach. - -## Network Performance - -To monitor network performance, real-time bandwidth measurements should regularly be taken to identify if the network is under high load. Applications like Wireshark can then be utilized to investigate network traffic and its impact on performance. This allows the networking team to analyze network traffic in real-time, identifying which connections require additional bandwidth. - -Additionally, automated alerts can be set up to send a message to our networking team when there are networking issues, allowing them to identify where the network is underperforming and how to adjust accordingly. - - -## Backup and Disaster Recovery. - -Backup and Disaster recovery can be implemented and monitored through the administration of an automated storage backup program – such as “Microsoft Azure Backup” (though we may need to switch from GCP first), or Veritas NetBackup, which offers automated storage backups for both, on-site and off-site storage. - -These storage logs should be regularly reviewed to ensure that all required information is stored safely, and incident response plans should be put in place in the event of the need for Disaster Recovery. - -## User Activity and Usage - -To monitor user activity and usage, logging mechanisms should be implemented to verify and record user authentication events. These logs will include information such as login attempts (both successful and unsuccessful). This allows the team to determine when an individual is connected to the network, therefore monitoring their usage. - -To better monitor activity and usage, Redback Operations can investigate implementing SIEMs to better record activity on devices, servers, applications, and security measures (such as firewalls) in the form of logs. - -Moreover, regular audits can take place, reviewing the usage of users (recorded by the logging systems previously explained). This can be used to identify how users navigate the system, what they access and what they have access to, allowing for appropriate changes to be made if required. - - - -## System Updates and Patches - -To monitor system updates and patches, patch management software, such as “Windows Server Update Services” or “System Center Configuration Manager” can be utilized to automatically patch and update the Redback Operations servers and systems to actively patch any bugs or exploits. In tandem with this, automatic updates will be provided when a new patch or update is available. - -Additionally, the implementation of tools such as “Nessus” or “OpenVAS” can be used to regularly scan for vulnerabilities in the system and server. These scans can then be logged and reported and accurately responded to via a previously explained patch management software. - -Finally, we can establish a monitoring/reporting system to track the deployment of patches, allowing us to maintain compliance with security protocols and actively respond to any issues that may arise in the patch deployment phase. - diff --git a/docs/cybersecurity/research/major-areas.md b/docs/cybersecurity/research/major-areas.md deleted file mode 100644 index 00e4838ea..000000000 --- a/docs/cybersecurity/research/major-areas.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -sidebar_position: 10 ---- - -# Major Areas of Redback to be Monitored -See following document for response - -:::info -**Author:** Saksham Rama -::: - -## Cloud Infrastructure: - -Monitoring the performance, availability, and security of the cloud infrastructure, such as virtual machines, databases, and storage, is crucial to ensure smooth operations and data protection. - -## Application Performance: - -Monitoring the performance of Redback Operations' applications, including response times, error rates, and resource utilization, helps identify bottlenecks, optimize performance, and maintain a positive user experience. - -## Resource Usage and Cost: - -Keeping track of resource usage and associated costs is essential for budgeting and cost optimization. Monitoring resource utilization helps identify underused or overprovisioned resources and adjust allocations accordingly. - -## Security and Compliance: - -Monitoring security events, vulnerabilities, and compliance with industry standards is vital to protect sensitive data and maintain regulatory compliance. This includes monitoring access controls, encryption, and authentication mechanisms. - -## Network Performance: - -Monitoring network latency, bandwidth, and traffic patterns helps ensure reliable communication between cloud services, applications, and users. Identifying and addressing network issues can prevent delays and improve overall performance. - -## Backup and Disaster Recovery: - -Monitoring backup processes and disaster recovery plans ensures data protection and business continuity. Regularly testing backups and recovery procedures helps maintain a robust disaster recovery strategy. - -## User Activity and Usage: - -Monitoring user activity and usage patterns can help identify potential issues, optimize resource allocation, and improve the overall user experience. This includes monitoring user authentication, authorization, and access to resources. - -## System Updates and Patches: - -Keeping track of system updates and patches is essential to maintain a secure and stable environment. Regularly applying updates and patches helps protect against known vulnerabilities and ensures optimal performance. - -## Conclusion: - -Monitoring these major areas will help Redback Operations maintain a secure, efficient, and cost-effective cloud infrastructure, ensuring smooth operations and a positive user experience. diff --git a/docs/cybersecurity/research/nagios/MQTT_Temperature_Plugin_Setup_Guide.md b/docs/cybersecurity/research/nagios/MQTT_Temperature_Plugin_Setup_Guide.md index e241567dd..874c34d5c 100644 --- a/docs/cybersecurity/research/nagios/MQTT_Temperature_Plugin_Setup_Guide.md +++ b/docs/cybersecurity/research/nagios/MQTT_Temperature_Plugin_Setup_Guide.md @@ -129,3 +129,4 @@ This completes the setup of the MQTT temperature monitoring plugin in Nagios. Yo + diff --git a/docs/cybersecurity/research/nagios/Nagios-Report.md b/docs/cybersecurity/research/nagios/Nagios-Report.md index a5ca35776..b2ae6be4a 100644 --- a/docs/cybersecurity/research/nagios/Nagios-Report.md +++ b/docs/cybersecurity/research/nagios/Nagios-Report.md @@ -406,3 +406,4 @@ define contact { Implementing Nagios for monitoring a network with IoT devices connected via an MQTT server is feasible, provided careful planning, configuration, and testing are carried out. Addressing potential gaps and challenges through stakeholder engagement and training will ensure a smooth implementation and effective network monitoring. By thoroughly preparing the environment, configuring Nagios to suit specific network needs, and rigorously testing the setup, the deployment can be successfully transitioned to production. With proper consultation, skill development, and a phased approach, Nagios can significantly enhance the monitoring capabilities of the network, ensuring reliable performance and prompt alerting for potential issues. + diff --git a/docs/cybersecurity/research/nagios/Redback_nagios_setup_guide.md b/docs/cybersecurity/research/nagios/Redback_nagios_setup_guide.md index d072c8625..083e9987a 100644 --- a/docs/cybersecurity/research/nagios/Redback_nagios_setup_guide.md +++ b/docs/cybersecurity/research/nagios/Redback_nagios_setup_guide.md @@ -233,3 +233,4 @@ Since there is another service running on port 80, change that to port 443 in or ![Apache 2 setup](img\apache2.png) **Figure 2: Apache 2 setup** + diff --git a/docs/data-warehousing/Data Anonymization/dataanonymization.md b/docs/data-warehousing/Data Anonymization/dataanonymization.md index d9c7391dc..ab5257323 100644 --- a/docs/data-warehousing/Data Anonymization/dataanonymization.md +++ b/docs/data-warehousing/Data Anonymization/dataanonymization.md @@ -72,3 +72,4 @@ facilitating research, and building trust within the healthcare ecosystem. By an sensitive attributes and masking identifiable information, organizations uphold ethical standards while harnessing the power of data-driven insights to improve patient outcomes and healthcare delivery + diff --git a/docs/data-warehousing/Data Lakehouse/Data Architecture.md b/docs/data-warehousing/Data Lakehouse/Data Architecture.md index ca20d22d5..ae4ca23cf 100644 --- a/docs/data-warehousing/Data Lakehouse/Data Architecture.md +++ b/docs/data-warehousing/Data Lakehouse/Data Architecture.md @@ -284,3 +284,4 @@ Most importantly, we need to incorporate an orchestration tool this will elimina processes involved in entering the data and remove potential for human error as part of this process. At the time of writing (TRI 1 2024) no decision has been made in regard to orchestration and has been raised as a possible project for Tri 2 2024. + diff --git a/docs/data-warehousing/Data Lakehouse/Data Warehouse Requirements.md b/docs/data-warehousing/Data Lakehouse/Data Warehouse Requirements.md index 574d42835..96d162323 100644 --- a/docs/data-warehousing/Data Lakehouse/Data Warehouse Requirements.md +++ b/docs/data-warehousing/Data Lakehouse/Data Warehouse Requirements.md @@ -241,4 +241,4 @@ Summary table of Data Lakehouse options Data storage for the initial implementation of the Data Lakehouse platform will be the Deakin virtual machine, this will operate as BareMetal on-premises storage. In future Trimesters there is scope to secure -funding for a cloud storage solution. \ No newline at end of file +funding for a cloud storage solution. diff --git a/docs/data-warehousing/Data preprocessing pipeline with MinIo/Data Preprocessing Pipeline Doc.md b/docs/data-warehousing/Data preprocessing pipeline with MinIo/Data Preprocessing Pipeline Doc.md index 296e03a39..bef612fbe 100644 --- a/docs/data-warehousing/Data preprocessing pipeline with MinIo/Data Preprocessing Pipeline Doc.md +++ b/docs/data-warehousing/Data preprocessing pipeline with MinIo/Data Preprocessing Pipeline Doc.md @@ -47,3 +47,4 @@ Once processed, the data is moved to 'Silver' buckets, categorized as cleaned an ## Conclusion The data preprocessing pipeline serves as a critical component in the data management ecosystem, bridging the gap between raw data collection and advanced data analysis. Its integration with MinIO highlights a commitment to leveraging advanced storage solutions to enhance data processing workflows. This theoretical approach not only supports current data needs but also anticipates future expansions, ensuring the pipeline remains a valuable asset in managing and utilizing data effectively. + diff --git a/docs/data-warehousing/Data preprocessing pipeline with MinIo/POC.md b/docs/data-warehousing/Data preprocessing pipeline with MinIo/POC.md index ee4d1e003..cfb2b36c1 100644 --- a/docs/data-warehousing/Data preprocessing pipeline with MinIo/POC.md +++ b/docs/data-warehousing/Data preprocessing pipeline with MinIo/POC.md @@ -96,3 +96,4 @@ The Proof of Concept successfully demonstrates that the data preprocessing pipel implemented in MinIO using Python. CSV files can be downloaded, cleaned, and moved between buckets efficiently, with clear logging and error handling in place. The pipeline is ready for scaling, automation, and integration into broader data workflows at Redback Operations. + diff --git a/docs/data-warehousing/Dremio/Dremio-API.md b/docs/data-warehousing/Dremio/Dremio-API.md index da71ead51..fd4c2a3d4 100644 --- a/docs/data-warehousing/Dremio/Dremio-API.md +++ b/docs/data-warehousing/Dremio/Dremio-API.md @@ -73,3 +73,4 @@ Which you can use just like any other dataframe like: ```python display(df) ``` + diff --git a/docs/data-warehousing/Dremio/Managing-the-structured-solution.md b/docs/data-warehousing/Dremio/Managing-the-structured-solution.md index 03ba541b5..7357600af 100644 --- a/docs/data-warehousing/Dremio/Managing-the-structured-solution.md +++ b/docs/data-warehousing/Dremio/Managing-the-structured-solution.md @@ -43,3 +43,4 @@ The flask api is a level of security and convenience on top of the dremio rest a The code for the app and docker container running it can be found [here](https://github.com/Jesse-Rees/redback-data-warehouse/tree/Structured-Solution/Structured%20Dremio%20Solution/Flask-api), that link is the same fork as the script and should be added to the main branch soon in the same directory. The guide on how to use the api as a data analyst will be uploaded alongside this one and should be found in the same folder labeled structured solution. + diff --git a/docs/data-warehousing/Instructional Documents/Data Warehouse Overview.md b/docs/data-warehousing/Instructional Documents/Data Warehouse Overview.md index f8c6f403a..10220f991 100644 --- a/docs/data-warehousing/Instructional Documents/Data Warehouse Overview.md +++ b/docs/data-warehousing/Instructional Documents/Data Warehouse Overview.md @@ -79,3 +79,4 @@ Kibana: [http://10.137.0.149:5601](http://10.137.0.149:5601) + diff --git a/docs/data-warehousing/Instructional Documents/Dremio Guide.md b/docs/data-warehousing/Instructional Documents/Dremio Guide.md index 13c15fa1c..4a0482de9 100644 --- a/docs/data-warehousing/Instructional Documents/Dremio Guide.md +++ b/docs/data-warehousing/Instructional Documents/Dremio Guide.md @@ -72,3 +72,4 @@ Alternatively, Dremio offers a SQL endpoint that through code you can query the See the documentation of [Dremio API ](https://redback-operations.github.io/redback-documentation/docs/data-warehousing/Data%20Lakehouse/Dremio-API(For%20data%20analysts)) also located in the Data warehouse documentation for a detailed explanation. + diff --git a/docs/data-warehousing/Instructional Documents/GitHub.md b/docs/data-warehousing/Instructional Documents/GitHub.md index 776bff604..83a62c20e 100644 --- a/docs/data-warehousing/Instructional Documents/GitHub.md +++ b/docs/data-warehousing/Instructional Documents/GitHub.md @@ -19,3 +19,4 @@ Here is a Redback video series that explains the steps to incorporate GitHub. Yo [GitHub cloning and forking Video](https://youtu.be/FVEpojv_Jxg?si=QxcT3Cgwr6BACQLk) + diff --git a/docs/data-warehousing/Instructional Documents/How To Access The File Upload Service.md b/docs/data-warehousing/Instructional Documents/How To Access The File Upload Service.md index a6b32c7a5..30e0b42fd 100644 --- a/docs/data-warehousing/Instructional Documents/How To Access The File Upload Service.md +++ b/docs/data-warehousing/Instructional Documents/How To Access The File Upload Service.md @@ -130,4 +130,4 @@ Original files are stored in Bronze and Pre-processed in silver ![origdl](./pictures/origdl.png) -![viewsilv](./pictures/viewsilv.png) \ No newline at end of file +![viewsilv](./pictures/viewsilv.png) diff --git a/docs/data-warehousing/Instructional Documents/Local Machine Guide.md b/docs/data-warehousing/Instructional Documents/Local Machine Guide.md index a946d5709..2e770c631 100644 --- a/docs/data-warehousing/Instructional Documents/Local Machine Guide.md +++ b/docs/data-warehousing/Instructional Documents/Local Machine Guide.md @@ -57,4 +57,4 @@ The following is to install a tool called RedisInsight to easily access and insp * **Host:** `localhost` * **Port:** `6379` * **Password:** `bugbOxRedis@123` - * *(Note: The container’s port is 6379. If prompted for a password, use `bugbOxRedis@123`.)* \ No newline at end of file + * *(Note: The container’s port is 6379. If prompted for a password, use `bugbOxRedis@123`.)* diff --git a/docs/data-warehousing/Instructional Documents/MinIO Guide.md b/docs/data-warehousing/Instructional Documents/MinIO Guide.md index d7dfecf11..0b2702287 100644 --- a/docs/data-warehousing/Instructional Documents/MinIO Guide.md +++ b/docs/data-warehousing/Instructional Documents/MinIO Guide.md @@ -68,4 +68,4 @@ secret_key = AWS_SECRET_KEY -``` \ No newline at end of file +``` diff --git a/docs/data-warehousing/Instructional Documents/Next Steps.md b/docs/data-warehousing/Instructional Documents/Next Steps.md index 817194c4d..f0f04649e 100644 --- a/docs/data-warehousing/Instructional Documents/Next Steps.md +++ b/docs/data-warehousing/Instructional Documents/Next Steps.md @@ -26,3 +26,4 @@ At the time of writing there are opportunities to: - Provide integration and orchestration designs to the existing data warehouse solutions - Incorporate production data (not sample data) from Redback projects into the Data Warehouse solutions in a meaningful way. + diff --git a/docs/data-warehousing/Instructional Documents/Not in Prod.md b/docs/data-warehousing/Instructional Documents/Not in Prod.md index 2c0285ab9..c4000445a 100644 --- a/docs/data-warehousing/Instructional Documents/Not in Prod.md +++ b/docs/data-warehousing/Instructional Documents/Not in Prod.md @@ -29,4 +29,4 @@ By following the address: [http://10.137.0.149:8888/](http://10.137.0.149:8888/) This notebook exists and is running in the virtual machine where Spark jobs can be configured and ran. This represents a functionality to code and run distributed Spark jobs within the virtual machine and has the advantage of being able to process large datasets using the Spark DAG scheduler and partitioning data with distributed computing. At the time of writing without large production datasets in the VM there isn't currently a need for this functionality yet. ![spark](./pictures/spark.png) - \ No newline at end of file + diff --git a/docs/data-warehousing/Instructional Documents/Redback Data Warehouse - Complete Guide.md b/docs/data-warehousing/Instructional Documents/Redback Data Warehouse - Complete Guide.md index 55a60049f..2875980a1 100644 --- a/docs/data-warehousing/Instructional Documents/Redback Data Warehouse - Complete Guide.md +++ b/docs/data-warehousing/Instructional Documents/Redback Data Warehouse - Complete Guide.md @@ -704,3 +704,4 @@ As the platform evolves, so will this guide. If you notice missing pieces or hav *version 1 - Document prepared by Daezel Goyal, Data Warehouse Leader – Redback Operations, May 2025* + diff --git a/docs/data-warehousing/Instructional Documents/VM Crash and next steps.md b/docs/data-warehousing/Instructional Documents/VM Crash and next steps.md index b85a80a78..8fa0664c2 100644 --- a/docs/data-warehousing/Instructional Documents/VM Crash and next steps.md +++ b/docs/data-warehousing/Instructional Documents/VM Crash and next steps.md @@ -145,3 +145,4 @@ This documentation ensures that future leaders and contributors **do not repeat --- *Document prepared by Daezel Goyal, Data Warehouse Leader – Redback Operations, May 2025* + diff --git a/docs/data-warehousing/Instructional Documents/VM Guide.md b/docs/data-warehousing/Instructional Documents/VM Guide.md index cb6174bbb..73923c0c1 100644 --- a/docs/data-warehousing/Instructional Documents/VM Guide.md +++ b/docs/data-warehousing/Instructional Documents/VM Guide.md @@ -150,4 +150,4 @@ fileuploadservice_dremio-data: external: true -``` \ No newline at end of file +``` diff --git a/docs/data-warehousing/Introduction to Data Warehouse.md b/docs/data-warehousing/Introduction to Data Warehouse.md index 1018863f8..989bc790c 100644 --- a/docs/data-warehousing/Introduction to Data Warehouse.md +++ b/docs/data-warehousing/Introduction to Data Warehouse.md @@ -70,3 +70,4 @@ Our data flows through a standardized pipeline that ensures quality and consiste --- Understanding the structure and purpose of a data warehouse is a fundamental step toward contributing effectively to data-centric projects. Whether you're interested in development, analysis, or operations, the Data Warehouse offers a solid foundation for impactful work at Redback. + diff --git a/docs/data-warehousing/MongoDb Connection/mongodbconnection.md b/docs/data-warehousing/MongoDb Connection/mongodbconnection.md index 694b5804f..96a44d798 100644 --- a/docs/data-warehousing/MongoDb Connection/mongodbconnection.md +++ b/docs/data-warehousing/MongoDb Connection/mongodbconnection.md @@ -107,3 +107,4 @@ cd "MongoDB Connection/Project1" - **Response**: - `200 OK`: Returns a success message if the document was deleted. - `404 Not Found`: If the document is not found. + diff --git a/docs/data-warehousing/Mosquitto/mosquitto_documentation.md b/docs/data-warehousing/Mosquitto/mosquitto_documentation.md index 91e7ba4aa..25b8d43c4 100644 --- a/docs/data-warehousing/Mosquitto/mosquitto_documentation.md +++ b/docs/data-warehousing/Mosquitto/mosquitto_documentation.md @@ -123,3 +123,4 @@ sudo tail -f /var/log/mosquitto/mosquitto.log | `/etc/mosquitto/conf.d/` | Directory for additional configs | | `/var/log/mosquitto/mosquitto.log` | Primary log file | | `/var/lib/mosquitto/` | Persistence data location | + diff --git a/docs/data-warehousing/Restic/restic.md b/docs/data-warehousing/Restic/restic.md index 986d59da7..e080efe69 100644 --- a/docs/data-warehousing/Restic/restic.md +++ b/docs/data-warehousing/Restic/restic.md @@ -150,3 +150,4 @@ docker-compose down - [Restic Documentation](https://restic.readthedocs.io/) - [Docker Documentation](https://docs.docker.com/) - [Docker Compose Documentation](https://docs.docker.com/compose/) + diff --git a/docs/data-warehousing/Streamlit tutorial/BugBox-Streamlit-Tutorial.md b/docs/data-warehousing/Streamlit tutorial/BugBox-Streamlit-Tutorial.md index 63777fc6d..69a1710ef 100644 --- a/docs/data-warehousing/Streamlit tutorial/BugBox-Streamlit-Tutorial.md +++ b/docs/data-warehousing/Streamlit tutorial/BugBox-Streamlit-Tutorial.md @@ -224,3 +224,4 @@ By following these instructions, you can set up, modify, and manage the SQLite d - Staff members have access to student data which are in the database and can also download all the student data as csv if needed. This will enable them to find the unique id/other details of students and recover QR Codes(in case they loose them) + diff --git a/docs/data-warehousing/Streamlit tutorial/Streamlit-vs-Gradio.md b/docs/data-warehousing/Streamlit tutorial/Streamlit-vs-Gradio.md index 7b4a0a9e2..2ba927933 100644 --- a/docs/data-warehousing/Streamlit tutorial/Streamlit-vs-Gradio.md +++ b/docs/data-warehousing/Streamlit tutorial/Streamlit-vs-Gradio.md @@ -56,3 +56,4 @@ Choosing between Streamlit and Gradio depends on specific project requirements a ![streamlit vs gradio](images/image-5.png) Reference: [Gradio vs. Streamlit Comparison on StackShare](https://stackshare.io/stackups/gradio-vs-streamlit#:~:text=In%20summary%2C%20Gradio%20and%20Streamlit%20have%20some%20key,community%20and%20documentation%20support%2C%20and%20ease%20of%20use.) + diff --git a/docs/data-warehousing/Streamlit tutorial/streamlit_tutorial.md b/docs/data-warehousing/Streamlit tutorial/streamlit_tutorial.md index d9c7a2107..c1d4a3b95 100644 --- a/docs/data-warehousing/Streamlit tutorial/streamlit_tutorial.md +++ b/docs/data-warehousing/Streamlit tutorial/streamlit_tutorial.md @@ -292,3 +292,4 @@ cd my_streamlit_app 3. [YouTube Tutorial on Streamlit](https://www.youtube.com/watch?v=ZZ4B0QUHuNc&list=PLtqF5YXg7GLmCvTswG32NqQypOuYkPRUE) 4. [Streamlit vs. Gradio: A Comprehensive Comparison](https://medium.com/@ShahabH/streamlit-vs-gradio-a-comprehensive-comparison-cc2f28b7b832) + diff --git a/docs/documentation-maintenance/approval-guide.md b/docs/documentation-maintenance/approval-guide.md index 252f41e0d..ee7372292 100644 --- a/docs/documentation-maintenance/approval-guide.md +++ b/docs/documentation-maintenance/approval-guide.md @@ -73,4 +73,4 @@ Often, large chunks of code is included without being included in code blocks. I If a document is submitted with technical data, please look over it carefully (or get someone from the Cyber Security team) to ensure no data has been leaked that may be sensitive to any projects or personal info. -Similarly, large portions of irrelevant data may not be ideal for this platform. Documents should also be checked for AI generation, if this is suspected, consult with mentors for next steps, however these should not be hosted (unless they are explicitly stated as AI generated) due to Deakin AI Policies. s \ No newline at end of file +Similarly, large portions of irrelevant data may not be ideal for this platform. Documents should also be checked for AI generation, if this is suspected, consult with mentors for next steps, however these should not be hosted (unless they are explicitly stated as AI generated) due to Deakin AI Policies. s diff --git a/docs/documentation-maintenance/future-plans.md b/docs/documentation-maintenance/future-plans.md index 9bb631b30..354a97082 100644 --- a/docs/documentation-maintenance/future-plans.md +++ b/docs/documentation-maintenance/future-plans.md @@ -30,3 +30,4 @@ Create more sophisticated, easier to understand tutorials. As well as more advan ### Homepage Revamp Currently the homepage is using the default Docusaurus template, Redback should utilise the skills on offer to make this more appealing. + diff --git a/docs/documentation-maintenance/general-info.md b/docs/documentation-maintenance/general-info.md index 53b9086b1..48e16ee9e 100644 --- a/docs/documentation-maintenance/general-info.md +++ b/docs/documentation-maintenance/general-info.md @@ -34,3 +34,4 @@ Cause: Image docs/cybersecurity/research/ids-and-wazuh/img/wazuh1.png used in do ``` This can be multiple things. Either the image is simply not present; the casing is wrong "image.png" vs "Image.pmg" vs "image.PNG" are all different, it needs to match in both the file and reference. Otherwise, check that the path is correct. + diff --git a/docs/documentation-maintenance/math-test.md b/docs/documentation-maintenance/math-test.md index 911826004..d5ed09da2 100644 --- a/docs/documentation-maintenance/math-test.md +++ b/docs/documentation-maintenance/math-test.md @@ -10,4 +10,4 @@ $$ Let $f\colon[a,b]\to\R$ be Riemann integrable. Let $F\colon[a,b]\to\R$ be $F(x)=\int_{a}^{x} f(t)\,dt$. Then $F$ is continuous, and at all $x$ such that -$f$ is continuous at $x$, $F$ is differentiable at $x$ with $F'(x)=f(x)$. \ No newline at end of file +$f$ is continuous at $x$, $F$ is differentiable at $x$ with $F'(x)=f(x)$. diff --git a/docs/example/example-nested/example.md b/docs/example/example-nested/example.md index a5b2e74a1..34abadcc5 100644 --- a/docs/example/example-nested/example.md +++ b/docs/example/example-nested/example.md @@ -8,3 +8,4 @@ Need some more folders? Add some folders within folders! ## Duplicate me! + diff --git a/docs/example/example.md b/docs/example/example.md index 1b94ba6e3..c037dfa32 100644 --- a/docs/example/example.md +++ b/docs/example/example.md @@ -47,4 +47,4 @@ Do things like this | blah | blah | blah | | ---- | ---- | ---- | | test | test | test | -| test | test | test | \ No newline at end of file +| test | test | test | diff --git a/docs/example/first-example.md b/docs/example/first-example.md index c00558823..b950d6d20 100644 --- a/docs/example/first-example.md +++ b/docs/example/first-example.md @@ -61,4 +61,4 @@ This will then go to the reviewers, who will then review your work to ensure it ## Done! -That's it! If you require any other assistance, please review the other tutorials on using Markdown and the file structures. \ No newline at end of file +That's it! If you require any other assistance, please review the other tutorials on using Markdown and the file structures. diff --git a/docs/example/lorem.md b/docs/example/lorem.md index 8b547ba43..43f53713e 100644 --- a/docs/example/lorem.md +++ b/docs/example/lorem.md @@ -23,3 +23,4 @@ Sed tempor imperdiet nisl, at suscipit urna molestie eu. Pellentesque viverra co - vitae lectus viverra - + diff --git a/docs/example/pdf-tutorial.mdx b/docs/example/pdf-tutorial.mdx index 21a7dc2b1..5449b3869 100644 --- a/docs/example/pdf-tutorial.mdx +++ b/docs/example/pdf-tutorial.mdx @@ -76,3 +76,4 @@ fork of [the repo](https://github.com/Redback-Operations/redback-documentation/b width="100%" height="800px" /> + diff --git a/docs/example/tutorial.md b/docs/example/tutorial.md index f7ab470c7..c9417b2d3 100644 --- a/docs/example/tutorial.md +++ b/docs/example/tutorial.md @@ -64,4 +64,4 @@ test ### Titles -#### Titles \ No newline at end of file +#### Titles diff --git a/docs/onboarding/company-profile.md b/docs/onboarding/company-profile.md index e73222488..85bdf071d 100644 --- a/docs/onboarding/company-profile.md +++ b/docs/onboarding/company-profile.md @@ -317,4 +317,4 @@ This project does not yet have a leader for Trimester 2, so the position is open - Flutter - Django - Python -- Firebase \ No newline at end of file +- Firebase diff --git a/docs/onboarding/github/github-org-guide.md b/docs/onboarding/github/github-org-guide.md index 7703ac78b..405539df2 100644 --- a/docs/onboarding/github/github-org-guide.md +++ b/docs/onboarding/github/github-org-guide.md @@ -221,4 +221,4 @@ README file: - Instructions on how to set up the repo and start working with it. Include prerequisites (e.g., for a JavaScript project, having Node installed) and step-by-step instructions that ensure the majority of students will be able to independently set up and run the project locally. -You may not have all this information ready yet for a new repository that doesn’t contain any code yet, so simply ensure you return to this step when you do. \ No newline at end of file +You may not have all this information ready yet for a new repository that doesn’t contain any code yet, so simply ensure you return to this step when you do. diff --git a/docs/onboarding/github/pull-requests.md b/docs/onboarding/github/pull-requests.md index 0a137760a..9bcc9ef66 100644 --- a/docs/onboarding/github/pull-requests.md +++ b/docs/onboarding/github/pull-requests.md @@ -117,4 +117,4 @@ compare branch drop-down menu to select the branch we made your changes in. 6. We then fill in our title and description for the pull request. -7. We then create the pull request that is ready for review, by clicking on Create Pull Request. \ No newline at end of file +7. We then create the pull request that is ready for review, by clicking on Create Pull Request. diff --git a/docs/orion-backend/airflowdoc.md b/docs/orion-backend/airflowdoc.md index 8a3d4afa4..29e4b910b 100644 --- a/docs/orion-backend/airflowdoc.md +++ b/docs/orion-backend/airflowdoc.md @@ -568,3 +568,4 @@ curl -X POST http://your-fastapi-service-url/trigger-test-kafka-dag/ - Implement timeouts and retries in client applications - Handle potential delays between DAG triggering and result availability - Monitor the API service logs for debugging issues# Apache Airflow Documentation for Face Detection and Feature Extraction Pipelines + diff --git a/docs/orion-backend/kafkadocs/readme.md b/docs/orion-backend/kafkadocs/readme.md index 1e1429166..5a2c55ea5 100644 --- a/docs/orion-backend/kafkadocs/readme.md +++ b/docs/orion-backend/kafkadocs/readme.md @@ -1182,4 +1182,5 @@ This section includes supporting materials such as definitions, external resourc + diff --git a/docs/project-1/iot/MQTTtoSerialCommunication_Markdown.md b/docs/project-1/iot/MQTTtoSerialCommunication_Markdown.md index 7c45d6788..199e61674 100644 --- a/docs/project-1/iot/MQTTtoSerialCommunication_Markdown.md +++ b/docs/project-1/iot/MQTTtoSerialCommunication_Markdown.md @@ -208,3 +208,4 @@ Handling serial port changes dynamically involves: · Continuous Monitoring and Error Handling: Implementing error handling in the main loop to detect and recover from serial communication errors, such as disconnections. This approach ensures that your system remains flexible and resilient to changes in the serial port configuration, providing a seamless user experience. + diff --git a/docs/project-1/iot/ble-connectivity/BLE-Auto-Connect-Script.md b/docs/project-1/iot/ble-connectivity/BLE-Auto-Connect-Script.md index 79721ffd9..9abbad524 100644 --- a/docs/project-1/iot/ble-connectivity/BLE-Auto-Connect-Script.md +++ b/docs/project-1/iot/ble-connectivity/BLE-Auto-Connect-Script.md @@ -119,4 +119,4 @@ Some improvements to the script are desireable and left for future team members - `bluetoothctl` - https://manpages.debian.org/unstable/bluez/bluetoothctl.1.en.html - `expect` introduction - https://phoenixnap.com/kb/linux-expect - Reading files using `tcl` (the backbone of `expect`) - https://wiki.tcl-lang.org/page/How+do+I+read+and+write+files+in+Tcl -- Bash script & expect script located in [scripts/ble-auto-connect/](https://github.com/Redback-Operations/redback-smartbike-iot/tree/main/scripts/ble-auto-connect) \ No newline at end of file +- Bash script & expect script located in [scripts/ble-auto-connect/](https://github.com/Redback-Operations/redback-smartbike-iot/tree/main/scripts/ble-auto-connect) diff --git a/docs/project-1/iot/ble-connectivity/BLEConnectivityFix.md b/docs/project-1/iot/ble-connectivity/BLEConnectivityFix.md index 985668fb5..d069e171e 100644 --- a/docs/project-1/iot/ble-connectivity/BLEConnectivityFix.md +++ b/docs/project-1/iot/ble-connectivity/BLEConnectivityFix.md @@ -33,3 +33,4 @@ Here are the steps to follow: 7) Run your script and the Bluetooth connectivity will stay on throughout the script being ran. \*Check the constants.py file in the lib file from the [redback-smartbike-iot](https://github.com/Redback-Operations/redback-smartbike-iot) repository. + diff --git a/docs/project-1/iot/codebase-documentation/Codebase-Overview.md b/docs/project-1/iot/codebase-documentation/Codebase-Overview.md index 27baac4ed..749210643 100644 --- a/docs/project-1/iot/codebase-documentation/Codebase-Overview.md +++ b/docs/project-1/iot/codebase-documentation/Codebase-Overview.md @@ -82,4 +82,4 @@ Drivers drive the functionality of the Smartbike. They connect, control and read ## Archive -The `Archive` directory holds old and retired code. This includes retired drivers (mostly predefined workout "routines" for the Smartbike), code for remotely connecting to and controlling the Raspberry Pi, a very different and old version of the VR game. It also holds old documentation and research. \ No newline at end of file +The `Archive` directory holds old and retired code. This includes retired drivers (mostly predefined workout "routines" for the Smartbike), code for remotely connecting to and controlling the Raspberry Pi, a very different and old version of the VR game. It also holds old documentation and research. diff --git a/docs/project-1/iot/codebase-documentation/Environment-Variables.md b/docs/project-1/iot/codebase-documentation/Environment-Variables.md index 9128d38a6..5ecadbffe 100644 --- a/docs/project-1/iot/codebase-documentation/Environment-Variables.md +++ b/docs/project-1/iot/codebase-documentation/Environment-Variables.md @@ -129,4 +129,4 @@ device_id = os.getenv('DEVICE_ID') ## Further Information - More information on [argparse](https://docs.python.org/3/library/argparse.html) -- More information on [shebangs](https://en.wikipedia.org/wiki/Shebang_(Unix)) \ No newline at end of file +- More information on [shebangs](https://en.wikipedia.org/wiki/Shebang_(Unix)) diff --git a/docs/project-1/iot/codebase-documentation/GATT.md b/docs/project-1/iot/codebase-documentation/GATT.md index b694560c1..012f7b65c 100644 --- a/docs/project-1/iot/codebase-documentation/GATT.md +++ b/docs/project-1/iot/codebase-documentation/GATT.md @@ -214,4 +214,4 @@ print(str(description)) - For more information on [GATT protocol](../technical-background-information/GATT.md) - For the `gatt` library's [source code](https://github.com/getsenic/gatt-python/blob/master/gatt/gatt_linux.py) - For the `gatt` library's [documentation](https://github.com/getsenic/gatt-python/blob/master/README.md) -- For the updated `gatt` library [Drivers/lib/gatt/gatt_linux.py](https://github.com/Redback-Operations/redback-smartbike-iot/tree/main/Drivers/lib/gatt/gatt_linux.py) \ No newline at end of file +- For the updated `gatt` library [Drivers/lib/gatt/gatt_linux.py](https://github.com/Redback-Operations/redback-smartbike-iot/tree/main/Drivers/lib/gatt/gatt_linux.py) diff --git a/docs/project-1/iot/codebase-documentation/MQTT-Client.md b/docs/project-1/iot/codebase-documentation/MQTT-Client.md index 16675314b..8a710201c 100644 --- a/docs/project-1/iot/codebase-documentation/MQTT-Client.md +++ b/docs/project-1/iot/codebase-documentation/MQTT-Client.md @@ -181,4 +181,4 @@ For more information on `paho-mqtt`: For our MQTT client-class & topics: - [Client-class code](https://github.com/Redback-Operations/redback-smartbike-iot/blob/main/Drivers/lib/mqtt_client.py) -- [Topics](MQTT-Topics.md) \ No newline at end of file +- [Topics](MQTT-Topics.md) diff --git a/docs/project-1/iot/codebase-documentation/MQTT-Topics.md b/docs/project-1/iot/codebase-documentation/MQTT-Topics.md index 119474267..e4710817f 100644 --- a/docs/project-1/iot/codebase-documentation/MQTT-Topics.md +++ b/docs/project-1/iot/codebase-documentation/MQTT-Topics.md @@ -102,4 +102,4 @@ View implemented topics in the drivers' code: - [Wahoo Headwin Fan](https://github.com/Redback-Operations/redback-smartbike-iot/blob/main/Drivers/fan/fan.py) - [TICKR Heart Rate Monitor](https://github.com/Redback-Operations/redback-smartbike-iot/blob/main/Drivers/heart_rate_sensor/heartrate.py) - [Wahoo Cadence Sensor](https://github.com/Redback-Operations/redback-smartbike-iot/blob/main/Drivers/cadence_sensor/cadence.py) -- [Button Driver](https://github.com/Redback-Operations/redback-smartbike-iot/blob/main/Drivers/button_control/button_control.py) \ No newline at end of file +- [Button Driver](https://github.com/Redback-Operations/redback-smartbike-iot/blob/main/Drivers/button_control/button_control.py) diff --git a/docs/project-1/iot/codebase-documentation/drivers/Button-Control.md b/docs/project-1/iot/codebase-documentation/drivers/Button-Control.md index 202694aa5..78331d3d4 100644 --- a/docs/project-1/iot/codebase-documentation/drivers/Button-Control.md +++ b/docs/project-1/iot/codebase-documentation/drivers/Button-Control.md @@ -46,4 +46,4 @@ The published payload on each press and release uses this a `JSON` structure: To see the `button_control` driver code: -[Drivers/button_control/button_control.py](https://github.com/Redback-Operations/redback-smartbike-iot/blob/main/Drivers/button_control/button_control.py) \ No newline at end of file +[Drivers/button_control/button_control.py](https://github.com/Redback-Operations/redback-smartbike-iot/blob/main/Drivers/button_control/button_control.py) diff --git a/docs/project-1/iot/codebase-documentation/drivers/Cadence-sensor.md b/docs/project-1/iot/codebase-documentation/drivers/Cadence-sensor.md index a0f78a154..1b930b54c 100644 --- a/docs/project-1/iot/codebase-documentation/drivers/Cadence-sensor.md +++ b/docs/project-1/iot/codebase-documentation/drivers/Cadence-sensor.md @@ -12,4 +12,4 @@ The Wahoo Cadence Sensor is redundant as the KICKR smart trainer has equivalent The `cadence_sensor` driver code is similar to other drivers and is redundant hence it is undocumented. To see the driver code: -[Drivers/cadence_sensor/cadence.py](https://github.com/Redback-Operations/redback-smartbike-iot/blob/main/Drivers/cadence_sensor/cadence.py) \ No newline at end of file +[Drivers/cadence_sensor/cadence.py](https://github.com/Redback-Operations/redback-smartbike-iot/blob/main/Drivers/cadence_sensor/cadence.py) diff --git a/docs/project-1/iot/codebase-documentation/drivers/Fan.md b/docs/project-1/iot/codebase-documentation/drivers/Fan.md index 095a06301..f4413ed81 100644 --- a/docs/project-1/iot/codebase-documentation/drivers/Fan.md +++ b/docs/project-1/iot/codebase-documentation/drivers/Fan.md @@ -63,4 +63,4 @@ It is better to let application developers decide how they want the fan's power ## Driver Location -[Drivers/fan/fan.py](https://github.com/Redback-Operations/redback-smartbike-iot/blob/main/Drivers/fan/fan.py) \ No newline at end of file +[Drivers/fan/fan.py](https://github.com/Redback-Operations/redback-smartbike-iot/blob/main/Drivers/fan/fan.py) diff --git a/docs/project-1/iot/codebase-documentation/drivers/Heart-rate-sensor.md b/docs/project-1/iot/codebase-documentation/drivers/Heart-rate-sensor.md index 9426d7353..c99a5141e 100644 --- a/docs/project-1/iot/codebase-documentation/drivers/Heart-rate-sensor.md +++ b/docs/project-1/iot/codebase-documentation/drivers/Heart-rate-sensor.md @@ -55,4 +55,4 @@ Heart rate data is published to the following topic: ## Driver Location -[Drivers/heart_rate_sensor/heartrate.py](https://github.com/Redback-Operations/redback-smartbike-iot/blob/main/Drivers/heart_rate_sensor/heartrate.py) \ No newline at end of file +[Drivers/heart_rate_sensor/heartrate.py](https://github.com/Redback-Operations/redback-smartbike-iot/blob/main/Drivers/heart_rate_sensor/heartrate.py) diff --git a/docs/project-1/iot/codebase-documentation/drivers/Kickr-climb-&-smart-trainer.md b/docs/project-1/iot/codebase-documentation/drivers/Kickr-climb-&-smart-trainer.md index 2d900fa87..8c28a653a 100644 --- a/docs/project-1/iot/codebase-documentation/drivers/Kickr-climb-&-smart-trainer.md +++ b/docs/project-1/iot/codebase-documentation/drivers/Kickr-climb-&-smart-trainer.md @@ -116,4 +116,4 @@ The VR game's incline control was developed to use the improved incline control ::: -Location - [Drivers/smartbike_driver/smartbike/](https://github.com/Redback-Operations/redback-smartbike-iot/tree/main/Drivers/smartbike) \ No newline at end of file +Location - [Drivers/smartbike_driver/smartbike/](https://github.com/Redback-Operations/redback-smartbike-iot/tree/main/Drivers/smartbike) diff --git a/docs/project-1/iot/introduction/Developer-Environment-Setup.md b/docs/project-1/iot/introduction/Developer-Environment-Setup.md index 4c8131989..8316cf4b5 100644 --- a/docs/project-1/iot/introduction/Developer-Environment-Setup.md +++ b/docs/project-1/iot/introduction/Developer-Environment-Setup.md @@ -50,3 +50,4 @@ Ask your project lead for tasks to get started on or... - See the Planner on Teams for tasks (it is like Trello). - [Delve into the code](https://github.com/Redback-Operations/redback-smartbike-iot) + diff --git a/docs/project-1/iot/introduction/Onboarding-Welcome.md b/docs/project-1/iot/introduction/Onboarding-Welcome.md index e28a6f559..a150264cb 100644 --- a/docs/project-1/iot/introduction/Onboarding-Welcome.md +++ b/docs/project-1/iot/introduction/Onboarding-Welcome.md @@ -47,4 +47,4 @@ Project 1 uses multiple repositories. You will likely need to contribute to all - [Setup your developer environment](Developer-Environment-Setup.md) - [Learn more about the Smartbike](Smartbike-Introduction.md) - [Learn how to start the Smartbike](../operation/Starting-Smartbike.md) -- [Delve into the code!](https://github.com/Redback-Operations/redback-smartbike-iot) \ No newline at end of file +- [Delve into the code!](https://github.com/Redback-Operations/redback-smartbike-iot) diff --git a/docs/project-1/iot/introduction/Smartbike-Introduction.md b/docs/project-1/iot/introduction/Smartbike-Introduction.md index a57e3e51c..1c266b1b4 100644 --- a/docs/project-1/iot/introduction/Smartbike-Introduction.md +++ b/docs/project-1/iot/introduction/Smartbike-Introduction.md @@ -171,4 +171,4 @@ Connected to the Raspberry Pi is two turning control buttons. The buttons are mo 4. **VR Game Sync Issues**: - Check the MQTT broker logs for connection errors. - - Restart the Raspberry Pi and VR application. \ No newline at end of file + - Restart the Raspberry Pi and VR application. diff --git a/docs/project-1/iot/operation/Starting-Smartbike.md b/docs/project-1/iot/operation/Starting-Smartbike.md index 62e1dd84f..e3890c607 100644 --- a/docs/project-1/iot/operation/Starting-Smartbike.md +++ b/docs/project-1/iot/operation/Starting-Smartbike.md @@ -45,4 +45,4 @@ bash iot/scripts/start_all.sh ![BLE indicator light](../img/smartbike-photos/kickr-connected.jpg) -*If BLE errors are encountered see the [ble-auto-connect script](../ble-connectivity/BLE-Auto-Connect-Script.md) or [BLE connectivity fix document](../ble-connectivity/BLEConnectivityFix.md).* \ No newline at end of file +*If BLE errors are encountered see the [ble-auto-connect script](../ble-connectivity/BLE-Auto-Connect-Script.md) or [BLE connectivity fix document](../ble-connectivity/BLEConnectivityFix.md).* diff --git a/docs/project-1/iot/technical-background-information/GATT.md b/docs/project-1/iot/technical-background-information/GATT.md index 993d1cd87..4ac3d3e0b 100644 --- a/docs/project-1/iot/technical-background-information/GATT.md +++ b/docs/project-1/iot/technical-background-information/GATT.md @@ -64,4 +64,4 @@ As these machines may also need to be controlled by a client to execute some sor ![image](img/control_point_request.png) -The FTMS control point characteristic enables control over the FTMS functions. Functions have unique operation codes (Op Codes) which are used to request they be executed. To send commands to the control point, the client must first subscribe to indications for the control point and then request control over the control point by using the Request Control Op Code 0x00. If control is given, then other functions can be executed by writing their Op Code and parameter values to the control point. Control over the control point can also be reset by writing the Op Code 0x01. \ No newline at end of file +The FTMS control point characteristic enables control over the FTMS functions. Functions have unique operation codes (Op Codes) which are used to request they be executed. To send commands to the control point, the client must first subscribe to indications for the control point and then request control over the control point by using the Request Control Op Code 0x00. If control is given, then other functions can be executed by writing their Op Code and parameter values to the control point. Control over the control point can also be reset by writing the Op Code 0x01. diff --git a/docs/project-1/vr/apk-exe-build-guide.md b/docs/project-1/vr/apk-exe-build-guide.md index 3147ece58..e67f09f74 100644 --- a/docs/project-1/vr/apk-exe-build-guide.md +++ b/docs/project-1/vr/apk-exe-build-guide.md @@ -80,4 +80,4 @@ Again, this process can take a considerable amount of time, depending on the spe Create a new folder in the project 1 files with the trimester and year you are studying this unit. Upload the APK and EXE files to your new folder so they can be accessed by everyone. -![Build file share location](img/unity-build-file-share.png) \ No newline at end of file +![Build file share location](img/unity-build-file-share.png) diff --git a/docs/project-1/vr/bike-input-and-movement.md b/docs/project-1/vr/bike-input-and-movement.md index 636f5961f..a88ccaed9 100644 --- a/docs/project-1/vr/bike-input-and-movement.md +++ b/docs/project-1/vr/bike-input-and-movement.md @@ -115,3 +115,4 @@ Best for: immersive VR, realistic terrain, and learning physics principles. * Gets input via `IPlayerInput.GetDirection()` * Passes input to `IBikeMover.HanldeInput()` * Movement logic is executed (e.g., wheel torque, transform rotation) + diff --git a/docs/project-1/vr/bike-setup.md b/docs/project-1/vr/bike-setup.md index 5681e2397..eebe923de 100644 --- a/docs/project-1/vr/bike-setup.md +++ b/docs/project-1/vr/bike-setup.md @@ -92,3 +92,4 @@ Handles persistent save/load and selection logic. * Ensures the selected `Bike` is subscribed for auto-save + diff --git a/docs/project-1/vr/design-handbook.md b/docs/project-1/vr/design-handbook.md index 6ffd7b651..43f74b44b 100644 --- a/docs/project-1/vr/design-handbook.md +++ b/docs/project-1/vr/design-handbook.md @@ -311,4 +311,4 @@ Files located: (Assets\Models\Other) >Figure 37 BustopV2 ![ParkBench](img/ParkBench.png) ->Figure 38 ParkBench \ No newline at end of file +>Figure 38 ParkBench diff --git a/docs/project-1/vr/game-design.md b/docs/project-1/vr/game-design.md index 1eabbc0b7..238d10713 100644 --- a/docs/project-1/vr/game-design.md +++ b/docs/project-1/vr/game-design.md @@ -199,3 +199,4 @@ VZFit links to bikes via a physical device that is purchased separately and only ![VZFit, played by OtterWorldly, 2022](img/vzfit.png) > [VZFit, OtterWorldly screenshot, 2022](https://www.youtube.com/watch?v=7Nn9adpeo-M) + diff --git a/docs/project-1/vr/mission.md b/docs/project-1/vr/mission.md index aef3de49f..56cd7ee79 100644 --- a/docs/project-1/vr/mission.md +++ b/docs/project-1/vr/mission.md @@ -54,3 +54,4 @@ public class Mission1 : Mission public override string MissionName => "Collect the Star"; public override int MissionNumber => 1; ``` + diff --git a/docs/project-1/vr/outline-effect.md b/docs/project-1/vr/outline-effect.md index 3f45ab0fb..da2a5e488 100644 --- a/docs/project-1/vr/outline-effect.md +++ b/docs/project-1/vr/outline-effect.md @@ -55,3 +55,4 @@ For improved performance: - Smooth normals will be baked in the editor If disabled, smooth normals are calculated at runtime on `Awake()` (may cause lag on large meshes). + diff --git a/docs/project-1/vr/software-requirements.md b/docs/project-1/vr/software-requirements.md index 36221a1d9..5505a5fe9 100644 --- a/docs/project-1/vr/software-requirements.md +++ b/docs/project-1/vr/software-requirements.md @@ -321,3 +321,4 @@ These features combine to create a dynamic system that appeals to fitness enthus - RPi = Raspberry pi - API = Application Programming Interface - VR = Virtual Reality + diff --git a/docs/project-2/Chat Bot/ChatBot.md b/docs/project-2/Chat Bot/ChatBot.md index d5649a7be..cfc982084 100644 --- a/docs/project-2/Chat Bot/ChatBot.md +++ b/docs/project-2/Chat Bot/ChatBot.md @@ -2,3 +2,4 @@ sidebar_position: 1 --- + diff --git a/docs/project-2/Data Science and Analytics/AlzheimersProject.md b/docs/project-2/Data Science and Analytics/AlzheimersProject.md index 11cd57dfb..b730a0aa1 100644 --- a/docs/project-2/Data Science and Analytics/AlzheimersProject.md +++ b/docs/project-2/Data Science and Analytics/AlzheimersProject.md @@ -64,3 +64,4 @@ The Dataset (n=373) consists of the following columns: [^5]: Buckner RL, Head D, Parker J, Fotenos AF, Marcus D, Morris JC, Snyder AZ. A unified approach for morphometric and functional data analysis in young, old, and demented adults using automated atlas-based head size normalization: reliability and validation against manual measurement of total intracranial volume. Neuroimage. 2004 Oct;23(2):724-38. doi: 10.1016/j.neuroimage.2004.06.018. PMID: 15488422. [^6]: Fotenos AF, Snyder AZ, Girton LE, Morris JC, Buckner RL. Normative estimates of cross-sectional and longitudinal brain volume decline in aging and AD. Neurology. 2005 Mar 22;64(6):1032-9. doi: 10.1212/01.WNL.0000154530.72969.11. PMID: 15781822. + diff --git a/docs/project-2/Data Science and Analytics/Best_Practices.md b/docs/project-2/Data Science and Analytics/Best_Practices.md index 0c6cc4a80..94d293220 100644 --- a/docs/project-2/Data Science and Analytics/Best_Practices.md +++ b/docs/project-2/Data Science and Analytics/Best_Practices.md @@ -93,3 +93,4 @@ Then, all anyone needs to do to get a working build of your code on their machin :::info **Document Creation:** 5 September 2024. **Last Edited:** 5 September 2024. **Authors:** Lachlan Costigan ::: + diff --git a/docs/project-2/Data Science and Analytics/DiabetesProject.md b/docs/project-2/Data Science and Analytics/DiabetesProject.md index f1c1f0887..d7adae515 100644 --- a/docs/project-2/Data Science and Analytics/DiabetesProject.md +++ b/docs/project-2/Data Science and Analytics/DiabetesProject.md @@ -83,3 +83,4 @@ The Dataset contains 17 columns and 520 records [^2]: https://www.abs.gov.au/statistics/health/causes-death/provisional-mortality-statistics/jan-may-2024 [^3]: https://www.kaggle.com/datasets/iammustafatz/diabetes-prediction-dataset/discussion/406676#2282358 [^4]: Islam, M. M. Faniqul et al. “Likelihood Prediction of Diabetes at Early Stage Using Data Mining Techniques.” Computer Vision and Machine Intelligence in Medical Image Analysis (2019): n. pag. + diff --git a/docs/project-2/Data Science and Analytics/FallDetection_ActivityMonitoring.md b/docs/project-2/Data Science and Analytics/FallDetection_ActivityMonitoring.md index 98c32d648..65509c57e 100644 --- a/docs/project-2/Data Science and Analytics/FallDetection_ActivityMonitoring.md +++ b/docs/project-2/Data Science and Analytics/FallDetection_ActivityMonitoring.md @@ -51,3 +51,4 @@ Models were trained using captured sensor data from the 1st wearable prototype :::info **Document Creation:** 5 September 2024. **Last Edited:** 5 September 2024. **Authors:** Lachlan Costigan ::: + diff --git a/docs/project-2/Data Science and Analytics/HeartAttackPrediction.md b/docs/project-2/Data Science and Analytics/HeartAttackPrediction.md index 7a29a8697..4d29199ff 100644 --- a/docs/project-2/Data Science and Analytics/HeartAttackPrediction.md +++ b/docs/project-2/Data Science and Analytics/HeartAttackPrediction.md @@ -65,3 +65,4 @@ The dataset used in heart_attack_prediction.ipynb is the Heart Attack Risk Predi The dataset used in the Heart_Disease_Prediction.ipynb notebook, looking at the discussion it seems to be synthetic (i.e generated by ChatGPT): [^1]:https://www.kaggle.com/datasets/iamsouravbanerjee/heart-attack-prediction-dataset/data + diff --git a/docs/project-2/Data Science and Analytics/ParkinsonsPrediction.md b/docs/project-2/Data Science and Analytics/ParkinsonsPrediction.md index 8a80fe134..ffe20c648 100644 --- a/docs/project-2/Data Science and Analytics/ParkinsonsPrediction.md +++ b/docs/project-2/Data Science and Analytics/ParkinsonsPrediction.md @@ -69,3 +69,4 @@ The data has the following features: [^2]:Little, M. (2007). Parkinsons [Dataset]. UCI Machine Learning Repository. https://doi.org/10.24432/C59C74. Accessible from http://archive.ics.uci.edu/dataset/174/parkinsons + diff --git a/docs/project-2/Data Science and Analytics/SleepDisorder.md b/docs/project-2/Data Science and Analytics/SleepDisorder.md index 71ccc0a8c..91ce06be6 100644 --- a/docs/project-2/Data Science and Analytics/SleepDisorder.md +++ b/docs/project-2/Data Science and Analytics/SleepDisorder.md @@ -41,3 +41,4 @@ The dataset used for initial training of the model is ICHI14-BORAZIO[^1][^2], co [^1]:Borazio, Marko & Berlin, Eugen & Kücükyildiz, Nagihan & Scholl, Philipp & Van Laerhoven, Kristof. (2014). Towards Benchmarked Sleep Detection with Inertial Wrist-worn Sensing Units. Proceedings - 2014 IEEE International Conference on Healthcare Informatics, ICHI 2014. 10.1109/ICHI.2014.24. [^2]: [Source for the dataset itself](https://www.researchgate.net/publication/305212784_ICHI14-Borazio) + diff --git a/docs/project-2/Data Science and Analytics/VoiceAssisstant.md b/docs/project-2/Data Science and Analytics/VoiceAssisstant.md index 3b243efaa..5d949f0da 100644 --- a/docs/project-2/Data Science and Analytics/VoiceAssisstant.md +++ b/docs/project-2/Data Science and Analytics/VoiceAssisstant.md @@ -70,3 +70,4 @@ To run the project on a local machine, follow these steps: :::info **Document Creation:** 5 September 2024. **Last Edited:** 5 September 2024. **Authors:** Lachlan Costigan ::: + diff --git a/docs/project-2/Device Design/Board_Init.md b/docs/project-2/Device Design/Board_Init.md index 30c386a6b..8c22a8d78 100644 --- a/docs/project-2/Device Design/Board_Init.md +++ b/docs/project-2/Device Design/Board_Init.md @@ -46,3 +46,4 @@ If you do decide to buy a debugger (They're cheap I just didn't want to wait nor :::info **Document Creation:** 15 December 2024. **Last Edited:** 15 December 2024. **Authors:** Lachlan Costigan ::: + diff --git a/docs/project-2/Device Design/Board_shakedown.md b/docs/project-2/Device Design/Board_shakedown.md index 3758dc36f..afdb4d100 100644 --- a/docs/project-2/Device Design/Board_shakedown.md +++ b/docs/project-2/Device Design/Board_shakedown.md @@ -68,3 +68,4 @@ In my experience we had 3 people (2 Sr, 1 Jr) in the IoT team in T2-24 and 2 peo :::info **Document Creation:** 15 December 2024. **Last Edited:** 08 January 2025. **Authors:** Lachlan Costigan ::: + diff --git a/docs/project-2/Device Design/Components.md b/docs/project-2/Device Design/Components.md index 5431d7863..66efb6245 100644 --- a/docs/project-2/Device Design/Components.md +++ b/docs/project-2/Device Design/Components.md @@ -59,3 +59,4 @@ As a hacked together solution, we will be using an off the shelf [USB-C - LiPO C :::info **Document Creation:** 5 September 2024. **Last Edited:** 5 September 2024. **Authors:** Lachlan Costigan ::: + diff --git a/docs/project-2/Device Design/Firebase.md b/docs/project-2/Device Design/Firebase.md index b237a66ff..4433f1c8b 100644 --- a/docs/project-2/Device Design/Firebase.md +++ b/docs/project-2/Device Design/Firebase.md @@ -19,3 +19,4 @@ https://youtu.be/vET7iuKpOCc **updated by**: Lachlan Costigan ::: + diff --git a/docs/project-2/Device Design/Wearable_device.md b/docs/project-2/Device Design/Wearable_device.md index 0dca0f820..f2f5a2fdd 100644 --- a/docs/project-2/Device Design/Wearable_device.md +++ b/docs/project-2/Device Design/Wearable_device.md @@ -158,3 +158,4 @@ Written Artifacts, reports and visual media are TBD :::info **Document Creation:** 05 September 2024. **Last Edited:** 08 January 2025. **Authors:** Lachlan Costigan ::: + diff --git a/docs/project-3/SafeCodeGuide.mdx b/docs/project-3/SafeCodeGuide.mdx index e60994772..7c8552e30 100755 --- a/docs/project-3/SafeCodeGuide.mdx +++ b/docs/project-3/SafeCodeGuide.mdx @@ -287,4 +287,4 @@ The server's file system contains data that attackers could use for malicious pu Here as soon as the server starts listening any outgoing HTTP request is denied. -
\ No newline at end of file +
diff --git a/docs/project-3/integration-of-data.md b/docs/project-3/integration-of-data.md index 7915b46a6..242423f3f 100644 --- a/docs/project-3/integration-of-data.md +++ b/docs/project-3/integration-of-data.md @@ -96,3 +96,4 @@ The Python scripts and Jupyter notebooks contain logic for analyzing the cycling ## Conclusion By integrating enhanced features focused on customization, simulation, and community, alongside adopting best practices from platforms like TrainerRoad, we can significantly improve user engagement and satisfaction. These strategies aim not only to enhance the individual training experience but also to build a vibrant, supportive community around our platform. The next steps involve detailed planning and development phases to bring these features to life, ensuring we maintain a user-centric approach throughout the process. + diff --git a/docs/project-3/research/cycling-data-description.md b/docs/project-3/research/cycling-data-description.md index cca0a82ba..61b62a89b 100644 --- a/docs/project-3/research/cycling-data-description.md +++ b/docs/project-3/research/cycling-data-description.md @@ -187,4 +187,4 @@ A random forest model was created to predict Real\_duration after dropping the f * total\_points -The model achieved a mean squared error (MSE) of approximately 0.0069. \ No newline at end of file +The model achieved a mean squared error (MSE) of approximately 0.0069. diff --git a/docs/project-3/research/cycling-duration-prediction-models.md b/docs/project-3/research/cycling-duration-prediction-models.md index 0dcc29279..2f4824869 100644 --- a/docs/project-3/research/cycling-duration-prediction-models.md +++ b/docs/project-3/research/cycling-duration-prediction-models.md @@ -85,4 +85,4 @@ A number of experiments were performed to test prediction models for duration of * The Linear Regressor was also the fastest model. -* It was concluded that a simple Linear Regression model could accurately predict workout duration and required the least resources to do so. \ No newline at end of file +* It was concluded that a simple Linear Regression model could accurately predict workout duration and required the least resources to do so. diff --git a/docs/project-3/research/cycling-ftp-prediction-models.md b/docs/project-3/research/cycling-ftp-prediction-models.md index d50dbfe69..1fd6776cc 100644 --- a/docs/project-3/research/cycling-ftp-prediction-models.md +++ b/docs/project-3/research/cycling-ftp-prediction-models.md @@ -67,4 +67,4 @@ A number of experiments were performed to test prediction models for duration of * The FtpPredictor class was documented to support automated solution documentation. -* Unit tests were added for the class. \ No newline at end of file +* Unit tests were added for the class. diff --git a/docs/project-3/research/developing-ml-models-for-football-prediction.md b/docs/project-3/research/developing-ml-models-for-football-prediction.md index 16a39c3ed..1dd0f7280 100644 --- a/docs/project-3/research/developing-ml-models-for-football-prediction.md +++ b/docs/project-3/research/developing-ml-models-for-football-prediction.md @@ -118,4 +118,4 @@ This project serves as a demonstration of applying machine learning techniques t [E0.csv](./attachments/E0.csv) -* * * \ No newline at end of file +* * * diff --git a/docs/project-3/research/functional-threshold-power.md b/docs/project-3/research/functional-threshold-power.md index aea697245..940d8b7cd 100644 --- a/docs/project-3/research/functional-threshold-power.md +++ b/docs/project-3/research/functional-threshold-power.md @@ -51,4 +51,4 @@ To learn more about FTP and its application in cycling, the following resources ## Conclusion -FTP, or Functional Threshold Power, is a vital metric for cyclists looking to improve their performance. By understanding FTP, you can tailor training, monitor progress, and enhance overall cycling experience. For both experienced and novice cyclists, incorporating FTP into training can lead to substantial improvements in cycling abilities. \ No newline at end of file +FTP, or Functional Threshold Power, is a vital metric for cyclists looking to improve their performance. By understanding FTP, you can tailor training, monitor progress, and enhance overall cycling experience. For both experienced and novice cyclists, incorporating FTP into training can lead to substantial improvements in cycling abilities. diff --git a/docs/project-3/research/heart-rate-zones.md b/docs/project-3/research/heart-rate-zones.md index 98eb826c6..d2a2e90b7 100644 --- a/docs/project-3/research/heart-rate-zones.md +++ b/docs/project-3/research/heart-rate-zones.md @@ -40,4 +40,4 @@ A general rule to calculate your maximum heart rate (MHR) is by subtracting your 3. Polar (2023). ‘Running Heart Rate Zones: The Basics’. Available at: [Heart Rate Zones | The Basics | Polar Journal](https://www.polar.com/blog/running-heart-rate-zones-basics/#:~:text=Heart%20rate%20zones%20can%20be,zone%20training%20for%20weight%20loss)(Access 22 November 2023). -4. John Hopkins Medicine (2023). ‘Understanding Your Target Heart Rate’. Available at: [Understanding Your Target Heart Rate | Johns Hopkins Medicine](https://www.hopkinsmedicine.org/health/wellness-and-prevention/understanding-your-target-heart-rate#:~:text=Target%20heart%20rate%20is%20generally,or%20170%20beats%20per%20minute) (Accessed 22 November 2023). \ No newline at end of file +4. John Hopkins Medicine (2023). ‘Understanding Your Target Heart Rate’. Available at: [Understanding Your Target Heart Rate | Johns Hopkins Medicine](https://www.hopkinsmedicine.org/health/wellness-and-prevention/understanding-your-target-heart-rate#:~:text=Target%20heart%20rate%20is%20generally,or%20170%20beats%20per%20minute) (Accessed 22 November 2023). diff --git a/docs/project-3/research/index.md b/docs/project-3/research/index.md index cd5c24e75..19192772c 100644 --- a/docs/project-3/research/index.md +++ b/docs/project-3/research/index.md @@ -74,4 +74,4 @@ This area contains the research findings and other documentation for the Sports This guide is designed to walk you through the process of integrating Python into Power BI, a synergy that unlocks a new realm of possibilities for data analysis and business intelligence. - ## Prerequisites \ No newline at end of file + ## Prerequisites diff --git a/docs/project-3/research/power-bi-github-integration.md b/docs/project-3/research/power-bi-github-integration.md index 206875db9..e539b4f74 100644 --- a/docs/project-3/research/power-bi-github-integration.md +++ b/docs/project-3/research/power-bi-github-integration.md @@ -53,4 +53,4 @@ This guide provides a step-by-step guide approach to establish a direct connecti * Power BI Documentation: [Power BI documentation - Power BI | Microsoft Learn](https://learn.microsoft.com/en-us/power-bi/) -* GitHub Help Documentation: [GitHub Docs](https://docs.github.com/en) \ No newline at end of file +* GitHub Help Documentation: [GitHub Docs](https://docs.github.com/en) diff --git a/docs/project-3/research/power-bi-python-integration.md b/docs/project-3/research/power-bi-python-integration.md index caf43fdf2..85fd2bafb 100644 --- a/docs/project-3/research/power-bi-python-integration.md +++ b/docs/project-3/research/power-bi-python-integration.md @@ -72,4 +72,4 @@ This guide is designed to walk you through the process of integrating Python int * Power BI Documentation: [Power BI documentation - Power BI | Microsoft Learn](https://learn.microsoft.com/en-us/power-bi/) -* Python Documentation: [Python 3.12.1 Documentation](https://docs.python.org/3/) \ No newline at end of file +* Python Documentation: [Python 3.12.1 Documentation](https://docs.python.org/3/) diff --git a/docs/project-3/research/sports-performance-overview.md b/docs/project-3/research/sports-performance-overview.md index 661efa2fd..d40af71e5 100644 --- a/docs/project-3/research/sports-performance-overview.md +++ b/docs/project-3/research/sports-performance-overview.md @@ -98,4 +98,4 @@ The objective is to select the best 11 players for the IPL 2023 team of the tour #### Objective -This analysis focuses on developing tailored models to forecast key player performances in batting and bowling. The goal is provide an accurate and detailed forecast for player performance, assisting in strategic planning and player selection. \ No newline at end of file +This analysis focuses on developing tailored models to forecast key player performances in batting and bowling. The goal is provide an accurate and detailed forecast for player performance, assisting in strategic planning and player selection. diff --git a/docs/project-3/research/strava-bulk-export-data-description.md b/docs/project-3/research/strava-bulk-export-data-description.md index 835b6220e..936234934 100644 --- a/docs/project-3/research/strava-bulk-export-data-description.md +++ b/docs/project-3/research/strava-bulk-export-data-description.md @@ -122,4 +122,4 @@ To clean the data: Once you have cleaned the data, you can load it into the GitHub repository for use by the prediction models. This will involve checking in the 'extended_activities_athlete_id.csv' file that was created in the 2.2 cell and all the .csv.gz files for the individual session data. -Create the pull request that includes these files. \ No newline at end of file +Create the pull request that includes these files. diff --git a/docs/project-3/research/web-scraping-in-python.md b/docs/project-3/research/web-scraping-in-python.md index 1e7ccf822..a0bfc539b 100644 --- a/docs/project-3/research/web-scraping-in-python.md +++ b/docs/project-3/research/web-scraping-in-python.md @@ -195,4 +195,4 @@ Web scraping involves extracting data from websites. Here's a step-by-step summa ## Authors -This comprehensive guide on web scraping was created collaboratively by Ramya Sekar and Adarsh Kallungal Sivaram. Ramya created the page and set the initial structure, while Adarsh added valuable insights and extra information to enrich the content. \ No newline at end of file +This comprehensive guide on web scraping was created collaboratively by Ramya Sekar and Adarsh Kallungal Sivaram. Ramya created the page and set the initial structure, while Adarsh added valuable insights and extra information to enrich the content. diff --git a/docs/project-3/sensors/bike_resistance_monitor.md b/docs/project-3/sensors/bike_resistance_monitor.md index e5da2f1ba..eeb71ee57 100644 --- a/docs/project-3/sensors/bike_resistance_monitor.md +++ b/docs/project-3/sensors/bike_resistance_monitor.md @@ -43,3 +43,4 @@ This device is designed to attach to the front of a bicycle, aimed at estimating - Ideal for road cyclists, triathletes, and cycling teams focused on performance optimization. - Useful in both training and competitive environments, particularly in time trials and triathlons where aerodynamics play a crucial role. + diff --git a/docs/project-3/sensors/running_temp_and_sweat.md b/docs/project-3/sensors/running_temp_and_sweat.md index 66bc78960..28313d007 100644 --- a/docs/project-3/sensors/running_temp_and_sweat.md +++ b/docs/project-3/sensors/running_temp_and_sweat.md @@ -39,3 +39,4 @@ The device is designed for runners, providing actionable insights into core body 8. **Water Resistance:** - Water-resistant up to 50 meters, suitable for training in various weather conditions and cross-training activities. + diff --git a/docs/project-3/sensors/swim_stroke_analyser.md b/docs/project-3/sensors/swim_stroke_analyser.md index 7ca9b6379..c53e0ec72 100644 --- a/docs/project-3/sensors/swim_stroke_analyser.md +++ b/docs/project-3/sensors/swim_stroke_analyser.md @@ -41,4 +41,4 @@ This device is a compact, wearable device designed for swimmers to wear on their **Applications:** - Suitable for competitive swimmers, swimming coaches, and swim training programs. -- Can be used in pools, open water, and controlled training environments. \ No newline at end of file +- Can be used in pools, open water, and controlled training environments. diff --git a/docs/project-3/workflowdoc.md b/docs/project-3/workflowdoc.md index 8847fbf9e..1913f8112 100644 --- a/docs/project-3/workflowdoc.md +++ b/docs/project-3/workflowdoc.md @@ -73,3 +73,4 @@ This document outlines the code review workflow designed to enhance the collabor + diff --git a/docs/project-4/Crowd-Monitoring-Detection/LLMs_training_testing.md b/docs/project-4/Crowd-Monitoring-Detection/LLMs_training_testing.md index 80b329ef8..c1179ad44 100644 --- a/docs/project-4/Crowd-Monitoring-Detection/LLMs_training_testing.md +++ b/docs/project-4/Crowd-Monitoring-Detection/LLMs_training_testing.md @@ -160,3 +160,4 @@ Chat with the language model by passing a custom prompt. ### To training your custom models please use the notebook from train_llms/Train_llms.ipynb + diff --git a/docs/project-4/Crowd-Monitoring-Detection/kafka.tutorial.md b/docs/project-4/Crowd-Monitoring-Detection/kafka.tutorial.md index 9c117a6e6..ac7ff57de 100644 --- a/docs/project-4/Crowd-Monitoring-Detection/kafka.tutorial.md +++ b/docs/project-4/Crowd-Monitoring-Detection/kafka.tutorial.md @@ -208,4 +208,4 @@ To install Kafka on a Linux system, follow these steps: Start sending messages to the Kafka topic using a producer: ```bash /opt/kafka/bin/kafka-console-producer.sh --topic - ``` \ No newline at end of file + ``` diff --git a/docs/project-4/Crowd-Monitoring/Crowd-Monitoring-Overview.md b/docs/project-4/Crowd-Monitoring/Crowd-Monitoring-Overview.md index 1bc899852..dd4ff6c2d 100644 --- a/docs/project-4/Crowd-Monitoring/Crowd-Monitoring-Overview.md +++ b/docs/project-4/Crowd-Monitoring/Crowd-Monitoring-Overview.md @@ -730,4 +730,4 @@ video_writer.release() cv2.destroyAllWindows() ``` ## Results -![Transformation result](img\gif.gif) \ No newline at end of file +![Transformation result](img\gif.gif) diff --git a/docs/project-4/Crowd-Monitoring/MongoDB-Overview.md b/docs/project-4/Crowd-Monitoring/MongoDB-Overview.md index c06cffdbd..5dda0b1b0 100644 --- a/docs/project-4/Crowd-Monitoring/MongoDB-Overview.md +++ b/docs/project-4/Crowd-Monitoring/MongoDB-Overview.md @@ -59,4 +59,4 @@ if current_time - last_update_time < update_interval: With the above code, by setting up a variable for interval time, we can easily adjust this variable to update the recorded data on MongoDB in every second, minute or hour. ## Results -![MongoDB Live Data](img\live_data.png) \ No newline at end of file +![MongoDB Live Data](img\live_data.png) diff --git a/docs/project-4/DataLogistic/Real-time-Data-Logistics-Processing-Strorage-MQTT-Kafka-MongoDB.md b/docs/project-4/DataLogistic/Real-time-Data-Logistics-Processing-Strorage-MQTT-Kafka-MongoDB.md index f0de8507f..e8ccac4e8 100644 --- a/docs/project-4/DataLogistic/Real-time-Data-Logistics-Processing-Strorage-MQTT-Kafka-MongoDB.md +++ b/docs/project-4/DataLogistic/Real-time-Data-Logistics-Processing-Strorage-MQTT-Kafka-MongoDB.md @@ -252,3 +252,4 @@ Kafka depends on Zookeeper for distributed coordination and management of topics [10] https://github.com/sergio11/iot_event_streaming_architecture + diff --git a/docs/project-4/Overview/Project-Overview.md b/docs/project-4/Overview/Project-Overview.md index 8eda6db67..8d54fd010 100644 --- a/docs/project-4/Overview/Project-Overview.md +++ b/docs/project-4/Overview/Project-Overview.md @@ -25,3 +25,4 @@ This knowledge will amplify performance standards in various sports. ## Conclusion In essence, Project Orion seeks to mirror the guiding brilliance of its celestial counterpart, aspiring to illuminate the sports technology landscape with innovative strategies focused on athlete safety and performance enhancement. This venture is poised to redefine the frontiers of technological applications in sports, positioning Project Orion as a pioneer and a source of inspiration in its field. + diff --git a/docs/project-4/Player-Tracking/Greyhounds_tracking.md b/docs/project-4/Player-Tracking/Greyhounds_tracking.md index 81c1c0910..a2b379089 100644 --- a/docs/project-4/Player-Tracking/Greyhounds_tracking.md +++ b/docs/project-4/Player-Tracking/Greyhounds_tracking.md @@ -84,3 +84,4 @@ We would like to extend our gratitude to the following: - **YOLOv8 and Ultralytics Communities:** Thank you for your contributions to the field of object detection and tracking. Your work has been instrumental in the development of our project. - **Roboflow:** Special thanks for providing platform and annotation tools that have significantly contributed to the accuracy and efficiency of our model. + diff --git a/docs/project-4/Player-Tracking/baseball-injury detection/Baseball.md b/docs/project-4/Player-Tracking/baseball-injury detection/Baseball.md index a41184a75..1a40e9a02 100644 --- a/docs/project-4/Player-Tracking/baseball-injury detection/Baseball.md +++ b/docs/project-4/Player-Tracking/baseball-injury detection/Baseball.md @@ -103,3 +103,4 @@ Trained using Adam optimizer and categorical crossentropy. Saved as `.h5` for ru ## Conclusion This capstone delivers a complete ML pipeline for video-based injury risk assessment in baseball. It demonstrates practical integration of computer vision, web development, and machine learning to solve real-world biomechanical problems in sports. + diff --git a/docs/project-4/Pose-estimation/pose_data_analytics.md b/docs/project-4/Pose-estimation/pose_data_analytics.md index 3b8f2b876..1b97d532c 100644 --- a/docs/project-4/Pose-estimation/pose_data_analytics.md +++ b/docs/project-4/Pose-estimation/pose_data_analytics.md @@ -73,3 +73,4 @@ The similarity between poses in two images is calculated and displayed. ## Conclusion This project focuses on pose estimation Data Analytics and its usecase and application in improving accuracy and keyframe detection. This file is used to visualise data from the pose_estimation_matching.ipynb model and detect weakpoints in the algorithm. + diff --git a/docs/project-4/Pose-estimation/pose_estimation_fitness.md b/docs/project-4/Pose-estimation/pose_estimation_fitness.md index fb20e3226..7c9852d30 100644 --- a/docs/project-4/Pose-estimation/pose_estimation_fitness.md +++ b/docs/project-4/Pose-estimation/pose_estimation_fitness.md @@ -69,3 +69,4 @@ Displays the best and worst exercise forms with corresponding strain graphs. ## Conclusion This project provides a comprehensive solution for pose estimation and strain analysis in fitness applications. It can be applied to sports analytics, personal training, and rehabilitation. + diff --git a/docs/project-4/Pose-estimation/pose_estimation_matching.md b/docs/project-4/Pose-estimation/pose_estimation_matching.md index dac670c90..cd03d91f7 100644 --- a/docs/project-4/Pose-estimation/pose_estimation_matching.md +++ b/docs/project-4/Pose-estimation/pose_estimation_matching.md @@ -76,3 +76,4 @@ The similarity between poses in two images is calculated and displayed. ## Conclusion This project provides a comprehensive solution for pose estimation and matching using deep learning techniques. It can be applied to various domains such as sports analytics, fitness applications, and human-computer interaction. + diff --git a/docs/project-4/Small_Object_Detection/Documentation.md b/docs/project-4/Small_Object_Detection/Documentation.md index f4f44d691..fcff52371 100644 --- a/docs/project-4/Small_Object_Detection/Documentation.md +++ b/docs/project-4/Small_Object_Detection/Documentation.md @@ -172,3 +172,4 @@ if uploaded_file is not None: st.write("Powered by YOLOv8 and SAHI.") ``` + diff --git a/docs/project-4/iot/Arduino_Nano_33_IoT_Integration_Analysis.md b/docs/project-4/iot/Arduino_Nano_33_IoT_Integration_Analysis.md index 181d01365..2f457d937 100644 --- a/docs/project-4/iot/Arduino_Nano_33_IoT_Integration_Analysis.md +++ b/docs/project-4/iot/Arduino_Nano_33_IoT_Integration_Analysis.md @@ -35,3 +35,4 @@ The integration of the Arduino Nano 33 IoT into our project is anticipated to si ## Conclusion The Arduino Nano 33 IoT stands out as the optimal choice for our player tracking and crowd monitoring project, offering a blend of connectivity, security, and flexibility unmatched by other platforms. Its selection is a testament to our commitment to leveraging cutting-edge technology to enhance safety, performance, and experience in sports and event management contexts. As we move forward, the Arduino Nano 33 IoT will serve as the technological backbone of our innovative monitoring solution, promising to redefine the standards of real-time data analysis and application in our field. + diff --git a/docs/project-4/iot/Arduino_Programming_Documentation.md b/docs/project-4/iot/Arduino_Programming_Documentation.md index ebaaec4b4..dcac09a7c 100644 --- a/docs/project-4/iot/Arduino_Programming_Documentation.md +++ b/docs/project-4/iot/Arduino_Programming_Documentation.md @@ -47,3 +47,4 @@ The Arduino processes this data to derive actionable insights, performing calcul ## Conclusion The study and application of Arduino programming are fundamental to the success of our player tracking and crowd monitoring project. By bridging hardware components with sophisticated software functionalities, we have created a versatile and powerful system. This foundation not only enables effective data collection and analysis but also ensures our project can adapt to future technological advancements and requirements. The knowledge and skills gained through this Arduino programming study provide a strong basis for innovative solutions in data-driven decision-making and operational efficiency in IoT applications. + diff --git a/docs/project-4/iot/Closed_Loop_FSM_Sensor_Integration.md b/docs/project-4/iot/Closed_Loop_FSM_Sensor_Integration.md index 45d9cd507..d5b86b01c 100644 --- a/docs/project-4/iot/Closed_Loop_FSM_Sensor_Integration.md +++ b/docs/project-4/iot/Closed_Loop_FSM_Sensor_Integration.md @@ -99,3 +99,4 @@ void handleSensorError() { ## Conclusion Integrating closed-loop systems and FSMs with multiple sensors in our project allows for more dynamic and responsive management of sensor data. This approach not only improves the accuracy and reliability of the data collected but also enhances the system's ability to adapt to different conditions and detect anomalies more effectively. + diff --git a/docs/project-4/iot/Data_parsing_guide_accelerometer.mdx b/docs/project-4/iot/Data_parsing_guide_accelerometer.mdx index a13a8e5ab..9f0cf2b29 100644 --- a/docs/project-4/iot/Data_parsing_guide_accelerometer.mdx +++ b/docs/project-4/iot/Data_parsing_guide_accelerometer.mdx @@ -65,3 +65,4 @@ Data parsing plays a critical role in the efficient and effective storage and ma [Mongo prior steps Link](https://drive.google.com/file/d/1Oz2dcAg6w2c4dPY5FORJOHEOjJ0Ecvb1/view?usp=drive_link) + diff --git a/docs/project-4/iot/Export_Sensor_Data_to_CSV_Guide.md b/docs/project-4/iot/Export_Sensor_Data_to_CSV_Guide.md index 6006eb1b2..fd8b08dc5 100644 --- a/docs/project-4/iot/Export_Sensor_Data_to_CSV_Guide.md +++ b/docs/project-4/iot/Export_Sensor_Data_to_CSV_Guide.md @@ -93,3 +93,4 @@ finally: ## Conclusion This guide provides a comprehensive method to capture sensor data from the MAX30102 and export it to a CSV file using Arduino and Python. This setup is ideal for those who need to collect and analyze physiological data for health monitoring or research purposes. + diff --git a/docs/project-4/iot/FSM_and_closed_loop_integration.mdx b/docs/project-4/iot/FSM_and_closed_loop_integration.mdx index eb1c16ff7..bc7dfe5e9 100644 --- a/docs/project-4/iot/FSM_and_closed_loop_integration.mdx +++ b/docs/project-4/iot/FSM_and_closed_loop_integration.mdx @@ -9,4 +9,4 @@ sidebar_position: 15 type="application/pdf" width="100%" height="800px" -/> \ No newline at end of file +/> diff --git a/docs/project-4/iot/Filterpy_library_for data_analysis.mdx b/docs/project-4/iot/Filterpy_library_for data_analysis.mdx index dfb70f930..b25d266a2 100644 --- a/docs/project-4/iot/Filterpy_library_for data_analysis.mdx +++ b/docs/project-4/iot/Filterpy_library_for data_analysis.mdx @@ -68,3 +68,4 @@ The filterpy package provides robust and easy-to-use Kalman filtering capabiliti - [Documentation](https://filterpy.readthedocs.io/en/latest/) - [Online Article on Using FilterPy](https://medium.com/@mike.roweprediger/using-the-filterpy-package-for-time-series-prediction-d8969b9bf5c6) - [Code Example](https://cocalc.com/share/public_paths/embed/7557a5ac1c870f1ec8f01271959b16b49df9d087/Appendix-F-FilterPy-Code.ipynb) + diff --git a/docs/project-4/iot/Future-Enhancements-for-Pi-Cam-Setup.mdx b/docs/project-4/iot/Future-Enhancements-for-Pi-Cam-Setup.mdx index d51667acd..64ae56dba 100644 --- a/docs/project-4/iot/Future-Enhancements-for-Pi-Cam-Setup.mdx +++ b/docs/project-4/iot/Future-Enhancements-for-Pi-Cam-Setup.mdx @@ -9,4 +9,4 @@ sidebar_position: 16 type="application/pdf" width="100%" height="800px" -/> \ No newline at end of file +/> diff --git a/docs/project-4/iot/HIVEMQ-report.mdx b/docs/project-4/iot/HIVEMQ-report.mdx index 008052680..a6a1cc6d9 100644 --- a/docs/project-4/iot/HIVEMQ-report.mdx +++ b/docs/project-4/iot/HIVEMQ-report.mdx @@ -9,4 +9,4 @@ sidebar_position: 17 type="application/pdf" width="100%" height="800px" -/> \ No newline at end of file +/> diff --git a/docs/project-4/iot/Haversine-gps-document.md b/docs/project-4/iot/Haversine-gps-document.md index 49d2a28ec..f0e28fea4 100644 --- a/docs/project-4/iot/Haversine-gps-document.md +++ b/docs/project-4/iot/Haversine-gps-document.md @@ -57,3 +57,4 @@ The Haversine formula is used to calculate the shortest distance between two poi ## Summary The Haversine formula is a fundamental tool for calculating distances between two points on the Earth's surface using latitude and longitude. This detailed explanation and the provided Arduino code illustrate how to implement the formula in a practical project, enhancing navigation and GIS applications. By understanding the formula and the code, you can accurately compute distances between geographic locations using Arduino. + diff --git a/docs/project-4/iot/HiveMQ_MQTT_Implementation_Guide.md b/docs/project-4/iot/HiveMQ_MQTT_Implementation_Guide.md index 612f30381..905b7bb12 100644 --- a/docs/project-4/iot/HiveMQ_MQTT_Implementation_Guide.md +++ b/docs/project-4/iot/HiveMQ_MQTT_Implementation_Guide.md @@ -115,3 +115,4 @@ client.loop_forever() ## Conclusion The integration of HiveMQ and MQTT into our sensor data collection project allows for robust, scalable, and efficient data communication. This setup ensures real-time data monitoring across different platforms, enhancing the capabilities of IoT applications in health monitoring. + diff --git a/docs/project-4/iot/IMU_accelerometer_data_collection_proccess.md b/docs/project-4/iot/IMU_accelerometer_data_collection_proccess.md index cbe25b35a..1c51c975b 100644 --- a/docs/project-4/iot/IMU_accelerometer_data_collection_proccess.md +++ b/docs/project-4/iot/IMU_accelerometer_data_collection_proccess.md @@ -6,3 +6,4 @@ sidebar_position: 5 ![Accelerometer IoT Diagram](img/Accelerometer_Iot_4.png) + diff --git a/docs/project-4/iot/MAX30102_Sensor_Documentation_Updated.md b/docs/project-4/iot/MAX30102_Sensor_Documentation_Updated.md index d06ca32cf..03abf490a 100644 --- a/docs/project-4/iot/MAX30102_Sensor_Documentation_Updated.md +++ b/docs/project-4/iot/MAX30102_Sensor_Documentation_Updated.md @@ -98,3 +98,4 @@ Analyzes health trends within large gatherings, aiding in the preemptive managem ## Conclusion The MAX30102 sensor is a pivotal component of our player tracking and crowd monitoring project. Its capabilities ensure that our system exceeds the necessary standards for effective real-time health monitoring in sports and event management. + diff --git a/docs/project-4/iot/MQTT-types.mdx b/docs/project-4/iot/MQTT-types.mdx index 331939679..8a718b309 100644 --- a/docs/project-4/iot/MQTT-types.mdx +++ b/docs/project-4/iot/MQTT-types.mdx @@ -9,4 +9,4 @@ sidebar_position: 17 type="application/pdf" width="100%" height="800px" -/> \ No newline at end of file +/> diff --git a/docs/project-4/iot/Oximeter_Sensor_Technology_Documentation.md b/docs/project-4/iot/Oximeter_Sensor_Technology_Documentation.md index 3dfada3ca..9ae94745f 100644 --- a/docs/project-4/iot/Oximeter_Sensor_Technology_Documentation.md +++ b/docs/project-4/iot/Oximeter_Sensor_Technology_Documentation.md @@ -38,3 +38,4 @@ Oximeter sensors are widely used in clinical settings, home health care, and wea Oximeter sensor technology provides a non-invasive, accurate, and invaluable means of monitoring oxygen saturation and heart rate. Its integration into wearable technology and health monitoring systems has revolutionized patient care, allowing for continuous, real-time health tracking. As technology advances, further enhancements in oximeter sensors are expected, expanding their applications and improving health outcomes. This report has outlined the operational principles and significance of oximeter sensor technology, emphasizing its critical role in modern health monitoring practices. + diff --git a/docs/project-4/iot/PiCam-and-RaspberryPi-setup.mdx b/docs/project-4/iot/PiCam-and-RaspberryPi-setup.mdx index 678ee95fe..8b620dc86 100644 --- a/docs/project-4/iot/PiCam-and-RaspberryPi-setup.mdx +++ b/docs/project-4/iot/PiCam-and-RaspberryPi-setup.mdx @@ -9,4 +9,4 @@ sidebar_position: 17 type="application/pdf" width="100%" height="800px" -/> \ No newline at end of file +/> diff --git a/docs/project-4/iot/Setting-up-Website-Report.mdx b/docs/project-4/iot/Setting-up-Website-Report.mdx index f33f8dfcd..b45cf1e65 100644 --- a/docs/project-4/iot/Setting-up-Website-Report.mdx +++ b/docs/project-4/iot/Setting-up-Website-Report.mdx @@ -9,4 +9,4 @@ sidebar_position: 17 type="application/pdf" width="100%" height="800px" -/> \ No newline at end of file +/> diff --git a/docs/project-4/iot/documentation -heart-sensor.md b/docs/project-4/iot/documentation -heart-sensor.md index 1b5321cff..d9c649eca 100644 --- a/docs/project-4/iot/documentation -heart-sensor.md +++ b/docs/project-4/iot/documentation -heart-sensor.md @@ -294,3 +294,4 @@ Restart both the Wahoo TICKR and Arduino Nano 33 IoT to reset connections. ## Video Tutorial For a video tutorial, watch [this YouTube video](https://youtu.be/X6fjwMR9INM). + diff --git a/docs/project-4/iot/final-code-documentation-and-tips-for-futur.md b/docs/project-4/iot/final-code-documentation-and-tips-for-futur.md index 8417cd54e..96d45747f 100644 --- a/docs/project-4/iot/final-code-documentation-and-tips-for-futur.md +++ b/docs/project-4/iot/final-code-documentation-and-tips-for-futur.md @@ -125,3 +125,4 @@ Here are some crucial aspects to consider when integrating various sensors into ![Data Flow Diagram](img/Data-Flow_diagram.png) Integrating multiple sensors into a single system offers both challenges and rewards. By addressing specific issues such as overlapping time intervals, BLE disconnections, and power supply management, the final system provides a robust platform for collecting and processing sensor data. This project serves as a valuable lesson in hardware integration, software optimization, and practical application of sensor technology. + diff --git a/docs/project-4/iot/kalmanFilterTutorial.mdx b/docs/project-4/iot/kalmanFilterTutorial.mdx index 82ff39698..569894703 100644 --- a/docs/project-4/iot/kalmanFilterTutorial.mdx +++ b/docs/project-4/iot/kalmanFilterTutorial.mdx @@ -26,3 +26,4 @@ If you're interested in more detailed notes, check out my handwritten notes avai [Access Handwritten Notes](https://drive.google.com/drive/folders/1TuXt5AqY2gl2EqvaFUxqWYKDS9PDKL4l?usp=sharing) + diff --git a/docs/project-4/iot/mongo-guide.mdx b/docs/project-4/iot/mongo-guide.mdx index 29944310d..d71430ad9 100644 --- a/docs/project-4/iot/mongo-guide.mdx +++ b/docs/project-4/iot/mongo-guide.mdx @@ -9,4 +9,4 @@ sidebar_position: 1 type="application/pdf" width="100%" height="800px" -/> \ No newline at end of file +/> diff --git a/docs/project-4/iot/setup-accelerometer.mdx b/docs/project-4/iot/setup-accelerometer.mdx index d347d40e6..6cdab94e7 100644 --- a/docs/project-4/iot/setup-accelerometer.mdx +++ b/docs/project-4/iot/setup-accelerometer.mdx @@ -10,3 +10,4 @@ sidebar_position: 12 width="100%" height="800px" /> + diff --git a/docs/project-5/AWS/Benefits-of-AWS.md b/docs/project-5/AWS/Benefits-of-AWS.md index 537d83b19..a0605211c 100644 --- a/docs/project-5/AWS/Benefits-of-AWS.md +++ b/docs/project-5/AWS/Benefits-of-AWS.md @@ -66,3 +66,4 @@ This extra layer of control helps manage and monitor access easily. ## Conclusion By using AWS IAM for Role-Based Access Control (RBAC), Bugbox has created a secure and flexible system for managing who can access different parts of the platform. With IAM, Bugbox can give users the right amount of access, scale as the platform grows, and integrate with other AWS services. This approach ensures security, reduces risk, and provides a safe learning environment for both educators and students. As the platform continues to expand, Bugbox will be able to adjust access controls easily and efficiently. + diff --git a/docs/project-5/AWS/Implementing-AWS.md b/docs/project-5/AWS/Implementing-AWS.md index 1ad206f62..f25ae0dc9 100644 --- a/docs/project-5/AWS/Implementing-AWS.md +++ b/docs/project-5/AWS/Implementing-AWS.md @@ -59,3 +59,4 @@ The following IAM policy provides write access to a Student role, specifically a } ] } + diff --git a/docs/project-5/AWS/Policies.md b/docs/project-5/AWS/Policies.md index 69ed839cf..ba07cf3c1 100644 --- a/docs/project-5/AWS/Policies.md +++ b/docs/project-5/AWS/Policies.md @@ -168,4 +168,4 @@ The file path dynamically changes based on the student who logs in: - **Dynamic Access**: Policies leverage `${aws:username}` to ensure automatic and secure folder assignment based on the logged-in user. - **Teacher and Admin Privileges**: Teachers have access to all student directories, while admins have unrestricted access to all directories. - **Ease of Management**: No manual intervention is needed to create or assign folders. -- **Security**: Unauthorized access is strictly prevented through specific policies. \ No newline at end of file +- **Security**: Unauthorized access is strictly prevented through specific policies. diff --git a/docs/project-5/AWS/RBAC-Documentation.md b/docs/project-5/AWS/RBAC-Documentation.md index 9fcf1445f..cd1f923cd 100644 --- a/docs/project-5/AWS/RBAC-Documentation.md +++ b/docs/project-5/AWS/RBAC-Documentation.md @@ -103,3 +103,4 @@ To properly implement RBAC, administrators need to create IAM users for each ind ## Conclusion By implementing RBAC with IAM and S3, Bugbox ensures that access to platform resources is secure, roles are clearly defined, and users only have access to what is necessary for their responsibilities. Tags enhance resource management and access control, while the IAM policy system ensures that permissions are correctly assigned, ensuring a compliant and secure environment for all users. + diff --git a/docs/project-5/Accessibility/Accessibility-marking-rubric.md b/docs/project-5/Accessibility/Accessibility-marking-rubric.md index 8c4ab6f88..d017b42b3 100644 --- a/docs/project-5/Accessibility/Accessibility-marking-rubric.md +++ b/docs/project-5/Accessibility/Accessibility-marking-rubric.md @@ -71,3 +71,4 @@ ________________________________________________________________________________ _________________________________________________________________________________________ _________________________________________________________________________________________ _________________________________________________________________________________________ + diff --git a/docs/project-5/Accessibility/Accessiblity-and-why.md b/docs/project-5/Accessibility/Accessiblity-and-why.md index f361e6a23..cdab86429 100644 --- a/docs/project-5/Accessibility/Accessiblity-and-why.md +++ b/docs/project-5/Accessibility/Accessiblity-and-why.md @@ -55,3 +55,4 @@ To ensure accessibility is part of the design, Bugbox can take several steps: Accessibility is an essential part of Bugbox’s goal to make STEM education engaging and open to all students. By ensuring the platform is easy to use for everyone, Bugbox helps students develop the skills they need to succeed in a technology-driven world. Accessibility doesn’t just benefit students with disabilities; it improves the overall experience for everyone, making Bugbox a more inclusive and innovative place to learn. In the end, accessibility is a core value that supports Bugbox’s mission to inspire the next generation of creators. + diff --git a/docs/project-5/Accessibility/guidelines.md b/docs/project-5/Accessibility/guidelines.md index 1a2df986c..04ace2bc4 100644 --- a/docs/project-5/Accessibility/guidelines.md +++ b/docs/project-5/Accessibility/guidelines.md @@ -224,3 +224,4 @@ Regular testing with real users and tools ensures your app remains accessible an ## Conclusion By following these accessibility guidelines, you can make your application more inclusive and usable for users with various disabilities. Consistently testing, incorporating feedback, and adhering to WCAG 2.1 standards will ensure your app is accessible, user-friendly, and compliant with legal requirements. + diff --git a/docs/project-5/Accessibility/validation-tools.md b/docs/project-5/Accessibility/validation-tools.md index 175905616..11f9346dd 100644 --- a/docs/project-5/Accessibility/validation-tools.md +++ b/docs/project-5/Accessibility/validation-tools.md @@ -107,3 +107,4 @@ Let’s do a quick run down of how Accessibility Validation tools can be used, u ## Conclusion Ensuring the accessibility of a digital platform, such as Bugbox, is essential for providing an inclusive and empowering learning experience for all users. By using a combination of automated testing tools, manual checks, and user testing, developers can identify and fix accessibility issues to create a more inclusive product. Regular testing and continuous improvements are necessary to maintain accessibility and ensure that all users, including those with disabilities, can fully engage with the platform. + diff --git a/docs/project-5/Cyber Security Recommendations/Competitors-Report.md b/docs/project-5/Cyber Security Recommendations/Competitors-Report.md index ff16f281c..d36462135 100644 --- a/docs/project-5/Cyber Security Recommendations/Competitors-Report.md +++ b/docs/project-5/Cyber Security Recommendations/Competitors-Report.md @@ -107,3 +107,4 @@ Each competitor employs a range of cybersecurity measures to protect user data a + diff --git a/docs/project-5/Cyber Security Recommendations/Cybecurity-Solutions-Review.md b/docs/project-5/Cyber Security Recommendations/Cybecurity-Solutions-Review.md index c4cf9fdd0..b39eee3e5 100644 --- a/docs/project-5/Cyber Security Recommendations/Cybecurity-Solutions-Review.md +++ b/docs/project-5/Cyber Security Recommendations/Cybecurity-Solutions-Review.md @@ -73,3 +73,4 @@ By leveraging cloud infrastructure for routine tasks and core cybersecurity serv ## Conclusion For Bugbox, adopting a hybrid cybersecurity strategy that balances cloud-based security solutions with in-house control over key aspects of its platform is the optimal choice. By leveraging the advanced security features offered by cloud providers like AWS, Bugbox can secure its infrastructure with minimal overhead, while in-house efforts can focus on building and maintaining custom security policies, access controls, and incident response mechanisms. This balanced approach allows Bugbox to scale securely, meet compliance requirements, and continue providing a safe, engaging learning environment for students and educators. + diff --git a/docs/project-5/Cyber Security Recommendations/RBAC-RestingDataManagement-Report.md b/docs/project-5/Cyber Security Recommendations/RBAC-RestingDataManagement-Report.md index 483319f68..299d1a322 100644 --- a/docs/project-5/Cyber Security Recommendations/RBAC-RestingDataManagement-Report.md +++ b/docs/project-5/Cyber Security Recommendations/RBAC-RestingDataManagement-Report.md @@ -98,3 +98,4 @@ The technical implementation of Data-at-Rest Encryption involves the following s ## Conclusion Implementing RBAC and Data-at-Rest management through encryption is crucial for Bugbox to secure its platform and maintain compliance with data protection regulations. RBAC limits access based on user roles, reducing the risk of unauthorized access, while encryption ensures that even if data is accessed, it remains protected. Together, these security measures provide a comprehensive approach to securing Bugbox’s educational platform. + diff --git a/docs/project-5/Cyber Security Recommendations/Recommended-Approaches-Report.md b/docs/project-5/Cyber Security Recommendations/Recommended-Approaches-Report.md index 6deb0057e..c14a20f07 100644 --- a/docs/project-5/Cyber Security Recommendations/Recommended-Approaches-Report.md +++ b/docs/project-5/Cyber Security Recommendations/Recommended-Approaches-Report.md @@ -136,3 +136,4 @@ Bugbox should conduct regular penetration tests to identify vulnerabilities that ## Conclusion Implementing these technical cybersecurity measures will significantly enhance Bugbox’s ability to protect its platform and users from evolving threats. By focusing on encryption, MFA, regular audits, access control, privacy compliance, and incident response, Bugbox can maintain a secure and trusted environment for educators and students. + diff --git a/docs/project-5/Gamification Research/Adding Gamification.md b/docs/project-5/Gamification Research/Adding Gamification.md index d33b3a162..7987dba40 100644 --- a/docs/project-5/Gamification Research/Adding Gamification.md +++ b/docs/project-5/Gamification Research/Adding Gamification.md @@ -53,3 +53,4 @@ By **Khushpreet Kaur Randhawa** and **Kavishka Prashanth Kevin Samaraskera** **Teacher Dashboards:** Provide teachers with dashboards to help them see how engaged their students are and track their progress. + diff --git a/docs/project-5/Gamification Research/Instant Feedback Mechanism.md b/docs/project-5/Gamification Research/Instant Feedback Mechanism.md index a37fc681d..0975f23c1 100644 --- a/docs/project-5/Gamification Research/Instant Feedback Mechanism.md +++ b/docs/project-5/Gamification Research/Instant Feedback Mechanism.md @@ -91,3 +91,4 @@ An effective instant feedback mechanism not only enhances the user experience bu + diff --git a/docs/project-5/Gamification Research/Questacon's study.md b/docs/project-5/Gamification Research/Questacon's study.md index e27cbacfd..f065bcb72 100644 --- a/docs/project-5/Gamification Research/Questacon's study.md +++ b/docs/project-5/Gamification Research/Questacon's study.md @@ -33,3 +33,4 @@ The games that are offered by Questacon are mentioned below: **Technological Integration:** The Exhibit Design and Development team at Questacon uses advanced computer graphics systems, like the Apple Macintosh, to create detailed and precise exhibit designs. This technological integration allows for more sophisticated and interactive displays. **Collaborative and Cultural Elements:** Questacon collaborates with organizations like Geoscience Australia to develop graphic exhibitions that use visual imagery, such as satellite data, to educate visitors. Additionally, Questacon incorporates cultural elements into its exhibits, such as a mural themed around the United Nations Sustainable Development Goals, created by local graffiti artists, and collaborations with Indigenous communities to blend traditional knowledge with modern technology. + diff --git a/docs/project-5/Gamification Research/UX Design for Gamification element.md b/docs/project-5/Gamification Research/UX Design for Gamification element.md index e498dd09b..ba2669451 100644 --- a/docs/project-5/Gamification Research/UX Design for Gamification element.md +++ b/docs/project-5/Gamification Research/UX Design for Gamification element.md @@ -97,3 +97,4 @@ Also, the Minecraft: Education Edition has collaborative features where students • **Parental Controls and Monitoring:** UX design should integrate easy-to-sue parental controls, allowing parents to monitor usage and restrict certain features. Clear communication of what data being collected and how it’s used fosters trust from both parents and schools. **For Example:** YouTube Kids offers a child-friendly navigation system where access to content is carefully curated, and parental controls are robust. Bugbox can incorporate simple, secure sign-ins with parental dashboards that allow parents to track their child's progress and restrict certain activities. + diff --git a/docs/project-5/Login Games/3d-solar-system.md b/docs/project-5/Login Games/3d-solar-system.md index 9114b32e3..089143b8b 100644 --- a/docs/project-5/Login Games/3d-solar-system.md +++ b/docs/project-5/Login Games/3d-solar-system.md @@ -90,3 +90,4 @@ For future development if drag and drop functionality is needed using **react-dn **see `Router.tsx` in Playground repository** ::: + diff --git a/docs/project-5/Login Games/mini-login-game.md b/docs/project-5/Login Games/mini-login-game.md index ee5637d11..7c6ddd4ab 100644 --- a/docs/project-5/Login Games/mini-login-game.md +++ b/docs/project-5/Login Games/mini-login-game.md @@ -87,3 +87,4 @@ For future development if drag and drop functionality is needed using **react-dn ::: + diff --git a/docs/project-5/Teacher-Reasearch/classroom-activities.md b/docs/project-5/Teacher-Reasearch/classroom-activities.md index 4936ba88d..4dc5d637a 100644 --- a/docs/project-5/Teacher-Reasearch/classroom-activities.md +++ b/docs/project-5/Teacher-Reasearch/classroom-activities.md @@ -147,3 +147,4 @@ Presentation and Reflection: Evaluate the group presentations based on their ana This activity combines learning about robotics and programming with space exploration, inspiring students to think critically and creatively about the possibilities of robotic technology in scientific discovery. + diff --git a/docs/project-5/Teacher-Reasearch/teacher-research.md b/docs/project-5/Teacher-Reasearch/teacher-research.md index de64f6c98..6fe3f844c 100644 --- a/docs/project-5/Teacher-Reasearch/teacher-research.md +++ b/docs/project-5/Teacher-Reasearch/teacher-research.md @@ -108,4 +108,4 @@ Here are the key questions and summarized responses: The feedback provided valuable insights into teachers' needs and concerns, such as the need for simple user interfaces, easy-to-follow lesson plans, and robust support systems to help them successfully integrate BugBox into their curriculum. These findings informed my recommendations on developing the teacher dashboard for BugBox, focusing on providing teachers with streamlined tools, detailed guides, and interactive content to enhance the robotics learning experience. ## Conclusion -Overall, the research confirmed that teachers are open to adopting robotics in their teaching but require a supportive framework, including intuitive software and well-structured lesson plans. As a result, I am now focusing on optimizing the BugBox teacher dashboard to address these needs, which will enhance the usability of the platform, enabling teachers to confidently incorporate robotics into their classrooms. This user-centric approach will ensure that BugBox becomes a valuable tool in modern education, empowering teachers and students alike. \ No newline at end of file +Overall, the research confirmed that teachers are open to adopting robotics in their teaching but require a supportive framework, including intuitive software and well-structured lesson plans. As a result, I am now focusing on optimizing the BugBox teacher dashboard to address these needs, which will enhance the usability of the platform, enabling teachers to confidently incorporate robotics into their classrooms. This user-centric approach will ensure that BugBox becomes a valuable tool in modern education, empowering teachers and students alike. diff --git a/docs/project-5/authentication-game.md b/docs/project-5/authentication-game.md index 8d3387b6f..2bf4f89ca 100644 --- a/docs/project-5/authentication-game.md +++ b/docs/project-5/authentication-game.md @@ -157,3 +157,4 @@ This entire process, from adapting AI-based designs to implementing them into a ![Frame *](img/Frame_6.png) This structure ensures that the game is played first, adding an interactive layer to the login process, as suggested by Dylan. + diff --git a/docs/project-5/mood-board.md b/docs/project-5/mood-board.md index 0a953cf5c..6e2c3dd54 100644 --- a/docs/project-5/mood-board.md +++ b/docs/project-5/mood-board.md @@ -29,4 +29,4 @@ The images show kids happily engaging in robotic and team activities, reflecting ![moodboard](img\Moodboard.jpg) -The board communicates an energetic, inclusive, and innovative brand identity targeted toward young learners and educators. \ No newline at end of file +The board communicates an energetic, inclusive, and innovative brand identity targeted toward young learners and educators. diff --git a/docs/project-5/new-mini-login-game.md b/docs/project-5/new-mini-login-game.md index 617df0e7b..c7acb12f9 100644 --- a/docs/project-5/new-mini-login-game.md +++ b/docs/project-5/new-mini-login-game.md @@ -79,3 +79,4 @@ This game helps users practice math skills in a fun and engaging way. - Visual Studio Code (VS Code) for code editing - Browser for testing (Chrome) - Terminal for running npm commands + diff --git a/docs/project-5/next-gen-dotty.md b/docs/project-5/next-gen-dotty.md index 5d2023ca0..96c479cb6 100644 --- a/docs/project-5/next-gen-dotty.md +++ b/docs/project-5/next-gen-dotty.md @@ -72,3 +72,4 @@ The current board, an Arduino Nano, is likely not able to power or handle the da So considering this, the Arduino Mega may be the best option going forward. It offers significantly more memory (30kB vs 248kB when removing bootloader usage) which is likely needed for the display and sound modules, nearly three times as many pins, and four serial ports which could be used for the modules. The Mega does come with a substantial price increase over the Nano, however for the longevity of the device, this price could be justified. The older Nano and PCBs could still be used in basic classes to avoid waste. + diff --git a/docs/project-5/privacy-policy.md b/docs/project-5/privacy-policy.md index a19a1b3d8..afff6f131 100644 --- a/docs/project-5/privacy-policy.md +++ b/docs/project-5/privacy-policy.md @@ -43,3 +43,4 @@ This Privacy Policy may be updated periodically to reflect changes in laws or pl ### 10. Contact Information For questions or concerns about these terms, please contact us at info@bugbox.com. + diff --git a/docs/project-5/teacher-dashboard.md b/docs/project-5/teacher-dashboard.md index b7e2977f5..86715ccc0 100644 --- a/docs/project-5/teacher-dashboard.md +++ b/docs/project-5/teacher-dashboard.md @@ -68,3 +68,4 @@ The Freeze/Unfreeze Tab is a valuable tool for classroom management. If a teache In addition to these functionalities, the dashboard enhances usability with visual feedback; hovering over the tabs on the left changes them to their respective colors, including the freeze and unfreeze buttons. This feature not only improves the aesthetic appeal but also provides clear, immediate feedback to the teacher, creating a user-friendly experience. ![Hover](img\Hover_Options.png) ![Hover Freeze/Unfreeze](img\Freeze_Unfreeze.png) + diff --git a/docs/project-5/terms-conditions.md b/docs/project-5/terms-conditions.md index e768bb480..d92aa8f3d 100644 --- a/docs/project-5/terms-conditions.md +++ b/docs/project-5/terms-conditions.md @@ -38,3 +38,4 @@ These Terms & Conditions are governed by the laws of …. ### 9. Contact Information For questions or concerns about these terms, please contact us at info@bugbox.com. + diff --git a/docs/web-mobile-app-dev/CMS-report/cms_research.md b/docs/web-mobile-app-dev/CMS-report/cms_research.md index 992c5cea1..50f3b0116 100644 --- a/docs/web-mobile-app-dev/CMS-report/cms_research.md +++ b/docs/web-mobile-app-dev/CMS-report/cms_research.md @@ -106,4 +106,4 @@ Redback Operations has various teams utilizing content management systems (CMS) - **Satisfaction:** - The team is pleased with the current data warehouse solutions in place. - **Challenges:** - - May require a CMS to manage data-related content, such as documentation, user guides, and data governance policies, as the data needs expand. \ No newline at end of file + - May require a CMS to manage data-related content, such as documentation, user guides, and data governance policies, as the data needs expand. diff --git a/docs/web-mobile-app-dev/backend.md b/docs/web-mobile-app-dev/backend.md index c209a3a7a..a25929d22 100644 --- a/docs/web-mobile-app-dev/backend.md +++ b/docs/web-mobile-app-dev/backend.md @@ -8,3 +8,4 @@ sidebar_position: 3 ### For all projects [![Redback CMS Repo card](https://github-readme-stats.vercel.app/api/pin/?username=Redback-Operations&repo=redback-cms)](https://github.com/Redback-Operations/redback-cms) + diff --git a/docs/web-mobile-app-dev/frontend/dos-donts.md b/docs/web-mobile-app-dev/frontend/dos-donts.md index 062af7b02..474d822a1 100644 --- a/docs/web-mobile-app-dev/frontend/dos-donts.md +++ b/docs/web-mobile-app-dev/frontend/dos-donts.md @@ -185,3 +185,4 @@ sidebar_position: 3 ![Correct action](./img/icon-success.svg) In that pull request creation screen, check the target and ensure your project repository is selected, not the template. + diff --git a/docs/web-mobile-app-dev/frontend/getting-started.md b/docs/web-mobile-app-dev/frontend/getting-started.md index 2b0c7d87b..01e204766 100644 --- a/docs/web-mobile-app-dev/frontend/getting-started.md +++ b/docs/web-mobile-app-dev/frontend/getting-started.md @@ -63,3 +63,4 @@ sidebar_label: Getting started - [TypeScript docs](https://www.typescriptlang.org/docs/) - [React Router docs](https://reactrouter.com/) - [Styled Components docs](https://styled-components.com/) + diff --git a/docs/web-mobile-app-dev/frontend/help/troubleshooting.md b/docs/web-mobile-app-dev/frontend/help/troubleshooting.md index a8ddce01b..7c0d4f845 100644 --- a/docs/web-mobile-app-dev/frontend/help/troubleshooting.md +++ b/docs/web-mobile-app-dev/frontend/help/troubleshooting.md @@ -28,3 +28,4 @@ Tip: If you are using Linux or WSL, using the CLI is a super easy way to do this - [Vite docs](https://vitejs.dev/guide/) + diff --git a/docs/web-mobile-app-dev/frontend/help/tutorials.md b/docs/web-mobile-app-dev/frontend/help/tutorials.md index 61eb1ae4f..9f20b8754 100644 --- a/docs/web-mobile-app-dev/frontend/help/tutorials.md +++ b/docs/web-mobile-app-dev/frontend/help/tutorials.md @@ -14,3 +14,4 @@ Short video tutorials covering the basics of setting up and contributing to Redb 2. [Storybook 101](https://www.loom.com/share/527a2b3bec2d430b805dd35e273e9f27?sid=31f6d006-271c-40ff-8412-a792aa61e03e) (9 minutes) 3. [Creating a new component + Styled Components 101](https://www.loom.com/share/79151a01446d4a798267b72dc01b6fa2) (15 minutes) 4. Accessibility 101 + Styled Components 102 (coming soon) + diff --git a/docs/web-mobile-app-dev/frontend/help/useful-links.md b/docs/web-mobile-app-dev/frontend/help/useful-links.md index 8b01a775a..7fa771e96 100644 --- a/docs/web-mobile-app-dev/frontend/help/useful-links.md +++ b/docs/web-mobile-app-dev/frontend/help/useful-links.md @@ -20,3 +20,4 @@ sidebar_label: Useful external links - [generate-react-cli](https://www.npmjs.com/package/generate-react-cli) - [ESLint](https://eslint.org/docs/latest/) - [eslint-plugin-project-structure](https://github.com/Igorkowalski94/eslint-plugin-project-structure) + diff --git a/docs/web-mobile-app-dev/frontend/leaders/new-repos.md b/docs/web-mobile-app-dev/frontend/leaders/new-repos.md index 178eae964..5f0e88987 100644 --- a/docs/web-mobile-app-dev/frontend/leaders/new-repos.md +++ b/docs/web-mobile-app-dev/frontend/leaders/new-repos.md @@ -18,3 +18,4 @@ If project leaders and the company web dev leader(s) agree there is a genuine ne For a shared library, it may be more appropriate to start from scratch but copy the structure, tools, and processes of the other codebases. All new repositories should be created in the [Redback Operations GitHub organisation](../../../onboarding/github/github-org-guide.md) in the first instance, **not** in personal accounts. This needs to be done by a project leader, company leader, mentor, or experienced student with "membership" of the org. + diff --git a/docs/web-mobile-app-dev/frontend/leaders/updating-from-template.md b/docs/web-mobile-app-dev/frontend/leaders/updating-from-template.md index f069831f1..4304b24d8 100644 --- a/docs/web-mobile-app-dev/frontend/leaders/updating-from-template.md +++ b/docs/web-mobile-app-dev/frontend/leaders/updating-from-template.md @@ -55,4 +55,4 @@ Due to merge conflicts and branch protection rules, the "sync fork" button may n - If there were any changes you discarded during the merge, explain why in the PR description (e.g., "We're already using a newer version of this package") ## Useful Links -- [GitHub docs: Syncing a fork](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork) \ No newline at end of file +- [GitHub docs: Syncing a fork](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork) diff --git a/docs/web-mobile-app-dev/frontend/new-components.md b/docs/web-mobile-app-dev/frontend/new-components.md index 8ccaaa671..45250bf9e 100644 --- a/docs/web-mobile-app-dev/frontend/new-components.md +++ b/docs/web-mobile-app-dev/frontend/new-components.md @@ -37,3 +37,4 @@ If you are creating your component in Redback UI, this will also generate: ### Further reading - [What are components in the front-end and why do we need them?](https://dev.to/xavortm/what-are-components-in-the-front-end-and-why-do-we-need-them-2o2p) - Alex Dimitrov - [Dos and Don'ts - Tech Stack](http://localhost:3000/redback-documentation/docs/web-mobile-app-dev/frontend/dos-donts#tech-stack) - Redback docs + diff --git a/docs/web-mobile-app-dev/frontend/new-routes.md b/docs/web-mobile-app-dev/frontend/new-routes.md index 63c4bc2d0..6a8dd2a9c 100644 --- a/docs/web-mobile-app-dev/frontend/new-routes.md +++ b/docs/web-mobile-app-dev/frontend/new-routes.md @@ -117,3 +117,4 @@ As mentioned briefly above, your page should be made up of components. If you fi ## Further reading - [Dos and Don'ts - Tech Stack](http://localhost:3000/redback-documentation/docs/web-mobile-app-dev/frontend/dos-donts#tech-stack) - Redback docs + diff --git a/docs/web-mobile-app-dev/frontend/projects.md b/docs/web-mobile-app-dev/frontend/projects.md index 57f1de5ae..d0e7a3ead 100644 --- a/docs/web-mobile-app-dev/frontend/projects.md +++ b/docs/web-mobile-app-dev/frontend/projects.md @@ -56,3 +56,4 @@ Please use these repositories in conjunction with Redback UI (for shared compone [![Redback Senior repo card](https://github-readme-stats.vercel.app/api/pin/?username=Redback-Operations&repo=redback-senior-web)](https://github.com/Redback-Operations/redback-senior-web) [![Redback Fit repo card](https://github-readme-stats.vercel.app/api/pin/?username=Redback-Operations&repo=redback-fit-web)](https://github.com/Redback-Operations/redback-fit-web) [![Redback Orion repo card](https://github-readme-stats.vercel.app/api/pin/?username=Redback-Operations&repo=redback-orion-web)](https://github.com/Redback-Operations/redback-orion-web) + diff --git a/docs/web-mobile-app-dev/frontend/react-router.md b/docs/web-mobile-app-dev/frontend/react-router.md index b2bf19574..489a06db8 100644 --- a/docs/web-mobile-app-dev/frontend/react-router.md +++ b/docs/web-mobile-app-dev/frontend/react-router.md @@ -6,3 +6,4 @@ sidebar_title: Using React Router # Using React Router Coming soon. + diff --git a/docs/web-mobile-app-dev/frontend/redback-ui.mdx b/docs/web-mobile-app-dev/frontend/redback-ui.mdx index c9995c410..e25aa3359 100644 --- a/docs/web-mobile-app-dev/frontend/redback-ui.mdx +++ b/docs/web-mobile-app-dev/frontend/redback-ui.mdx @@ -81,3 +81,4 @@ This process must be performed by someone with write access to the GitHub reposi + diff --git a/docs/web-mobile-app-dev/frontend/styled-components.md b/docs/web-mobile-app-dev/frontend/styled-components.md index 9134e49cf..776353b9d 100644 --- a/docs/web-mobile-app-dev/frontend/styled-components.md +++ b/docs/web-mobile-app-dev/frontend/styled-components.md @@ -183,3 +183,4 @@ Please follow the [Creating a new component](./new-components.md) guide when cre - [Styled Components documentation](https://styled-components.com/) - [Polished documentation](https://polished.js.org/) - [Redback UI themes](https://redback-operations.github.io/redback-ui/?path=/docs/design-tokens-colours--docs) + diff --git a/docs/web-mobile-app-dev/frontend/submitting-work.md b/docs/web-mobile-app-dev/frontend/submitting-work.md index 078bf732a..f48c2728b 100644 --- a/docs/web-mobile-app-dev/frontend/submitting-work.md +++ b/docs/web-mobile-app-dev/frontend/submitting-work.md @@ -63,3 +63,4 @@ Before raising a pull request, please ensure the below checks pass. - [Project structure linter docs](https://github.com/Igorkowalski94/eslint-plugin-project-structure) - [ESLint in WebStorm](https://www.jetbrains.com/help/webstorm/eslint.html) - How to configure ESLint in WebStorm and fix formatting on save - [ESLint VS Code extension](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) - can be figured to fix formatting on save + diff --git a/docs/web-mobile-app-dev/frontend/tests.md b/docs/web-mobile-app-dev/frontend/tests.md index 139c6222a..5d6e6bab8 100644 --- a/docs/web-mobile-app-dev/frontend/tests.md +++ b/docs/web-mobile-app-dev/frontend/tests.md @@ -11,3 +11,4 @@ More details coming soon. ## Useful links - [React Testing Library cheatsheet](https://testing-library.com/docs/react-testing-library/cheatsheet/) - [Jest DOM matchers](https://github.com/testing-library/jest-dom?tab=readme-ov-file#custom-matchers) + diff --git a/docs/web-mobile-app-dev/frontend/upskilling.md b/docs/web-mobile-app-dev/frontend/upskilling.md index 876cdd202..a583850cd 100644 --- a/docs/web-mobile-app-dev/frontend/upskilling.md +++ b/docs/web-mobile-app-dev/frontend/upskilling.md @@ -49,3 +49,4 @@ There are many ways to achieve the same thing in web development, but it is impo When finding further resources yourself, always ensure they are up-to-date and relevant to the version of the technology we are using. For example, if you are learning React, the current version is 18 and function components are generally preferred over class components. Older resources may go into detail about class components and lifecycle methods which are no longer considered best practice. ::: + diff --git a/docs/web-mobile-app-dev/mobile-doc/mobile-projects.md b/docs/web-mobile-app-dev/mobile-doc/mobile-projects.md index 3fff43736..81085f70c 100644 --- a/docs/web-mobile-app-dev/mobile-doc/mobile-projects.md +++ b/docs/web-mobile-app-dev/mobile-doc/mobile-projects.md @@ -14,3 +14,4 @@ sidebar_position: 0 [![Readme Card](https://github-readme-stats.vercel.app/api/pin/?username=Redback-Operations&repo=redback-senior-mobile)](https://github.com/Redback-Operations/redback-senior-mobile) [![Readme Card](https://github-readme-stats.vercel.app/api/pin/?username=Redback-Operations&repo=redback-fit-mobile)](https://github.com/Redback-Operations/redback-fit-mobile) [![Readme Card](https://github-readme-stats.vercel.app/api/pin/?username=Redback-Operations&repo=redback-orion-mobile)](https://github.com/Redback-Operations/redback-orion-mobile) + diff --git a/docs/web-mobile-app-dev/mobile-doc/smartbike-mobile-backend.md b/docs/web-mobile-app-dev/mobile-doc/smartbike-mobile-backend.md index d584a294c..16841865f 100644 --- a/docs/web-mobile-app-dev/mobile-doc/smartbike-mobile-backend.md +++ b/docs/web-mobile-app-dev/mobile-doc/smartbike-mobile-backend.md @@ -139,3 +139,4 @@ pip install python-dotenv Restart Visual Studio Code or your IDE to ensure the environment is refreshed. + diff --git a/docs/web-mobile-app-dev/mobile-doc/smartbike-readme.md b/docs/web-mobile-app-dev/mobile-doc/smartbike-readme.md index 9e92b2a9c..de26193e1 100644 --- a/docs/web-mobile-app-dev/mobile-doc/smartbike-readme.md +++ b/docs/web-mobile-app-dev/mobile-doc/smartbike-readme.md @@ -72,3 +72,4 @@ git push # You might need to set the upstream branch if it's a new branch ### Happy Coding! Remember, if in doubt about any steps or issues, contact your project leader for assistance. +