Adding internal inf and AD testing methodologies

[BC-Lucille]

Adding methodologies for internal infrastructure and active directory testing.

[Copilot]

Pull Request Overview

This PR adds two comprehensive testing methodologies for internal infrastructure and Active Directory environments. The methodologies provide structured checklists for security assessments, covering reconnaissance, vulnerability identification, and exploitation techniques.

• Adds a detailed Internal Network Penetration Testing methodology covering network reconnaissance, protocol assessments, and service enumeration
• Adds an Active Directory Testing methodology focusing on AD-specific attacks and privilege escalation techniques
• Both methodologies include tool recommendations and structured approach to testing various components

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 7 comments.

File	Description
methodologies/Internal_Network_Methodology.json	Comprehensive methodology for internal network infrastructure testing including reconnaissance, protocols, databases, and web applications
methodologies/Active_Directory_Methodology.json	Structured methodology for Active Directory security testing including NTLM relay, DACL abuse, SCCM, ADCS, and Kerberos attacks

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

Duplicate key 'unpatched_software_cve' found. This key was already defined on line 41, which will cause JSON parsing issues.

[Copilot]

Duplicate key 'outdated_unsupported_os' found. This key was already defined on line 47, which will cause JSON parsing issues.

[Copilot]

Duplicate key 'traffic_poisoning' found. This key was already defined on line 53, which will cause JSON parsing issues.

Suggested change

	"key": "traffic_poisoning",
	"key": "unpatched_software_cve_2",
	"title": "Unpatched Software & CVEs",
	"description": "Identify the use of outdated and unpatched software in use throughout the network. Assess which publicly disclosed vulnerabilities impact these software versions. ",
	"tools": "Nmap, Zenmap"
	},
	{
	"key": "outdated_unsupported_os_2",
	"title": "Outdated and Unsupported Operating Systems",
	"description": "Identify hosts using outdated and end-of-life operating systems.",
	"tools": "Nessus, nmap"
	},
	{
	"key": "traffic_poisoning_2",

[Copilot]

Trailing space after the period in the description text.

Suggested change

	"description": "Identify the use of outdated and unpatched software in use throughout the network. Assess which publicly disclosed vulnerabilities impact these software versions. ",
	"description": "Identify the use of outdated and unpatched software in use throughout the network. Assess which publicly disclosed vulnerabilities impact these software versions.",

[Copilot]

Trailing space after the period in the description text.

Suggested change

	"description": "Identify the use of outdated and unpatched software in use throughout the network. Assess which publicly disclosed vulnerabilities impact these software versions. ",
	"description": "Identify the use of outdated and unpatched software in use throughout the network. Assess which publicly disclosed vulnerabilities impact these software versions.",

[Copilot]

Double space between 'from' and 'available', and trailing space after the period.

Suggested change

	"description": "Attempt to brute-force files from available TFTP servers. For any enumerated files, search for the presence of sensitive data (e.g credentials, configuration data). Fingerprint the TFTP software version and assess whether it is impacted by known vulnerabilities. ",
	"description": "Attempt to brute-force files from available TFTP servers. For any enumerated files, search for the presence of sensitive data (e.g credentials, configuration data). Fingerprint the TFTP software version and assess whether it is impacted by known vulnerabilities.",

[Copilot]

Double space between 'using' and 'default'.

Suggested change

	"description": "Determine whether you can gain access to the MSSQL server(s) using default or weak credentials (e.g sa:sa).",
	"description": "Determine whether you can gain access to the MSSQL server(s) using default or weak credentials (e.g sa:sa).",

[adarshaks91]

raised a new one here: #23