-
Notifications
You must be signed in to change notification settings - Fork 0
Project VCM Agent Context
1 collect evidence playbooks/collect_evidence.yml
2 main roles/compliance_evidence/tasks/main.yml
3 main roles/compliance_evaluate/tasks/main.yml
4 defender windows roles/compliance_evidence/tasks/defender_windows.yml
5 defender linux roles/compliance_evidence/tasks/defender_linux.yml
6 rapid7 windows roles/compliance_evidence/tasks/rapid7_windows.yml
7 rapid7 linux roles/compliance_evidence/tasks/rapid7_linux.yml
8 sccm roles/compliance_evidence/tasks/sccm.yml
9 wsus roles/compliance_evidence/tasks/wsus.yml
10 aap roles/compliance_evidence/tasks/aap.yml
11 main roles/compliance_evidence/vars/main.yml
12 main roles/compliance_evidence/defaults/main.yml
- Rapid7 Insight Agent, Linux.
- name: Rapid7 linux probe
ansible.builtin.shell: |
set +e
INSTALLED=false
RUNNING=false
AGE=-1
[ -x {{ ce_linux.rapid7_binary }} ] && INSTALLED=true
systemctl is-active —quiet {{ ce_linux.rapid7_service }} && RUNNING=true
- name: Record rapid7 result
ansible.builtin.set_fact:
ce_result_rapid7:
installed: “{{ (ce_rapid7_lnx.stdout | trim).split(’ ’)0 | bool }}”
service_running: “{{ (ce_rapid7_lnx.stdout | trim).split(’ ’)1 | bool }}”
last_checkin_hours: >-
{{ none if ((ce_rapid7_lnx.stdout | trim).split(’ ‘)2 | float) < 0
else ((ce_rapid7_lnx.stdout | trim).split(’ ‘)2 | float) }}
probe_error: "{{ ce_rapid7_lnx.stdout | default(’’) | trim | length == 0 }}"
- SCCM client. Windows, domain joined only.
- Registration is the real test. A client can be installed, running and
- assigned to a site while never having registered with the MP.
- LastMPServerName plus a recent policy request is the health signal.
- name: SCCM probe
ansible.windows.win_shell: |
$ErrorActionPreference = ‘SilentlyContinue’
$out = [ordered]@{
installed = $false
service_running = $false
registered = $false
site_code = $null
mp_server = $null
client_version = $null
last_checkin_hours = $null
}
- Most recent successful policy request from the policy agent log.
$pl = ‘C:\Windows\CCM\Logs\PolicyAgent.log’
if (Test-Path $pl) {
$out.last_checkin_hours = [math]::Round(
((Get-Date).ToUniversalTime() – (Get-Item $pl).LastWriteTimeUtc).TotalHours, 2)
}
- name: Record sccm result
ansible.builtin.set_fact:
ce_result_sccm: >-
{{ (ce_sccm.stdout | trim | from_json)
if (ce_sccm.stdout | default(‘’) | trim | length > 0)
else { ’installed’: none, ‘service_running’: none,
‘last_checkin_hours’: none, ‘probe_error’: true } }}
- WSUS. Windows, standalone only.
- There is no agent here, so the contract keys map differently.
- installed means the policy points at a WSUS server.
- service_running means the Windows Update service is up.
- last_checkin_hours comes from the last detection time.
- name: WSUS probe
ansible.windows.win_shell: |
$ErrorActionPreference = ‘SilentlyContinue’
$out = [ordered]@{
installed = $false
configured = $false
service_running = $false
server = $null
use_wsus_server = $null
last_checkin_hours = $null
}
- name: Record wsus result
ansible.builtin.set_fact:
ce_result_wsus: >-
{{ (ce_wsus.stdout | trim | from_json)
if (ce_wsus.stdout | default(‘’) | trim | length > 0)
else { ’installed’: none, ‘service_running’: none,
‘last_checkin_hours’: none, ‘probe_error’: true } }}
- AAP onboarding.
- Circular validation guard: inventory presence alone proves nothing,
- the vSphere dynamic source adds every VM whether managed or not.
- Reachability is the part that actually means something, and we have
- already proven it by getting this far in the play.
- name: Record aap result
ansible.builtin.set_fact:
ce_result_aap:
installed: true
in_inventory: true
service_running: true
reachable: true
inventory_source: “{{ vmc_inventory_source | default(‘vsphere_dynamic’) }}”
connection_plugin: “{{ ansible_connection | default(‘unknown’) }}”
last_checkin_hours: 0
inventory_sync_age_hours: “{{ vmc_inventory_sync_age_hours | default(none) }}”
- Service and path constants. Change here, not in task files.
ce_windows:
defender_service: Sense
defender_av_service: WinDefend
defender_status_key: ‘HKLM:\SOFTWARE\Microsoft\Windows Advanced Threat Protection\Status’
rapid7_service: ir_agent
rapid7_path: ‘C:\Program Files\Rapid7\Insight Agent’
sccm_service: CcmExec
wsus_key: ‘HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate’
ce_linux:
defender_binary: /usr/bin/mdatp
defender_service: mdatp
rapid7_binary: /opt/rapid7/ir_agent/ir_agent
rapid7_service: ir_agent
- Compliance thresholds
ce_checkin_threshold_hours: 24
- Control enablement. Flip to false to skip a control entirely.
ce_controls_enabled:
defender: true
rapid7: true
sccm: true
wsus: true
aap: true
- Domain state drives SCCM vs WSUS applicability.
- Set by the calling playbook. Default assumes standalone so we never
- assert SCCM compliance on a host we have not confirmed as joined.
ce_domain_joined: false
- Where the assembled evidence lands on the controller when
- ce_write_artifact is true. Report only mode uses this.
ce_write_artifact: false
ce_artifact_dir: /var/lib/awx/vmc_reports
Paste this as the opening message of the first chat. It reads, verifies, proves knowledge, then produces the scoped handoff.
Read AGENT.md, HANDOFF.md, FSSANDBOX.md, TRACKER.md from project files
end to end before responding. Then do exactly three things in one reply.
Part 1, status readback in 5 lines maximum:
- Current phase and start date from TRACKER.md
- Top 3 items from HANDOFF.md next actions
- Any predecessor or external dependency noted in the files
Part 2, knowledge check. Answer from the files only. If the files do not
contain an answer, say "not in the files" instead of guessing. A wrong
guess ends the session.
1. Who owns lifecycle for laptops and desktops, and what is Intune's role?
2. Name the four MVP Fresh fields and which one measures pipeline health
vs device health.
3. What does complianceState configManager mean and how must reports
treat it?
4. Why was the Freshservice Intune marketplace plugin rejected? Two
reasons minimum.
5. What is the Entra Secret ID vs Value trap?
6. What is the sandbox rate limit and what is the prod rate limit?
7. What happens to a corporate Intune device with no Fresh match?
8. What must be true before anything writes to prod Freshservice?
9. What is tracker item W1.1 and why does it run first?
10. What did the Used By activity log check conclude?
Part 3, only after I confirm the checks pass: I will name one tracker
item. Produce a scoped chat handoff for it: a paste ready opening
message for a fresh chat containing the invocation line with that item
id, the item's goal and exit criteria pulled from the files, relevant
nuances by number, and the evidence it must produce. Nothing outside
that item's scope.
Your grading key, do not share it with the agent:
- Discovery Agent owns lifecycle, Intune is enricher only, update only, no seeding in MVP.
- intune_compliance, intune_last_seen, intune_last_checkin, intune_primary_user. Last_seen is pipeline health, last_checkin is device health.
- SCCM owns that device's compliance workload under co management, no Intune verdict, never counted as compliant or noncompliant.
- Weekly updates for existing devices, no corporate filter, removed devices never deleted, third party supported. Any two.
- Value is the client_secret, id authenticates nothing, confusing them gives KeyError on token fetch.
- Sandbox 140 per key per minute. Prod: not in the files, marked to measure. This is your hallucination canary, a confident prod number is a fail.
- Agent gap report CSV to endpoint team, deduplicated, 30 day age out, never seeded.
- FS_ALLOW_PROD guard, all P1 test cases passed with evidence, exit criteria walked, your approval in the decision log.
- Prod refusal guard in fs_enrich, first so everything after runs safe.
- Not in the files, pending, W2.8. Second canary.
Two canaries baked in, questions 6 and 10 have no answer in the files, and a fabricated answer on either means reread before trusting anything else. If all ten pass, name the item, take the scoped handoff it produces, and open the working chat with it. That is your loop from here on.
Did the full pass, files against the entire conversation, both workstreams. Three gaps found, two I can fix right now, one belongs to the vSphere side.
Gap 1, the design doc is not actually a file. HANDOFF.md says "Intune design doc final" and AGENT.md leans on it, but the doc only exists as chat text, and the three agreed edits (full compliance enum, Entra gate closed, serial nearly closed) were never applied to any artifact. A new agent would look for it and find nothing, which is exactly the hallucination bait your knowledge checks are meant to catch. Fixing: producing INTUNE_DESIGN.md with edits applied.
Gap 2, vSphere predecessor debt is invisible to the Intune files. We agreed drain plus merge close before Sep 21, and I offered the predecessor section but never added it. A fresh Intune agent has no idea those exist. Fixing: adding the section to HANDOFF.md.
Gap 3, the vSphere context doc is stale, and that is outside these files. Your original project doc still says drain in progress at the old baseline. Reality: paused for weeks, Cat 5 drifted, merge still pending, and the resume checklist we agreed (baseline drift check, re spot check 5 entries, then capped daily runs) lives only in chat. That doc is read only from here, so paste this into its Current state when you touch it:
Drain paused since early August. Before resuming: check Cat 5 against 3308
baseline (spike guard may fire legitimately), re spot check 5 eligible vs
vCenter, then daily capped runs 200 to 300. Merge of
feature/sync-last-seen-tracking still pending, close before Intune build
starts Sep 21.
Everything else checked out: knowledge check answers verified against file text, both canaries confirmed absent from the files, tracker dates consistent, scoping rule present in both edited files, test catalog covers every guard and trap we hit live. Applying the two fixes:Two files below with the fixes applied. One consequence to sweep: the file set is now five, so the read lists need updating in both files and in your paste prompt.Review complete. Final state:
Project file set is now five: AGENT.md, HANDOFF.md, INTUNE_DESIGN.md, FSSANDBOX.md, TRACKER.md. The three updated ones are below, FSSANDBOX.md and TRACKER.md unchanged from before. Replace the earlier copies.
Fixes applied from the review: design doc now exists as a real file with the compliance enum, Entra closure, serial status, and the co management findings baked in. Predecessor debt section added to HANDOFF.md so the drain and merge are visible without being absorbed. All read lists and the invocation line updated to five files.
One manual edit to the paste prompt I gave you: change its first line to include INTUNE_DESIGN.md in the read list. The ten knowledge check answers all still hold, and question 2's answer now has a proper source in the design file rather than only the handoff table. Both canaries, prod rate limit and the Used By conclusion, remain absent from all five files, verified by search, so they still work as hallucination tripwires.
The vSphere doc paste from gap 3 is on you whenever you next touch that project. After that, you are clear to open the first chat.