Skip to content

Conversation

@Mouse933
Copy link

This PR is simply for cleaning out the SDO document hub. I've removed the original copies of the four directories that were present, and have stored them in the archive files so the information on them isn't lost.

This will make it easier to navigate the onboarding process for SecDevOps as there will now only be two files shown when opening the document hub, the archive files and the onboarding process, with the onboarding directory being the first to be seen by new users.

As this simply cleans out the files, there are no changes outside what was sent in my previous PR.

@Mouse933 Mouse933 requested review from a team as code owners January 17, 2026 07:55
@github-actions
Copy link

🔒 OWASP Scanner Results

Vulnerabilities were detected:

### File: docs/cybersecurity/SecDevOps Team/Archived Files/Azure Boards Project Management/Azure DevOps Comparative Assessment.md

🔒 OWASP Scanner Results for docs/cybersecurity/SecDevOps Team/Archived Files/Azure Boards Project Management/Azure DevOps Comparative Assessment.md

✅ No vulnerabilities found.


### File: docs/cybersecurity/SecDevOps Team/Archived Files/Azure Boards Project Management/Azure DevOps Quick Start Guide.md

🔒 OWASP Scanner Results for docs/cybersecurity/SecDevOps Team/Archived Files/Azure Boards Project Management/Azure DevOps Quick Start Guide.md

✅ No vulnerabilities found.


### File: docs/cybersecurity/SecDevOps Team/Archived Files/Azure Boards Project Management/_category_.json

🔒 OWASP Scanner Results for docs/cybersecurity/SecDevOps Team/Archived Files/Azure Boards Project Management/_category_.json

✅ No vulnerabilities found.


### File: docs/cybersecurity/SecDevOps Team/Archived Files/Coding Best Practices/Introduction.md

🔒 OWASP Scanner Results for docs/cybersecurity/SecDevOps Team/Archived Files/Coding Best Practices/Introduction.md

✅ No vulnerabilities found.


### File: docs/cybersecurity/SecDevOps Team/Archived Files/Coding Best Practices/Section1.md

🔒 OWASP Scanner Results for docs/cybersecurity/SecDevOps Team/Archived Files/Coding Best Practices/Section1.md

✅ No vulnerabilities found.


### File: docs/cybersecurity/SecDevOps Team/Archived Files/Coding Best Practices/Section2.md

🔒 OWASP Scanner Results for docs/cybersecurity/SecDevOps Team/Archived Files/Coding Best Practices/Section2.md

✅ No vulnerabilities found.


### File: docs/cybersecurity/SecDevOps Team/Archived Files/Coding Best Practices/Section3.md

🔒 OWASP Scanner Results for docs/cybersecurity/SecDevOps Team/Archived Files/Coding Best Practices/Section3.md

✅ No vulnerabilities found.


### File: docs/cybersecurity/SecDevOps Team/Archived Files/Coding Best Practices/Section4.md

🔒 OWASP Scanner Results for docs/cybersecurity/SecDevOps Team/Archived Files/Coding Best Practices/Section4.md

✅ No vulnerabilities found.


### File: docs/cybersecurity/SecDevOps Team/Archived Files/Coding Best Practices/_category_.json

🔒 OWASP Scanner Results for docs/cybersecurity/SecDevOps Team/Archived Files/Coding Best Practices/_category_.json

✅ No vulnerabilities found.


### File: docs/cybersecurity/SecDevOps Team/Archived Files/README.md

🔒 OWASP Scanner Results for docs/cybersecurity/SecDevOps Team/Archived Files/README.md

✅ No vulnerabilities found.


### File: docs/cybersecurity/SecDevOps Team/Archived Files/_category_.json

🔒 OWASP Scanner Results for docs/cybersecurity/SecDevOps Team/Archived Files/_category_.json

✅ No vulnerabilities found.


### File: docs/cybersecurity/SecDevOps Team/Archived Files/azure/_category_.json

🔒 OWASP Scanner Results for docs/cybersecurity/SecDevOps Team/Archived Files/azure/_category_.json

✅ No vulnerabilities found.


### File: docs/cybersecurity/SecDevOps Team/Archived Files/azure/azure-proposal.md

🔒 OWASP Scanner Results for docs/cybersecurity/SecDevOps Team/Archived Files/azure/azure-proposal.md

✅ No vulnerabilities found.


### File: docs/cybersecurity/SecDevOps Team/Archived Files/secure-code/Bandit_Documentation.md

🔒 OWASP Scanner Results for docs/cybersecurity/SecDevOps Team/Archived Files/secure-code/Bandit_Documentation.md

A03: Sensitive Data Exposure (1 findings)

Summary: HIGH: 1

  • Line 61 | Severity HIGH | Confidence MEDIUM
    → Potential hardcoded sensitive data: pattern = re.compile(r'(?i)(password|secret|key|token)\s*=\s*["'][^"\']+["']')

### File: docs/cybersecurity/SecDevOps Team/Archived Files/secure-code/Dependency-Scanner-Report.md

🔒 OWASP Scanner Results for docs/cybersecurity/SecDevOps Team/Archived Files/secure-code/Dependency-Scanner-Report.md

✅ No vulnerabilities found.


### File: docs/cybersecurity/SecDevOps Team/Archived Files/secure-code/Dependency-Scanner.md

🔒 OWASP Scanner Results for docs/cybersecurity/SecDevOps Team/Archived Files/secure-code/Dependency-Scanner.md

✅ No vulnerabilities found.


### File: docs/cybersecurity/SecDevOps Team/Archived Files/secure-code/OWASP-Top-10-review.md

🔒 OWASP Scanner Results for docs/cybersecurity/SecDevOps Team/Archived Files/secure-code/OWASP-Top-10-review.md

✅ No vulnerabilities found.


### File: docs/cybersecurity/SecDevOps Team/Archived Files/secure-code/TLSPlan.md

🔒 OWASP Scanner Results for docs/cybersecurity/SecDevOps Team/Archived Files/secure-code/TLSPlan.md

✅ No vulnerabilities found.


### File: docs/cybersecurity/SecDevOps Team/Archived Files/secure-code/TLS_Proof_of_Concept_plus_automation.md

🔒 OWASP Scanner Results for docs/cybersecurity/SecDevOps Team/Archived Files/secure-code/TLS_Proof_of_Concept_plus_automation.md

✅ No vulnerabilities found.


### File: docs/cybersecurity/SecDevOps Team/Archived Files/secure-code/_category_.json

🔒 OWASP Scanner Results for docs/cybersecurity/SecDevOps Team/Archived Files/secure-code/_category_.json

✅ No vulnerabilities found.


### File: docs/cybersecurity/SecDevOps Team/Archived Files/secure-code/adjusting-mac.md

🔒 OWASP Scanner Results for docs/cybersecurity/SecDevOps Team/Archived Files/secure-code/adjusting-mac.md

A03: Sensitive Data Exposure (1 findings)

Summary: HIGH: 1

  • Line 25 | Severity HIGH | Confidence HIGH
    → Weak hashing algorithm detected: This update hashes the MAC address using MD5, to the encode it in Base64, then it shortens it to 10

### File: docs/cybersecurity/SecDevOps Team/Archived Files/secure-code/flutter-best-practice.md

🔒 OWASP Scanner Results for docs/cybersecurity/SecDevOps Team/Archived Files/secure-code/flutter-best-practice.md

A04: Insecure Design (1 findings)

Summary: MEDIUM: 1

  • Line 98 | Severity MEDIUM | Confidence LOW
    → Potential insecure design marker: - Jailbroken devices allow attackers to bypass security measures and import

### File: docs/cybersecurity/SecDevOps Team/Archived Files/secure-code/project-1-MQTT.md

🔒 OWASP Scanner Results for docs/cybersecurity/SecDevOps Team/Archived Files/secure-code/project-1-MQTT.md

✅ No vulnerabilities found.


### File: docs/cybersecurity/SecDevOps Team/Archived Files/secure-code/project1-mqtt-secure-code-review.md

🔒 OWASP Scanner Results for docs/cybersecurity/SecDevOps Team/Archived Files/secure-code/project1-mqtt-secure-code-review.md

A09: Security Logging and Monitoring Failures (2 findings)

Summary: MEDIUM: 2

  • Line 126 | Severity MEDIUM | Confidence LOW
    → Exception handled with print() instead of proper logging/alerting near: except Exception as e:
  • Line 143 | Severity MEDIUM | Confidence LOW
    → Exception handled with print() instead of proper logging/alerting near: except Exception as e:

### File: docs/cybersecurity/SecDevOps Team/Archived Files/secure-code/secure-code-review-methodologies.md

🔒 OWASP Scanner Results for docs/cybersecurity/SecDevOps Team/Archived Files/secure-code/secure-code-review-methodologies.md

✅ No vulnerabilities found.

⛔ Please address these before merging.

Copy link

@raymondchoy14 raymondchoy14 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good to go

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants