Skip to content

Commit c518b70

Browse files
andrew-aikenandrew-aiken
committed
Move stuff arond in the docs subfolder
1 parent d30ffc6 commit c518b70

File tree

13 files changed

+91
-16
lines changed

13 files changed

+91
-16
lines changed

‎config/_default/languages.yaml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ en:
5252
name: "NECCDC 2026"
5353
url: "/history/2026/"
5454
weight: 4
55-
55+
5656
- identifier: "history"
5757
name: "History"
5858
url: "/history/"

‎content/en/docs/_index.md‎

Lines changed: 2 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -3,11 +3,5 @@ title: "Docs"
33
description: "Lander for NECCDL Resources"
44
---
55

6-
## NECCDL
7-
8-
- [Discord Verification](discord-verification)
9-
10-
## NECCDC
11-
12-
- [Incident Report Template](files/IncidentReportTemplate.pdf)
13-
- [Red Team Advice](red_team_advice)
6+
Work in progress lander for NECCDC resource.
7+
If you have any sugesstions please open an issue or submit a PR.

‎content/en/docs/neccdc/_index.md‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
---
2+
title: "NECCDC"
3+
description: "Resource on getting started competing at NECCDC"
4+
type: midlist
5+
---
6+
7+
- [Discord Verification](discord-verification)

content/en/docs/discord-verification/index.md renamed to content/en/docs/neccdc/discord-verification/index.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,7 @@
11
---
22
title: "Discord Verification"
33
description: "How to verify your account on the NECCDL Discord server"
4-
_build:
5-
list: never
4+
includeInList: false
65
---
76

87
As a measure to reduce spam, NECCDL requires all participants to verify their Discord accounts before being allowed into the general NECCDL Discord server.

‎content/en/docs/red-team/_index.md‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
---
2+
title: "Red Team"
3+
description: "NECCDC red team resources"
4+
type: midlist
5+
---
6+
7+
- [Incident Response Report Template](files/IncidentResponseReportTemplate.pdf)
8+
- [Red Team Advice](red-team-advice)
9+
- [Sample Incident Response Report](sample-ir)

content/en/docs/files/IncidentReportTemplate.pdf renamed to content/en/docs/red-team/files/IncidentResponseReportTemplate.pdf

File renamed without changes.

content/en/docs/red_team_advice/index.md renamed to content/en/docs/red-team/red-team-advice/index.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,7 @@
11
---
22
title: "NECCDC Red Team Advice"
3-
description: "TODO"
4-
_build:
5-
list: never
3+
description: ""
4+
includeInList: false
65
---
76

87
## Incident Reports can help win back points, but only if they are good!

‎content/en/docs/red-team/sample-ir/index.md‎

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
---
2+
title: "Sample IR Report"
3+
description: ""
4+
includeInList: false
5+
---
6+
7+
## Executive Summary
8+
On January 31st, the organization identified a security incident involving the compromise of our Windows Domain Controller, a critical system responsible for authentication, authorization, and identity management across our enterprise.
9+
Due to the central role of this system, the incident was treated as a high severity event and we escalated response immediately.
10+
Initial investigation determined that an unauthorized actor gained Administrator access to the Windows Domain Controller and installed malicious software. The malicious software can only cause a denial of service to our enterprise environment due to the capability to continually reboot the Domain Controller.
11+
However, the attacker had the potential to access or manipulate user accounts, group policies, and authentication mechanisms across the domain.
12+
At this time, there is no evidence of data exfiltration or persistent lateral movement beyond the affected systems, but forensic research is still ongoing.
13+
Upon detection, the Incident Response team executed containment actions, including removing the malicious software from affected systems, revoking compromised credentials, and restricting domain access to prevent further unauthorized activity. A full forensic analysis was initiated to determine the scope, timeline, and impact of the compromise.
14+
We will continue to pursue remediation according to our Incident Response Plan for this type of event which will include:
15+
16+
Mandatory password resets for all domain accounts, review and cleanup of privileged access, validation of Group Policy Objects, and deployment of additional monitoring and detection capabilities.
17+
Relevant stakeholders were notified, and the incident was handled in accordance with internal security policies. Regulatory disclosures will occur as required.
18+
The organization successfully contained the incident, restored normal operations, and implemented corrective actions to reduce the likelihood of recurrence.
19+
A post-incident review is underway to address root causes, improve security posture, and enhance detection and response capabilities moving forward.

‎content/en/docs/white-team/_index.md‎

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
---
2+
title: "White Team"
3+
description: "NECCDC white team resources"
4+
type: midlist
5+
---

‎content/en/sponsor/index.md‎

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
---
22
title: "Sponsor"
33
description: The Northeast Collegiate Cyber Defense League would not be possible without our generous support from out sponsors
4-
includeInList: false
54
date: 1970-01-01
65
---
76

0 commit comments

Comments
 (0)