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.
ACS IT Operations maintains a documented asset inventory for your area of
responsibility. An internal auditor found that the inventory has not been
validated against the real environment in over a year.
Your job is to use CyDeploy Community Edition to discover what is actually
operating inside your assigned pod, compare it against the documented
inventory, and report any asset that is running but is not documented.
You are not asked to fix anything in this lab. Discovery and documentation only.
By the end of this lab you will be able to:
CMMC context: asset identification underpins the SI practices — you cannot
protect, patch, or monitor a system that nobody knows exists.
10.51.<your pod number>.0/24).| System | Where | What you use it for |
|---|---|---|
PODXX-SRV (via Guacamole) |
Your Guacamole connection list | Reading lab documents and recording your response |
| CyDeploy Community Edition | As installed by your instructor | Discovering assets inside your pod |
| Your pod artifact folder | C:\CyberLab\PodXX\SI-Artifacts\CyDeploy\ |
Lab documents, worksheet, and your response file |
You may discover only your own pod.
You may not scan:
acs-p01.local) or the domain controllers,10.50.0.0/16 or 192.168.1.0/24.Scanning outside your pod is a lab-integrity violation, and the verifier will
fail your submission if the scope you record is broader than your pod.
C:\CyberLab\PodXX\SI-Artifacts\CyDeploy\.PXX_Discovery_Scenario.txt. This is your tasking from IT Operations.PXX_Expected_Asset_Inventory.csv. This is what ACS believes is inPXX_CyDeploy_Discovery_Worksheet.docx.StudentResponses\SI-M5-L1.json in Notepad and fill it in:
analyst — your student namediscovery_scope — the scope you actually used (must be your pod)undocumented_asset_identified — "yes" or "no"finding — name the undocumented asset and state the problemevidence — how you know: what CyDeploy showed and what the inventorycompleted — trueYour submission is complete when all of the following exist in
C:\CyberLab\PodXX\SI-Artifacts\CyDeploy\:
| Evidence | File |
|---|---|
| Completed worksheet | PXX_CyDeploy_Discovery_Worksheet.docx |
| Completed response file | StudentResponses\SI-M5-L1.json |
Your response file must contain a named finding, a scope limited to your pod,
and evidence that a reviewer can verify against the seeded inventory.
Verification is automatic. You do not run anything yourself, and you do not need
access to AWX.
SI-M5-L1.json response file.The CyDeploy folder is empty or missing.
The lab has not been seeded for your pod yet. Tell your instructor; do not create
the files yourself.
CyDeploy will not start.
Confirm with your instructor that it has been installed on the system you are
using. Do not download or install it yourself.
Discovery returns nothing.
Check that the scope you entered matches your pod's network
(10.51.<pod number>.0/24) and that you used your pod, not another.
Discovery seems to return systems from outside my pod.
Stop, do not record them, and tell your instructor immediately. Then re-run with
a scope limited to your pod.
I cannot edit the JSON file.
Open it with Notepad. Keep the quotation marks and commas exactly as they are —
if the file is not valid JSON, verification fails with "is not valid JSON".
The tracker says my scope is outside my assigned pod.
The discovery_scope value you recorded is broader than your pod. Correct it to
your pod only, and re-run discovery if your actual scan was too broad.
Nothing changed after I saved.
Verification runs on a schedule, not instantly. Wait for the next run before
assuming something is wrong.