Lesson 5.8: Capstone: assessing an acquired domain before the trust
Northwind has bought Brightwater Analytics, a small company with its own Active Directory domain, BW.NORTHWIND.EXAMPLE. Next month the two domains are to be joined by a trust, and a trust lets problems in one domain reach the other. Before that, you assess Brightwater's domain with everything in this course: privileged groups, roastable accounts, password policy, replication rights, LAPS and SYSVOL. You record each finding with its severity, evidence and fix, sort them, seal the report, and give a clear recommendation about the trust.
26 min
You will learn to
- Assess a domain end to end from a Linux workstation
- Record findings with severity, evidence and fix
- Prioritise a critical finding
- Seal a report with a hash
- Recommend conditions for a domain trust
Key terms
- Domain trust
- A relationship that lets users of one domain be authenticated by another.
- Finding
- One problem, written with area, severity, evidence and fix.
- Severity
- How urgent a finding is: CRITICAL, HIGH, MEDIUM, LOW.
- Report seal
- A hash of the report taken when it's delivered.
- Remediation owner
- The named person responsible for fixing a finding by a date.
← Path traversal and command injection · All lessons · IDS alerts with Suricata →