STATUS: STAGED — NOT YET AVAILABLE TO ACTIVE STUDENTS.
This lab becomes available when your instructor announces that CyDeploy
Community Edition has been installed in the lab environment.
A tool tells you what it sees. It does not know your organization's policy.
CyDeploy has reported a set of conditions in your pod. Some of them are real
problems. Some of them are exactly what ACS expects. One of them is a deviation
that ACS has already formally approved. At least one cannot be judged without
more information.
Your job is to turn raw output into findings — decisions supported by the ACS
baseline, the approved software list, and the exception register.
You are not asked to remediate anything in this lab. Analysis only.
By the end of this lab you will be able to:
| System | Where | What you use it for |
|---|---|---|
PODXX-SRV (via Guacamole) |
Your Guacamole connection list | Reading reference documents and recording your response |
| CyDeploy Community Edition | As installed by your instructor | Configuration/discovery review of your pod |
| Your pod artifact folder | C:\CyberLab\PodXX\SI-Artifacts\CyDeploy\ |
Reference documents, worksheet, and your response file |
Review your own pod only. Do not review another pod, the shared domain, the
domain controllers, or the management network.
C:\CyberLab\PodXX\SI-Artifacts\CyDeploy\.PXX_Observed_Conditions.txt. It lists the observations OBS-01OBS-05 you must classify.PXX_Configuration_Baseline.pdf — what ACS requiresPXX_Approved_Software_List.csv — what ACS has approvedPXX_Exception_Register.csv — what ACS has formally exceptedPXX_CyDeploy_Findings_Worksheet.docx. For every observation, record:
Finding, Expected, Approved Exception, orNeeds InvestigationStudentResponses\SI-M5-L2.json in Notepad. For each of the fiveclassification and justification. Then set analystcompleted to true.Ask, in this order:
ExpectedApproved ExceptionFindingNeeds InvestigationAn exception that is not written down does not exist. An expired exception is not
an exception.
| Evidence | File |
|---|---|
| Completed worksheet | PXX_CyDeploy_Findings_Worksheet.docx |
| Completed response file | StudentResponses\SI-M5-L2.json |
Every one of the five observations must have a classification and a
justification. A classification with no justification is not evidence and will
fail verification.
Verification is automatic. You do not run anything yourself, and you do not need
access to AWX.
SI-M5-L2.json response file.A reference document is missing.
The lab has not been fully seeded for your pod. Tell your instructor; do not
create the files yourself.
The exception register looks like it excuses everything.
Read it carefully: check the item, the approval, and the expiry date. It applies
to one specific item.
I think an observation is both a finding and an exception.
It can only be one. If a current, approved exception covers exactly that item,
it is an approved exception.
The tracker says an observation is classified incorrectly.
Your classification does not match the baseline. Re-read the relevant baseline
section for that observation and reconsider.
The tracker says a justification is required.
Your justification is missing or too short to be meaningful. State which
reference you used and why it supports your classification.
I cannot edit the JSON file.
Open it with Notepad, and keep the structure valid — quotation marks, commas,
and brackets must stay as they are.