{"text":"Application audit on RESEARCH-ASSET-44de8cf55f1c805f recorded that an application requested repeated screen captures. The event references principal-17ee862a652063ef. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Security retest SEC-044385f0b4a6 covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Switch telemetry on PEOPLE-ASSET-2fae865ac519b354 recorded that an address mapping changed repeatedly on a local segment. The event references principal-cadf13732271e411. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Vpn audit on RESEARCH-ASSET-f104c6cff8b4f120 recorded that a remote-access VPN session was established. The event references principal-18bc30314e242812. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Kubernetes audit on FINANCE-ASSET-8c8a0667d1ab346c recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-8cde8f18db765ef8. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"File access audit on ENGINEERING-ASSET-9bb4a75d3491a9be recorded that a process opened a local credential-store file. The event references principal-f9c37bdee298aeea. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Key service audit on LEGAL-ASSET-c93c39a0bf6d5d2d recorded that a principal issued a burst of key-service decrypt requests. The event references principal-a9f8c5175e6aa291. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Change CHG-a1f2fe64c7b5 lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Mail flow logs on FINANCE-ASSET-05268a477e8094f0 recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-ab4f2f7ab1b6ae29. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Event service audit on ENGINEERING-ASSET-93dff18c1d7d23e9 recorded that an event log was cleared by a privileged request. The event references principal-32227ffe2b6b23ca. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Compute audit on PEOPLE-ASSET-fe0429fc4ead052f recorded that a principal launched multiple compute instances. The event references principal-4fe369a19d9b5bd1. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Systemd audit on PEOPLE-ASSET-e24082f3c52d3f39 recorded that a service unit file was changed and the unit reloaded. The event references principal-b49269ba3a97e459. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-a8138dad11c0 accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Egress flow logs on OPERATIONS-ASSET-2513c8d77423854c recorded that a workload opened an encrypted connection to an external service. The event references principal-ec2152640ea901f5. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Registry audit on PROCUREMENT-ASSET-76d816b7b04f4b8f recorded that a workload pulled a container image from a registry. The event references principal-12ce95b5667b0630. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Directory audit on COMMUNICATIONS-ASSET-014161d1ab75992f recorded that a principal requested directory replication data. The event references principal-06ff5e4392c8395e. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Dhcp telemetry on RESEARCH-ASSET-e4b53bee781b0891 recorded that a server issued DHCP offers on a monitored segment. The event references principal-7d24baa0336a4972. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"File audit on FINANCE-ASSET-2004b1d4a03fd309 recorded that a process rewrote multiple files into encrypted containers. The event references principal-9560a602e126689a. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Kubernetes audit on ENGINEERING-ASSET-893d9de1f805e218 recorded that a cluster admission policy was changed. The event references principal-63fff86ce57d7e9d. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Office audit on SALES-ASSET-bd4695abc7ff04ad recorded that a document macro launched a child interpreter. The event references principal-9bfaf02fa70a4f6b. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Repository audit on OPERATIONS-ASSET-d75290e6ed1a6d85 recorded that a repository collaborator received elevated permissions. The event references principal-b26cea051978a58c. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Policy audit on SUPPORT-ASSET-6952fff6cd8e7039 recorded that an audit policy was changed to collect fewer event categories. The event references principal-c6ab36fb929298bf. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Key service audit on PROCUREMENT-ASSET-97184c5c539ee822 recorded that a principal issued a burst of key-service decrypt requests. The event references principal-d47010910e744f5c. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Flow logs on FINANCE-ASSET-b04c464556b8fa8d recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-4fa1efc3a212390d. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Oauth audit on RESEARCH-ASSET-0631ea2256cf662a recorded that an application received consent for additional account scopes. The event references principal-8da4697a549d31b3. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-97759d66f964 before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Oauth audit on COMMUNICATIONS-ASSET-d085212f92517588 recorded that an application received consent for additional account scopes. The event references principal-410957c7717cf0fe. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"File audit on RESEARCH-ASSET-29f4cb3c7a29beaf recorded that access permissions were broadened on a directory tree. The event references principal-9b108c0888253ab1. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Dns control audit on LEGAL-ASSET-b16c2ea371640162 recorded that an authoritative DNS record was updated. The event references principal-162d081f9776c04e. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Application audit on PEOPLE-ASSET-16eca898293194f8 recorded that an application read clipboard contents repeatedly. The event references principal-9ece0c292d6cf355. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Module audit on ENGINEERING-ASSET-ef21d634c2b3a94b recorded that a process loaded a library from an application-local directory. The event references principal-47653e2725b4086f. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"File audit on PROCUREMENT-ASSET-5c83620233b8b110 recorded that a process deleted many files within a short interval. The event references principal-eb86b20544a85de9. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Ssh audit on PEOPLE-ASSET-97ff8f8fa97fd164 recorded that an SSH session opened and requested elevated command execution. The event references principal-60b1e96c2c9d3478. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Dns server audit on PEOPLE-ASSET-9dfdc0288f418b98 recorded that a client requested a DNS zone transfer. The event references principal-fb173264d38aac45. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-fbd45685b3f0 before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Identity audit on LEGAL-ASSET-943053d6267ac572 recorded that a service account established an interactive session. The event references principal-158c8b7f105115ea. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Cloud identity audit on SALES-ASSET-97a28d40051be12b recorded that a principal received a policy granting additional permissions. The event references principal-e45a694b7e0b8b49. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Identity audit on SUPPORT-ASSET-f9b39e12fc139ef0 recorded that an account registered a new MFA method. The event references principal-3c523bf81b3a031f. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Application audit on SALES-ASSET-a8b331f6bbbdf2ee recorded that a runtime configuration setting was updated. The event references principal-21cb8dcf748912e9. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Driver audit on LEGAL-ASSET-1d7f06f84da720a0 recorded that a kernel driver was loaded after a package installation. The event references principal-419a1d9d514f9429. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-72ec59f6786b specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Certificate audit on LEGAL-ASSET-028cc6c15478424c recorded that a service certificate was replaced. The event references principal-ab2a10d3b09a07d5. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Driver audit on FINANCE-ASSET-4d3885b7e2a2eaaa recorded that a kernel driver was loaded after a package installation. The event references principal-93dddd296bcd4a0a. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"File audit on LEGAL-ASSET-f437cecc468ccf1f recorded that access permissions were broadened on a directory tree. The event references principal-1d5f4386a802d873. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Egress flow logs on PEOPLE-ASSET-9176797d1eb78aff recorded that a workload opened an encrypted connection to an external service. The event references principal-eeab4c2bc996daf9. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Certificate audit on RESEARCH-ASSET-a52c58b217e48a75 recorded that a service certificate was replaced. The event references principal-8f17b08464430d9f. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Cloud control audit on PROCUREMENT-ASSET-bf71ebbd91fab3f3 recorded that a cloud logging destination was disabled. The event references principal-24b082eff9f1c2cb. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Api gateway logs on PROCUREMENT-ASSET-1c1b6a1c5f9b9bd8 recorded that a client issued a burst of API requests. The event references principal-257e72e6a629f939. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Repository audit on SUPPORT-ASSET-f2c722947f994337 recorded that a repository collaborator received elevated permissions. The event references principal-81983e01bdfb552d. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Ci audit on SALES-ASSET-58f9b0d2c10b53d7 recorded that a build pipeline definition gained a new execution step. The event references principal-db424878959459e6. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-ae23e4db0484, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Federation audit on COMMUNICATIONS-ASSET-866384484e84ef96 recorded that a tenant federation setting was updated. The event references principal-e2dd8e40c0e17294. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-3eff39a09fa7, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Driver audit on LEGAL-ASSET-1d7f06f84da720a0 recorded that a kernel driver was loaded after a package installation. The event references principal-419a1d9d514f9429. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Storage access logs on OPERATIONS-ASSET-4a7bbac68a963680 recorded that a principal downloaded many objects from a storage bucket. The event references principal-9881a91f6d808755. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Oauth audit on RESEARCH-ASSET-0631ea2256cf662a recorded that an application received consent for additional account scopes. The event references principal-8da4697a549d31b3. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"File audit on PEOPLE-ASSET-a99509e663c1444d recorded that a process rewrote multiple files into encrypted containers. The event references principal-dc7744cab585a5e1. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Kerberos audit on PROCUREMENT-ASSET-f07f0980cf620efa recorded that an account requested service tickets for multiple services. The event references principal-6dd83c14e2a9dd31. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Firewall audit on OPERATIONS-ASSET-f066243659fb5412 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-9b3165faa785f1a5. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Dhcp telemetry on FINANCE-ASSET-99d84bf5e5de071b recorded that a server issued DHCP offers on a monitored segment. The event references principal-e238480421ab2c07. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Cloud control audit on PROCUREMENT-ASSET-bf71ebbd91fab3f3 recorded that a cloud logging destination was disabled. The event references principal-24b082eff9f1c2cb. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Assessment SEC-3e4d9b00ae95 explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Winrm audit on COMMUNICATIONS-ASSET-2bb6a89a28755b1e recorded that a remote management session invoked a command on a managed host. The event references principal-2ae22aaef9849f17. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Share audit on PROCUREMENT-ASSET-d3ee6d1f094d6ce0 recorded that a new network file share was published. The event references principal-9978a814a123a526. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"File audit on PEOPLE-ASSET-2821cb52cece6fb9 recorded that a shell startup profile gained an additional command. The event references principal-6665fccc697a255b. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Security retest SEC-213f4b894287 covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Browser audit on SUPPORT-ASSET-089bd1e438aae68a recorded that a browser extension with page-reading permissions was installed. The event references principal-05dd057e76f4173e. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Flow logs on PROCUREMENT-ASSET-6efd3fd7c57f6ea6 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-2f79b909f0a96c76. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Mail and proxy logs on OPERATIONS-ASSET-7ac4ed112230cbe5 recorded that a user opened a URL delivered in an email message. The event references principal-b1bb74d41be20948. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Mfa audit on PROCUREMENT-ASSET-9ec036de13de448d recorded that multiple MFA challenges were issued during a short interval. The event references principal-906c50bf72cf0c69. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Assessment SEC-d2c9c51ac007 explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Cloud control audit on RESEARCH-ASSET-7f111a5abf79c08a recorded that a session deleted a group of cloud resources. The event references principal-e374d397f062ff2d. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Switch telemetry on LEGAL-ASSET-1643dbdebba2d78d recorded that an address mapping changed repeatedly on a local segment. The event references principal-c39fe907de3611c7. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Api gateway logs on ENGINEERING-ASSET-51721c37d612a2f5 recorded that a client issued a burst of API requests. The event references principal-b27ef27161423988. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Session audit on RESEARCH-ASSET-5cafc83fecebfc2d recorded that the same session token appeared from different client addresses. The event references principal-fe88f832c0c25c20. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Share audit on SALES-ASSET-af32e6af472026fd recorded that a new network file share was published. The event references principal-f1240dad3caae0d8. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Cloud control audit on ENGINEERING-ASSET-2f0ebfbab41474df recorded that a session deleted a group of cloud resources. The event references principal-eab0d8cb49ca354d. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-73ea70ba6d4d accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Proxy logs on FINANCE-ASSET-f9b86d6f6b974e8f recorded that a client transferred a large payload to an external storage endpoint. The event references principal-252b9a9159e9be98. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-91ccafe55630 before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Account audit on COMMUNICATIONS-ASSET-9a834b6edbe1b57f recorded that a local user account was created on a managed system. The event references principal-57644d2a7475e5ae. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Dhcp telemetry on COMMUNICATIONS-ASSET-a7af3c886d8ee570 recorded that a server issued DHCP offers on a monitored segment. The event references principal-aa2878e706226d96. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Driver audit on OPERATIONS-ASSET-16afbb03ee82c54d recorded that a kernel driver was loaded after a package installation. The event references principal-32362e7a45f17c8f. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-dc77a030325b match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Windows logon audit on OPERATIONS-ASSET-4a019c17c7542e6c recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-dd10cd046f3074f7. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Wmi audit on COMMUNICATIONS-ASSET-03aadd8a551fef8d recorded that a management request started a process through WMI. The event references principal-1c1aa32fcc8fde6b. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Registry audit on SALES-ASSET-2cd7195afaa340c4 recorded that a registry logon-start entry was created. The event references principal-4dafe2d9d91101fd. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Policy audit on COMMUNICATIONS-ASSET-6bd03c52fee36269 recorded that an audit policy was changed to collect fewer event categories. The event references principal-89ce4ef5b0451d62. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Cloud identity audit on PROCUREMENT-ASSET-ec7ad16199b37527 recorded that a principal received a policy granting additional permissions. The event references principal-8b968a5cde5474fa. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Mail flow logs on PEOPLE-ASSET-9ba2c53dc33b0530 recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-5b015560df1e299f. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Ci secret audit on PEOPLE-ASSET-50143023c0d694b1 recorded that a build job requested a protected pipeline secret. The event references principal-236f39206994ec5b. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Macos launch audit on OPERATIONS-ASSET-26bdf3f25161f2be recorded that a launch agent definition was installed in a user context. The event references principal-707a961a9c8924fd. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-5e747af4f14d covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Compute audit on OPERATIONS-ASSET-ac6d22bf5640da77 recorded that a principal launched multiple compute instances. The event references principal-dec83605ca771167. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"File audit on LEGAL-ASSET-f437cecc468ccf1f recorded that access permissions were broadened on a directory tree. The event references principal-1d5f4386a802d873. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Office audit on LEGAL-ASSET-7baa0b7a7bcbd13a recorded that a document macro launched a child interpreter. The event references principal-4d965a283abc96ce. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Flow logs on SUPPORT-ASSET-103a412104563dae recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-a1ca47883deef1d3. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Policy audit on PROCUREMENT-ASSET-f2878461512a2696 recorded that an audit policy was changed to collect fewer event categories. The event references principal-2bb61efdeda82dac. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Flow logs on OPERATIONS-ASSET-edf434a71b109006 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-16d324cd052a6682. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Office audit on ENGINEERING-ASSET-8b497889760890b7 recorded that a document macro launched a child interpreter. The event references principal-348623c716d723c6. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Mfa audit on SALES-ASSET-413206c0391aae90 recorded that multiple MFA challenges were issued during a short interval. The event references principal-13b992911a08e483. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Kubernetes audit on SUPPORT-ASSET-46e0923b16c1de93 recorded that a cluster admission policy was changed. The event references principal-eb0f85c559534d98. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-10730954a43f before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Kubernetes audit on ENGINEERING-ASSET-893d9de1f805e218 recorded that a cluster admission policy was changed. The event references principal-63fff86ce57d7e9d. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Pki audit on PEOPLE-ASSET-3dbf336f859282fe recorded that a principal requested a certificate using an authentication template. The event references principal-bc62db6b4c821f23. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Cloud control audit on SUPPORT-ASSET-f20f7641faecc324 recorded that a cloud logging destination was disabled. The event references principal-4d58eb61705c0ae8. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Code integrity audit on SUPPORT-ASSET-d243663dca87b63a recorded that an executable without a publisher signature started from a writable directory. The event references principal-ac7fc8d288d921e2. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Pki audit on OPERATIONS-ASSET-075517e7328277d9 recorded that a principal requested a certificate using an authentication template. The event references principal-c9b353c364fde4c3. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Federation audit on PROCUREMENT-ASSET-627d4b1e14d07688 recorded that a tenant federation setting was updated. The event references principal-be363e08050ad9ec. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Driver audit on SUPPORT-ASSET-19c2a39ea2af2cbe recorded that a kernel driver was loaded after a package installation. The event references principal-f5704bc0d4a6300d. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Agent audit on PEOPLE-ASSET-145b133cd9883db8 recorded that a privileged session changed endpoint monitoring settings. The event references principal-3cdfd17f049efdd9. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Mail and proxy logs on PROCUREMENT-ASSET-f73ebff8c2f46ccc recorded that a user opened a URL delivered in an email message. The event references principal-81190b386823c031. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-d01fa56be80f before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Firewall audit on LEGAL-ASSET-a8345e2e1a01ff48 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-74a2c9033c8d23b7. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Api gateway logs on OPERATIONS-ASSET-5d940a8c3c4b311c recorded that a client issued a burst of API requests. The event references principal-9965146148dbdc29. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Runtime audit on PEOPLE-ASSET-616ef8f8f0889aaf recorded that a process connected to the container runtime socket. The event references principal-685ce977f92924b1. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Storage audit on OPERATIONS-ASSET-07e77010a446667b recorded that a session deleted several storage snapshots. The event references principal-fc81340c87f20845. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Event service audit on PROCUREMENT-ASSET-1656ac96cf7e6b6f recorded that an event log was cleared by a privileged request. The event references principal-994f7078cfaa2558. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-4d88ef476f7b match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Mail audit on LEGAL-ASSET-131d8c518786695c recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-3bea6da72e330e1b. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"File access audit on LEGAL-ASSET-c0436d9a797b6aac recorded that a process opened a local credential-store file. The event references principal-8f957f68f520d591. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Smb audit on COMMUNICATIONS-ASSET-88088ffb8b08e158 recorded that a session enumerated a file share and read multiple files. The event references principal-82b755f6442bfd40. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Proxy logs on PEOPLE-ASSET-47b1cfa33ae643a0 recorded that a client transferred a large payload to an external storage endpoint. The event references principal-eefc70a315bcfb3b. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-57237ec208fa match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Storage audit on ENGINEERING-ASSET-b38bdd9cc61bbac2 recorded that an object-storage access policy was broadened. The event references principal-8585f4d7b4e61651. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Mail audit on FINANCE-ASSET-ea1b6c24422b456d recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-44026a910bd0b4c9. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-e8304a8f42c5 specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Runtime audit on LEGAL-ASSET-67b364f8c09b4aef recorded that a process connected to the container runtime socket. The event references principal-a26c56705eacce84. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Smb audit on RESEARCH-ASSET-130b1b37c48e2c18 recorded that a session enumerated a file share and read multiple files. The event references principal-143930e21a998c01. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"File access audit on FINANCE-ASSET-334508df57fe9f23 recorded that a process opened a local credential-store file. The event references principal-0966351ff7c24bff. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Network control audit on COMMUNICATIONS-ASSET-b93121e4b22b1a29 recorded that a cloud security group gained a broad ingress rule. The event references principal-8f16c182ac4bbc7f. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Gateway logs on LEGAL-ASSET-4deff653cf2694f9 recorded that a client established a long-lived encapsulated network session. The event references principal-76329b77e1b0e6b1. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Registry audit on SALES-ASSET-2cd7195afaa340c4 recorded that a registry logon-start entry was created. The event references principal-4dafe2d9d91101fd. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Registry audit on RESEARCH-ASSET-73e0cbd02049afd1 recorded that a workload pulled a container image from a registry. The event references principal-34d7877cf1ae898f. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Database audit on COMMUNICATIONS-ASSET-4fefa2aaca8d930a recorded that a session changed a database table definition. The event references principal-257c7d24c9971d35. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-42eab180e7df match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Federation audit on PROCUREMENT-ASSET-627d4b1e14d07688 recorded that a tenant federation setting was updated. The event references principal-be363e08050ad9ec. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Package registry audit on LEGAL-ASSET-904ec76dbb996774 recorded that a principal published a new package version. The event references principal-3920a37e9b8e2b42. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-ebff72a828ec accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Cloud control audit on PROCUREMENT-ASSET-1ca061884feb0239 recorded that a session deleted a group of cloud resources. The event references principal-bde2c278c233490d. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-5f3dacbc2df2 explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Kubernetes audit on ENGINEERING-ASSET-03ff797dc0608058 recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-84d60009e20971fc. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-32b0ed0d6d7c accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Database audit on PEOPLE-ASSET-aeb9e932203e4086 recorded that a session changed a database table definition. The event references principal-4c123413716680f3. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Api gateway logs on RESEARCH-ASSET-43a3327a7670f557 recorded that a client issued a burst of API requests. The event references principal-19db88a740f22c57. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Vpn audit on ENGINEERING-ASSET-10805fb79cd039f2 recorded that a remote-access VPN session was established. The event references principal-ee63fc11c18dbead. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Process access audit on SUPPORT-ASSET-a8d87f27cfdb843f recorded that a process requested read access to another process memory space. The event references principal-8eabe5478e5a2271. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Ci secret audit on PEOPLE-ASSET-50143023c0d694b1 recorded that a build job requested a protected pipeline secret. The event references principal-236f39206994ec5b. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Mail flow logs on PROCUREMENT-ASSET-992b1e99dffe114d recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-ffd659ab57383ff2. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Cloud control audit on PEOPLE-ASSET-12878cc06ce2eeff recorded that resources were created in a region with little prior activity. The event references principal-504d0a8a24feb6ee. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Package registry audit on ENGINEERING-ASSET-468e2f1736323150 recorded that a principal published a new package version. The event references principal-cbfd72c0328f2633. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Kubernetes audit on FINANCE-ASSET-8c8a0667d1ab346c recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-8cde8f18db765ef8. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Switch telemetry on PROCUREMENT-ASSET-c13f623edc6be72c recorded that an address mapping changed repeatedly on a local segment. The event references principal-464589d30bf27aee. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Package registry audit on PROCUREMENT-ASSET-742ad97982b567e2 recorded that a principal published a new package version. The event references principal-5921bb600425987a. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-66cc8f2d0c9f match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Systemd audit on RESEARCH-ASSET-eeb116f31cbce82f recorded that a service unit file was changed and the unit reloaded. The event references principal-f39102d395b571c9. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"File access audit on COMMUNICATIONS-ASSET-5eb665c77394105b recorded that a process opened a local credential-store file. The event references principal-a9229a1030eb8134. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Backup audit on FINANCE-ASSET-7d6385ebfb9a8a83 recorded that a backup retention policy was shortened. The event references principal-87f1c31296aed897. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Kerberos audit on SUPPORT-ASSET-cee89b8c79f8f807 recorded that an account requested service tickets for multiple services. The event references principal-ba01468b28096ded. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Identity audit on SUPPORT-ASSET-f9b39e12fc139ef0 recorded that an account registered a new MFA method. The event references principal-3c523bf81b3a031f. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Event service audit on FINANCE-ASSET-9334935a696bff2c recorded that an event log was cleared by a privileged request. The event references principal-f4f6381e73c7f8ed. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Mail audit on SUPPORT-ASSET-af2380a8ab001950 recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-d2de6ff979b628f2. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Application audit on RESEARCH-ASSET-11f390ae672643c2 recorded that a runtime configuration setting was updated. The event references principal-1a691de3cb24648f. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Cloud identity audit on PROCUREMENT-ASSET-cb3bd3ac326cf3b2 recorded that a principal assumed a role in another account. The event references principal-131a52eaecf4978f. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Proxy logs on LEGAL-ASSET-11a1797ca70316c7 recorded that a client transferred a large payload to an external storage endpoint. The event references principal-0b83b39a8d8a6fb4. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Identity audit on LEGAL-ASSET-f678141e2b084a32 recorded that an account registered a new MFA method. The event references principal-500c71ca31b016a9. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Module audit on OPERATIONS-ASSET-da72125783fc7146 recorded that a process loaded a library from an application-local directory. The event references principal-88a37cd2d0222e86. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Change CHG-6e0282c5eaed lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Switch telemetry on ENGINEERING-ASSET-271d6935661ca5b6 recorded that an address mapping changed repeatedly on a local segment. The event references principal-2aa672d045fc50f4. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Cloud identity audit on RESEARCH-ASSET-8d54a31e0957dabb recorded that a principal assumed a role in another account. The event references principal-8a3eb5c757201646. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Compute audit on FINANCE-ASSET-428507c521e75c88 recorded that a principal launched multiple compute instances. The event references principal-a167ad7ce21b7604. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"File audit on ENGINEERING-ASSET-b0203944931a2946 recorded that a process compressed files from several directories into an archive. The event references principal-c59c85332aba5a32. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Federation audit on FINANCE-ASSET-834ce73eb8e2d5f1 recorded that a tenant federation setting was updated. The event references principal-b4c9940f6c199e33. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-d7bed0598eb7 explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Systemd audit on LEGAL-ASSET-1602066d8a3d5246 recorded that a service unit file was changed and the unit reloaded. The event references principal-cdc1cfc697d46ed4. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"File audit on COMMUNICATIONS-ASSET-20dd539a3853169a recorded that a shell startup profile gained an additional command. The event references principal-c281969fbd0779dd. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Api gateway logs on PEOPLE-ASSET-010de515bde4832b recorded that a client issued a burst of API requests. The event references principal-828fabb7c52c8ecb. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Process audit on COMMUNICATIONS-ASSET-32e7de18e8d35e66 recorded that a Python interpreter loaded a script and contacted a service. The event references principal-2424b5e4e4370c09. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-d769bb21c3af specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Browser audit on FINANCE-ASSET-5beff27234a79da1 recorded that a browser extension with page-reading permissions was installed. The event references principal-f62be1e2c47a255f. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Ssh audit on ENGINEERING-ASSET-3a8203b9b7564af2 recorded that an SSH session opened and requested elevated command execution. The event references principal-f927bd6e5e00e3e2. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Backup audit on COMMUNICATIONS-ASSET-34bf9b07e39c1f16 recorded that a backup retention policy was shortened. The event references principal-e0e79be492923c4a. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Identity audit on OPERATIONS-ASSET-0bbb0193ab08eb6e recorded that a service account established an interactive session. The event references principal-de6a7bc5c123923c. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Compute audit on ENGINEERING-ASSET-67df6013e7bda695 recorded that a principal launched multiple compute instances. The event references principal-d74238a9b43b1893. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Registry audit on ENGINEERING-ASSET-3288f3a3a57d4d49 recorded that a registry logon-start entry was created. The event references principal-ab71b58d6c6b1b8b. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Smb audit on PROCUREMENT-ASSET-663a220061cd4095 recorded that a session enumerated a file share and read multiple files. The event references principal-ae5de00ea82776e7. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Change CHG-c00c3a42f57d lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Database audit on SALES-ASSET-19142cf000a582b0 recorded that a session read several tables and exported the query result. The event references principal-5991e381a26e4376. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Network control audit on COMMUNICATIONS-ASSET-b93121e4b22b1a29 recorded that a cloud security group gained a broad ingress rule. The event references principal-8f16c182ac4bbc7f. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-63999d40baae, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Process audit on LEGAL-ASSET-ffdcc64fc856fa3d recorded that a JavaScript interpreter executed a local script. The event references principal-a45f3b91beb56205. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Federation audit on PROCUREMENT-ASSET-627d4b1e14d07688 recorded that a tenant federation setting was updated. The event references principal-be363e08050ad9ec. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-cc8678bd92a7, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Ci secret audit on PEOPLE-ASSET-50143023c0d694b1 recorded that a build job requested a protected pipeline secret. The event references principal-236f39206994ec5b. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Macos launch audit on COMMUNICATIONS-ASSET-a6af7f5427b7cdc8 recorded that a launch agent definition was installed in a user context. The event references principal-1aeb8103bbf51c1f. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Kerberos audit on COMMUNICATIONS-ASSET-d9b65f7833a03be8 recorded that an account requested service tickets for multiple services. The event references principal-bce81f4ae551beca. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Systemd audit on SALES-ASSET-4e41129f633ac17f recorded that a service unit file was changed and the unit reloaded. The event references principal-6e1812150b898dbc. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Identity audit on PROCUREMENT-ASSET-595810a122b584e8 recorded that a service account established an interactive session. The event references principal-786fe31fade4e850. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Browser audit on COMMUNICATIONS-ASSET-242d23ba4ad50b88 recorded that a browser extension with page-reading permissions was installed. The event references principal-c4eaf539de0f6aa8. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-7037588cf3e7 accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Egress flow logs on SUPPORT-ASSET-ff3badb46e903585 recorded that a workload opened an encrypted connection to an external service. The event references principal-ef7dbc8f1e7b6a52. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-8e39f3f1559f match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Macos launch audit on PROCUREMENT-ASSET-cefeabfcdbb75ff5 recorded that a launch agent definition was installed in a user context. The event references principal-61b165b4264637cc. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Script audit on PROCUREMENT-ASSET-d3383e3f3b9c4acb recorded that a script interpreter decoded an encoded argument before execution. The event references principal-b7570e0e965cd679. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Cloud control audit on RESEARCH-ASSET-7f111a5abf79c08a recorded that a session deleted a group of cloud resources. The event references principal-e374d397f062ff2d. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-9a9b7d687acd before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Share audit on PROCUREMENT-ASSET-d3ee6d1f094d6ce0 recorded that a new network file share was published. The event references principal-9978a814a123a526. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-cf1c5d72bf49 match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Switch telemetry on SUPPORT-ASSET-8a0f455136f22cce recorded that an address mapping changed repeatedly on a local segment. The event references principal-598fd0cdb7a2c2dd. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Task scheduler audit on PEOPLE-ASSET-967b5df7e748b2ff recorded that a scheduled task was registered to execute a program at logon. The event references principal-80092436d4633e85. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Runtime audit on PEOPLE-ASSET-616ef8f8f0889aaf recorded that a process connected to the container runtime socket. The event references principal-685ce977f92924b1. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Driver audit on SUPPORT-ASSET-19c2a39ea2af2cbe recorded that a kernel driver was loaded after a package installation. The event references principal-f5704bc0d4a6300d. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Function audit on COMMUNICATIONS-ASSET-6eba6dd15491bb00 recorded that a serverless function package and execution settings were updated. The event references principal-a52d85256a55e315. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-6020a477f6fd, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Cloud identity audit on FINANCE-ASSET-44723c4a98b3d8ba recorded that a principal received a policy granting additional permissions. The event references principal-ddbfe461888a8cb6. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"File access audit on COMMUNICATIONS-ASSET-5eb665c77394105b recorded that a process opened a local credential-store file. The event references principal-a9229a1030eb8134. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Dns control audit on SUPPORT-ASSET-daac2768071affbb recorded that an authoritative DNS record was updated. The event references principal-004b930761f504d4. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Dns server audit on OPERATIONS-ASSET-77c8f7df02d0b548 recorded that a client requested a DNS zone transfer. The event references principal-de675342a884898f. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Database audit on RESEARCH-ASSET-0df9b1ba7848d017 recorded that a session read several tables and exported the query result. The event references principal-78007df53b70739e. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Flow logs on SUPPORT-ASSET-103a412104563dae recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-a1ca47883deef1d3. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Kubernetes audit on PROCUREMENT-ASSET-fa28de9adbfdddd4 recorded that a pod was created with privileged execution enabled. The event references principal-c0583fecec986fcd. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Secret manager audit on LEGAL-ASSET-473919a6141fb4d1 recorded that a workload read several secret versions. The event references principal-be429b8818a2a6bf. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Agent audit on SUPPORT-ASSET-9325bde68edaa545 recorded that a privileged session changed endpoint monitoring settings. The event references principal-1641f4bad60d9f93. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-261579b999e9 explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Cloud control audit on FINANCE-ASSET-b563459bb8af8f48 recorded that a session deleted a group of cloud resources. The event references principal-a8340a0f60620156. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Dhcp telemetry on SALES-ASSET-b9c8816924ddc5c0 recorded that a server issued DHCP offers on a monitored segment. The event references principal-c2f4772a3b098c6c. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Key service audit on OPERATIONS-ASSET-a2b77b051a5e88ca recorded that a principal issued a burst of key-service decrypt requests. The event references principal-2d26323a698b32c1. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Driver audit on PEOPLE-ASSET-9e9f7519775a6002 recorded that a kernel driver was loaded after a package installation. The event references principal-4bafb24bfe647837. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Browser audit on FINANCE-ASSET-5beff27234a79da1 recorded that a browser extension with page-reading permissions was installed. The event references principal-f62be1e2c47a255f. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-a02b248736d8 specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Ssh audit on FINANCE-ASSET-370d0df1776daaea recorded that an SSH session opened and requested elevated command execution. The event references principal-d8496f14d2489876. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Agent audit on LEGAL-ASSET-6d17adf81f6fe3af recorded that a privileged session changed endpoint monitoring settings. The event references principal-f72780533376e28a. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Assessment SEC-621e843eee55 explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Storage audit on PEOPLE-ASSET-4b18ae09e42fe01b recorded that an object-storage access policy was broadened. The event references principal-7721904d8c389cbb. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Kubernetes audit on SALES-ASSET-0cbf08d6604881c3 recorded that a workload mounted a directory from its host filesystem. The event references principal-df9957e225592b1d. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-cbce8a8d5c88, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Kubernetes audit on SUPPORT-ASSET-99bd1381f9f84168 recorded that a pod was created with privileged execution enabled. The event references principal-4de29bd2a93d9674. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Cloud identity audit on PROCUREMENT-ASSET-ec7ad16199b37527 recorded that a principal received a policy granting additional permissions. The event references principal-8b968a5cde5474fa. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-d1451a5b8b62 match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Group audit on ENGINEERING-ASSET-d30b74960b951b72 recorded that an account was added to a privileged local group. The event references principal-81526d7aed4e1797. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Cloud control audit on SALES-ASSET-5ed8420ac6bfabb9 recorded that a session deleted a group of cloud resources. The event references principal-e108fb64fd38558b. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Service audit on SUPPORT-ASSET-2eb791dfb1c8878d recorded that a new automatically started service was registered. The event references principal-7742e70843824b66. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Backup audit on ENGINEERING-ASSET-e13f2ff83c899d5b recorded that a backup retention policy was shortened. The event references principal-31afc311e47df634. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Api gateway logs on SALES-ASSET-67b00a7811823c9c recorded that a client issued a burst of API requests. The event references principal-0a02b6edf23f48b5. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Identity audit on FINANCE-ASSET-8c4f9dd18c643b5e recorded that repeated failed sign-ins were recorded for an account. The event references principal-e15b307c4e5bf156. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Account audit on RESEARCH-ASSET-a444b46456cd6186 recorded that a local user account was created on a managed system. The event references principal-dd1721a44a27272f. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Dns server audit on ENGINEERING-ASSET-aec07c525ec55aac recorded that a client requested a DNS zone transfer. The event references principal-4c0d05a21a35e460. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Registry audit on SUPPORT-ASSET-3b0593850dd40f7b recorded that a registry logon-start entry was created. The event references principal-d3ff9c757ce4b24b. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Change CHG-9dafe0e0a6a2 lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Database audit on FINANCE-ASSET-f03ba1a6a369cf03 recorded that a session read several tables and exported the query result. The event references principal-f892103a2793bbab. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Firewall audit on PROCUREMENT-ASSET-2bed3490436bbbc8 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-90a45122531200f3. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Dns server audit on SALES-ASSET-76b84b3e5488545e recorded that a client requested a DNS zone transfer. The event references principal-2d34f2bcf00115a7. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Directory audit on FINANCE-ASSET-4f2fe0486abb5c95 recorded that a principal requested directory replication data. The event references principal-b40239cccc5bf96a. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Identity audit on SALES-ASSET-17bd921cea441a1f recorded that repeated failed sign-ins were recorded for an account. The event references principal-d02e40aae87e9ff0. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-f3a081c12b89, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Smb audit on RESEARCH-ASSET-130b1b37c48e2c18 recorded that a session enumerated a file share and read multiple files. The event references principal-143930e21a998c01. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Process audit on RESEARCH-ASSET-ff9cda8159f26be2 recorded that a remote-support application started an interactive session. The event references principal-c2840b0826e54ab4. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Script audit on COMMUNICATIONS-ASSET-ad52eab51d5bfbe3 recorded that a script interpreter decoded an encoded argument before execution. The event references principal-b20c6bb2ef5361bb. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Identity audit on RESEARCH-ASSET-6952971d9edc688b recorded that an account registered a new MFA method. The event references principal-b16ea02f54cbbb97. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Event service audit on OPERATIONS-ASSET-6bb0ff67f6f8dbd2 recorded that an event log was cleared by a privileged request. The event references principal-1c69ef2988f5b8db. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Ci audit on FINANCE-ASSET-5cdbdad4be0dcfbd recorded that a build pipeline definition gained a new execution step. The event references principal-248c78edaf5546c1. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Assessment SEC-8cad85d31514 explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Service audit on OPERATIONS-ASSET-fd16a6acf8f54a9a recorded that a new automatically started service was registered. The event references principal-c9af46ed7e55064b. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Database audit on OPERATIONS-ASSET-dec2bfd2d0808b67 recorded that a session changed a database table definition. The event references principal-0583f5a376c3e442. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-924c5ab39967, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Module audit on RESEARCH-ASSET-49e502fa5df5f407 recorded that a process loaded a library from an application-local directory. The event references principal-52065da876a99294. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Mail audit on SALES-ASSET-1d2f1acd8ca606b9 recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-eaa00c222951727e. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Systemd audit on OPERATIONS-ASSET-42dd1f251b2cefd5 recorded that a service unit file was changed and the unit reloaded. The event references principal-27edc61f63f1f31a. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"File audit on PROCUREMENT-ASSET-f66c7d2cd9a00208 recorded that a process compressed files from several directories into an archive. The event references principal-1608ac7a92b15a7f. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"File audit on COMMUNICATIONS-ASSET-4e97ae367849b7ff recorded that a process deleted many files within a short interval. The event references principal-0d2d1e13b6f37e28. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"File audit on SALES-ASSET-a4a69365dce2152a recorded that a shell startup profile gained an additional command. The event references principal-3637027719cb9240. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Certificate audit on SUPPORT-ASSET-bf2e59d8cf05d409 recorded that a service certificate was replaced. The event references principal-3f10d0f128334232. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-e71c4559849d explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Winrm audit on SUPPORT-ASSET-635c3348db734709 recorded that a remote management session invoked a command on a managed host. The event references principal-f79466b09a2bb0fa. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Kerberos audit on OPERATIONS-ASSET-15b32c4f5f91cc11 recorded that an account requested service tickets for multiple services. The event references principal-86eb3dff1abf1690. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Change CHG-746056774c9e lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Application audit on SALES-ASSET-a8b331f6bbbdf2ee recorded that a runtime configuration setting was updated. The event references principal-21cb8dcf748912e9. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Kubernetes audit on LEGAL-ASSET-d5c1c420f1077ded recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-1d6426e1ff1f69c4. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-28b19d5ecaae match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"File audit on LEGAL-ASSET-f437cecc468ccf1f recorded that access permissions were broadened on a directory tree. The event references principal-1d5f4386a802d873. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-5a75877ec45e specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Oauth audit on RESEARCH-ASSET-0631ea2256cf662a recorded that an application received consent for additional account scopes. The event references principal-8da4697a549d31b3. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Cloud control audit on RESEARCH-ASSET-7f111a5abf79c08a recorded that a session deleted a group of cloud resources. The event references principal-e374d397f062ff2d. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Registry audit on PEOPLE-ASSET-493d3bd95ab44b29 recorded that a registry logon-start entry was created. The event references principal-b4c380fe3bd5d692. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Dhcp telemetry on OPERATIONS-ASSET-495d89e0df4422f6 recorded that a server issued DHCP offers on a monitored segment. The event references principal-ad2763e8b3d1fe71. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Gateway logs on RESEARCH-ASSET-6dcd3c5959922161 recorded that a client established a long-lived encapsulated network session. The event references principal-d901ab75b47ec726. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Flow logs on RESEARCH-ASSET-6a2a326a382bb0b4 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-56d66c0e0a2c4463. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Session audit on PROCUREMENT-ASSET-375b33e301ac9b62 recorded that the same session token appeared from different client addresses. The event references principal-c5f1efc48ec3f681. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Service audit on LEGAL-ASSET-c576aa1679d54c28 recorded that a new automatically started service was registered. The event references principal-7b1165f4385ce850. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Ci audit on SUPPORT-ASSET-be888d94d309deab recorded that a build pipeline definition gained a new execution step. The event references principal-f55be257f884a1b4. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-7ea6fba7e92a, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Kubernetes audit on OPERATIONS-ASSET-e9cb557fa33c100a recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-d1c39d3b8db93b55. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Flow logs on PEOPLE-ASSET-747d1cebe72c1281 recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-d7e614d288290a88. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-ed1a60c54546 match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"File access audit on RESEARCH-ASSET-41c0744f3eec824f recorded that a process opened a local credential-store file. The event references principal-22db2b4742c4cf72. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Assessment SEC-d314e48c0865 explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Mail flow logs on SALES-ASSET-40ddb7fd75836262 recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-4279d4843faab477. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Repository audit on FINANCE-ASSET-107bba51318f26e9 recorded that a user cloned several source repositories. The event references principal-f147d2a9dbf7d7a7. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-0ad2f70d6ba6 before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Process access audit on PROCUREMENT-ASSET-a371e419fb9da077 recorded that a process requested read access to another process memory space. The event references principal-47b9eca6b126bee7. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Process audit on SALES-ASSET-796c322bf9ce4051 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-eb12aa9934f163d5. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Cloud control audit on SALES-ASSET-bfb02fef7d44a1a0 recorded that a cloud logging destination was disabled. The event references principal-cabdd3811f019647. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Database audit on FINANCE-ASSET-7b5f1daa45ffd071 recorded that a session changed a database table definition. The event references principal-eec005bb1596cf1c. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Application audit on SUPPORT-ASSET-1e6a7efeb4ea574b recorded that a runtime configuration setting was updated. The event references principal-8bffad7489ed2f67. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"File audit on PEOPLE-ASSET-a99509e663c1444d recorded that a process rewrote multiple files into encrypted containers. The event references principal-dc7744cab585a5e1. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Kubernetes audit on OPERATIONS-ASSET-e5571d0159c5e55b recorded that a pod was created with privileged execution enabled. The event references principal-4016297e67e67765. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-8d29f4726b22 match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Cloud control audit on RESEARCH-ASSET-2cbe7527ba09f822 recorded that resources were created in a region with little prior activity. The event references principal-3490db46f4cacc07. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-b1257e937bb3 match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Registry audit on ENGINEERING-ASSET-bd489c9ae7fbc817 recorded that a workload pulled a container image from a registry. The event references principal-95061e15f3e7bbec. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Account audit on OPERATIONS-ASSET-ad56fc4183b7ca9d recorded that a local user account was created on a managed system. The event references principal-fe2941e164dbf1c4. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-37fdbbbb1f79 match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Runtime audit on LEGAL-ASSET-67b364f8c09b4aef recorded that a process connected to the container runtime socket. The event references principal-a26c56705eacce84. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-6332c883839f specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Session audit on SUPPORT-ASSET-39c9a292833723e5 recorded that the same session token appeared from different client addresses. The event references principal-a5ec7d156048f10f. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-cede59290fc3, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Task scheduler audit on OPERATIONS-ASSET-0c0ccf4949e6876b recorded that a scheduled task was registered to execute a program at logon. The event references principal-6b1b6724d1e28e1c. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Module audit on SUPPORT-ASSET-75579d877216839e recorded that a process loaded a library from an application-local directory. The event references principal-bf9534edb641c536. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Event service audit on COMMUNICATIONS-ASSET-a0753c1183185be8 recorded that an event log was cleared by a privileged request. The event references principal-3da9da5b32a84636. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Share audit on ENGINEERING-ASSET-15ac20dc277a74c4 recorded that a new network file share was published. The event references principal-33c52b08167e103b. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-0abe726cfb4b explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Secret manager audit on PEOPLE-ASSET-406b99330a23361c recorded that a workload read several secret versions. The event references principal-c3699eaad53ba8ba. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Ssh audit on SALES-ASSET-95483443a44dd70e recorded that an SSH session opened and requested elevated command execution. The event references principal-ee7405179574875a. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Account audit on LEGAL-ASSET-00d4a961cd35ae5d recorded that a local user account was created on a managed system. The event references principal-ffacf4516ce71040. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Smb audit on ENGINEERING-ASSET-167b039744d858de recorded that a session enumerated a file share and read multiple files. The event references principal-dae2d90d16568727. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Configuration audit on COMMUNICATIONS-ASSET-6d0a4b6d77bc51b5 recorded that a client proxy setting was changed. The event references principal-096d695d5dfbc71f. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-08b404b8e440 covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Pki audit on OPERATIONS-ASSET-075517e7328277d9 recorded that a principal requested a certificate using an authentication template. The event references principal-c9b353c364fde4c3. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Database audit on ENGINEERING-ASSET-5b5cb77077baa64c recorded that a session changed a database table definition. The event references principal-6bfe365bf3961695. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Runtime audit on ENGINEERING-ASSET-275c1751b3b56ff6 recorded that a process connected to the container runtime socket. The event references principal-560134bf0a39e092. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Browser audit on FINANCE-ASSET-5beff27234a79da1 recorded that a browser extension with page-reading permissions was installed. The event references principal-f62be1e2c47a255f. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"File audit on COMMUNICATIONS-ASSET-4e97ae367849b7ff recorded that a process deleted many files within a short interval. The event references principal-0d2d1e13b6f37e28. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Service audit on ENGINEERING-ASSET-ef233e13b4aa7209 recorded that a new automatically started service was registered. The event references principal-aa6e053019f9dc60. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Resolver logs on SALES-ASSET-17cdfcbdaddd4989 recorded that a client requested many long, high-entropy DNS labels. The event references principal-fddd379e6737bcc0. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-b2e64229228f specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Function audit on SUPPORT-ASSET-639b47faa57b7d52 recorded that a serverless function package and execution settings were updated. The event references principal-142321e2377f77dd. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Change CHG-1c703da20b30 lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Identity audit on OPERATIONS-ASSET-bc3d71283010bd0f recorded that an account password was reset through a recovery workflow. The event references principal-65a355a045f94503. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-643745179126 explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Identity audit on SUPPORT-ASSET-9a791522c1b9c744 recorded that an account password was reset through a recovery workflow. The event references principal-bd3f8b10beb2211f. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Process audit on OPERATIONS-ASSET-495b246de141f994 recorded that a Python interpreter loaded a script and contacted a service. The event references principal-3264c9e681183a21. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-4826e26a0aa9 match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Repository audit on ENGINEERING-ASSET-501895f2c603da6f recorded that a user cloned several source repositories. The event references principal-08a3df240a2c2acb. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-c02e94fec34e match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Winrm audit on SALES-ASSET-53a0ec06a529813d recorded that a remote management session invoked a command on a managed host. The event references principal-d315b25d4a3677cf. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Identity audit on PEOPLE-ASSET-d81992a54d0e0cd4 recorded that a service account established an interactive session. The event references principal-0bc399328dfcae48. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Package registry audit on SALES-ASSET-70769ae6745858de recorded that a principal published a new package version. The event references principal-06efaa74600c0f91. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Browser audit on PROCUREMENT-ASSET-50d8010904173019 recorded that a browser extension with page-reading permissions was installed. The event references principal-8e2e0553f52a5216. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-871f21de7799 accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Dns server audit on COMMUNICATIONS-ASSET-3ba853c8b87dee93 recorded that a client requested a DNS zone transfer. The event references principal-fbb1839d1793e373. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"File audit on COMMUNICATIONS-ASSET-23cdf3c51f4342c4 recorded that access permissions were broadened on a directory tree. The event references principal-fb51510da2f10fbb. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Cron audit on SUPPORT-ASSET-0f143a13847207ad recorded that a recurring job definition was added to the system schedule. The event references principal-940a8e24d3cd68aa. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Function audit on PEOPLE-ASSET-7a184783e26cf4b6 recorded that a serverless function package and execution settings were updated. The event references principal-20e08b043fa3eb3a. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Office audit on PROCUREMENT-ASSET-9c9a63eb958fdaa6 recorded that a document macro launched a child interpreter. The event references principal-40d050ba88a97331. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Assessment SEC-0268e6e88bdc explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Ssh audit on SUPPORT-ASSET-842f8e08ea10f95b recorded that an SSH session opened and requested elevated command execution. The event references principal-3779cc64299d1a95. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Resolver logs on ENGINEERING-ASSET-02301b26ed9cf1c5 recorded that a client requested many long, high-entropy DNS labels. The event references principal-8e3fc22d3aadc906. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Script audit on ENGINEERING-ASSET-e2ddc97a2c3f555e recorded that a script interpreter decoded an encoded argument before execution. The event references principal-f5db620bfae68583. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"File audit on ENGINEERING-ASSET-1a60a1286916ad01 recorded that access permissions were broadened on a directory tree. The event references principal-1a1a48bb1e529fb0. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-071b4999b07f match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Windows logon audit on OPERATIONS-ASSET-4a019c17c7542e6c recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-dd10cd046f3074f7. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Dns server audit on FINANCE-ASSET-b5978ac018c6f58c recorded that a client requested a DNS zone transfer. The event references principal-eef8de7d2245f076. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Vpn audit on COMMUNICATIONS-ASSET-cf88b5e111fdd1c4 recorded that a remote-access VPN session was established. The event references principal-323dccf79a1a961c. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Process audit on SALES-ASSET-d7499e681a58affc recorded that a JavaScript interpreter executed a local script. The event references principal-ce0d21f659b72ac8. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Assessment SEC-978b0f77a1db explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Browser audit on SALES-ASSET-2c13db88f9fe11a1 recorded that a browser extension with page-reading permissions was installed. The event references principal-dfbfeb6ce6f75d60. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Assessment SEC-9586e2c5f7f6 explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Browser audit on ENGINEERING-ASSET-f6edb397c93f1bb4 recorded that a browser extension with page-reading permissions was installed. The event references principal-bf7a3feca21483cd. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Change CHG-67a0264d055b lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Application audit on SUPPORT-ASSET-1e6a7efeb4ea574b recorded that a runtime configuration setting was updated. The event references principal-8bffad7489ed2f67. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Ci audit on FINANCE-ASSET-5cdbdad4be0dcfbd recorded that a build pipeline definition gained a new execution step. The event references principal-248c78edaf5546c1. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Mail audit on FINANCE-ASSET-ea1b6c24422b456d recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-44026a910bd0b4c9. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Flow logs on ENGINEERING-ASSET-eb2e69d274ba28c2 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-95a534f7e0b0cad5. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Database audit on RESEARCH-ASSET-0df9b1ba7848d017 recorded that a session read several tables and exported the query result. The event references principal-78007df53b70739e. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Identity audit on PROCUREMENT-ASSET-595810a122b584e8 recorded that a service account established an interactive session. The event references principal-786fe31fade4e850. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Share audit on ENGINEERING-ASSET-15ac20dc277a74c4 recorded that a new network file share was published. The event references principal-33c52b08167e103b. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Kerberos audit on OPERATIONS-ASSET-15b32c4f5f91cc11 recorded that an account requested service tickets for multiple services. The event references principal-86eb3dff1abf1690. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Storage access logs on COMMUNICATIONS-ASSET-560f077b5b32381f recorded that a principal downloaded many objects from a storage bucket. The event references principal-2c20310dc28bca65. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-0243bed32c17 match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Repository audit on COMMUNICATIONS-ASSET-74eb656a821bda53 recorded that a repository collaborator received elevated permissions. The event references principal-aeb807368ce77066. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Cloud control audit on OPERATIONS-ASSET-ba4ce4cf529ac35c recorded that a session deleted a group of cloud resources. The event references principal-2a7a606b1116d324. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Dhcp telemetry on OPERATIONS-ASSET-495d89e0df4422f6 recorded that a server issued DHCP offers on a monitored segment. The event references principal-ad2763e8b3d1fe71. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Process audit on LEGAL-ASSET-1d30eece58fd02aa recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-73ea530a0de82f6d. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-acca8e606736 match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Smb audit on PROCUREMENT-ASSET-663a220061cd4095 recorded that a session enumerated a file share and read multiple files. The event references principal-ae5de00ea82776e7. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Package registry audit on FINANCE-ASSET-39c7276454a893cc recorded that a principal published a new package version. The event references principal-9e718ff7956300e6. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Security retest SEC-9032d3d3edb0 covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Repository audit on SUPPORT-ASSET-fb6027084fb1957b recorded that a user cloned several source repositories. The event references principal-6318dd66af34e88b. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Oauth audit on FINANCE-ASSET-ab8c40ef4ea54ef3 recorded that an application received consent for additional account scopes. The event references principal-c6dc8dd297f2cce8. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-6d671fee5cc6 accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Office audit on OPERATIONS-ASSET-a21bbd8f65591dc7 recorded that a document macro launched a child interpreter. The event references principal-640ebd4004779cca. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Driver audit on OPERATIONS-ASSET-16afbb03ee82c54d recorded that a kernel driver was loaded after a package installation. The event references principal-32362e7a45f17c8f. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Configuration audit on SALES-ASSET-9818a0f135cc7c5d recorded that a client proxy setting was changed. The event references principal-50e5e76cf1a92613. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Storage audit on OPERATIONS-ASSET-29e0421fa3b9bb88 recorded that an object-storage access policy was broadened. The event references principal-e4fd29cc648a5ac6. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"File audit on RESEARCH-ASSET-08266be3d48a0589 recorded that a process compressed files from several directories into an archive. The event references principal-ba2e548a2cd0e827. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Service audit on OPERATIONS-ASSET-53e47c7270341ae1 recorded that a remote service-control request created and started a temporary service. The event references principal-ae8a8a74a000dff1. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"File access audit on RESEARCH-ASSET-41c0744f3eec824f recorded that a process opened a local credential-store file. The event references principal-22db2b4742c4cf72. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Pki audit on PROCUREMENT-ASSET-4fa9108f30037594 recorded that a principal requested a certificate using an authentication template. The event references principal-7c9716b1c94aea0e. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Security retest SEC-073d4db3f5b8 covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"File audit on PROCUREMENT-ASSET-f66c7d2cd9a00208 recorded that a process compressed files from several directories into an archive. The event references principal-1608ac7a92b15a7f. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Kubernetes audit on PEOPLE-ASSET-46959b0322e15f66 recorded that a pod was created with privileged execution enabled. The event references principal-8e6c04f200191e81. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Secret manager audit on SALES-ASSET-b73f8978ef6e4f27 recorded that a workload read several secret versions. The event references principal-d6b84c181926e6a9. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Runtime audit on PROCUREMENT-ASSET-ef2802409ab5a514 recorded that a process connected to the container runtime socket. The event references principal-81a676edf02534d4. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Runtime audit on SALES-ASSET-65e80c7b6f9129ee recorded that a process connected to the container runtime socket. The event references principal-e74aec44693d5ee6. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Identity audit on PROCUREMENT-ASSET-847c16861843d993 recorded that repeated failed sign-ins were recorded for an account. The event references principal-177e5d83a23e0f5b. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Mail flow logs on RESEARCH-ASSET-a506e0d5600d9442 recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-27bdbe6c899d3b5b. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Windows logon audit on PROCUREMENT-ASSET-6de9173566128253 recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-1e31ae283e3821b5. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Key service audit on FINANCE-ASSET-57ca74510903ebd4 recorded that a principal issued a burst of key-service decrypt requests. The event references principal-79b7e5a3aa2edd24. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-486d4b207f64 explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Database audit on SALES-ASSET-19142cf000a582b0 recorded that a session read several tables and exported the query result. The event references principal-5991e381a26e4376. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"File audit on FINANCE-ASSET-a2913f2126217458 recorded that access permissions were broadened on a directory tree. The event references principal-05896b0efe4a938e. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Session audit on PROCUREMENT-ASSET-375b33e301ac9b62 recorded that the same session token appeared from different client addresses. The event references principal-c5f1efc48ec3f681. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Certificate audit on FINANCE-ASSET-e16767dd715979b6 recorded that a service certificate was replaced. The event references principal-f8a1311de5964c87. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-992d40111ef6 match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Package registry audit on LEGAL-ASSET-904ec76dbb996774 recorded that a principal published a new package version. The event references principal-3920a37e9b8e2b42. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Network control audit on LEGAL-ASSET-8a1d97d0c15ac118 recorded that a cloud security group gained a broad ingress rule. The event references principal-52d39a8366e69bf4. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Kubernetes audit on SALES-ASSET-3af15ceafaf37a50 recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-4e40a79e1d1cac1f. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Macos launch audit on PROCUREMENT-ASSET-cefeabfcdbb75ff5 recorded that a launch agent definition was installed in a user context. The event references principal-61b165b4264637cc. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-aed54b153bee match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Egress flow logs on PROCUREMENT-ASSET-dec31bc9d60afefc recorded that a workload opened an encrypted connection to an external service. The event references principal-552eff98281f8ed1. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-a2951cdd9ad1 match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Mail and proxy logs on ENGINEERING-ASSET-d6ab66ae0acf6c7d recorded that a user opened a URL delivered in an email message. The event references principal-0a6867792e03bc3b. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-349b494b1581 match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"File audit on SUPPORT-ASSET-5e6185480b7124c6 recorded that a shell startup profile gained an additional command. The event references principal-51f94e540bbb4321. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Kubernetes audit on OPERATIONS-ASSET-bc31964912cf4d1d recorded that a cluster admission policy was changed. The event references principal-c0a0ee553024f5ef. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Mail flow logs on ENGINEERING-ASSET-b3fe8e13b124582a recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-4618a2ddb02b8454. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Waf logs on PROCUREMENT-ASSET-be57d152ab66f42b recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-c19a63b81ac51b37. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Switch telemetry on OPERATIONS-ASSET-30a277f008dd59f9 recorded that an address mapping changed repeatedly on a local segment. The event references principal-f95a18784ccda07e. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"File audit on SALES-ASSET-f0f53d618a5c2238 recorded that a process compressed files from several directories into an archive. The event references principal-a24a28fb5a9017a6. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Mfa audit on PEOPLE-ASSET-e45fffd30cf466e9 recorded that multiple MFA challenges were issued during a short interval. The event references principal-3cbfe5aa85664020. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Mail audit on SALES-ASSET-bd6fcb0d83d6d9d8 recorded that an account received delegated access to a mailbox. The event references principal-44c7b65ec7f1b04b. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Service audit on PROCUREMENT-ASSET-7131a22a8a5e3488 recorded that a new automatically started service was registered. The event references principal-7eed072979ca83fe. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Change CHG-56d95849e793 lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Gateway logs on ENGINEERING-ASSET-8864632089fd4c50 recorded that a client established a long-lived encapsulated network session. The event references principal-90ee640b3b5c5162. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Directory audit on LEGAL-ASSET-e41057b50163ec62 recorded that a principal requested directory replication data. The event references principal-27103a43ea428bc2. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Switch telemetry on COMMUNICATIONS-ASSET-bcb43f0616b1a470 recorded that an address mapping changed repeatedly on a local segment. The event references principal-ea5a7f0eef9db0e7. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Macos launch audit on FINANCE-ASSET-050b0e8279760750 recorded that a launch agent definition was installed in a user context. The event references principal-7354e7b956585560. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-1843d5adc79d specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Dns server audit on ENGINEERING-ASSET-aec07c525ec55aac recorded that a client requested a DNS zone transfer. The event references principal-4c0d05a21a35e460. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-f3cc0f2a81fc specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Kubernetes audit on ENGINEERING-ASSET-74d13411d760b9a6 recorded that a role binding granted a principal additional cluster permissions. The event references principal-dbf4764de8118d40. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-7dea0ed053b4 explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Windows logon audit on OPERATIONS-ASSET-4a019c17c7542e6c recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-dd10cd046f3074f7. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-d77dd0c5b438 specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Winrm audit on COMMUNICATIONS-ASSET-2bb6a89a28755b1e recorded that a remote management session invoked a command on a managed host. The event references principal-2ae22aaef9849f17. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Event service audit on PEOPLE-ASSET-3e7af42f465f079f recorded that an event log was cleared by a privileged request. The event references principal-7e44d019c9f83317. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Gateway logs on RESEARCH-ASSET-6dcd3c5959922161 recorded that a client established a long-lived encapsulated network session. The event references principal-d901ab75b47ec726. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Change CHG-68d8428b390d lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Driver audit on SALES-ASSET-74116b6362e956da recorded that a kernel driver was loaded after a package installation. The event references principal-9eaf8c722428f29b. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Ssh audit on OPERATIONS-ASSET-324bfe1afe152ff0 recorded that an SSH session opened and requested elevated command execution. The event references principal-db6e14b705505251. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Share audit on COMMUNICATIONS-ASSET-155e7e0f58a0bc23 recorded that a new network file share was published. The event references principal-91339ef7c416f6ed. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Cloud control audit on OPERATIONS-ASSET-ba4ce4cf529ac35c recorded that a session deleted a group of cloud resources. The event references principal-2a7a606b1116d324. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-901d6d6611b0 match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Firewall audit on COMMUNICATIONS-ASSET-4f1cc73dbbdce003 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-3c942f0a8856cd1e. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Api gateway logs on OPERATIONS-ASSET-5d940a8c3c4b311c recorded that a client issued a burst of API requests. The event references principal-9965146148dbdc29. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-4e095d7a4c55 match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Cloud control audit on COMMUNICATIONS-ASSET-c7835ea641b313a9 recorded that a session deleted a group of cloud resources. The event references principal-5e2ab493e683591c. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Storage audit on COMMUNICATIONS-ASSET-4c8d4447eef18c17 recorded that an object-storage access policy was broadened. The event references principal-2ee0983ecf5d6d25. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"File audit on SALES-ASSET-6ae931d0f4c709bb recorded that access permissions were broadened on a directory tree. The event references principal-d574e0d5ffd134ab. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Database audit on LEGAL-ASSET-1c120ddc82665e7a recorded that a session read several tables and exported the query result. The event references principal-4636f85408e4dae9. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Ssh audit on PROCUREMENT-ASSET-76513cf046529603 recorded that an SSH session opened and requested elevated command execution. The event references principal-5b3a8f0f85403c14. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Process access audit on SUPPORT-ASSET-a8d87f27cfdb843f recorded that a process requested read access to another process memory space. The event references principal-8eabe5478e5a2271. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-753beeb96df5 before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Winrm audit on OPERATIONS-ASSET-5123f251af3bff40 recorded that a remote management session invoked a command on a managed host. The event references principal-f7aa03e82682bdc9. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Kubernetes audit on SALES-ASSET-b7d7628f8816a948 recorded that a role binding granted a principal additional cluster permissions. The event references principal-76cb7e33983ecb6a. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Api gateway logs on FINANCE-ASSET-7a64770a61e92e29 recorded that a client issued a burst of API requests. The event references principal-43cf908ee519b246. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Network control audit on ENGINEERING-ASSET-2d4a799851b7227b recorded that a cloud security group gained a broad ingress rule. The event references principal-5b7cb16d420fdcdc. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-eaa47edc4689 specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Function audit on ENGINEERING-ASSET-1db2f1c877763b47 recorded that a serverless function package and execution settings were updated. The event references principal-79d1bb9e5af18d47. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Application audit on PEOPLE-ASSET-fcad7cf3be4e4115 recorded that a runtime configuration setting was updated. The event references principal-1c596d52504e0c0f. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Application audit on LEGAL-ASSET-235dadbbfdbe7d33 recorded that an application requested repeated screen captures. The event references principal-31391eee810ce402. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Ssh audit on PROCUREMENT-ASSET-76513cf046529603 recorded that an SSH session opened and requested elevated command execution. The event references principal-5b3a8f0f85403c14. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Smb audit on LEGAL-ASSET-cbd503b9d9dce0b4 recorded that a session enumerated a file share and read multiple files. The event references principal-308281e8cf667587. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Kubernetes audit on ENGINEERING-ASSET-74d13411d760b9a6 recorded that a role binding granted a principal additional cluster permissions. The event references principal-dbf4764de8118d40. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Waf logs on SALES-ASSET-8a0f506e8e518bc0 recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-eb2ba7446fb1565a. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-5e52c28226d9 match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Ci audit on OPERATIONS-ASSET-3c47f8e04ce54395 recorded that a build pipeline definition gained a new execution step. The event references principal-4e3a0bcc0149b2b6. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Session audit on FINANCE-ASSET-15bdb8a9163b0abc recorded that the same session token appeared from different client addresses. The event references principal-ce316de1911fbf84. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Network control audit on SUPPORT-ASSET-badb98bf2185855c recorded that a cloud security group gained a broad ingress rule. The event references principal-1a508d07acbfb51b. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Key service audit on LEGAL-ASSET-c93c39a0bf6d5d2d recorded that a principal issued a burst of key-service decrypt requests. The event references principal-a9f8c5175e6aa291. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Task scheduler audit on LEGAL-ASSET-9a82bb1a05cff6a6 recorded that a scheduled task was registered to execute a program at logon. The event references principal-5c02a139758a7988. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Pki audit on PROCUREMENT-ASSET-4fa9108f30037594 recorded that a principal requested a certificate using an authentication template. The event references principal-7c9716b1c94aea0e. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Mail audit on SALES-ASSET-1d2f1acd8ca606b9 recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-eaa00c222951727e. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Event service audit on OPERATIONS-ASSET-6bb0ff67f6f8dbd2 recorded that an event log was cleared by a privileged request. The event references principal-1c69ef2988f5b8db. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Dhcp telemetry on SUPPORT-ASSET-ea5b723e111a60c0 recorded that a server issued DHCP offers on a monitored segment. The event references principal-f0fe04f7d6936857. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-fc0db5de02db accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Key service audit on OPERATIONS-ASSET-a2b77b051a5e88ca recorded that a principal issued a burst of key-service decrypt requests. The event references principal-2d26323a698b32c1. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Kubernetes audit on COMMUNICATIONS-ASSET-396281c213cbfe7d recorded that a role binding granted a principal additional cluster permissions. The event references principal-490795a3fa64d894. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-483b62e36618 match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Module audit on SALES-ASSET-0a5edb66b7d6ecd7 recorded that a process loaded a library from an application-local directory. The event references principal-adbbffe7727b888c. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Policy audit on ENGINEERING-ASSET-691918f61c7ec7b2 recorded that an audit policy was changed to collect fewer event categories. The event references principal-86d0e35aa5d8e487. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-13d4083175bf match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Kubernetes audit on FINANCE-ASSET-d7b2da83577ab38d recorded that a pod was created with privileged execution enabled. The event references principal-5177d7ecbc348aa2. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-574fc4b59238 accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Cloud control audit on LEGAL-ASSET-152843552545f6c2 recorded that a session deleted a group of cloud resources. The event references principal-441348e944e96c5c. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Kerberos audit on LEGAL-ASSET-6ee4a0334d8b0730 recorded that an account requested service tickets for multiple services. The event references principal-2772005981d83d01. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Resolver logs on PEOPLE-ASSET-aa9ea5738fc3afe1 recorded that a client requested many long, high-entropy DNS labels. The event references principal-bd6f946855b371b5. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Agent audit on RESEARCH-ASSET-01cc4805ed6fe45d recorded that a privileged session changed endpoint monitoring settings. The event references principal-fb3e99ff7e75f725. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Repository audit on COMMUNICATIONS-ASSET-fc7d932dec68a3a4 recorded that a user cloned several source repositories. The event references principal-f9163c8da3ccc09a. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Pki audit on COMMUNICATIONS-ASSET-a88e156f33159899 recorded that a principal requested a certificate using an authentication template. The event references principal-0a19afbf9253f4fc. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Database audit on SUPPORT-ASSET-9310282a796b35af recorded that a session changed a database table definition. The event references principal-c009c7c60f3c400f. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Egress flow logs on FINANCE-ASSET-6fc2f9679740efc1 recorded that a workload opened an encrypted connection to an external service. The event references principal-b6c8a10c3d36b1fc. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Assessment SEC-6844b6db1c05 explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Storage access logs on PEOPLE-ASSET-c7aae9977fa123ac recorded that a principal downloaded many objects from a storage bucket. The event references principal-8d5cca2185bede9c. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Cloud control audit on LEGAL-ASSET-152843552545f6c2 recorded that a session deleted a group of cloud resources. The event references principal-441348e944e96c5c. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Cloud identity audit on SALES-ASSET-8e5fe4f751d14789 recorded that a new programmatic access key was issued to a principal. The event references principal-42ddd98f6ef91f59. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Kubernetes audit on OPERATIONS-ASSET-914b85ff52bb152e recorded that a role binding granted a principal additional cluster permissions. The event references principal-23475897d2814771. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Dns control audit on PEOPLE-ASSET-4210d86f84839a74 recorded that an authoritative DNS record was updated. The event references principal-92f6f8227c610f96. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Ssh audit on SALES-ASSET-95483443a44dd70e recorded that an SSH session opened and requested elevated command execution. The event references principal-ee7405179574875a. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Registry audit on OPERATIONS-ASSET-bb2e321557973238 recorded that a registry logon-start entry was created. The event references principal-48a0f7ab86053bfa. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Backup audit on SALES-ASSET-6933f79c2a57f98c recorded that a backup retention policy was shortened. The event references principal-9b63e3d52602597e. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Mail and proxy logs on PROCUREMENT-ASSET-f73ebff8c2f46ccc recorded that a user opened a URL delivered in an email message. The event references principal-81190b386823c031. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Saas audit on FINANCE-ASSET-7dbfabaebbf506b5 recorded that a user requested a bulk export from a business application. The event references principal-147dd62c19db648c. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Process audit on SALES-ASSET-96ce257e2204a8a5 recorded that a remote-support application started an interactive session. The event references principal-ae9cce396ea567fe. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Application audit on ENGINEERING-ASSET-83152a55ea1c27b8 recorded that an application read clipboard contents repeatedly. The event references principal-d08677bd055caebe. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Dns control audit on SUPPORT-ASSET-daac2768071affbb recorded that an authoritative DNS record was updated. The event references principal-004b930761f504d4. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Agent audit on PEOPLE-ASSET-145b133cd9883db8 recorded that a privileged session changed endpoint monitoring settings. The event references principal-3cdfd17f049efdd9. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Switch telemetry on LEGAL-ASSET-1643dbdebba2d78d recorded that an address mapping changed repeatedly on a local segment. The event references principal-c39fe907de3611c7. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Systemd audit on OPERATIONS-ASSET-42dd1f251b2cefd5 recorded that a service unit file was changed and the unit reloaded. The event references principal-27edc61f63f1f31a. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Dns server audit on FINANCE-ASSET-b5978ac018c6f58c recorded that a client requested a DNS zone transfer. The event references principal-eef8de7d2245f076. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Secret manager audit on RESEARCH-ASSET-9ed518d17fe68d7a recorded that a workload read several secret versions. The event references principal-7f1b48c31f4c5822. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-c4881fb82fa2 before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Identity audit on COMMUNICATIONS-ASSET-ae1258c834d83e6f recorded that an account password was reset through a recovery workflow. The event references principal-98f97f4d1c43e756. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Windows logon audit on FINANCE-ASSET-08f4600838c704c1 recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-9a25429fc1580f3b. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Kubernetes audit on OPERATIONS-ASSET-e9cb557fa33c100a recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-d1c39d3b8db93b55. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Dns control audit on COMMUNICATIONS-ASSET-9ae5b908b35b63ef recorded that an authoritative DNS record was updated. The event references principal-b17631352023456c. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Device and file audit on COMMUNICATIONS-ASSET-f491a02c80ff7ee4 recorded that files were copied to a removable storage device. The event references principal-b586401867cc7a49. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Application audit on PROCUREMENT-ASSET-9ae629f20e56becc recorded that a runtime configuration setting was updated. The event references principal-be5a20df9fa68e8b. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Resolver logs on ENGINEERING-ASSET-02301b26ed9cf1c5 recorded that a client requested many long, high-entropy DNS labels. The event references principal-8e3fc22d3aadc906. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-0a02fc0ca6f4 specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Cloud control audit on COMMUNICATIONS-ASSET-c7835ea641b313a9 recorded that a session deleted a group of cloud resources. The event references principal-5e2ab493e683591c. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Cloud identity audit on COMMUNICATIONS-ASSET-a2643d4e14311066 recorded that a principal assumed a role in another account. The event references principal-3ce172a931fefefa. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"File audit on RESEARCH-ASSET-e40ef73f48b09e4f recorded that a shell startup profile gained an additional command. The event references principal-2434130e3913b6f0. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-db91b4a0448f, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Session audit on PEOPLE-ASSET-2f7cb210c1411ef5 recorded that the same session token appeared from different client addresses. The event references principal-254fb3d8a50b95f2. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"File audit on LEGAL-ASSET-f437cecc468ccf1f recorded that access permissions were broadened on a directory tree. The event references principal-1d5f4386a802d873. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-5a75877ec45e before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Ssh audit on FINANCE-ASSET-370d0df1776daaea recorded that an SSH session opened and requested elevated command execution. The event references principal-d8496f14d2489876. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Service audit on SALES-ASSET-fffc2b9a7422ce6b recorded that a remote service-control request created and started a temporary service. The event references principal-ab058eda0f6e9097. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Waf logs on SALES-ASSET-8a0f506e8e518bc0 recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-eb2ba7446fb1565a. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-5e52c28226d9 match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Account audit on ENGINEERING-ASSET-bce5c50695a23c43 recorded that a local user account was created on a managed system. The event references principal-1a94579d85980de4. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-3c988239c03b match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Cloud identity audit on FINANCE-ASSET-e7ffd7ca6e67a506 recorded that a principal assumed a role in another account. The event references principal-9b4f65d2a19e9629. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Cloud control audit on PEOPLE-ASSET-a565fc161c06dbdd recorded that a cloud logging destination was disabled. The event references principal-b1342e9d7cf466d7. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Office audit on LEGAL-ASSET-7baa0b7a7bcbd13a recorded that a document macro launched a child interpreter. The event references principal-4d965a283abc96ce. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Security retest SEC-42f7c7a46979 covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Pki audit on ENGINEERING-ASSET-1be9c96304b0e927 recorded that a principal requested a certificate using an authentication template. The event references principal-86425f445bb7386e. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Database audit on SALES-ASSET-19142cf000a582b0 recorded that a session read several tables and exported the query result. The event references principal-5991e381a26e4376. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Change CHG-453705ad73a7 lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Module audit on PROCUREMENT-ASSET-234ebd90da532d08 recorded that a process loaded a library from an application-local directory. The event references principal-2bfaedc31b23b886. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Gateway logs on PEOPLE-ASSET-755d4ede711826a7 recorded that a client established a long-lived encapsulated network session. The event references principal-3095e007e6941bdd. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Api gateway logs on COMMUNICATIONS-ASSET-25487240e8c2e247 recorded that a client issued a burst of API requests. The event references principal-23ca7dbb4aa37ade. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Ssh audit on PEOPLE-ASSET-97ff8f8fa97fd164 recorded that an SSH session opened and requested elevated command execution. The event references principal-60b1e96c2c9d3478. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Task scheduler audit on ENGINEERING-ASSET-03b8a656580bfb25 recorded that a scheduled task was registered to execute a program at logon. The event references principal-2a3a3ccb2ea52460. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-a3f8c9a20f72 accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Task scheduler audit on RESEARCH-ASSET-21bf6f06fdc5117a recorded that a scheduled task was registered to execute a program at logon. The event references principal-0cdfb8ebb9ac46b3. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-0f3ff901a1ab match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"File audit on FINANCE-ASSET-2a7828c17a1b3f24 recorded that a shell startup profile gained an additional command. The event references principal-4b7e3cd5eb46c9e6. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Security retest SEC-ae7adb579b41 covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Storage access logs on SUPPORT-ASSET-467cdf660d5e57c4 recorded that a principal downloaded many objects from a storage bucket. The event references principal-83eeaee20b7f40f8. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Directory audit on FINANCE-ASSET-4f2fe0486abb5c95 recorded that a principal requested directory replication data. The event references principal-b40239cccc5bf96a. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Share audit on PROCUREMENT-ASSET-d3ee6d1f094d6ce0 recorded that a new network file share was published. The event references principal-9978a814a123a526. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Storage access logs on OPERATIONS-ASSET-4a7bbac68a963680 recorded that a principal downloaded many objects from a storage bucket. The event references principal-9881a91f6d808755. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Repository audit on ENGINEERING-ASSET-19fede4e07d7366c recorded that a repository collaborator received elevated permissions. The event references principal-22c3a4b3adce2401. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Account audit on RESEARCH-ASSET-a444b46456cd6186 recorded that a local user account was created on a managed system. The event references principal-dd1721a44a27272f. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-b2a34a2cc6c7 explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Identity audit on COMMUNICATIONS-ASSET-4abec775a52c95c2 recorded that repeated failed sign-ins were recorded for an account. The event references principal-a42f44848e926187. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Repository audit on OPERATIONS-ASSET-2cc6b5c22c3989e5 recorded that a user cloned several source repositories. The event references principal-e45f970cca2e32b9. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"File access audit on PROCUREMENT-ASSET-0b755d0602adf157 recorded that a process opened a local credential-store file. The event references principal-7e6f29a9069cca6a. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-a162a8b0caf7 match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Cloud identity audit on ENGINEERING-ASSET-af1e93943ab29f9c recorded that a new programmatic access key was issued to a principal. The event references principal-44b79fe1a6fcf9a1. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Account audit on SUPPORT-ASSET-4f664bc059385d17 recorded that a local user account was created on a managed system. The event references principal-1db165dfba5895ba. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Cloud control audit on COMMUNICATIONS-ASSET-c7835ea641b313a9 recorded that a session deleted a group of cloud resources. The event references principal-5e2ab493e683591c. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Registry audit on RESEARCH-ASSET-e5e233361fd38697 recorded that a registry logon-start entry was created. The event references principal-83333208692c8fd1. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Application audit on RESEARCH-ASSET-44de8cf55f1c805f recorded that an application requested repeated screen captures. The event references principal-17ee862a652063ef. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Application audit on ENGINEERING-ASSET-83152a55ea1c27b8 recorded that an application read clipboard contents repeatedly. The event references principal-d08677bd055caebe. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Change CHG-5f849f943496 lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Winrm audit on ENGINEERING-ASSET-6e5e1ed61987467a recorded that a remote management session invoked a command on a managed host. The event references principal-c372b39c0d58be55. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-e547a9053c51 match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Package registry audit on OPERATIONS-ASSET-b20136404dfc240b recorded that a principal published a new package version. The event references principal-97ed055b6e1a57e6. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-3c87bebd62b4, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Configuration audit on SUPPORT-ASSET-75f85e5b495f1222 recorded that a client proxy setting was changed. The event references principal-02061922c2bafcd3. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Module audit on SALES-ASSET-0a5edb66b7d6ecd7 recorded that a process loaded a library from an application-local directory. The event references principal-adbbffe7727b888c. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Share audit on ENGINEERING-ASSET-15ac20dc277a74c4 recorded that a new network file share was published. The event references principal-33c52b08167e103b. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Application audit on RESEARCH-ASSET-21c212dc3255aa17 recorded that an application read clipboard contents repeatedly. The event references principal-8f2a965b2d84c102. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Service audit on COMMUNICATIONS-ASSET-9cb10b4818b88629 recorded that a remote service-control request created and started a temporary service. The event references principal-9f1825f9f69c7e5f. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-4ed8382c9c58 before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Browser audit on COMMUNICATIONS-ASSET-242d23ba4ad50b88 recorded that a browser extension with page-reading permissions was installed. The event references principal-c4eaf539de0f6aa8. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-7037588cf3e7, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Certificate audit on OPERATIONS-ASSET-3ca9753ca5075c61 recorded that a service certificate was replaced. The event references principal-15f1c60782059a24. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Cloud identity audit on LEGAL-ASSET-7e0cfa13cd7f5efc recorded that a new programmatic access key was issued to a principal. The event references principal-578071150bb49966. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Module audit on FINANCE-ASSET-6b165174917b5734 recorded that a process loaded a library from an application-local directory. The event references principal-ecca7e9b2841d1cc. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Security retest SEC-ef4078f07111 covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Api gateway logs on SUPPORT-ASSET-13bc954846049d2f recorded that a client issued a burst of API requests. The event references principal-d482be68e022a834. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Cron audit on LEGAL-ASSET-fa5ca79bc164009d recorded that a recurring job definition was added to the system schedule. The event references principal-07e12ac009730cba. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Application audit on FINANCE-ASSET-92ef4a42892b1789 recorded that an application read clipboard contents repeatedly. The event references principal-13f5550b59519bb2. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Egress flow logs on SUPPORT-ASSET-ff3badb46e903585 recorded that a workload opened an encrypted connection to an external service. The event references principal-ef7dbc8f1e7b6a52. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-8e39f3f1559f accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Directory audit on FINANCE-ASSET-4f2fe0486abb5c95 recorded that a principal requested directory replication data. The event references principal-b40239cccc5bf96a. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Process access audit on SUPPORT-ASSET-a8d87f27cfdb843f recorded that a process requested read access to another process memory space. The event references principal-8eabe5478e5a2271. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"File audit on FINANCE-ASSET-a4971629c23d55d9 recorded that a process compressed files from several directories into an archive. The event references principal-c74fdddea36d843d. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Session audit on COMMUNICATIONS-ASSET-9a4f765d7218bb33 recorded that the same session token appeared from different client addresses. The event references principal-961620617e88f850. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Mail audit on PEOPLE-ASSET-23ff12ac4cce3df1 recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-210b267fe07fa398. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Storage audit on FINANCE-ASSET-47f72b6b10bf47c7 recorded that a session deleted several storage snapshots. The event references principal-6ce8e4c42cc80c2d. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Service audit on FINANCE-ASSET-d962ba7a33513380 recorded that a new automatically started service was registered. The event references principal-238acc934bc77540. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Saas audit on OPERATIONS-ASSET-f4bc429edd233279 recorded that a user requested a bulk export from a business application. The event references principal-0d93bc3cb85c4be3. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Mfa audit on COMMUNICATIONS-ASSET-ce18db2b3211944f recorded that multiple MFA challenges were issued during a short interval. The event references principal-5c71c8caf74a8fa1. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Browser audit on PROCUREMENT-ASSET-50d8010904173019 recorded that a browser extension with page-reading permissions was installed. The event references principal-8e2e0553f52a5216. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Application audit on FINANCE-ASSET-5311585386f59d86 recorded that an application requested repeated screen captures. The event references principal-6f04a55a0eba4c05. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Mail audit on SALES-ASSET-bd6fcb0d83d6d9d8 recorded that an account received delegated access to a mailbox. The event references principal-44c7b65ec7f1b04b. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Process access audit on ENGINEERING-ASSET-6c512bf3bb9f3c6e recorded that a process requested read access to another process memory space. The event references principal-0c750e6c9b19f34e. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Pki audit on FINANCE-ASSET-3748aa367e539143 recorded that a principal requested a certificate using an authentication template. The event references principal-d4df29576d1acbb5. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Mail audit on PEOPLE-ASSET-0dab505ef5721fa1 recorded that an account received delegated access to a mailbox. The event references principal-867e051f8d4b0f18. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-14d17e79f9ba accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Process audit on COMMUNICATIONS-ASSET-5b837c3960f14bc6 recorded that a JavaScript interpreter executed a local script. The event references principal-f91a7e6de3b60959. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Kubernetes audit on RESEARCH-ASSET-e5b9e413bdef9d8d recorded that a pod was created with privileged execution enabled. The event references principal-74b8c2bcccc76ba0. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Cron audit on SUPPORT-ASSET-0f143a13847207ad recorded that a recurring job definition was added to the system schedule. The event references principal-940a8e24d3cd68aa. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Storage audit on LEGAL-ASSET-5cc263cd7974e410 recorded that a session deleted several storage snapshots. The event references principal-548b73b08858de12. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Process audit on PEOPLE-ASSET-2c32b67a1236291b recorded that a remote-support application started an interactive session. The event references principal-3d51474c05227a94. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Process audit on RESEARCH-ASSET-4c23face5574e971 recorded that a JavaScript interpreter executed a local script. The event references principal-4325acfa278d2f70. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Secret manager audit on SALES-ASSET-b73f8978ef6e4f27 recorded that a workload read several secret versions. The event references principal-d6b84c181926e6a9. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Group audit on SALES-ASSET-0d02096325648024 recorded that an account was added to a privileged local group. The event references principal-2cfc43945d846816. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Compute audit on PROCUREMENT-ASSET-507dec859fa3003b recorded that a principal launched multiple compute instances. The event references principal-611c292a786d76ca. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Firewall audit on ENGINEERING-ASSET-4346eb459a11971a recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-62f6e1ae625e9e27. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Process audit on ENGINEERING-ASSET-2b855d0d88712cb8 recorded that a JavaScript interpreter executed a local script. The event references principal-3943e4c085d81398. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Switch telemetry on ENGINEERING-ASSET-271d6935661ca5b6 recorded that an address mapping changed repeatedly on a local segment. The event references principal-2aa672d045fc50f4. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Kubernetes audit on PEOPLE-ASSET-3e58a2eca5c63a44 recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-8f985c1a713a28f2. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-300a08b7dfb0 accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Proxy logs on RESEARCH-ASSET-2d6466dd3f8c1f6b recorded that a client transferred a large payload to an external storage endpoint. The event references principal-136b3bcae45dcdcd. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Change CHG-f0d7cdb75d80 lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Federation audit on PEOPLE-ASSET-307988f8a71d4999 recorded that a tenant federation setting was updated. The event references principal-c9e7767b005f5591. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Storage access logs on RESEARCH-ASSET-59340bda9ea1f273 recorded that a principal downloaded many objects from a storage bucket. The event references principal-516ae6385fac5df9. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-826aca68b239 before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Firewall audit on FINANCE-ASSET-d80ee8804a4ec6b6 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-b21644c32449b9a0. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Firewall audit on COMMUNICATIONS-ASSET-4f1cc73dbbdce003 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-3c942f0a8856cd1e. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Device and file audit on OPERATIONS-ASSET-e188a7d05dfbf7ee recorded that files were copied to a removable storage device. The event references principal-4cd6803b897580b7. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Service audit on SALES-ASSET-ee4f4ed67afc3eae recorded that a new automatically started service was registered. The event references principal-ae21c97b6a858bb0. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Key service audit on PEOPLE-ASSET-51157cbfcf0e7f8b recorded that a principal issued a burst of key-service decrypt requests. The event references principal-8c512aac8f2c3631. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Windows logon audit on ENGINEERING-ASSET-9a2b7e9a3eb1704f recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-d502784167672763. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-ffecd7d37058 before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Registry audit on PROCUREMENT-ASSET-76d816b7b04f4b8f recorded that a workload pulled a container image from a registry. The event references principal-12ce95b5667b0630. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Policy audit on PROCUREMENT-ASSET-f2878461512a2696 recorded that an audit policy was changed to collect fewer event categories. The event references principal-2bb61efdeda82dac. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Mail audit on FINANCE-ASSET-c2947168e63669b0 recorded that an account received delegated access to a mailbox. The event references principal-33d9797e6b81280e. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Session audit on SUPPORT-ASSET-39c9a292833723e5 recorded that the same session token appeared from different client addresses. The event references principal-a5ec7d156048f10f. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Winrm audit on SUPPORT-ASSET-635c3348db734709 recorded that a remote management session invoked a command on a managed host. The event references principal-f79466b09a2bb0fa. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-155006af6112 match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Oauth audit on ENGINEERING-ASSET-6abd006369fb2ea6 recorded that an application received consent for additional account scopes. The event references principal-7b515ef2be2fa58b. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Kubernetes audit on FINANCE-ASSET-915256a7e7a6d4a6 recorded that a role binding granted a principal additional cluster permissions. The event references principal-49e34ed22123229a. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Change CHG-01c80adbd9d4 lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Pki audit on PEOPLE-ASSET-3dbf336f859282fe recorded that a principal requested a certificate using an authentication template. The event references principal-bc62db6b4c821f23. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Registry audit on PEOPLE-ASSET-493d3bd95ab44b29 recorded that a registry logon-start entry was created. The event references principal-b4c380fe3bd5d692. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Oauth audit on RESEARCH-ASSET-0631ea2256cf662a recorded that an application received consent for additional account scopes. The event references principal-8da4697a549d31b3. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Switch telemetry on PEOPLE-ASSET-2fae865ac519b354 recorded that an address mapping changed repeatedly on a local segment. The event references principal-cadf13732271e411. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Dns server audit on FINANCE-ASSET-b5978ac018c6f58c recorded that a client requested a DNS zone transfer. The event references principal-eef8de7d2245f076. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"File access audit on RESEARCH-ASSET-41c0744f3eec824f recorded that a process opened a local credential-store file. The event references principal-22db2b4742c4cf72. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Cloud identity audit on ENGINEERING-ASSET-af1e93943ab29f9c recorded that a new programmatic access key was issued to a principal. The event references principal-44b79fe1a6fcf9a1. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Kerberos audit on RESEARCH-ASSET-add8a0192da6108f recorded that an account requested service tickets for multiple services. The event references principal-2289755f000d3a1a. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Proxy logs on SUPPORT-ASSET-eadf40ef6aff627a recorded that a client transferred a large payload to an external storage endpoint. The event references principal-77e382cc165fce08. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Agent audit on RESEARCH-ASSET-01cc4805ed6fe45d recorded that a privileged session changed endpoint monitoring settings. The event references principal-fb3e99ff7e75f725. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Change CHG-1242f26f3b6a lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Key service audit on FINANCE-ASSET-57ca74510903ebd4 recorded that a principal issued a burst of key-service decrypt requests. The event references principal-79b7e5a3aa2edd24. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Flow logs on PEOPLE-ASSET-747d1cebe72c1281 recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-d7e614d288290a88. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Cloud identity audit on FINANCE-ASSET-44723c4a98b3d8ba recorded that a principal received a policy granting additional permissions. The event references principal-ddbfe461888a8cb6. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Application audit on SUPPORT-ASSET-1e6a7efeb4ea574b recorded that a runtime configuration setting was updated. The event references principal-8bffad7489ed2f67. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Dhcp telemetry on COMMUNICATIONS-ASSET-a7af3c886d8ee570 recorded that a server issued DHCP offers on a monitored segment. The event references principal-aa2878e706226d96. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Kubernetes audit on SALES-ASSET-b7d7628f8816a948 recorded that a role binding granted a principal additional cluster permissions. The event references principal-76cb7e33983ecb6a. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"File audit on PROCUREMENT-ASSET-5c83620233b8b110 recorded that a process deleted many files within a short interval. The event references principal-eb86b20544a85de9. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Cloud identity audit on SALES-ASSET-8e5fe4f751d14789 recorded that a new programmatic access key was issued to a principal. The event references principal-42ddd98f6ef91f59. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Group audit on LEGAL-ASSET-c0290e976cae1a6c recorded that an account was added to a privileged local group. The event references principal-0e07ba3cca839e79. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Pki audit on PROCUREMENT-ASSET-4fa9108f30037594 recorded that a principal requested a certificate using an authentication template. The event references principal-7c9716b1c94aea0e. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Policy audit on OPERATIONS-ASSET-bb5aff052239026f recorded that an audit policy was changed to collect fewer event categories. The event references principal-08ce997b82328b8f. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Ci audit on SUPPORT-ASSET-be888d94d309deab recorded that a build pipeline definition gained a new execution step. The event references principal-f55be257f884a1b4. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-7ea6fba7e92a accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Kubernetes audit on ENGINEERING-ASSET-cad5b32322e2d059 recorded that a pod was created with privileged execution enabled. The event references principal-b5a63a5d1fffe886. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-f3bca58b76ed match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Resolver logs on RESEARCH-ASSET-abc39d656b9d30aa recorded that a client requested many long, high-entropy DNS labels. The event references principal-5aebc86024ffc2a8. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Security retest SEC-c3b9b7a5a0b1 covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Service audit on OPERATIONS-ASSET-fd16a6acf8f54a9a recorded that a new automatically started service was registered. The event references principal-c9af46ed7e55064b. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-276f3164aa47 explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"File audit on SUPPORT-ASSET-96c72864072032c8 recorded that a process deleted many files within a short interval. The event references principal-7a907f6a20c3a4ff. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"File access audit on SUPPORT-ASSET-701fe361a48ad8d6 recorded that a process opened a local credential-store file. The event references principal-0923914a571f26a3. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Identity audit on RESEARCH-ASSET-88e52266f5af4a21 recorded that a service account established an interactive session. The event references principal-d08379cdebfa5913. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Driver audit on SUPPORT-ASSET-19c2a39ea2af2cbe recorded that a kernel driver was loaded after a package installation. The event references principal-f5704bc0d4a6300d. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Application audit on OPERATIONS-ASSET-cf2679e9708fa36f recorded that a runtime configuration setting was updated. The event references principal-3db05afeebe1db89. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Pki audit on RESEARCH-ASSET-5892d31dbb5ae49e recorded that a principal requested a certificate using an authentication template. The event references principal-5044ec496f46d2cd. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-887ddbb4679a explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Storage access logs on FINANCE-ASSET-c07c58461c3886b7 recorded that a principal downloaded many objects from a storage bucket. The event references principal-636661caf69ea2cc. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Flow logs on RESEARCH-ASSET-6a2a326a382bb0b4 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-56d66c0e0a2c4463. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-c927e53599b4 match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Kubernetes audit on SUPPORT-ASSET-70672b7c7f3d80de recorded that a workload mounted a directory from its host filesystem. The event references principal-bb9a9a5a1ac32931. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-c93bb9efa8a1 explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"File audit on COMMUNICATIONS-ASSET-aa99d2f314263fcc recorded that a process compressed files from several directories into an archive. The event references principal-f14ddee6e5692d20. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Identity audit on RESEARCH-ASSET-77b0ab4459df7f50 recorded that repeated failed sign-ins were recorded for an account. The event references principal-ef9a3ac0fa7044a5. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-189c1f550f6d match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Dns control audit on PEOPLE-ASSET-4210d86f84839a74 recorded that an authoritative DNS record was updated. The event references principal-92f6f8227c610f96. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Application audit on COMMUNICATIONS-ASSET-365eaf894be6367d recorded that an application read clipboard contents repeatedly. The event references principal-c9d903188ad53746. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"File audit on ENGINEERING-ASSET-b0203944931a2946 recorded that a process compressed files from several directories into an archive. The event references principal-c59c85332aba5a32. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-058df65fd991, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Pki audit on SALES-ASSET-34ed542c065cfc50 recorded that a principal requested a certificate using an authentication template. The event references principal-bd8f51ad03539dfb. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Kubernetes audit on LEGAL-ASSET-d5c1c420f1077ded recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-1d6426e1ff1f69c4. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Mail audit on RESEARCH-ASSET-fad2d601f38f7cda recorded that an account received delegated access to a mailbox. The event references principal-b5e074cc28811f03. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Office audit on SUPPORT-ASSET-b861b71047f83874 recorded that a document macro launched a child interpreter. The event references principal-41f626db101e0b15. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-88ca403423fc specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Resolver logs on SALES-ASSET-17cdfcbdaddd4989 recorded that a client requested many long, high-entropy DNS labels. The event references principal-fddd379e6737bcc0. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Kubernetes audit on SUPPORT-ASSET-46e0923b16c1de93 recorded that a cluster admission policy was changed. The event references principal-eb0f85c559534d98. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-10730954a43f match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Flow logs on PROCUREMENT-ASSET-cd965c50b19b4b1f recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-3abc068e3f191445. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Security retest SEC-e9f5d88049ad covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Package registry audit on PROCUREMENT-ASSET-742ad97982b567e2 recorded that a principal published a new package version. The event references principal-5921bb600425987a. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Service audit on FINANCE-ASSET-271527485b0e477e recorded that a remote service-control request created and started a temporary service. The event references principal-31971ac078081c89. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Assessment SEC-3ef78a9e1b77 explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Mail audit on OPERATIONS-ASSET-3bd074cdd8f9b5e6 recorded that an account received delegated access to a mailbox. The event references principal-81775ab116c002d8. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Switch telemetry on OPERATIONS-ASSET-30a277f008dd59f9 recorded that an address mapping changed repeatedly on a local segment. The event references principal-f95a18784ccda07e. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Wmi audit on FINANCE-ASSET-9fd34fa594551e66 recorded that a management request started a process through WMI. The event references principal-1f38151c7990e366. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Storage access logs on PEOPLE-ASSET-c7aae9977fa123ac recorded that a principal downloaded many objects from a storage bucket. The event references principal-8d5cca2185bede9c. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Registry audit on COMMUNICATIONS-ASSET-c99d7ada90aece83 recorded that a workload pulled a container image from a registry. The event references principal-c5705a8b2e1e260b. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Oauth audit on COMMUNICATIONS-ASSET-d085212f92517588 recorded that an application received consent for additional account scopes. The event references principal-410957c7717cf0fe. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"File audit on PROCUREMENT-ASSET-5c83620233b8b110 recorded that a process deleted many files within a short interval. The event references principal-eb86b20544a85de9. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Registry audit on SUPPORT-ASSET-f57e1958aa803333 recorded that a workload pulled a container image from a registry. The event references principal-10cd1718e32b6b5f. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Configuration audit on OPERATIONS-ASSET-f3ed5a9b931a0951 recorded that a client proxy setting was changed. The event references principal-d8940d417fc4c9bd. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Process access audit on FINANCE-ASSET-247c48e4c49c174e recorded that a process requested read access to another process memory space. The event references principal-601055cfd3a85372. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-3a04bb5e382e match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"File audit on LEGAL-ASSET-4a73488ba2d33df6 recorded that a process rewrote multiple files into encrypted containers. The event references principal-9d7037ae8c34aa83. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-fd853d056a66 explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Vpn audit on PEOPLE-ASSET-8b15c5e5fc77cfb3 recorded that a remote-access VPN session was established. The event references principal-61e8cff53a9f17ad. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Assessment SEC-8461e47ea5ef explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"File audit on COMMUNICATIONS-ASSET-7174b9fee0b011b4 recorded that a process rewrote multiple files into encrypted containers. The event references principal-8e2fefcd77348cfa. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Identity audit on OPERATIONS-ASSET-71fc600bd08a667f recorded that an account registered a new MFA method. The event references principal-717e0b47f1247c8b. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Process access audit on COMMUNICATIONS-ASSET-5d86ffc7f1150e70 recorded that a process requested read access to another process memory space. The event references principal-4279d106b274e43e. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Cloud identity audit on LEGAL-ASSET-be33ff15ebf5e263 recorded that a principal assumed a role in another account. The event references principal-a89c01a9848a96c2. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Database audit on PEOPLE-ASSET-aeb9e932203e4086 recorded that a session changed a database table definition. The event references principal-4c123413716680f3. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Waf logs on SUPPORT-ASSET-e0ebcdef3dfa8416 recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-3a687906c9bbefbc. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Gateway logs on SUPPORT-ASSET-bfcdc7fd12a63ce3 recorded that a client established a long-lived encapsulated network session. The event references principal-076e693836d2e9e9. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Compute audit on FINANCE-ASSET-428507c521e75c88 recorded that a principal launched multiple compute instances. The event references principal-a167ad7ce21b7604. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Secret manager audit on OPERATIONS-ASSET-9fccf4aa5cb6d2fb recorded that a workload read several secret versions. The event references principal-67a3ab465380b229. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Runtime audit on COMMUNICATIONS-ASSET-da48b46f34e4599d recorded that a process connected to the container runtime socket. The event references principal-3deaf11c55ba9307. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-683608b52fd6 explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Storage audit on SUPPORT-ASSET-519ebc03fcafbccd recorded that a session deleted several storage snapshots. The event references principal-1671f42126c1c5f8. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-708bedbab6cb before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"File audit on LEGAL-ASSET-bda990f3a65f05d4 recorded that a process compressed files from several directories into an archive. The event references principal-e0bfbf7c864c739b. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-1601231e62aa match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Application audit on ENGINEERING-ASSET-0a500e9acaab2792 recorded that an application requested repeated screen captures. The event references principal-f9139e2001fef8f3. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Macos launch audit on PROCUREMENT-ASSET-cefeabfcdbb75ff5 recorded that a launch agent definition was installed in a user context. The event references principal-61b165b4264637cc. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Proxy logs on COMMUNICATIONS-ASSET-5a2ac13c8b310540 recorded that a client transferred a large payload to an external storage endpoint. The event references principal-d735b0162330748a. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Change CHG-45e2d294c4ba lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Kubernetes audit on PROCUREMENT-ASSET-2f62998057d28724 recorded that a role binding granted a principal additional cluster permissions. The event references principal-4457a8d289298830. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Package registry audit on PROCUREMENT-ASSET-742ad97982b567e2 recorded that a principal published a new package version. The event references principal-5921bb600425987a. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Repository audit on SUPPORT-ASSET-f2c722947f994337 recorded that a repository collaborator received elevated permissions. The event references principal-81983e01bdfb552d. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-a6357ab061c5 explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Waf logs on RESEARCH-ASSET-f279330020f0e645 recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-a38184b376034ec2. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-bee285300fd3 match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Egress flow logs on SALES-ASSET-a811cdcc9969f943 recorded that a workload opened an encrypted connection to an external service. The event references principal-17514c019150a73d. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Vpn audit on OPERATIONS-ASSET-3b10a040384bc85b recorded that a remote-access VPN session was established. The event references principal-e69c38b8397d46ff. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Function audit on ENGINEERING-ASSET-1db2f1c877763b47 recorded that a serverless function package and execution settings were updated. The event references principal-79d1bb9e5af18d47. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-bdd718719c15 explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Registry audit on LEGAL-ASSET-27fcaf5b02ef0a74 recorded that a registry logon-start entry was created. The event references principal-b668661833835ee3. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Device and file audit on RESEARCH-ASSET-6da8ae6d7bfc1fd2 recorded that files were copied to a removable storage device. The event references principal-6e75da4e311027c4. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Smb audit on PROCUREMENT-ASSET-663a220061cd4095 recorded that a session enumerated a file share and read multiple files. The event references principal-ae5de00ea82776e7. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Share audit on FINANCE-ASSET-689b8f41db9ab4f4 recorded that a new network file share was published. The event references principal-604eb4041d82448c. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Event service audit on ENGINEERING-ASSET-93dff18c1d7d23e9 recorded that an event log was cleared by a privileged request. The event references principal-32227ffe2b6b23ca. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Kubernetes audit on SALES-ASSET-ffd4e9bc10275050 recorded that a pod was created with privileged execution enabled. The event references principal-02bcfaa51dffcded. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Windows logon audit on LEGAL-ASSET-30d47fccd7c65f45 recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-5fc9e45b889f41d1. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Mail audit on FINANCE-ASSET-ea1b6c24422b456d recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-44026a910bd0b4c9. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Kubernetes audit on COMMUNICATIONS-ASSET-396281c213cbfe7d recorded that a role binding granted a principal additional cluster permissions. The event references principal-490795a3fa64d894. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Smb audit on FINANCE-ASSET-c99a2728b7b98f2b recorded that a session enumerated a file share and read multiple files. The event references principal-40d6614472abce2d. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Kubernetes audit on OPERATIONS-ASSET-914b85ff52bb152e recorded that a role binding granted a principal additional cluster permissions. The event references principal-23475897d2814771. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Device and file audit on PEOPLE-ASSET-6b2be688c0738ea2 recorded that files were copied to a removable storage device. The event references principal-cb796dfd2a52dfa6. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Identity audit on PROCUREMENT-ASSET-3df9ef7ebe927a33 recorded that an account registered a new MFA method. The event references principal-8231b7a1d02ca56c. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Backup audit on SUPPORT-ASSET-cc26a0f722f080c9 recorded that a backup retention policy was shortened. The event references principal-d64cfde7265390a0. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-5f9ce19e951f, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Firewall audit on PROCUREMENT-ASSET-2bed3490436bbbc8 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-90a45122531200f3. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Device and file audit on SALES-ASSET-3b11bf4bc19f47f9 recorded that files were copied to a removable storage device. The event references principal-342176cf658025b8. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Application audit on RESEARCH-ASSET-11f390ae672643c2 recorded that a runtime configuration setting was updated. The event references principal-1a691de3cb24648f. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Function audit on PEOPLE-ASSET-7a184783e26cf4b6 recorded that a serverless function package and execution settings were updated. The event references principal-20e08b043fa3eb3a. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Firewall audit on COMMUNICATIONS-ASSET-4f1cc73dbbdce003 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-3c942f0a8856cd1e. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Oauth audit on SALES-ASSET-8a294b7f6b4fb5ec recorded that an application received consent for additional account scopes. The event references principal-4be7952cadd1c600. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Cloud control audit on PEOPLE-ASSET-357f734fad0406df recorded that a session deleted a group of cloud resources. The event references principal-50a694af17f32a70. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Account audit on LEGAL-ASSET-00d4a961cd35ae5d recorded that a local user account was created on a managed system. The event references principal-ffacf4516ce71040. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Cloud control audit on FINANCE-ASSET-f3ec32c70b0e59d9 recorded that resources were created in a region with little prior activity. The event references principal-8d633cfbda070abb. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Module audit on FINANCE-ASSET-6b165174917b5734 recorded that a process loaded a library from an application-local directory. The event references principal-ecca7e9b2841d1cc. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Ci secret audit on LEGAL-ASSET-210117fa7f63e7fa recorded that a build job requested a protected pipeline secret. The event references principal-bafb03e4143599bb. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Event service audit on RESEARCH-ASSET-79d1b62714d14ec4 recorded that an event log was cleared by a privileged request. The event references principal-78e29e015c8aeb2f. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Database audit on LEGAL-ASSET-3632866debb967ca recorded that a session changed a database table definition. The event references principal-862aa2954135f309. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-41b98ada4784 match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Driver audit on FINANCE-ASSET-4d3885b7e2a2eaaa recorded that a kernel driver was loaded after a package installation. The event references principal-93dddd296bcd4a0a. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Directory audit on SALES-ASSET-59c719c0c63878b3 recorded that a principal requested directory replication data. The event references principal-cb15573feb355e86. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-342730cb2714 match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"File audit on PEOPLE-ASSET-572ab49b4fda25fd recorded that access permissions were broadened on a directory tree. The event references principal-892e9ce9179f90fe. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Saas audit on SALES-ASSET-3ad767047dba4a21 recorded that a user requested a bulk export from a business application. The event references principal-b81a4cbeea8a89df. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Security retest SEC-fda6895f2225 covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Dhcp telemetry on LEGAL-ASSET-5112544cfce28921 recorded that a server issued DHCP offers on a monitored segment. The event references principal-176187e9b5662d2e. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Gateway logs on COMMUNICATIONS-ASSET-01bdebe9cfb40e2b recorded that a client established a long-lived encapsulated network session. The event references principal-298b7f8258456986. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Waf logs on RESEARCH-ASSET-f279330020f0e645 recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-a38184b376034ec2. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Browser audit on SALES-ASSET-2c13db88f9fe11a1 recorded that a browser extension with page-reading permissions was installed. The event references principal-dfbfeb6ce6f75d60. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Package registry audit on PEOPLE-ASSET-63788b9d7987296c recorded that a principal published a new package version. The event references principal-1efd21efeb7b167e. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Systemd audit on SALES-ASSET-4e41129f633ac17f recorded that a service unit file was changed and the unit reloaded. The event references principal-6e1812150b898dbc. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-ffa9ced26248 match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Wmi audit on PEOPLE-ASSET-0793506618492b13 recorded that a management request started a process through WMI. The event references principal-517018be0d1cff5c. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Secret manager audit on RESEARCH-ASSET-9ed518d17fe68d7a recorded that a workload read several secret versions. The event references principal-7f1b48c31f4c5822. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-c4881fb82fa2 specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Kubernetes audit on LEGAL-ASSET-3c1eaaf59969b766 recorded that a workload mounted a directory from its host filesystem. The event references principal-a5edc19c7aca724f. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Pki audit on PROCUREMENT-ASSET-4fa9108f30037594 recorded that a principal requested a certificate using an authentication template. The event references principal-7c9716b1c94aea0e. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-073d4db3f5b8 explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Storage audit on OPERATIONS-ASSET-07e77010a446667b recorded that a session deleted several storage snapshots. The event references principal-fc81340c87f20845. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Identity audit on SUPPORT-ASSET-15695a645557b69f recorded that repeated failed sign-ins were recorded for an account. The event references principal-51d00d36a920ed83. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"File audit on PROCUREMENT-ASSET-f66c7d2cd9a00208 recorded that a process compressed files from several directories into an archive. The event references principal-1608ac7a92b15a7f. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-7e87fe2aa5e2 match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Mail and proxy logs on PEOPLE-ASSET-73f46f787c3750bc recorded that a user opened a URL delivered in an email message. The event references principal-ae3654afd7401601. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-17bd3eef08c5, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Module audit on LEGAL-ASSET-2be7e49aaf02b41c recorded that a process loaded a library from an application-local directory. The event references principal-8d4bc02ab462cace. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Cloud identity audit on ENGINEERING-ASSET-02b155235f1959ea recorded that a principal received a policy granting additional permissions. The event references principal-d5dc51acc5293d03. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Egress flow logs on ENGINEERING-ASSET-244beee7b921f878 recorded that a workload opened an encrypted connection to an external service. The event references principal-0a5b130156e24d17. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Ci secret audit on OPERATIONS-ASSET-e1c6669f5f29a589 recorded that a build job requested a protected pipeline secret. The event references principal-e8010ec93fff4989. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Saas audit on SUPPORT-ASSET-2e07b9359e958267 recorded that a user requested a bulk export from a business application. The event references principal-b7211075b62be127. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Cloud identity audit on ENGINEERING-ASSET-00c2f8de5ff4a52c recorded that a principal assumed a role in another account. The event references principal-4cb5db7ee766c0fa. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-67dbd4556ef3, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Process access audit on SUPPORT-ASSET-a8d87f27cfdb843f recorded that a process requested read access to another process memory space. The event references principal-8eabe5478e5a2271. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-753beeb96df5 specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Dhcp telemetry on ENGINEERING-ASSET-16a2bd6b5dab3cb6 recorded that a server issued DHCP offers on a monitored segment. The event references principal-d5a61a238fb861fb. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Process audit on COMMUNICATIONS-ASSET-332afb2165aa1448 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-afe5b84c8ef31787. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-aadb3c045a0e match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Identity audit on COMMUNICATIONS-ASSET-4abec775a52c95c2 recorded that repeated failed sign-ins were recorded for an account. The event references principal-a42f44848e926187. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Resolver logs on LEGAL-ASSET-3fa235a88f26dc9e recorded that a client requested many long, high-entropy DNS labels. The event references principal-1767397f4dd4b5b0. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Egress flow logs on RESEARCH-ASSET-33b44f93ed777432 recorded that a workload opened an encrypted connection to an external service. The event references principal-33501a4209ab69ba. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Process audit on LEGAL-ASSET-8a212c2ca8ae49ba recorded that a Python interpreter loaded a script and contacted a service. The event references principal-a6319754fd6d1b91. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-a5caa7ca28c5 match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Session audit on PEOPLE-ASSET-2f7cb210c1411ef5 recorded that the same session token appeared from different client addresses. The event references principal-254fb3d8a50b95f2. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"File audit on SALES-ASSET-f998f822d677efcd recorded that a process rewrote multiple files into encrypted containers. The event references principal-354f7ba2d1c31de7. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-f6a9a074fa9b before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Process access audit on PEOPLE-ASSET-e69cbb53fe5c9e6a recorded that a process requested read access to another process memory space. The event references principal-b9eeb1db9d8c686f. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Backup audit on SUPPORT-ASSET-cc26a0f722f080c9 recorded that a backup retention policy was shortened. The event references principal-d64cfde7265390a0. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Kerberos audit on PROCUREMENT-ASSET-f07f0980cf620efa recorded that an account requested service tickets for multiple services. The event references principal-6dd83c14e2a9dd31. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-31a805cc0a9d, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Api gateway logs on OPERATIONS-ASSET-5d940a8c3c4b311c recorded that a client issued a burst of API requests. The event references principal-9965146148dbdc29. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-4e095d7a4c55 before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Service audit on PEOPLE-ASSET-7556bd332c3c0972 recorded that a remote service-control request created and started a temporary service. The event references principal-40ab931ed8bd0b59. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Mail audit on RESEARCH-ASSET-0a4e5d836144a737 recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-3b98b2ee8f80fa29. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Module audit on FINANCE-ASSET-6b165174917b5734 recorded that a process loaded a library from an application-local directory. The event references principal-ecca7e9b2841d1cc. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Kubernetes audit on PROCUREMENT-ASSET-8857c7021ba70cdd recorded that a cluster admission policy was changed. The event references principal-0637e683dcd7afbd. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Cloud identity audit on SUPPORT-ASSET-d4887989aac3f6e3 recorded that a principal assumed a role in another account. The event references principal-ccdf0cbbc01cef8e. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Process audit on PEOPLE-ASSET-b5f000212e4e1683 recorded that a Python interpreter loaded a script and contacted a service. The event references principal-364f40722069431e. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Directory audit on OPERATIONS-ASSET-f0615ba52c4fafcb recorded that a principal requested directory replication data. The event references principal-c94c73361a03e2ca. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-9986197c0c6a match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Kubernetes audit on RESEARCH-ASSET-ca81e4dea7e4d440 recorded that a workload mounted a directory from its host filesystem. The event references principal-142014dd00377291. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-7ea4c276c605 accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Code integrity audit on RESEARCH-ASSET-b23d57d440170815 recorded that an executable without a publisher signature started from a writable directory. The event references principal-a70693803f9dbb50. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Kubernetes audit on PROCUREMENT-ASSET-2f62998057d28724 recorded that a role binding granted a principal additional cluster permissions. The event references principal-4457a8d289298830. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Process audit on SALES-ASSET-796c322bf9ce4051 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-eb12aa9934f163d5. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-f5fec0df3509 accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Compute audit on PROCUREMENT-ASSET-507dec859fa3003b recorded that a principal launched multiple compute instances. The event references principal-611c292a786d76ca. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Module audit on LEGAL-ASSET-2be7e49aaf02b41c recorded that a process loaded a library from an application-local directory. The event references principal-8d4bc02ab462cace. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Assessment SEC-4d69547aa5b7 explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Agent audit on SALES-ASSET-4f0c6ee9e7bb90ab recorded that a privileged session changed endpoint monitoring settings. The event references principal-b547aa127479e0eb. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Registry audit on LEGAL-ASSET-d0480e188fd31f60 recorded that a workload pulled a container image from a registry. The event references principal-160b2d0cefee47e2. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Service audit on OPERATIONS-ASSET-53e47c7270341ae1 recorded that a remote service-control request created and started a temporary service. The event references principal-ae8a8a74a000dff1. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Cloud control audit on ENGINEERING-ASSET-2f0ebfbab41474df recorded that a session deleted a group of cloud resources. The event references principal-eab0d8cb49ca354d. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Windows logon audit on SALES-ASSET-6ef3ee3501c6fc3e recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-9c0f223e81092f12. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-04329f2bdb2b specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Compute audit on PROCUREMENT-ASSET-507dec859fa3003b recorded that a principal launched multiple compute instances. The event references principal-611c292a786d76ca. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-f18ef81a9679 specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Gateway logs on FINANCE-ASSET-0eba77ccb6dbdba6 recorded that a client established a long-lived encapsulated network session. The event references principal-5f89b733086ddfa5. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Cloud identity audit on ENGINEERING-ASSET-02b155235f1959ea recorded that a principal received a policy granting additional permissions. The event references principal-d5dc51acc5293d03. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Process audit on LEGAL-ASSET-ffdcc64fc856fa3d recorded that a JavaScript interpreter executed a local script. The event references principal-a45f3b91beb56205. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Assessment SEC-d8d923cb9588 explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Database audit on COMMUNICATIONS-ASSET-b51d02175f1c9085 recorded that a session read several tables and exported the query result. The event references principal-61c8ab03c285a7c1. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Kubernetes audit on COMMUNICATIONS-ASSET-f76c1c782f04bc0e recorded that a workload mounted a directory from its host filesystem. The event references principal-ea22af4c35053180. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Systemd audit on LEGAL-ASSET-1602066d8a3d5246 recorded that a service unit file was changed and the unit reloaded. The event references principal-cdc1cfc697d46ed4. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Winrm audit on SUPPORT-ASSET-635c3348db734709 recorded that a remote management session invoked a command on a managed host. The event references principal-f79466b09a2bb0fa. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Process access audit on RESEARCH-ASSET-d44095e784b89a49 recorded that a process requested read access to another process memory space. The event references principal-961efc1f116f534c. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Wmi audit on SUPPORT-ASSET-3ffcf7de08c7ab9e recorded that a management request started a process through WMI. The event references principal-6bf936da5c9a2c76. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Systemd audit on ENGINEERING-ASSET-0abbd02cc9ffea8d recorded that a service unit file was changed and the unit reloaded. The event references principal-7986cde737b4fe49. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Mail audit on PROCUREMENT-ASSET-57a43dc80cfc93ed recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-40142beb1db7ce4d. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Identity audit on LEGAL-ASSET-10052cae7e6f5c6e recorded that an account password was reset through a recovery workflow. The event references principal-69df9c6ec5ef584b. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-9420679a032c, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Cloud control audit on SUPPORT-ASSET-e66fe35db626a7f0 recorded that resources were created in a region with little prior activity. The event references principal-84f7c4bc4b40ce6e. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Wmi audit on SUPPORT-ASSET-3ffcf7de08c7ab9e recorded that a management request started a process through WMI. The event references principal-6bf936da5c9a2c76. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Dhcp telemetry on PROCUREMENT-ASSET-40822febba29ea21 recorded that a server issued DHCP offers on a monitored segment. The event references principal-140fc1a13a173a5d. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Pki audit on COMMUNICATIONS-ASSET-a88e156f33159899 recorded that a principal requested a certificate using an authentication template. The event references principal-0a19afbf9253f4fc. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Task scheduler audit on SUPPORT-ASSET-fe6538271f60c593 recorded that a scheduled task was registered to execute a program at logon. The event references principal-a844a2602a6529d6. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Compute audit on RESEARCH-ASSET-d341eca93691633b recorded that a principal launched multiple compute instances. The event references principal-cf04d4cb340e6373. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-e0312841dcdd match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Task scheduler audit on PROCUREMENT-ASSET-bd3697f2e2b8950e recorded that a scheduled task was registered to execute a program at logon. The event references principal-1483881099fae9be. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Application audit on SALES-ASSET-9a8acf9f0cbf6165 recorded that an application read clipboard contents repeatedly. The event references principal-114c22ed14b6a3d7. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Macos launch audit on COMMUNICATIONS-ASSET-a6af7f5427b7cdc8 recorded that a launch agent definition was installed in a user context. The event references principal-1aeb8103bbf51c1f. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-4dbae22ab73b accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Windows logon audit on FINANCE-ASSET-08f4600838c704c1 recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-9a25429fc1580f3b. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Flow logs on ENGINEERING-ASSET-eb2e69d274ba28c2 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-95a534f7e0b0cad5. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Mail flow logs on OPERATIONS-ASSET-b187da0291cabbc9 recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-3df241ac15d172ff. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Change CHG-54539ebdf474 lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Waf logs on LEGAL-ASSET-558884e90876ee10 recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-3ea85690224829da. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"File access audit on OPERATIONS-ASSET-1494559c806dea5d recorded that a process opened a local credential-store file. The event references principal-c4b1fa13e42018fb. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Process audit on ENGINEERING-ASSET-2b855d0d88712cb8 recorded that a JavaScript interpreter executed a local script. The event references principal-3943e4c085d81398. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Ssh audit on ENGINEERING-ASSET-3a8203b9b7564af2 recorded that an SSH session opened and requested elevated command execution. The event references principal-f927bd6e5e00e3e2. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-5bfd8dc1b6b2, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Identity audit on LEGAL-ASSET-3e81b75ec6767272 recorded that repeated failed sign-ins were recorded for an account. The event references principal-4e9f85f638a1922a. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Registry audit on FINANCE-ASSET-7f731069af53e8e1 recorded that a workload pulled a container image from a registry. The event references principal-b80084fb240685bf. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Flow logs on PROCUREMENT-ASSET-6efd3fd7c57f6ea6 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-2f79b909f0a96c76. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-511018847469 match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Dns server audit on PROCUREMENT-ASSET-e8eb2bcb15a480a1 recorded that a client requested a DNS zone transfer. The event references principal-937daedbc93fd7dd. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Assessment SEC-f4366df64a20 explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Configuration audit on COMMUNICATIONS-ASSET-6d0a4b6d77bc51b5 recorded that a client proxy setting was changed. The event references principal-096d695d5dfbc71f. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Kubernetes audit on SALES-ASSET-b7d7628f8816a948 recorded that a role binding granted a principal additional cluster permissions. The event references principal-76cb7e33983ecb6a. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Pki audit on SUPPORT-ASSET-70be4dd0be19b589 recorded that a principal requested a certificate using an authentication template. The event references principal-3490e3ca6541e91e. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-3de4617f4158 before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Registry audit on COMMUNICATIONS-ASSET-c99d7ada90aece83 recorded that a workload pulled a container image from a registry. The event references principal-c5705a8b2e1e260b. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Dns server audit on RESEARCH-ASSET-ea10daa512b8b485 recorded that a client requested a DNS zone transfer. The event references principal-8e8e3e27caaa4cef. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Registry audit on COMMUNICATIONS-ASSET-bfd346cad4d024a4 recorded that a registry logon-start entry was created. The event references principal-74f1b84012bd604a. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Registry audit on FINANCE-ASSET-6f5ecd36af234140 recorded that a registry logon-start entry was created. The event references principal-ce9587e0dadb3215. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Group audit on PROCUREMENT-ASSET-b50d9791f482d6f4 recorded that an account was added to a privileged local group. The event references principal-c07c3b076842f6c0. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Kubernetes audit on PEOPLE-ASSET-95c9822ffcf4a444 recorded that a cluster admission policy was changed. The event references principal-e51b094fe6b69872. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Storage audit on PROCUREMENT-ASSET-283ac93c3c2be26b recorded that a session deleted several storage snapshots. The event references principal-84f457c32ccdb7a6. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Change CHG-070258039740 lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Systemd audit on ENGINEERING-ASSET-0abbd02cc9ffea8d recorded that a service unit file was changed and the unit reloaded. The event references principal-7986cde737b4fe49. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Kubernetes audit on PROCUREMENT-ASSET-8857c7021ba70cdd recorded that a cluster admission policy was changed. The event references principal-0637e683dcd7afbd. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Configuration audit on ENGINEERING-ASSET-05746d5c7e76781e recorded that a client proxy setting was changed. The event references principal-f4f857793a1cd276. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Event service audit on PEOPLE-ASSET-3e7af42f465f079f recorded that an event log was cleared by a privileged request. The event references principal-7e44d019c9f83317. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Security retest SEC-49d281fc1c3c covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Office audit on SUPPORT-ASSET-b861b71047f83874 recorded that a document macro launched a child interpreter. The event references principal-41f626db101e0b15. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Session audit on LEGAL-ASSET-a93d2c4f4ac53314 recorded that the same session token appeared from different client addresses. The event references principal-4ff9816ed8758404. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Dns control audit on SALES-ASSET-47a87d0c2fc4257b recorded that an authoritative DNS record was updated. The event references principal-3d712bbcbd3470d6. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Database audit on COMMUNICATIONS-ASSET-b51d02175f1c9085 recorded that a session read several tables and exported the query result. The event references principal-61c8ab03c285a7c1. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-68d6c9f266e6 accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Flow logs on LEGAL-ASSET-fa7ff1fc0a223203 recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-1ef2548f2594a804. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Flow logs on RESEARCH-ASSET-6a2a326a382bb0b4 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-56d66c0e0a2c4463. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Runtime audit on OPERATIONS-ASSET-b6b114583f048adf recorded that a process connected to the container runtime socket. The event references principal-2a53a47b4b50aacf. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-6dc1dce0e28e before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Registry audit on PROCUREMENT-ASSET-623aa42bae025131 recorded that a registry logon-start entry was created. The event references principal-9f2c57eab5b3cfda. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Script audit on PROCUREMENT-ASSET-d3383e3f3b9c4acb recorded that a script interpreter decoded an encoded argument before execution. The event references principal-b7570e0e965cd679. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Change CHG-db0a659d6762 lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Dhcp telemetry on COMMUNICATIONS-ASSET-a7af3c886d8ee570 recorded that a server issued DHCP offers on a monitored segment. The event references principal-aa2878e706226d96. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"File audit on OPERATIONS-ASSET-a72fe66e9e140fe9 recorded that a process compressed files from several directories into an archive. The event references principal-41403cc0bff319ee. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Ci audit on RESEARCH-ASSET-1bb40eb620dce13c recorded that a build pipeline definition gained a new execution step. The event references principal-1e7493e87ff48bbe. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Certificate audit on OPERATIONS-ASSET-3ca9753ca5075c61 recorded that a service certificate was replaced. The event references principal-15f1c60782059a24. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Mail and proxy logs on SALES-ASSET-86e0136e86dcbb64 recorded that a user opened a URL delivered in an email message. The event references principal-090cc1db12274cd7. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Ci secret audit on SALES-ASSET-ad09caa9a6596785 recorded that a build job requested a protected pipeline secret. The event references principal-5cac9dd38eee5122. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Browser audit on ENGINEERING-ASSET-f6edb397c93f1bb4 recorded that a browser extension with page-reading permissions was installed. The event references principal-bf7a3feca21483cd. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Kubernetes audit on COMMUNICATIONS-ASSET-789b240d08ec701b recorded that a pod was created with privileged execution enabled. The event references principal-bd54f828538e68ca. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"File audit on SUPPORT-ASSET-5e6185480b7124c6 recorded that a shell startup profile gained an additional command. The event references principal-51f94e540bbb4321. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Identity audit on LEGAL-ASSET-10052cae7e6f5c6e recorded that an account password was reset through a recovery workflow. The event references principal-69df9c6ec5ef584b. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Cloud identity audit on SUPPORT-ASSET-d4887989aac3f6e3 recorded that a principal assumed a role in another account. The event references principal-ccdf0cbbc01cef8e. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-ccb1da25e3a3 accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Kerberos audit on PROCUREMENT-ASSET-f07f0980cf620efa recorded that an account requested service tickets for multiple services. The event references principal-6dd83c14e2a9dd31. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Identity audit on PEOPLE-ASSET-5f5eb7d500371474 recorded that an account registered a new MFA method. The event references principal-7c9584053a66a813. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Mfa audit on ENGINEERING-ASSET-4741e70baa0f7c7a recorded that multiple MFA challenges were issued during a short interval. The event references principal-7a266bf7aed055c1. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-c0f4f9da777b specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Repository audit on FINANCE-ASSET-dc6e3bd56c8a0a87 recorded that a repository collaborator received elevated permissions. The event references principal-28c1f6e75f00c284. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Security retest SEC-77e5e3928a51 covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Service audit on LEGAL-ASSET-c27c6fe8739fc291 recorded that a remote service-control request created and started a temporary service. The event references principal-473978dbe47e2846. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Dns server audit on RESEARCH-ASSET-ea10daa512b8b485 recorded that a client requested a DNS zone transfer. The event references principal-8e8e3e27caaa4cef. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Security retest SEC-c16d719a8f2e covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Ssh audit on COMMUNICATIONS-ASSET-c7c949ba2f23f6e5 recorded that an SSH session opened and requested elevated command execution. The event references principal-3a7b389506fbf3c1. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-f244ef337f31 accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Winrm audit on FINANCE-ASSET-f7f3ea9e3a52d83c recorded that a remote management session invoked a command on a managed host. The event references principal-13d8273b51b14066. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Assessment SEC-a18264203472 explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Flow logs on OPERATIONS-ASSET-edf434a71b109006 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-16d324cd052a6682. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Identity audit on SALES-ASSET-08c0f29601b74bfa recorded that an account registered a new MFA method. The event references principal-4c8bc42872a0ca65. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Certificate audit on PEOPLE-ASSET-4d0259660c317b95 recorded that a service certificate was replaced. The event references principal-f191ea3a323e48f8. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Office audit on SALES-ASSET-bd4695abc7ff04ad recorded that a document macro launched a child interpreter. The event references principal-9bfaf02fa70a4f6b. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Security retest SEC-17e48eb573c0 covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Cloud identity audit on SUPPORT-ASSET-0acaf32cb86c9787 recorded that a new programmatic access key was issued to a principal. The event references principal-f4c6ed272feaab73. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"File access audit on ENGINEERING-ASSET-9bb4a75d3491a9be recorded that a process opened a local credential-store file. The event references principal-f9c37bdee298aeea. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Smb audit on SALES-ASSET-f9e0160f65640ecb recorded that a session enumerated a file share and read multiple files. The event references principal-5b93bfe2ff3ce2df. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Service audit on RESEARCH-ASSET-8d77d8342c20fbff recorded that a remote service-control request created and started a temporary service. The event references principal-211275ad14685644. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Certificate audit on FINANCE-ASSET-e16767dd715979b6 recorded that a service certificate was replaced. The event references principal-f8a1311de5964c87. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Wmi audit on OPERATIONS-ASSET-c2921eb1d36d866a recorded that a management request started a process through WMI. The event references principal-1c1a48cb243f47fb. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Office audit on OPERATIONS-ASSET-a21bbd8f65591dc7 recorded that a document macro launched a child interpreter. The event references principal-640ebd4004779cca. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Secret manager audit on SALES-ASSET-b73f8978ef6e4f27 recorded that a workload read several secret versions. The event references principal-d6b84c181926e6a9. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-2b7d0a97534d match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Kubernetes audit on SALES-ASSET-0cbf08d6604881c3 recorded that a workload mounted a directory from its host filesystem. The event references principal-df9957e225592b1d. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Assessment SEC-cbce8a8d5c88 explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Cloud control audit on RESEARCH-ASSET-2cbe7527ba09f822 recorded that resources were created in a region with little prior activity. The event references principal-3490db46f4cacc07. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Policy audit on PROCUREMENT-ASSET-f2878461512a2696 recorded that an audit policy was changed to collect fewer event categories. The event references principal-2bb61efdeda82dac. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Dns server audit on SALES-ASSET-76b84b3e5488545e recorded that a client requested a DNS zone transfer. The event references principal-2d34f2bcf00115a7. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-2435de04b5c4 explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Waf logs on PROCUREMENT-ASSET-be57d152ab66f42b recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-c19a63b81ac51b37. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-490d2194478e specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Database audit on RESEARCH-ASSET-0df9b1ba7848d017 recorded that a session read several tables and exported the query result. The event references principal-78007df53b70739e. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Assessment SEC-e10b975df468 explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Code integrity audit on SUPPORT-ASSET-d243663dca87b63a recorded that an executable without a publisher signature started from a writable directory. The event references principal-ac7fc8d288d921e2. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Process audit on RESEARCH-ASSET-701eef6083bb4949 recorded that a Python interpreter loaded a script and contacted a service. The event references principal-9ed7f8cc72bbc316. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Application audit on OPERATIONS-ASSET-82d2279115651372 recorded that an application read clipboard contents repeatedly. The event references principal-d93f4c8e19d295a8. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-49cd5ed18f81 explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Winrm audit on ENGINEERING-ASSET-6e5e1ed61987467a recorded that a remote management session invoked a command on a managed host. The event references principal-c372b39c0d58be55. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Repository audit on SALES-ASSET-60f45c01cacb2ad7 recorded that a repository collaborator received elevated permissions. The event references principal-59983edc6542b65a. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Repository audit on RESEARCH-ASSET-ddfa89ff412603e8 recorded that a user cloned several source repositories. The event references principal-a086fb65d451cd31. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-704824135431 specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Gateway logs on LEGAL-ASSET-4deff653cf2694f9 recorded that a client established a long-lived encapsulated network session. The event references principal-76329b77e1b0e6b1. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Kubernetes audit on ENGINEERING-ASSET-74d13411d760b9a6 recorded that a role binding granted a principal additional cluster permissions. The event references principal-dbf4764de8118d40. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Identity audit on FINANCE-ASSET-17a7d4bc3e0dfc99 recorded that a service account established an interactive session. The event references principal-ba443b5f7751e8bc. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Winrm audit on LEGAL-ASSET-6240747fe412756f recorded that a remote management session invoked a command on a managed host. The event references principal-bff5de31e17ff348. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Database audit on PROCUREMENT-ASSET-88d6e016f81704ea recorded that a session changed a database table definition. The event references principal-a7367e91f7bc0a1d. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Repository audit on SUPPORT-ASSET-fb6027084fb1957b recorded that a user cloned several source repositories. The event references principal-6318dd66af34e88b. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Wmi audit on FINANCE-ASSET-9fd34fa594551e66 recorded that a management request started a process through WMI. The event references principal-1f38151c7990e366. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-845038adcea7 explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Flow logs on LEGAL-ASSET-fa7ff1fc0a223203 recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-1ef2548f2594a804. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Process audit on ENGINEERING-ASSET-db715ea0863774ba recorded that a remote-support application started an interactive session. The event references principal-ca4d1a946cc4272b. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"File audit on LEGAL-ASSET-4a73488ba2d33df6 recorded that a process rewrote multiple files into encrypted containers. The event references principal-9d7037ae8c34aa83. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Cloud control audit on SALES-ASSET-c5ac5bf2061a85e1 recorded that resources were created in a region with little prior activity. The event references principal-213b93a3248e4777. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-eeab5ca29100 match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Process access audit on PEOPLE-ASSET-e69cbb53fe5c9e6a recorded that a process requested read access to another process memory space. The event references principal-b9eeb1db9d8c686f. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-3af3a18d3709 match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Smb audit on COMMUNICATIONS-ASSET-88088ffb8b08e158 recorded that a session enumerated a file share and read multiple files. The event references principal-82b755f6442bfd40. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Repository audit on ENGINEERING-ASSET-19fede4e07d7366c recorded that a repository collaborator received elevated permissions. The event references principal-22c3a4b3adce2401. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-59dfcb263fbe explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Ci secret audit on ENGINEERING-ASSET-2fc72026491758e8 recorded that a build job requested a protected pipeline secret. The event references principal-ef329c66a1330a2f. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Egress flow logs on ENGINEERING-ASSET-244beee7b921f878 recorded that a workload opened an encrypted connection to an external service. The event references principal-0a5b130156e24d17. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-e7776854d5cd explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Service audit on SALES-ASSET-fffc2b9a7422ce6b recorded that a remote service-control request created and started a temporary service. The event references principal-ab058eda0f6e9097. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-c605f1192ab5 accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Ssh audit on PROCUREMENT-ASSET-76513cf046529603 recorded that an SSH session opened and requested elevated command execution. The event references principal-5b3a8f0f85403c14. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Service audit on LEGAL-ASSET-c27c6fe8739fc291 recorded that a remote service-control request created and started a temporary service. The event references principal-473978dbe47e2846. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-734d274f478e match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Cron audit on LEGAL-ASSET-fa5ca79bc164009d recorded that a recurring job definition was added to the system schedule. The event references principal-07e12ac009730cba. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Directory audit on SALES-ASSET-59c719c0c63878b3 recorded that a principal requested directory replication data. The event references principal-cb15573feb355e86. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Compute audit on OPERATIONS-ASSET-ac6d22bf5640da77 recorded that a principal launched multiple compute instances. The event references principal-dec83605ca771167. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"File audit on PEOPLE-ASSET-cc74b22d2c2ca8f7 recorded that a process compressed files from several directories into an archive. The event references principal-e9c54c5535050840. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-f58b61eba89c, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Script audit on FINANCE-ASSET-8f7a7c5dae3d75b5 recorded that a script interpreter decoded an encoded argument before execution. The event references principal-7a6a17f9162097f1. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Identity audit on PEOPLE-ASSET-d81992a54d0e0cd4 recorded that a service account established an interactive session. The event references principal-0bc399328dfcae48. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Proxy logs on LEGAL-ASSET-11a1797ca70316c7 recorded that a client transferred a large payload to an external storage endpoint. The event references principal-0b83b39a8d8a6fb4. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Mail and proxy logs on PEOPLE-ASSET-73f46f787c3750bc recorded that a user opened a URL delivered in an email message. The event references principal-ae3654afd7401601. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Device and file audit on PROCUREMENT-ASSET-804fb2eb4bbf7ddf recorded that files were copied to a removable storage device. The event references principal-25d93f161d21c79f. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"File audit on PROCUREMENT-ASSET-de47614145685908 recorded that a shell startup profile gained an additional command. The event references principal-602bb5bc7aad1155. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Process audit on LEGAL-ASSET-ffdcc64fc856fa3d recorded that a JavaScript interpreter executed a local script. The event references principal-a45f3b91beb56205. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Mail and proxy logs on RESEARCH-ASSET-0d6948f11ee5b28e recorded that a user opened a URL delivered in an email message. The event references principal-fdb003c9c4c80093. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Ci secret audit on OPERATIONS-ASSET-e1c6669f5f29a589 recorded that a build job requested a protected pipeline secret. The event references principal-e8010ec93fff4989. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Process access audit on LEGAL-ASSET-60fd34b6e0203a0f recorded that a process requested read access to another process memory space. The event references principal-1e4fdc2f020fb533. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Application audit on LEGAL-ASSET-2b053903e1a723bb recorded that an application read clipboard contents repeatedly. The event references principal-36dbf50d505a5d2a. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Macos launch audit on SALES-ASSET-9700c4adcf12629e recorded that a launch agent definition was installed in a user context. The event references principal-fd31ea054fd63d39. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Repository audit on PEOPLE-ASSET-ab514f2b7cf1ca44 recorded that a repository collaborator received elevated permissions. The event references principal-49f43d9a0cf7b13c. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Security retest SEC-fdc9cbf7ebac covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Storage audit on FINANCE-ASSET-47f72b6b10bf47c7 recorded that a session deleted several storage snapshots. The event references principal-6ce8e4c42cc80c2d. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Group audit on COMMUNICATIONS-ASSET-c7bad2289a06229c recorded that an account was added to a privileged local group. The event references principal-45633364c2ed091b. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Firewall audit on SUPPORT-ASSET-e85c56705ce7aa30 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-9b678cb3b90b393c. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Federation audit on ENGINEERING-ASSET-ed48b05a54cba0b4 recorded that a tenant federation setting was updated. The event references principal-7dac1305cd5fd7e7. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Identity audit on ENGINEERING-ASSET-17f1d906d8c35962 recorded that a service account established an interactive session. The event references principal-4e2ae7344e474fce. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-6823b059a3f0 match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"File audit on ENGINEERING-ASSET-52718af8394d4c73 recorded that a shell startup profile gained an additional command. The event references principal-7fbddd513d8c8d82. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Registry audit on FINANCE-ASSET-6f5ecd36af234140 recorded that a registry logon-start entry was created. The event references principal-ce9587e0dadb3215. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-8de00ebb0048 explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Driver audit on ENGINEERING-ASSET-aa761eb37a133a6c recorded that a kernel driver was loaded after a package installation. The event references principal-b792fcefc38ccc53. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-e6d2ff99c94e match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Kubernetes audit on LEGAL-ASSET-360df78a99aa884c recorded that a cluster admission policy was changed. The event references principal-fdbbb745932ee2f1. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-1c156e162697 specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Browser audit on RESEARCH-ASSET-b0be4ff24f6a9c7d recorded that a browser extension with page-reading permissions was installed. The event references principal-c445644ab42572e7. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Database audit on OPERATIONS-ASSET-dec2bfd2d0808b67 recorded that a session changed a database table definition. The event references principal-0583f5a376c3e442. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Application audit on PEOPLE-ASSET-fcad7cf3be4e4115 recorded that a runtime configuration setting was updated. The event references principal-1c596d52504e0c0f. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"File access audit on PEOPLE-ASSET-4246817b50ce1d24 recorded that a process opened a local credential-store file. The event references principal-69567a3aa8e45657. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Dns server audit on SUPPORT-ASSET-99242b48e0f1290b recorded that a client requested a DNS zone transfer. The event references principal-c5b7de8a13a46984. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Application audit on PEOPLE-ASSET-b6c838eeab685d8f recorded that an application requested repeated screen captures. The event references principal-22d369aeea462cc7. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Database audit on PROCUREMENT-ASSET-e086d2946f81e9d3 recorded that a session read several tables and exported the query result. The event references principal-6283c0702f8c752e. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Macos launch audit on PEOPLE-ASSET-f2ccd0993eb11ff9 recorded that a launch agent definition was installed in a user context. The event references principal-ff81666bc8b89437. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Change CHG-20b5cf30f87e lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Mail audit on RESEARCH-ASSET-fad2d601f38f7cda recorded that an account received delegated access to a mailbox. The event references principal-b5e074cc28811f03. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Dhcp telemetry on SALES-ASSET-b9c8816924ddc5c0 recorded that a server issued DHCP offers on a monitored segment. The event references principal-c2f4772a3b098c6c. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Macos launch audit on SALES-ASSET-9700c4adcf12629e recorded that a launch agent definition was installed in a user context. The event references principal-fd31ea054fd63d39. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Macos launch audit on ENGINEERING-ASSET-20d414dac3bf58ed recorded that a launch agent definition was installed in a user context. The event references principal-9f713f5b46efadf7. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-61d6fb70dda0 covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Service audit on COMMUNICATIONS-ASSET-7e54b0ca38e553fe recorded that a new automatically started service was registered. The event references principal-7d549ca6bce506ce. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-209a92ddba75, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Egress flow logs on PEOPLE-ASSET-9176797d1eb78aff recorded that a workload opened an encrypted connection to an external service. The event references principal-eeab4c2bc996daf9. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-504c2df20702, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Identity audit on FINANCE-ASSET-a32c9481137674af recorded that an account password was reset through a recovery workflow. The event references principal-b0dec7cad50c7fe1. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Federation audit on RESEARCH-ASSET-85e9941ba25e96bb recorded that a tenant federation setting was updated. The event references principal-863b72c786eda302. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"File audit on SUPPORT-ASSET-0129618ced8fc8ec recorded that a process compressed files from several directories into an archive. The event references principal-8432d907b9ba200c. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Systemd audit on PROCUREMENT-ASSET-e562e2af350db7c6 recorded that a service unit file was changed and the unit reloaded. The event references principal-a239fb376cfcf526. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Agent audit on PEOPLE-ASSET-145b133cd9883db8 recorded that a privileged session changed endpoint monitoring settings. The event references principal-3cdfd17f049efdd9. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-9749b3e190f3 specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Identity audit on SALES-ASSET-880860857ffcd92f recorded that a service account established an interactive session. The event references principal-6480886757402cfa. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Script audit on SUPPORT-ASSET-1db9fff8dffdd6e2 recorded that a script interpreter decoded an encoded argument before execution. The event references principal-cddc3f00bf167947. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-4e87278bbf8a before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Share audit on PROCUREMENT-ASSET-d3ee6d1f094d6ce0 recorded that a new network file share was published. The event references principal-9978a814a123a526. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Wmi audit on PROCUREMENT-ASSET-fda18a4350cff1b3 recorded that a management request started a process through WMI. The event references principal-cba091012017387e. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Agent audit on LEGAL-ASSET-6d17adf81f6fe3af recorded that a privileged session changed endpoint monitoring settings. The event references principal-f72780533376e28a. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Kubernetes audit on LEGAL-ASSET-82e9dc780e2f0fb0 recorded that a pod was created with privileged execution enabled. The event references principal-7d1067f1bf4b8bd0. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Api gateway logs on SALES-ASSET-67b00a7811823c9c recorded that a client issued a burst of API requests. The event references principal-0a02b6edf23f48b5. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-7a59a26bccfd specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Database audit on LEGAL-ASSET-3632866debb967ca recorded that a session changed a database table definition. The event references principal-862aa2954135f309. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-41b98ada4784 accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Application audit on PEOPLE-ASSET-b6c838eeab685d8f recorded that an application requested repeated screen captures. The event references principal-22d369aeea462cc7. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Saas audit on PROCUREMENT-ASSET-94508e8090c4e3fa recorded that a user requested a bulk export from a business application. The event references principal-d0cfd5ec7d96061d. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Saas audit on ENGINEERING-ASSET-0edd073ede2359c9 recorded that a user requested a bulk export from a business application. The event references principal-273e879f8b9e8512. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-73af046f35a0 specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Storage audit on OPERATIONS-ASSET-29e0421fa3b9bb88 recorded that an object-storage access policy was broadened. The event references principal-e4fd29cc648a5ac6. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-4648242cc648 covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Network control audit on OPERATIONS-ASSET-bd217021cb34aa91 recorded that a cloud security group gained a broad ingress rule. The event references principal-2dc6c3bb2730ad8e. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Key service audit on SUPPORT-ASSET-32d985d5324796c4 recorded that a principal issued a burst of key-service decrypt requests. The event references principal-82b70d458957b545. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Change CHG-3c094b38782f lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Repository audit on SALES-ASSET-b9ab0defeef57d69 recorded that a user cloned several source repositories. The event references principal-0da3c44a52b416ce. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Directory audit on SUPPORT-ASSET-657351ecbd6ea04f recorded that a principal requested directory replication data. The event references principal-415e143ac445aa25. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Identity audit on RESEARCH-ASSET-77b0ab4459df7f50 recorded that repeated failed sign-ins were recorded for an account. The event references principal-ef9a3ac0fa7044a5. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Storage audit on SUPPORT-ASSET-4d8e24bcff05f227 recorded that an object-storage access policy was broadened. The event references principal-5112ec3a6a51c1b1. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Cloud control audit on FINANCE-ASSET-b563459bb8af8f48 recorded that a session deleted a group of cloud resources. The event references principal-a8340a0f60620156. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-d5ee7f1c850d match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"File audit on COMMUNICATIONS-ASSET-23cdf3c51f4342c4 recorded that access permissions were broadened on a directory tree. The event references principal-fb51510da2f10fbb. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-177563af3c0f covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Application audit on SUPPORT-ASSET-bc02457e5d2c9364 recorded that an application read clipboard contents repeatedly. The event references principal-5b5cc7cba3470ef8. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-759600e2d74a explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Script audit on PROCUREMENT-ASSET-d3383e3f3b9c4acb recorded that a script interpreter decoded an encoded argument before execution. The event references principal-b7570e0e965cd679. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Dns control audit on ENGINEERING-ASSET-62a2603633015b4a recorded that an authoritative DNS record was updated. The event references principal-38391a49d25a310a. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-2ac5927929dc, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Flow logs on PROCUREMENT-ASSET-6efd3fd7c57f6ea6 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-2f79b909f0a96c76. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Application audit on PROCUREMENT-ASSET-9ae629f20e56becc recorded that a runtime configuration setting was updated. The event references principal-be5a20df9fa68e8b. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Assessment SEC-475afd67bbb7 explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Flow logs on ENGINEERING-ASSET-6ee9ce19d8b1f530 recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-5923ac86626d7de4. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Code integrity audit on SUPPORT-ASSET-d243663dca87b63a recorded that an executable without a publisher signature started from a writable directory. The event references principal-ac7fc8d288d921e2. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-d890bf9aa7dd accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Resolver logs on LEGAL-ASSET-3fa235a88f26dc9e recorded that a client requested many long, high-entropy DNS labels. The event references principal-1767397f4dd4b5b0. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Resolver logs on LEGAL-ASSET-3fa235a88f26dc9e recorded that a client requested many long, high-entropy DNS labels. The event references principal-1767397f4dd4b5b0. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Identity audit on ENGINEERING-ASSET-f3a5e6ca5f4810c3 recorded that an account registered a new MFA method. The event references principal-a81b0853166bb0e5. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-695a4bab7436 match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Mfa audit on PROCUREMENT-ASSET-9ec036de13de448d recorded that multiple MFA challenges were issued during a short interval. The event references principal-906c50bf72cf0c69. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Service audit on PROCUREMENT-ASSET-28254d89b1701083 recorded that a remote service-control request created and started a temporary service. The event references principal-cfe7f7b5911dcb16. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Vpn audit on COMMUNICATIONS-ASSET-cf88b5e111fdd1c4 recorded that a remote-access VPN session was established. The event references principal-323dccf79a1a961c. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-b91bd47acd0f accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Module audit on LEGAL-ASSET-2be7e49aaf02b41c recorded that a process loaded a library from an application-local directory. The event references principal-8d4bc02ab462cace. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Module audit on ENGINEERING-ASSET-ef21d634c2b3a94b recorded that a process loaded a library from an application-local directory. The event references principal-47653e2725b4086f. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Application audit on SALES-ASSET-5a207e0d30dc6722 recorded that an application requested repeated screen captures. The event references principal-e579eecfc7c0f733. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Code integrity audit on SALES-ASSET-c410ab31c1f04772 recorded that an executable without a publisher signature started from a writable directory. The event references principal-9e4abca76b69be64. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Smb audit on COMMUNICATIONS-ASSET-88088ffb8b08e158 recorded that a session enumerated a file share and read multiple files. The event references principal-82b755f6442bfd40. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Registry audit on COMMUNICATIONS-ASSET-c99d7ada90aece83 recorded that a workload pulled a container image from a registry. The event references principal-c5705a8b2e1e260b. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Windows logon audit on ENGINEERING-ASSET-9a2b7e9a3eb1704f recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-d502784167672763. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-ffecd7d37058 match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Application audit on PEOPLE-ASSET-16eca898293194f8 recorded that an application read clipboard contents repeatedly. The event references principal-9ece0c292d6cf355. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Winrm audit on OPERATIONS-ASSET-5123f251af3bff40 recorded that a remote management session invoked a command on a managed host. The event references principal-f7aa03e82682bdc9. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Dns control audit on COMMUNICATIONS-ASSET-9ae5b908b35b63ef recorded that an authoritative DNS record was updated. The event references principal-b17631352023456c. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Oauth audit on ENGINEERING-ASSET-6abd006369fb2ea6 recorded that an application received consent for additional account scopes. The event references principal-7b515ef2be2fa58b. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Storage access logs on SALES-ASSET-9e32b40d91582c35 recorded that a principal downloaded many objects from a storage bucket. The event references principal-71bb68cca0a6547d. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Winrm audit on SALES-ASSET-53a0ec06a529813d recorded that a remote management session invoked a command on a managed host. The event references principal-d315b25d4a3677cf. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Database audit on FINANCE-ASSET-f03ba1a6a369cf03 recorded that a session read several tables and exported the query result. The event references principal-f892103a2793bbab. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Key service audit on OPERATIONS-ASSET-a2b77b051a5e88ca recorded that a principal issued a burst of key-service decrypt requests. The event references principal-2d26323a698b32c1. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Macos launch audit on LEGAL-ASSET-924fcf03a30c9333 recorded that a launch agent definition was installed in a user context. The event references principal-188d4edbd5c47469. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-5924701f7b2a, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Cloud control audit on ENGINEERING-ASSET-2f0ebfbab41474df recorded that a session deleted a group of cloud resources. The event references principal-eab0d8cb49ca354d. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Kubernetes audit on SUPPORT-ASSET-70672b7c7f3d80de recorded that a workload mounted a directory from its host filesystem. The event references principal-bb9a9a5a1ac32931. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Flow logs on FINANCE-ASSET-a52520aa18fc5145 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-d9480c5f3eeb0f53. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Smb audit on RESEARCH-ASSET-130b1b37c48e2c18 recorded that a session enumerated a file share and read multiple files. The event references principal-143930e21a998c01. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Mail flow logs on SUPPORT-ASSET-4fe85cf52fa083ac recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-b1c48571a99cb1b2. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Cloud identity audit on PROCUREMENT-ASSET-cb3bd3ac326cf3b2 recorded that a principal assumed a role in another account. The event references principal-131a52eaecf4978f. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-5d8ac42312f8 before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Kubernetes audit on SALES-ASSET-0cbf08d6604881c3 recorded that a workload mounted a directory from its host filesystem. The event references principal-df9957e225592b1d. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Service audit on COMMUNICATIONS-ASSET-9cb10b4818b88629 recorded that a remote service-control request created and started a temporary service. The event references principal-9f1825f9f69c7e5f. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Kubernetes audit on OPERATIONS-ASSET-f1f73c739188a298 recorded that a workload mounted a directory from its host filesystem. The event references principal-5a00d24e558e0ba4. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Flow logs on SALES-ASSET-e03d7f92d970afc6 recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-7f74331f29d46d56. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Identity audit on COMMUNICATIONS-ASSET-2afac15aebb6997b recorded that an account registered a new MFA method. The event references principal-48533b26142b2db4. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Egress flow logs on LEGAL-ASSET-1a606b14eab96fee recorded that a workload opened an encrypted connection to an external service. The event references principal-d6bec1039eca165c. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Kubernetes audit on LEGAL-ASSET-360df78a99aa884c recorded that a cluster admission policy was changed. The event references principal-fdbbb745932ee2f1. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Registry audit on COMMUNICATIONS-ASSET-bfd346cad4d024a4 recorded that a registry logon-start entry was created. The event references principal-74f1b84012bd604a. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Storage audit on ENGINEERING-ASSET-cd853382d1a0a281 recorded that a session deleted several storage snapshots. The event references principal-39dd7d8e5cbb8cc6. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-835456d8a6ed before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Mail audit on LEGAL-ASSET-2836d47d3aa0d5af recorded that an account received delegated access to a mailbox. The event references principal-e1699b7a3eeb56fc. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Wmi audit on RESEARCH-ASSET-ff750cc74100e1ac recorded that a management request started a process through WMI. The event references principal-2a6d4aeffc691fda. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Assessment SEC-1d18db7ff87a explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Flow logs on COMMUNICATIONS-ASSET-9213739a917e9a5d recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-fd59ae210210a351. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Device and file audit on PEOPLE-ASSET-6b2be688c0738ea2 recorded that files were copied to a removable storage device. The event references principal-cb796dfd2a52dfa6. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Repository audit on PROCUREMENT-ASSET-032fc4cf1761029e recorded that a repository collaborator received elevated permissions. The event references principal-c9c8d15f73a824e8. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-145957eb0da9 match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Storage audit on PEOPLE-ASSET-1ba8659c3031d7f0 recorded that a session deleted several storage snapshots. The event references principal-cf538081eb476d29. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Process access audit on LEGAL-ASSET-60fd34b6e0203a0f recorded that a process requested read access to another process memory space. The event references principal-1e4fdc2f020fb533. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Certificate audit on OPERATIONS-ASSET-3ca9753ca5075c61 recorded that a service certificate was replaced. The event references principal-15f1c60782059a24. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-8b1493d8ccb3 specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Macos launch audit on SALES-ASSET-9700c4adcf12629e recorded that a launch agent definition was installed in a user context. The event references principal-fd31ea054fd63d39. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Cloud control audit on PROCUREMENT-ASSET-bf71ebbd91fab3f3 recorded that a cloud logging destination was disabled. The event references principal-24b082eff9f1c2cb. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Cloud identity audit on SALES-ASSET-8e5fe4f751d14789 recorded that a new programmatic access key was issued to a principal. The event references principal-42ddd98f6ef91f59. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Kubernetes audit on SUPPORT-ASSET-46e0923b16c1de93 recorded that a cluster admission policy was changed. The event references principal-eb0f85c559534d98. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Group audit on SALES-ASSET-0d02096325648024 recorded that an account was added to a privileged local group. The event references principal-2cfc43945d846816. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-7a8ce36a3ce8, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Ci secret audit on PROCUREMENT-ASSET-7ef0c5a6d6fc8733 recorded that a build job requested a protected pipeline secret. The event references principal-77e6930e6b3513f9. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Smb audit on PEOPLE-ASSET-d3a371e9da6189cb recorded that a session enumerated a file share and read multiple files. The event references principal-4aae8f7eba9ba686. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"File access audit on LEGAL-ASSET-c0436d9a797b6aac recorded that a process opened a local credential-store file. The event references principal-8f957f68f520d591. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-d7a98acc45a1, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Egress flow logs on PROCUREMENT-ASSET-dec31bc9d60afefc recorded that a workload opened an encrypted connection to an external service. The event references principal-552eff98281f8ed1. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Identity audit on RESEARCH-ASSET-88e52266f5af4a21 recorded that a service account established an interactive session. The event references principal-d08379cdebfa5913. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-145968eea008 match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Mail and proxy logs on FINANCE-ASSET-75c33a0daf443282 recorded that a user opened a URL delivered in an email message. The event references principal-4da288c1eb5d26af. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Application audit on FINANCE-ASSET-be2eeaec3ad85eb4 recorded that a runtime configuration setting was updated. The event references principal-1d937b1c297b00f3. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Cloud control audit on FINANCE-ASSET-f3ec32c70b0e59d9 recorded that resources were created in a region with little prior activity. The event references principal-8d633cfbda070abb. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Flow logs on FINANCE-ASSET-a52520aa18fc5145 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-d9480c5f3eeb0f53. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Storage access logs on PEOPLE-ASSET-c7aae9977fa123ac recorded that a principal downloaded many objects from a storage bucket. The event references principal-8d5cca2185bede9c. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Process access audit on COMMUNICATIONS-ASSET-5d86ffc7f1150e70 recorded that a process requested read access to another process memory space. The event references principal-4279d106b274e43e. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Session audit on FINANCE-ASSET-15bdb8a9163b0abc recorded that the same session token appeared from different client addresses. The event references principal-ce316de1911fbf84. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Policy audit on RESEARCH-ASSET-9236351eaaf332af recorded that an audit policy was changed to collect fewer event categories. The event references principal-9505995ed7eba439. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Flow logs on COMMUNICATIONS-ASSET-d5fd0288e752f79f recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-fd4faa7e0445166d. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Repository audit on SALES-ASSET-60f45c01cacb2ad7 recorded that a repository collaborator received elevated permissions. The event references principal-59983edc6542b65a. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"File audit on PEOPLE-ASSET-2821cb52cece6fb9 recorded that a shell startup profile gained an additional command. The event references principal-6665fccc697a255b. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Policy audit on SUPPORT-ASSET-6952fff6cd8e7039 recorded that an audit policy was changed to collect fewer event categories. The event references principal-c6ab36fb929298bf. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Configuration audit on RESEARCH-ASSET-c3d25c02edb1b375 recorded that a client proxy setting was changed. The event references principal-c2c0e84c38c559bb. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Winrm audit on OPERATIONS-ASSET-5123f251af3bff40 recorded that a remote management session invoked a command on a managed host. The event references principal-f7aa03e82682bdc9. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-f3d2b22e1fef match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Cloud identity audit on PROCUREMENT-ASSET-e334c75ea7c7bbae recorded that a new programmatic access key was issued to a principal. The event references principal-754b76246081ca60. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Identity audit on PEOPLE-ASSET-ab714026bdcab67f recorded that repeated failed sign-ins were recorded for an account. The event references principal-b8f5dfca5dbf6b01. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Oauth audit on LEGAL-ASSET-00c7e53409190f35 recorded that an application received consent for additional account scopes. The event references principal-aa7e16ffa8e68220. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Saas audit on FINANCE-ASSET-7dbfabaebbf506b5 recorded that a user requested a bulk export from a business application. The event references principal-147dd62c19db648c. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Macos launch audit on RESEARCH-ASSET-76ee756c91d53577 recorded that a launch agent definition was installed in a user context. The event references principal-cd202933651b57f9. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Function audit on RESEARCH-ASSET-82ba6903f0ade88c recorded that a serverless function package and execution settings were updated. The event references principal-07c155fce40b0c1d. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Identity audit on PROCUREMENT-ASSET-3df9ef7ebe927a33 recorded that an account registered a new MFA method. The event references principal-8231b7a1d02ca56c. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-68a45e2631d3 explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Api gateway logs on COMMUNICATIONS-ASSET-25487240e8c2e247 recorded that a client issued a burst of API requests. The event references principal-23ca7dbb4aa37ade. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Cloud control audit on PROCUREMENT-ASSET-bf71ebbd91fab3f3 recorded that a cloud logging destination was disabled. The event references principal-24b082eff9f1c2cb. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Dns control audit on RESEARCH-ASSET-f829e9e9bed9564b recorded that an authoritative DNS record was updated. The event references principal-9fdc73540b6a06a8. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Runtime audit on COMMUNICATIONS-ASSET-da48b46f34e4599d recorded that a process connected to the container runtime socket. The event references principal-3deaf11c55ba9307. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Gateway logs on RESEARCH-ASSET-6dcd3c5959922161 recorded that a client established a long-lived encapsulated network session. The event references principal-d901ab75b47ec726. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Application audit on LEGAL-ASSET-988ab05a6aaafddb recorded that a runtime configuration setting was updated. The event references principal-2cc56950de78c750. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Vpn audit on ENGINEERING-ASSET-10805fb79cd039f2 recorded that a remote-access VPN session was established. The event references principal-ee63fc11c18dbead. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-989e6473ce09, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Identity audit on OPERATIONS-ASSET-71fc600bd08a667f recorded that an account registered a new MFA method. The event references principal-717e0b47f1247c8b. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Identity audit on ENGINEERING-ASSET-f3a5e6ca5f4810c3 recorded that an account registered a new MFA method. The event references principal-a81b0853166bb0e5. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Mail audit on SUPPORT-ASSET-af2380a8ab001950 recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-d2de6ff979b628f2. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Change CHG-2c6a4c5aaf39 lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Network control audit on PEOPLE-ASSET-30b5158319199c4f recorded that a cloud security group gained a broad ingress rule. The event references principal-4d55ccd8cef6e438. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Database audit on SUPPORT-ASSET-a2d3ef51f6508fc5 recorded that a session read several tables and exported the query result. The event references principal-fc443d6fe94147f2. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Mail audit on RESEARCH-ASSET-0a4e5d836144a737 recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-3b98b2ee8f80fa29. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-021bb3123f73, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Cloud control audit on COMMUNICATIONS-ASSET-53a6ecae622bccee recorded that a cloud logging destination was disabled. The event references principal-cf25374694280e00. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Proxy logs on ENGINEERING-ASSET-55fbfe9ce1b9adb6 recorded that a client transferred a large payload to an external storage endpoint. The event references principal-9db93a1b04a04fcd. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Configuration audit on LEGAL-ASSET-654fecba9ad263c2 recorded that a client proxy setting was changed. The event references principal-40cdbd7119e49afd. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"File audit on COMMUNICATIONS-ASSET-20dd539a3853169a recorded that a shell startup profile gained an additional command. The event references principal-c281969fbd0779dd. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Ssh audit on ENGINEERING-ASSET-3a8203b9b7564af2 recorded that an SSH session opened and requested elevated command execution. The event references principal-f927bd6e5e00e3e2. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-5bfd8dc1b6b2 explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Configuration audit on PEOPLE-ASSET-5afa9d0b44139e46 recorded that a client proxy setting was changed. The event references principal-c6f3609cd125d978. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Compute audit on LEGAL-ASSET-4cc59a71aa46b3a9 recorded that a principal launched multiple compute instances. The event references principal-662e807a43fa7c2b. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Identity audit on SUPPORT-ASSET-3fdea2c42e845651 recorded that a service account established an interactive session. The event references principal-6872260152bd6bd7. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Oauth audit on FINANCE-ASSET-ab8c40ef4ea54ef3 recorded that an application received consent for additional account scopes. The event references principal-c6dc8dd297f2cce8. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Policy audit on SALES-ASSET-8b2e5805c0958f81 recorded that an audit policy was changed to collect fewer event categories. The event references principal-55b368edee8e470a. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Process access audit on ENGINEERING-ASSET-6c512bf3bb9f3c6e recorded that a process requested read access to another process memory space. The event references principal-0c750e6c9b19f34e. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Share audit on FINANCE-ASSET-689b8f41db9ab4f4 recorded that a new network file share was published. The event references principal-604eb4041d82448c. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Vpn audit on LEGAL-ASSET-89bfbe721ce26047 recorded that a remote-access VPN session was established. The event references principal-2ac6b6b7ff50c84a. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"File audit on LEGAL-ASSET-fdae576414dd7376 recorded that a process deleted many files within a short interval. The event references principal-a6b7ec4e30bafd95. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Account audit on SALES-ASSET-b02113ff8562d223 recorded that a local user account was created on a managed system. The event references principal-3cbed1cc8fc2d897. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Cloud identity audit on RESEARCH-ASSET-8d54a31e0957dabb recorded that a principal assumed a role in another account. The event references principal-8a3eb5c757201646. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Dns server audit on SUPPORT-ASSET-99242b48e0f1290b recorded that a client requested a DNS zone transfer. The event references principal-c5b7de8a13a46984. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Kubernetes audit on COMMUNICATIONS-ASSET-789b240d08ec701b recorded that a pod was created with privileged execution enabled. The event references principal-bd54f828538e68ca. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Mail flow logs on PROCUREMENT-ASSET-992b1e99dffe114d recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-ffd659ab57383ff2. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Storage access logs on SALES-ASSET-9e32b40d91582c35 recorded that a principal downloaded many objects from a storage bucket. The event references principal-71bb68cca0a6547d. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-3413eac86d97 match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Pki audit on SALES-ASSET-34ed542c065cfc50 recorded that a principal requested a certificate using an authentication template. The event references principal-bd8f51ad03539dfb. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Package registry audit on ENGINEERING-ASSET-468e2f1736323150 recorded that a principal published a new package version. The event references principal-cbfd72c0328f2633. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Directory audit on RESEARCH-ASSET-717c1ed36129eee9 recorded that a principal requested directory replication data. The event references principal-71255b0539b4ae1e. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-278977d61497 specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Device and file audit on PROCUREMENT-ASSET-804fb2eb4bbf7ddf recorded that files were copied to a removable storage device. The event references principal-25d93f161d21c79f. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-00c4d0f69ad6 match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Repository audit on RESEARCH-ASSET-f2f0b485da92764a recorded that a repository collaborator received elevated permissions. The event references principal-883f23b0e04d7f14. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Kubernetes audit on FINANCE-ASSET-4f8f4d9f800ab9a6 recorded that a cluster admission policy was changed. The event references principal-0f727ece26b623bd. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-3a72ca142510 match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Kubernetes audit on RESEARCH-ASSET-ca81e4dea7e4d440 recorded that a workload mounted a directory from its host filesystem. The event references principal-142014dd00377291. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Backup audit on COMMUNICATIONS-ASSET-34bf9b07e39c1f16 recorded that a backup retention policy was shortened. The event references principal-e0e79be492923c4a. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Directory audit on ENGINEERING-ASSET-74de670cde6f3c91 recorded that a principal requested directory replication data. The event references principal-2491cc3af8b17009. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Key service audit on PROCUREMENT-ASSET-97184c5c539ee822 recorded that a principal issued a burst of key-service decrypt requests. The event references principal-d47010910e744f5c. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Mfa audit on OPERATIONS-ASSET-60e8646a52166a20 recorded that multiple MFA challenges were issued during a short interval. The event references principal-db3cac7564325f27. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Code integrity audit on OPERATIONS-ASSET-06f732c807773233 recorded that an executable without a publisher signature started from a writable directory. The event references principal-28681a2e3d3ce90b. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Session audit on SUPPORT-ASSET-39c9a292833723e5 recorded that the same session token appeared from different client addresses. The event references principal-a5ec7d156048f10f. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Account audit on COMMUNICATIONS-ASSET-9a834b6edbe1b57f recorded that a local user account was created on a managed system. The event references principal-57644d2a7475e5ae. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Share audit on SALES-ASSET-af32e6af472026fd recorded that a new network file share was published. The event references principal-f1240dad3caae0d8. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-3ea12578c75f, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Mail and proxy logs on PROCUREMENT-ASSET-f73ebff8c2f46ccc recorded that a user opened a URL delivered in an email message. The event references principal-81190b386823c031. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-d01fa56be80f specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Resolver logs on SUPPORT-ASSET-b02540e08d1a5e1b recorded that a client requested many long, high-entropy DNS labels. The event references principal-ac999136f4795cef. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Cloud control audit on SUPPORT-ASSET-e66fe35db626a7f0 recorded that resources were created in a region with little prior activity. The event references principal-84f7c4bc4b40ce6e. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Secret manager audit on FINANCE-ASSET-848c4b906d36b1f9 recorded that a workload read several secret versions. The event references principal-2d99961e29099c47. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Package registry audit on SALES-ASSET-70769ae6745858de recorded that a principal published a new package version. The event references principal-06efaa74600c0f91. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Egress flow logs on FINANCE-ASSET-6fc2f9679740efc1 recorded that a workload opened an encrypted connection to an external service. The event references principal-b6c8a10c3d36b1fc. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Application audit on SUPPORT-ASSET-0d07ed7bee9ce5d7 recorded that an application requested repeated screen captures. The event references principal-1f37918578f8f184. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Identity audit on LEGAL-ASSET-943053d6267ac572 recorded that a service account established an interactive session. The event references principal-158c8b7f105115ea. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Mail and proxy logs on ENGINEERING-ASSET-d6ab66ae0acf6c7d recorded that a user opened a URL delivered in an email message. The event references principal-0a6867792e03bc3b. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Storage audit on RESEARCH-ASSET-4fe3f3661fdb65de recorded that a session deleted several storage snapshots. The event references principal-c8575d45e94d3ebb. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Kubernetes audit on PROCUREMENT-ASSET-a7191d519031e89b recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-a4246f24c83acd17. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Driver audit on LEGAL-ASSET-1d7f06f84da720a0 recorded that a kernel driver was loaded after a package installation. The event references principal-419a1d9d514f9429. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Application audit on PROCUREMENT-ASSET-4c611d31ce0dab93 recorded that an application read clipboard contents repeatedly. The event references principal-8af1d70f167ed8d6. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Dhcp telemetry on PROCUREMENT-ASSET-40822febba29ea21 recorded that a server issued DHCP offers on a monitored segment. The event references principal-140fc1a13a173a5d. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-b24e2fbed3da before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Account audit on ENGINEERING-ASSET-bce5c50695a23c43 recorded that a local user account was created on a managed system. The event references principal-1a94579d85980de4. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Database audit on SUPPORT-ASSET-9310282a796b35af recorded that a session changed a database table definition. The event references principal-c009c7c60f3c400f. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-74bbd29bc698 explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Service audit on PEOPLE-ASSET-222cba6353f1d99f recorded that a new automatically started service was registered. The event references principal-e5172d8225074491. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Flow logs on PEOPLE-ASSET-48ed1d716acee890 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-d5ba1580babde1ed. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Function audit on PEOPLE-ASSET-7a184783e26cf4b6 recorded that a serverless function package and execution settings were updated. The event references principal-20e08b043fa3eb3a. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-aea3da9ba3d2 specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Secret manager audit on PROCUREMENT-ASSET-b6e8aa184c246f29 recorded that a workload read several secret versions. The event references principal-3c8c2cffa7cd4de8. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Cloud identity audit on LEGAL-ASSET-be33ff15ebf5e263 recorded that a principal assumed a role in another account. The event references principal-a89c01a9848a96c2. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Service audit on SUPPORT-ASSET-2eb791dfb1c8878d recorded that a new automatically started service was registered. The event references principal-7742e70843824b66. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Process audit on LEGAL-ASSET-8a212c2ca8ae49ba recorded that a Python interpreter loaded a script and contacted a service. The event references principal-a6319754fd6d1b91. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"File audit on PROCUREMENT-ASSET-de47614145685908 recorded that a shell startup profile gained an additional command. The event references principal-602bb5bc7aad1155. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Process audit on ENGINEERING-ASSET-b8d24c4e39635b0b recorded that a Python interpreter loaded a script and contacted a service. The event references principal-59e5008660f946a5. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Flow logs on SUPPORT-ASSET-30ebec702fd5fb40 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-cc4ef6967d7bd3d5. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Kubernetes audit on OPERATIONS-ASSET-f1f73c739188a298 recorded that a workload mounted a directory from its host filesystem. The event references principal-5a00d24e558e0ba4. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Process audit on COMMUNICATIONS-ASSET-3540d4ca6c64eb07 recorded that a remote-support application started an interactive session. The event references principal-e3fe7b2bae9cee75. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-4205899ebb90 before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Api gateway logs on LEGAL-ASSET-d8cde4dc3ebdd0ca recorded that a client issued a burst of API requests. The event references principal-9252cd194de4e3ac. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Account audit on SALES-ASSET-b02113ff8562d223 recorded that a local user account was created on a managed system. The event references principal-3cbed1cc8fc2d897. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Windows logon audit on SUPPORT-ASSET-b7addff92f67af33 recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-5b8a266b76f35fee. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Repository audit on PROCUREMENT-ASSET-7cc2509e9eb69ebb recorded that a user cloned several source repositories. The event references principal-39fa91ed4065a325. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Kubernetes audit on PROCUREMENT-ASSET-2f62998057d28724 recorded that a role binding granted a principal additional cluster permissions. The event references principal-4457a8d289298830. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-dd1386d92959 match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Vpn audit on PEOPLE-ASSET-8b15c5e5fc77cfb3 recorded that a remote-access VPN session was established. The event references principal-61e8cff53a9f17ad. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Registry audit on RESEARCH-ASSET-73e0cbd02049afd1 recorded that a workload pulled a container image from a registry. The event references principal-34d7877cf1ae898f. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-f3348301fd45, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Application audit on RESEARCH-ASSET-21c212dc3255aa17 recorded that an application read clipboard contents repeatedly. The event references principal-8f2a965b2d84c102. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Winrm audit on SUPPORT-ASSET-635c3348db734709 recorded that a remote management session invoked a command on a managed host. The event references principal-f79466b09a2bb0fa. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-155006af6112 match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Kubernetes audit on SALES-ASSET-bd821e033a435876 recorded that a cluster admission policy was changed. The event references principal-57ab3d2d3751af5f. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-9a86594e8a12 specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Ci audit on COMMUNICATIONS-ASSET-9c71cbe9ba5a6116 recorded that a build pipeline definition gained a new execution step. The event references principal-0b9701ae91042079. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Key service audit on FINANCE-ASSET-57ca74510903ebd4 recorded that a principal issued a burst of key-service decrypt requests. The event references principal-79b7e5a3aa2edd24. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-486d4b207f64 specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Driver audit on PROCUREMENT-ASSET-caa474ba78b6dce6 recorded that a kernel driver was loaded after a package installation. The event references principal-c43c37da7fba502b. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Ssh audit on FINANCE-ASSET-370d0df1776daaea recorded that an SSH session opened and requested elevated command execution. The event references principal-d8496f14d2489876. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Vpn audit on LEGAL-ASSET-89bfbe721ce26047 recorded that a remote-access VPN session was established. The event references principal-2ac6b6b7ff50c84a. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Share audit on PEOPLE-ASSET-29ff2158775d3e8d recorded that a new network file share was published. The event references principal-d660d14bb1dc5e12. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Function audit on OPERATIONS-ASSET-7bf3d2cc7f955758 recorded that a serverless function package and execution settings were updated. The event references principal-2b7da48bc74786c4. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Kubernetes audit on FINANCE-ASSET-915256a7e7a6d4a6 recorded that a role binding granted a principal additional cluster permissions. The event references principal-49e34ed22123229a. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Security retest SEC-01c80adbd9d4 covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Cron audit on FINANCE-ASSET-3836d6a68d057960 recorded that a recurring job definition was added to the system schedule. The event references principal-c8b819a1d7d4650c. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Policy audit on ENGINEERING-ASSET-691918f61c7ec7b2 recorded that an audit policy was changed to collect fewer event categories. The event references principal-86d0e35aa5d8e487. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Backup audit on LEGAL-ASSET-0b947a06b2f86efb recorded that a backup retention policy was shortened. The event references principal-ec8805dd5dc564d0. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Identity audit on OPERATIONS-ASSET-71fc600bd08a667f recorded that an account registered a new MFA method. The event references principal-717e0b47f1247c8b. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Saas audit on SUPPORT-ASSET-2e07b9359e958267 recorded that a user requested a bulk export from a business application. The event references principal-b7211075b62be127. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Process audit on PROCUREMENT-ASSET-e094a3806b86f26f recorded that a remote-support application started an interactive session. The event references principal-0e21b55912ebea78. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Browser audit on PEOPLE-ASSET-48ee486909d7e37c recorded that a browser extension with page-reading permissions was installed. The event references principal-0d329542446b1b23. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-1a5b6dff7c03 specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Module audit on RESEARCH-ASSET-49e502fa5df5f407 recorded that a process loaded a library from an application-local directory. The event references principal-52065da876a99294. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Policy audit on PEOPLE-ASSET-4626b13b6c89e82c recorded that an audit policy was changed to collect fewer event categories. The event references principal-dc47a10146c766ea. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Cloud identity audit on OPERATIONS-ASSET-3155b7b471a38d4e recorded that a principal received a policy granting additional permissions. The event references principal-e51b01012b559bdf. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Mfa audit on SUPPORT-ASSET-72ab1273fb4de7e8 recorded that multiple MFA challenges were issued during a short interval. The event references principal-ed28d619781ff3d6. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Wmi audit on PEOPLE-ASSET-0793506618492b13 recorded that a management request started a process through WMI. The event references principal-517018be0d1cff5c. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Package registry audit on SALES-ASSET-70769ae6745858de recorded that a principal published a new package version. The event references principal-06efaa74600c0f91. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Cron audit on COMMUNICATIONS-ASSET-d8fc966dee08cb0c recorded that a recurring job definition was added to the system schedule. The event references principal-703666e706c43b5e. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Waf logs on FINANCE-ASSET-2688c7caaa5c3540 recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-fa0ae08c81b790e0. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Winrm audit on PEOPLE-ASSET-f67c81ba2aebe0a8 recorded that a remote management session invoked a command on a managed host. The event references principal-380dff97d88676ce. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Kubernetes audit on RESEARCH-ASSET-7116d85c35ffeedd recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-5cfd10bdd7720813. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-4cc56eeee7f2 before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"File audit on RESEARCH-ASSET-29f4cb3c7a29beaf recorded that access permissions were broadened on a directory tree. The event references principal-9b108c0888253ab1. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Mail and proxy logs on LEGAL-ASSET-bdb95e0606dac9b6 recorded that a user opened a URL delivered in an email message. The event references principal-5ab74a82bf3ac244. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-3a9cee23a0aa match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Cloud control audit on SALES-ASSET-c5ac5bf2061a85e1 recorded that resources were created in a region with little prior activity. The event references principal-213b93a3248e4777. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Runtime audit on FINANCE-ASSET-f76f44e364cb49d4 recorded that a process connected to the container runtime socket. The event references principal-61088a6af6fdfeb5. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Repository audit on PEOPLE-ASSET-e8dfe6d75dbb8e1e recorded that a user cloned several source repositories. The event references principal-e971d955c552fbff. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Group audit on SUPPORT-ASSET-32af0f049b4169a7 recorded that an account was added to a privileged local group. The event references principal-b75a2d708106954b. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Group audit on LEGAL-ASSET-c0290e976cae1a6c recorded that an account was added to a privileged local group. The event references principal-0e07ba3cca839e79. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Repository audit on FINANCE-ASSET-dc6e3bd56c8a0a87 recorded that a repository collaborator received elevated permissions. The event references principal-28c1f6e75f00c284. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Application audit on LEGAL-ASSET-235dadbbfdbe7d33 recorded that an application requested repeated screen captures. The event references principal-31391eee810ce402. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-a74899edc4e4 specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Office audit on PEOPLE-ASSET-d75bb0ba4ef1bfaf recorded that a document macro launched a child interpreter. The event references principal-882202a717331e69. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Group audit on COMMUNICATIONS-ASSET-c7bad2289a06229c recorded that an account was added to a privileged local group. The event references principal-45633364c2ed091b. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Runtime audit on ENGINEERING-ASSET-275c1751b3b56ff6 recorded that a process connected to the container runtime socket. The event references principal-560134bf0a39e092. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"File audit on FINANCE-ASSET-a2913f2126217458 recorded that access permissions were broadened on a directory tree. The event references principal-05896b0efe4a938e. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-60ce4a668486 match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Task scheduler audit on FINANCE-ASSET-ee3bbbf183a6aaf2 recorded that a scheduled task was registered to execute a program at logon. The event references principal-6b358d24fc67440c. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Kerberos audit on FINANCE-ASSET-0b0adcb58a633d21 recorded that an account requested service tickets for multiple services. The event references principal-bbbe909c0396acf3. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Vpn audit on OPERATIONS-ASSET-3b10a040384bc85b recorded that a remote-access VPN session was established. The event references principal-e69c38b8397d46ff. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Cloud control audit on RESEARCH-ASSET-2cbe7527ba09f822 recorded that resources were created in a region with little prior activity. The event references principal-3490db46f4cacc07. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Flow logs on FINANCE-ASSET-b04c464556b8fa8d recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-4fa1efc3a212390d. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-aec5cf47c772 match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Pki audit on OPERATIONS-ASSET-075517e7328277d9 recorded that a principal requested a certificate using an authentication template. The event references principal-c9b353c364fde4c3. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-d6828c1ea27c match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Mail and proxy logs on FINANCE-ASSET-75c33a0daf443282 recorded that a user opened a URL delivered in an email message. The event references principal-4da288c1eb5d26af. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-40811f7a8c47, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Configuration audit on LEGAL-ASSET-654fecba9ad263c2 recorded that a client proxy setting was changed. The event references principal-40cdbd7119e49afd. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Directory audit on FINANCE-ASSET-4f2fe0486abb5c95 recorded that a principal requested directory replication data. The event references principal-b40239cccc5bf96a. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Code integrity audit on SALES-ASSET-c410ab31c1f04772 recorded that an executable without a publisher signature started from a writable directory. The event references principal-9e4abca76b69be64. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Identity audit on FINANCE-ASSET-17a7d4bc3e0dfc99 recorded that a service account established an interactive session. The event references principal-ba443b5f7751e8bc. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Identity audit on LEGAL-ASSET-f678141e2b084a32 recorded that an account registered a new MFA method. The event references principal-500c71ca31b016a9. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-b99f3317fa99 before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Office audit on PEOPLE-ASSET-d75bb0ba4ef1bfaf recorded that a document macro launched a child interpreter. The event references principal-882202a717331e69. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Cloud control audit on SALES-ASSET-bfb02fef7d44a1a0 recorded that a cloud logging destination was disabled. The event references principal-cabdd3811f019647. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Waf logs on PEOPLE-ASSET-b68587853256629c recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-a0a816963fae146a. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Wmi audit on LEGAL-ASSET-a70f3384c72ee597 recorded that a management request started a process through WMI. The event references principal-d9be46a6c47bd578. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Identity audit on FINANCE-ASSET-17a7d4bc3e0dfc99 recorded that a service account established an interactive session. The event references principal-ba443b5f7751e8bc. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-52d95787acdb match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Group audit on SALES-ASSET-0d02096325648024 recorded that an account was added to a privileged local group. The event references principal-2cfc43945d846816. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Assessment SEC-7a8ce36a3ce8 explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"File audit on COMMUNICATIONS-ASSET-20dd539a3853169a recorded that a shell startup profile gained an additional command. The event references principal-c281969fbd0779dd. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Compute audit on RESEARCH-ASSET-d341eca93691633b recorded that a principal launched multiple compute instances. The event references principal-cf04d4cb340e6373. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Module audit on SUPPORT-ASSET-75579d877216839e recorded that a process loaded a library from an application-local directory. The event references principal-bf9534edb641c536. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Mail and proxy logs on SUPPORT-ASSET-79dbee71e86c40be recorded that a user opened a URL delivered in an email message. The event references principal-1603764c68a231e0. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"File audit on PEOPLE-ASSET-2821cb52cece6fb9 recorded that a shell startup profile gained an additional command. The event references principal-6665fccc697a255b. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Egress flow logs on PEOPLE-ASSET-9176797d1eb78aff recorded that a workload opened an encrypted connection to an external service. The event references principal-eeab4c2bc996daf9. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Driver audit on SALES-ASSET-74116b6362e956da recorded that a kernel driver was loaded after a package installation. The event references principal-9eaf8c722428f29b. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-65b9697dae48 before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Secret manager audit on COMMUNICATIONS-ASSET-0901e5043739c868 recorded that a workload read several secret versions. The event references principal-811d7f224d798eaf. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Waf logs on SUPPORT-ASSET-e0ebcdef3dfa8416 recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-3a687906c9bbefbc. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Ci audit on ENGINEERING-ASSET-2c0d231544308107 recorded that a build pipeline definition gained a new execution step. The event references principal-aba5ed9cc375c5ec. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Dhcp telemetry on PROCUREMENT-ASSET-40822febba29ea21 recorded that a server issued DHCP offers on a monitored segment. The event references principal-140fc1a13a173a5d. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Process audit on PROCUREMENT-ASSET-4c9b1e536ca1f43f recorded that a Python interpreter loaded a script and contacted a service. The event references principal-f1d7ec01883c26bc. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Process access audit on PEOPLE-ASSET-e69cbb53fe5c9e6a recorded that a process requested read access to another process memory space. The event references principal-b9eeb1db9d8c686f. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-3af3a18d3709 match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Policy audit on ENGINEERING-ASSET-691918f61c7ec7b2 recorded that an audit policy was changed to collect fewer event categories. The event references principal-86d0e35aa5d8e487. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Flow logs on OPERATIONS-ASSET-edf434a71b109006 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-16d324cd052a6682. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-bd109364c1f5, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Application audit on SALES-ASSET-a8b331f6bbbdf2ee recorded that a runtime configuration setting was updated. The event references principal-21cb8dcf748912e9. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Network control audit on RESEARCH-ASSET-e48fcfb18287d725 recorded that a cloud security group gained a broad ingress rule. The event references principal-0f1496ca8a6383fd. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Backup audit on PROCUREMENT-ASSET-8055bd5873ef3941 recorded that a backup retention policy was shortened. The event references principal-ab63e55288bca196. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Waf logs on COMMUNICATIONS-ASSET-5ce6d959f09ef085 recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-ded293726939201b. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Kubernetes audit on SUPPORT-ASSET-99bd1381f9f84168 recorded that a pod was created with privileged execution enabled. The event references principal-4de29bd2a93d9674. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-3c9a3bbc2a6b match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Kubernetes audit on SUPPORT-ASSET-95dbeaaf93770ec1 recorded that a role binding granted a principal additional cluster permissions. The event references principal-fae5a1331ea1b683. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Package registry audit on COMMUNICATIONS-ASSET-7fd940c9dbda3462 recorded that a principal published a new package version. The event references principal-07091e1d888fa67d. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"File audit on FINANCE-ASSET-2004b1d4a03fd309 recorded that a process rewrote multiple files into encrypted containers. The event references principal-9560a602e126689a. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-4c175dda522b match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Account audit on PROCUREMENT-ASSET-6b3dfabb9fc718fa recorded that a local user account was created on a managed system. The event references principal-67628d1182b40e07. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Process access audit on ENGINEERING-ASSET-6c512bf3bb9f3c6e recorded that a process requested read access to another process memory space. The event references principal-0c750e6c9b19f34e. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Ci secret audit on PROCUREMENT-ASSET-7ef0c5a6d6fc8733 recorded that a build job requested a protected pipeline secret. The event references principal-77e6930e6b3513f9. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Kubernetes audit on SUPPORT-ASSET-46e0923b16c1de93 recorded that a cluster admission policy was changed. The event references principal-eb0f85c559534d98. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Cloud identity audit on RESEARCH-ASSET-809fdc9f1154a3c8 recorded that a principal received a policy granting additional permissions. The event references principal-58f2cdd79c2b5788. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"File audit on SUPPORT-ASSET-528c23bdb207b71c recorded that access permissions were broadened on a directory tree. The event references principal-f1bdbe7329a336ab. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-0a43b3b46982 match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Mfa audit on RESEARCH-ASSET-900be36a816445ab recorded that multiple MFA challenges were issued during a short interval. The event references principal-fdb4d3be95b990c6. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"File audit on LEGAL-ASSET-b2789a781837a87b recorded that a shell startup profile gained an additional command. The event references principal-d7a3487fce82090e. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Cloud control audit on LEGAL-ASSET-57d9881033f6b349 recorded that resources were created in a region with little prior activity. The event references principal-3d1e3e3a52fd0eed. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Systemd audit on LEGAL-ASSET-1602066d8a3d5246 recorded that a service unit file was changed and the unit reloaded. The event references principal-cdc1cfc697d46ed4. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Saas audit on PROCUREMENT-ASSET-94508e8090c4e3fa recorded that a user requested a bulk export from a business application. The event references principal-d0cfd5ec7d96061d. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Code integrity audit on PEOPLE-ASSET-4048dcb975a46f2e recorded that an executable without a publisher signature started from a writable directory. The event references principal-d449d23aa96125e6. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Network control audit on COMMUNICATIONS-ASSET-b93121e4b22b1a29 recorded that a cloud security group gained a broad ingress rule. The event references principal-8f16c182ac4bbc7f. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-63999d40baae accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Registry audit on SUPPORT-ASSET-f57e1958aa803333 recorded that a workload pulled a container image from a registry. The event references principal-10cd1718e32b6b5f. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Identity audit on LEGAL-ASSET-943053d6267ac572 recorded that a service account established an interactive session. The event references principal-158c8b7f105115ea. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Backup audit on SALES-ASSET-6933f79c2a57f98c recorded that a backup retention policy was shortened. The event references principal-9b63e3d52602597e. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Kubernetes audit on ENGINEERING-ASSET-af728a774d91dcb8 recorded that a workload mounted a directory from its host filesystem. The event references principal-6a5b731d9f44ffa6. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Winrm audit on LEGAL-ASSET-6240747fe412756f recorded that a remote management session invoked a command on a managed host. The event references principal-bff5de31e17ff348. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-480576df7510 match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Compute audit on LEGAL-ASSET-4cc59a71aa46b3a9 recorded that a principal launched multiple compute instances. The event references principal-662e807a43fa7c2b. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Cloud control audit on RESEARCH-ASSET-2bdeaeb6bfb8b9b8 recorded that a cloud logging destination was disabled. The event references principal-00477aa276d23b17. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"File audit on ENGINEERING-ASSET-34a8ce1c539d9368 recorded that a process deleted many files within a short interval. The event references principal-c1c689ef96642a7c. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Function audit on SALES-ASSET-461c1fc508bcc3ad recorded that a serverless function package and execution settings were updated. The event references principal-f88b3cc6828a81db. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Mail flow logs on FINANCE-ASSET-05268a477e8094f0 recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-ab4f2f7ab1b6ae29. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Flow logs on LEGAL-ASSET-bb14ef480a9f5aa0 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-343b8b6d62a9710b. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-0b0992a46df5 match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Mail audit on PEOPLE-ASSET-23ff12ac4cce3df1 recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-210b267fe07fa398. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Pki audit on PEOPLE-ASSET-3dbf336f859282fe recorded that a principal requested a certificate using an authentication template. The event references principal-bc62db6b4c821f23. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-0bba12298ced match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Package registry audit on ENGINEERING-ASSET-468e2f1736323150 recorded that a principal published a new package version. The event references principal-cbfd72c0328f2633. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-60286f7097f7 explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Package registry audit on COMMUNICATIONS-ASSET-7fd940c9dbda3462 recorded that a principal published a new package version. The event references principal-07091e1d888fa67d. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-b8726cb133ef accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Configuration audit on PEOPLE-ASSET-5afa9d0b44139e46 recorded that a client proxy setting was changed. The event references principal-c6f3609cd125d978. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-d88ab608ff72 before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Systemd audit on FINANCE-ASSET-2646ce4052597344 recorded that a service unit file was changed and the unit reloaded. The event references principal-38069415a5ef6919. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Database audit on PROCUREMENT-ASSET-88d6e016f81704ea recorded that a session changed a database table definition. The event references principal-a7367e91f7bc0a1d. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-27a359cd571e match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Cron audit on PEOPLE-ASSET-4b3199ab3c63dd2d recorded that a recurring job definition was added to the system schedule. The event references principal-f1110cbb064f6627. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Storage audit on RESEARCH-ASSET-6e2b243ec7d7a919 recorded that an object-storage access policy was broadened. The event references principal-262db57bffaea9f7. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Assessment SEC-65c23636bdd2 explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Identity audit on PROCUREMENT-ASSET-595810a122b584e8 recorded that a service account established an interactive session. The event references principal-786fe31fade4e850. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Application audit on PEOPLE-ASSET-fcad7cf3be4e4115 recorded that a runtime configuration setting was updated. The event references principal-1c596d52504e0c0f. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-33992d4d43f9 before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Ssh audit on ENGINEERING-ASSET-3a8203b9b7564af2 recorded that an SSH session opened and requested elevated command execution. The event references principal-f927bd6e5e00e3e2. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Cloud identity audit on PROCUREMENT-ASSET-cb3bd3ac326cf3b2 recorded that a principal assumed a role in another account. The event references principal-131a52eaecf4978f. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-5d8ac42312f8 match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Saas audit on SALES-ASSET-3ad767047dba4a21 recorded that a user requested a bulk export from a business application. The event references principal-b81a4cbeea8a89df. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Kubernetes audit on PEOPLE-ASSET-fb423ebd814658c2 recorded that a role binding granted a principal additional cluster permissions. The event references principal-1e6683e3ee80066c. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Resolver logs on LEGAL-ASSET-3fa235a88f26dc9e recorded that a client requested many long, high-entropy DNS labels. The event references principal-1767397f4dd4b5b0. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Change CHG-eb5863186793 lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Runtime audit on SUPPORT-ASSET-70bd103925bca47e recorded that a process connected to the container runtime socket. The event references principal-cf65589a3d4ad7b6. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Process audit on LEGAL-ASSET-1d30eece58fd02aa recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-73ea530a0de82f6d. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Mail audit on ENGINEERING-ASSET-784f3c782f3ac855 recorded that an account received delegated access to a mailbox. The event references principal-2080f4d9197e7c3e. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-4dbfd768c1f2 accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Saas audit on SALES-ASSET-3ad767047dba4a21 recorded that a user requested a bulk export from a business application. The event references principal-b81a4cbeea8a89df. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Change CHG-fda6895f2225 lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Share audit on SALES-ASSET-af32e6af472026fd recorded that a new network file share was published. The event references principal-f1240dad3caae0d8. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"File audit on SALES-ASSET-a4a69365dce2152a recorded that a shell startup profile gained an additional command. The event references principal-3637027719cb9240. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Application audit on COMMUNICATIONS-ASSET-365eaf894be6367d recorded that an application read clipboard contents repeatedly. The event references principal-c9d903188ad53746. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-9ea49b505462 match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Office audit on LEGAL-ASSET-7baa0b7a7bcbd13a recorded that a document macro launched a child interpreter. The event references principal-4d965a283abc96ce. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Kerberos audit on LEGAL-ASSET-6ee4a0334d8b0730 recorded that an account requested service tickets for multiple services. The event references principal-2772005981d83d01. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-8a7cb2fd4048, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Proxy logs on SALES-ASSET-c3dbe91c60733c60 recorded that a client transferred a large payload to an external storage endpoint. The event references principal-fbf3a8a302b7a6c9. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"File audit on SALES-ASSET-6ae931d0f4c709bb recorded that access permissions were broadened on a directory tree. The event references principal-d574e0d5ffd134ab. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Systemd audit on FINANCE-ASSET-2646ce4052597344 recorded that a service unit file was changed and the unit reloaded. The event references principal-38069415a5ef6919. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Mail audit on PROCUREMENT-ASSET-57a43dc80cfc93ed recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-40142beb1db7ce4d. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Identity audit on PEOPLE-ASSET-d81992a54d0e0cd4 recorded that a service account established an interactive session. The event references principal-0bc399328dfcae48. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-2e2572590e8a accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Cron audit on LEGAL-ASSET-fa5ca79bc164009d recorded that a recurring job definition was added to the system schedule. The event references principal-07e12ac009730cba. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Session audit on PROCUREMENT-ASSET-375b33e301ac9b62 recorded that the same session token appeared from different client addresses. The event references principal-c5f1efc48ec3f681. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Assessment SEC-13d721df8d28 explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"File audit on OPERATIONS-ASSET-f5bfac37e0e6e52e recorded that access permissions were broadened on a directory tree. The event references principal-c5603af4c6f0f506. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Kubernetes audit on FINANCE-ASSET-d7b2da83577ab38d recorded that a pod was created with privileged execution enabled. The event references principal-5177d7ecbc348aa2. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Saas audit on LEGAL-ASSET-febb39399ce8713a recorded that a user requested a bulk export from a business application. The event references principal-56038be98666605f. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Agent audit on PROCUREMENT-ASSET-92d810ab505277a2 recorded that a privileged session changed endpoint monitoring settings. The event references principal-ae67200926ed1d7a. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Share audit on PEOPLE-ASSET-29ff2158775d3e8d recorded that a new network file share was published. The event references principal-d660d14bb1dc5e12. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Service audit on RESEARCH-ASSET-83637b2bf6e44350 recorded that a new automatically started service was registered. The event references principal-9f4043a1a42fcc90. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Cron audit on ENGINEERING-ASSET-0d57cc07ded38310 recorded that a recurring job definition was added to the system schedule. The event references principal-db05c7bee0f112c7. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Kubernetes audit on COMMUNICATIONS-ASSET-789b240d08ec701b recorded that a pod was created with privileged execution enabled. The event references principal-bd54f828538e68ca. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Task scheduler audit on PROCUREMENT-ASSET-bd3697f2e2b8950e recorded that a scheduled task was registered to execute a program at logon. The event references principal-1483881099fae9be. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Saas audit on FINANCE-ASSET-7dbfabaebbf506b5 recorded that a user requested a bulk export from a business application. The event references principal-147dd62c19db648c. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-a8cb6b552478 explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Share audit on RESEARCH-ASSET-f2c54bce84c236d2 recorded that a new network file share was published. The event references principal-0e202f3a7615eefc. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Mail audit on OPERATIONS-ASSET-3bd074cdd8f9b5e6 recorded that an account received delegated access to a mailbox. The event references principal-81775ab116c002d8. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Identity audit on PROCUREMENT-ASSET-847c16861843d993 recorded that repeated failed sign-ins were recorded for an account. The event references principal-177e5d83a23e0f5b. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Cloud identity audit on LEGAL-ASSET-a018d5a0c035a322 recorded that a principal received a policy granting additional permissions. The event references principal-e37ce5811af67681. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-147c915a5591 match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Mfa audit on SUPPORT-ASSET-72ab1273fb4de7e8 recorded that multiple MFA challenges were issued during a short interval. The event references principal-ed28d619781ff3d6. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-858a32a3b17e specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"File audit on FINANCE-ASSET-2a7828c17a1b3f24 recorded that a shell startup profile gained an additional command. The event references principal-4b7e3cd5eb46c9e6. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Kubernetes audit on PEOPLE-ASSET-3e58a2eca5c63a44 recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-8f985c1a713a28f2. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Process audit on SALES-ASSET-d7499e681a58affc recorded that a JavaScript interpreter executed a local script. The event references principal-ce0d21f659b72ac8. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Federation audit on COMMUNICATIONS-ASSET-866384484e84ef96 recorded that a tenant federation setting was updated. The event references principal-e2dd8e40c0e17294. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Registry audit on FINANCE-ASSET-6f5ecd36af234140 recorded that a registry logon-start entry was created. The event references principal-ce9587e0dadb3215. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-8de00ebb0048 match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Mail flow logs on COMMUNICATIONS-ASSET-60efe7c42d543cb2 recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-6db1155a76f69a6b. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Kubernetes audit on FINANCE-ASSET-915256a7e7a6d4a6 recorded that a role binding granted a principal additional cluster permissions. The event references principal-49e34ed22123229a. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Federation audit on PEOPLE-ASSET-307988f8a71d4999 recorded that a tenant federation setting was updated. The event references principal-c9e7767b005f5591. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Certificate audit on PROCUREMENT-ASSET-90178e3809a5e39e recorded that a service certificate was replaced. The event references principal-4bfd3026e3966135. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Change CHG-392cc2b82945 lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Firewall audit on SUPPORT-ASSET-e85c56705ce7aa30 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-9b678cb3b90b393c. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Office audit on PROCUREMENT-ASSET-9c9a63eb958fdaa6 recorded that a document macro launched a child interpreter. The event references principal-40d050ba88a97331. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Repository audit on SALES-ASSET-60f45c01cacb2ad7 recorded that a repository collaborator received elevated permissions. The event references principal-59983edc6542b65a. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Pki audit on SALES-ASSET-34ed542c065cfc50 recorded that a principal requested a certificate using an authentication template. The event references principal-bd8f51ad03539dfb. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Egress flow logs on SUPPORT-ASSET-ff3badb46e903585 recorded that a workload opened an encrypted connection to an external service. The event references principal-ef7dbc8f1e7b6a52. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Account audit on SUPPORT-ASSET-4f664bc059385d17 recorded that a local user account was created on a managed system. The event references principal-1db165dfba5895ba. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-6fd850aa9f83 match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Storage access logs on ENGINEERING-ASSET-cfa9edf25dbd11b0 recorded that a principal downloaded many objects from a storage bucket. The event references principal-9a3a0f64a8f2a35d. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Application audit on FINANCE-ASSET-92ef4a42892b1789 recorded that an application read clipboard contents repeatedly. The event references principal-13f5550b59519bb2. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Change CHG-5f9748db384d lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Identity audit on COMMUNICATIONS-ASSET-cdebef5d9dc25fc4 recorded that a service account established an interactive session. The event references principal-ecbde67b88dd7d93. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-bebfff361ebf before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Application audit on OPERATIONS-ASSET-cf2679e9708fa36f recorded that a runtime configuration setting was updated. The event references principal-3db05afeebe1db89. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"File audit on ENGINEERING-ASSET-1a60a1286916ad01 recorded that access permissions were broadened on a directory tree. The event references principal-1a1a48bb1e529fb0. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"File audit on PROCUREMENT-ASSET-a3fde179ef5ff962 recorded that access permissions were broadened on a directory tree. The event references principal-bb1784cca8241c87. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-63b0d544f31e explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Account audit on COMMUNICATIONS-ASSET-9a834b6edbe1b57f recorded that a local user account was created on a managed system. The event references principal-57644d2a7475e5ae. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Registry audit on PROCUREMENT-ASSET-623aa42bae025131 recorded that a registry logon-start entry was created. The event references principal-9f2c57eab5b3cfda. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Application audit on PEOPLE-ASSET-b6c838eeab685d8f recorded that an application requested repeated screen captures. The event references principal-22d369aeea462cc7. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-3f3f917b83ae match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Session audit on OPERATIONS-ASSET-650805187004af92 recorded that the same session token appeared from different client addresses. The event references principal-fe1f7195dd801273. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Process audit on OPERATIONS-ASSET-495b246de141f994 recorded that a Python interpreter loaded a script and contacted a service. The event references principal-3264c9e681183a21. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Identity audit on ENGINEERING-ASSET-7b28b0fa9a166d69 recorded that repeated failed sign-ins were recorded for an account. The event references principal-1962d3f4c712b2c7. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Office audit on RESEARCH-ASSET-b8dbacd37bf5b2aa recorded that a document macro launched a child interpreter. The event references principal-fd35021fb1b91014. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Module audit on FINANCE-ASSET-6b165174917b5734 recorded that a process loaded a library from an application-local directory. The event references principal-ecca7e9b2841d1cc. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-ef4078f07111 explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Configuration audit on SALES-ASSET-9818a0f135cc7c5d recorded that a client proxy setting was changed. The event references principal-50e5e76cf1a92613. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Oauth audit on SUPPORT-ASSET-f8746b96a88e1b30 recorded that an application received consent for additional account scopes. The event references principal-7f165276ca2b480a. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Application audit on PEOPLE-ASSET-16eca898293194f8 recorded that an application read clipboard contents repeatedly. The event references principal-9ece0c292d6cf355. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Security retest SEC-fcab3fdf29c0 covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Process audit on PEOPLE-ASSET-2c32b67a1236291b recorded that a remote-support application started an interactive session. The event references principal-3d51474c05227a94. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"File audit on RESEARCH-ASSET-e40ef73f48b09e4f recorded that a shell startup profile gained an additional command. The event references principal-2434130e3913b6f0. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-db91b4a0448f accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Storage access logs on PROCUREMENT-ASSET-8beb52fc6c4219bf recorded that a principal downloaded many objects from a storage bucket. The event references principal-de077f5f8d45beed. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-b5e02eb95883 before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Cloud identity audit on PROCUREMENT-ASSET-e334c75ea7c7bbae recorded that a new programmatic access key was issued to a principal. The event references principal-754b76246081ca60. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Script audit on RESEARCH-ASSET-a67da4eb1517ea03 recorded that a script interpreter decoded an encoded argument before execution. The event references principal-e606a4602bed6561. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Cloud identity audit on PROCUREMENT-ASSET-e334c75ea7c7bbae recorded that a new programmatic access key was issued to a principal. The event references principal-754b76246081ca60. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Assessment SEC-7d1f1899d709 explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Policy audit on PEOPLE-ASSET-4626b13b6c89e82c recorded that an audit policy was changed to collect fewer event categories. The event references principal-dc47a10146c766ea. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-2c769e9c247f match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Vpn audit on LEGAL-ASSET-89bfbe721ce26047 recorded that a remote-access VPN session was established. The event references principal-2ac6b6b7ff50c84a. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Dns server audit on LEGAL-ASSET-9a776b98cec96a9e recorded that a client requested a DNS zone transfer. The event references principal-b7047a9785be46d4. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Event service audit on OPERATIONS-ASSET-6bb0ff67f6f8dbd2 recorded that an event log was cleared by a privileged request. The event references principal-1c69ef2988f5b8db. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-f99060f953c4 explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Saas audit on SALES-ASSET-3ad767047dba4a21 recorded that a user requested a bulk export from a business application. The event references principal-b81a4cbeea8a89df. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Repository audit on ENGINEERING-ASSET-19fede4e07d7366c recorded that a repository collaborator received elevated permissions. The event references principal-22c3a4b3adce2401. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Change CHG-59dfcb263fbe lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Identity audit on OPERATIONS-ASSET-775dd42bd2b2e216 recorded that repeated failed sign-ins were recorded for an account. The event references principal-2f8b852f1ede3573. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-c16aa050fbd5, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Kubernetes audit on ENGINEERING-ASSET-893d9de1f805e218 recorded that a cluster admission policy was changed. The event references principal-63fff86ce57d7e9d. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-715af2fa1178 match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Storage audit on SALES-ASSET-54a03152e889d43f recorded that a session deleted several storage snapshots. The event references principal-69a5261a8cfb5a4d. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-b04f5b558551 before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Kerberos audit on ENGINEERING-ASSET-ca968191bd4b09c5 recorded that an account requested service tickets for multiple services. The event references principal-48c928131e4a9922. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-b238dfd87fa8 covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Repository audit on PROCUREMENT-ASSET-7cc2509e9eb69ebb recorded that a user cloned several source repositories. The event references principal-39fa91ed4065a325. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Directory audit on LEGAL-ASSET-e41057b50163ec62 recorded that a principal requested directory replication data. The event references principal-27103a43ea428bc2. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-ca0715abb5c4 specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Database audit on SUPPORT-ASSET-a2d3ef51f6508fc5 recorded that a session read several tables and exported the query result. The event references principal-fc443d6fe94147f2. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Change CHG-74a720c22b6f lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Driver audit on PEOPLE-ASSET-9e9f7519775a6002 recorded that a kernel driver was loaded after a package installation. The event references principal-4bafb24bfe647837. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-cc5acd342ca5 accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Api gateway logs on PEOPLE-ASSET-010de515bde4832b recorded that a client issued a burst of API requests. The event references principal-828fabb7c52c8ecb. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Share audit on LEGAL-ASSET-f4d3a91d6248c724 recorded that a new network file share was published. The event references principal-9174cfcb163194b8. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Oauth audit on OPERATIONS-ASSET-1d059cb4cf3d2fe1 recorded that an application received consent for additional account scopes. The event references principal-68400bad9534528c. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Event service audit on LEGAL-ASSET-1725494bd06479c8 recorded that an event log was cleared by a privileged request. The event references principal-2d006b9d45394524. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Code integrity audit on RESEARCH-ASSET-b23d57d440170815 recorded that an executable without a publisher signature started from a writable directory. The event references principal-a70693803f9dbb50. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-e836abd00bfd match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Proxy logs on OPERATIONS-ASSET-63a9838a229b6bdc recorded that a client transferred a large payload to an external storage endpoint. The event references principal-1a271b9f4504e35e. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Resolver logs on RESEARCH-ASSET-abc39d656b9d30aa recorded that a client requested many long, high-entropy DNS labels. The event references principal-5aebc86024ffc2a8. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Change CHG-c3b9b7a5a0b1 lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Cloud identity audit on PEOPLE-ASSET-f0da82528453fc68 recorded that a principal received a policy granting additional permissions. The event references principal-c5a646fec9c6789b. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Package registry audit on LEGAL-ASSET-904ec76dbb996774 recorded that a principal published a new package version. The event references principal-3920a37e9b8e2b42. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Ci secret audit on FINANCE-ASSET-b6445d71bd651026 recorded that a build job requested a protected pipeline secret. The event references principal-634acd477e34564f. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Storage access logs on SALES-ASSET-9e32b40d91582c35 recorded that a principal downloaded many objects from a storage bucket. The event references principal-71bb68cca0a6547d. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-3413eac86d97 accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Cloud control audit on SUPPORT-ASSET-f20f7641faecc324 recorded that a cloud logging destination was disabled. The event references principal-4d58eb61705c0ae8. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Change CHG-4c654c8b0252 lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Share audit on OPERATIONS-ASSET-a9f5766b40361ce4 recorded that a new network file share was published. The event references principal-e591af365aeb634a. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Ssh audit on COMMUNICATIONS-ASSET-c7c949ba2f23f6e5 recorded that an SSH session opened and requested elevated command execution. The event references principal-3a7b389506fbf3c1. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Proxy logs on SUPPORT-ASSET-eadf40ef6aff627a recorded that a client transferred a large payload to an external storage endpoint. The event references principal-77e382cc165fce08. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Driver audit on COMMUNICATIONS-ASSET-b8154a780e8f0180 recorded that a kernel driver was loaded after a package installation. The event references principal-5b575ab65094c162. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Code integrity audit on FINANCE-ASSET-17d7fd3ccdbe7a13 recorded that an executable without a publisher signature started from a writable directory. The event references principal-8715ecce18f6c074. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Storage audit on FINANCE-ASSET-47f72b6b10bf47c7 recorded that a session deleted several storage snapshots. The event references principal-6ce8e4c42cc80c2d. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-ebc43c967274 match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Configuration audit on FINANCE-ASSET-74d3e5b9407ece66 recorded that a client proxy setting was changed. The event references principal-00bf9f3d44fd549a. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Ci secret audit on SALES-ASSET-ad09caa9a6596785 recorded that a build job requested a protected pipeline secret. The event references principal-5cac9dd38eee5122. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-af8275029cde before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Cloud identity audit on PROCUREMENT-ASSET-ec7ad16199b37527 recorded that a principal received a policy granting additional permissions. The event references principal-8b968a5cde5474fa. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Windows logon audit on FINANCE-ASSET-08f4600838c704c1 recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-9a25429fc1580f3b. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-98e85f54a44d match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Pki audit on RESEARCH-ASSET-5892d31dbb5ae49e recorded that a principal requested a certificate using an authentication template. The event references principal-5044ec496f46d2cd. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Oauth audit on SUPPORT-ASSET-f8746b96a88e1b30 recorded that an application received consent for additional account scopes. The event references principal-7f165276ca2b480a. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Identity audit on PROCUREMENT-ASSET-b4ae6e9e4fb445a9 recorded that an account password was reset through a recovery workflow. The event references principal-b2c1bc21d87bb7c1. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Repository audit on SALES-ASSET-b9ab0defeef57d69 recorded that a user cloned several source repositories. The event references principal-0da3c44a52b416ce. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-5c81596a07c9 before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Switch telemetry on FINANCE-ASSET-c82eb7bf49c6713c recorded that an address mapping changed repeatedly on a local segment. The event references principal-24aa90be68c12c8b. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Function audit on SUPPORT-ASSET-639b47faa57b7d52 recorded that a serverless function package and execution settings were updated. The event references principal-142321e2377f77dd. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-1c703da20b30 covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Repository audit on LEGAL-ASSET-f07ffc46adc231a4 recorded that a repository collaborator received elevated permissions. The event references principal-d071e326612f692d. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-3a502e5c88ef, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Cloud identity audit on PEOPLE-ASSET-120c32cb226f1634 recorded that a new programmatic access key was issued to a principal. The event references principal-1aef76f9cfa1105d. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-f7c662d51f9c specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Cloud control audit on PROCUREMENT-ASSET-3d72a13549b9a584 recorded that resources were created in a region with little prior activity. The event references principal-a14765e1d71ea435. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Kubernetes audit on SUPPORT-ASSET-95dbeaaf93770ec1 recorded that a role binding granted a principal additional cluster permissions. The event references principal-fae5a1331ea1b683. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Change CHG-de69c4d19064 lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Mfa audit on SUPPORT-ASSET-72ab1273fb4de7e8 recorded that multiple MFA challenges were issued during a short interval. The event references principal-ed28d619781ff3d6. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Cloud identity audit on PEOPLE-ASSET-db5bfc23857c8681 recorded that a principal assumed a role in another account. The event references principal-3e8604b26d44d800. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Mail audit on PEOPLE-ASSET-23ff12ac4cce3df1 recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-210b267fe07fa398. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Kubernetes audit on PEOPLE-ASSET-36a1a728506cc2a7 recorded that a workload mounted a directory from its host filesystem. The event references principal-b1c8c5f8e9de87c2. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Security retest SEC-2d9f2f87fc6f covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Wmi audit on PROCUREMENT-ASSET-fda18a4350cff1b3 recorded that a management request started a process through WMI. The event references principal-cba091012017387e. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Cloud identity audit on ENGINEERING-ASSET-00c2f8de5ff4a52c recorded that a principal assumed a role in another account. The event references principal-4cb5db7ee766c0fa. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Key service audit on SUPPORT-ASSET-32d985d5324796c4 recorded that a principal issued a burst of key-service decrypt requests. The event references principal-82b70d458957b545. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Compute audit on PEOPLE-ASSET-fe0429fc4ead052f recorded that a principal launched multiple compute instances. The event references principal-4fe369a19d9b5bd1. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-29f2557339e9, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"File audit on OPERATIONS-ASSET-a77dace88afed479 recorded that a process rewrote multiple files into encrypted containers. The event references principal-9bd0bfba4bc5c80f. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Cloud control audit on ENGINEERING-ASSET-1c2668b46715bf02 recorded that resources were created in a region with little prior activity. The event references principal-974cef6dad8360ab. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-c8171b4c58bf accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Flow logs on COMMUNICATIONS-ASSET-d5fd0288e752f79f recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-fd4faa7e0445166d. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Resolver logs on COMMUNICATIONS-ASSET-064116140685fdd2 recorded that a client requested many long, high-entropy DNS labels. The event references principal-a53098877c1921c0. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-77c2d4b208c9, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Key service audit on PROCUREMENT-ASSET-97184c5c539ee822 recorded that a principal issued a burst of key-service decrypt requests. The event references principal-d47010910e744f5c. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-79bddc0e5ae6, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Database audit on SUPPORT-ASSET-a2d3ef51f6508fc5 recorded that a session read several tables and exported the query result. The event references principal-fc443d6fe94147f2. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-74a720c22b6f covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Session audit on LEGAL-ASSET-a93d2c4f4ac53314 recorded that the same session token appeared from different client addresses. The event references principal-4ff9816ed8758404. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-565ec33c2b00, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Application audit on RESEARCH-ASSET-11f390ae672643c2 recorded that a runtime configuration setting was updated. The event references principal-1a691de3cb24648f. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Security retest SEC-5ee027dec439 covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Waf logs on COMMUNICATIONS-ASSET-5ce6d959f09ef085 recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-ded293726939201b. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Cron audit on COMMUNICATIONS-ASSET-d8fc966dee08cb0c recorded that a recurring job definition was added to the system schedule. The event references principal-703666e706c43b5e. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Application audit on PROCUREMENT-ASSET-0b973fc190e51fb9 recorded that an application requested repeated screen captures. The event references principal-6d7c52f4e39422b1. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Certificate audit on SALES-ASSET-d2e9e0997da46974 recorded that a service certificate was replaced. The event references principal-0e407d6273aa8758. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Process audit on SUPPORT-ASSET-0577991db5a15090 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-d0dbfe56694e1edd. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-48f20570fc3e explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Key service audit on RESEARCH-ASSET-fa35f918dce61e29 recorded that a principal issued a burst of key-service decrypt requests. The event references principal-139260250781ca0e. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Federation audit on RESEARCH-ASSET-85e9941ba25e96bb recorded that a tenant federation setting was updated. The event references principal-863b72c786eda302. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Service audit on COMMUNICATIONS-ASSET-7e54b0ca38e553fe recorded that a new automatically started service was registered. The event references principal-7d549ca6bce506ce. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-209a92ddba75 explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Application audit on COMMUNICATIONS-ASSET-c8d077447f8b8c1d recorded that an application requested repeated screen captures. The event references principal-062e1b2072504f50. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Account audit on OPERATIONS-ASSET-ad56fc4183b7ca9d recorded that a local user account was created on a managed system. The event references principal-fe2941e164dbf1c4. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Kubernetes audit on LEGAL-ASSET-82e9dc780e2f0fb0 recorded that a pod was created with privileged execution enabled. The event references principal-7d1067f1bf4b8bd0. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-c21babb0ee65 explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Application audit on PROCUREMENT-ASSET-9ae629f20e56becc recorded that a runtime configuration setting was updated. The event references principal-be5a20df9fa68e8b. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Cloud control audit on PROCUREMENT-ASSET-3d72a13549b9a584 recorded that resources were created in a region with little prior activity. The event references principal-a14765e1d71ea435. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Application audit on FINANCE-ASSET-be2eeaec3ad85eb4 recorded that a runtime configuration setting was updated. The event references principal-1d937b1c297b00f3. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Database audit on SUPPORT-ASSET-9310282a796b35af recorded that a session changed a database table definition. The event references principal-c009c7c60f3c400f. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Secret manager audit on RESEARCH-ASSET-9ed518d17fe68d7a recorded that a workload read several secret versions. The event references principal-7f1b48c31f4c5822. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Flow logs on OPERATIONS-ASSET-498d986f9a323163 recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-921d661770eeeb14. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-63d72b693284 specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Cloud identity audit on LEGAL-ASSET-be33ff15ebf5e263 recorded that a principal assumed a role in another account. The event references principal-a89c01a9848a96c2. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-59e7f99b3808 match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"File audit on OPERATIONS-ASSET-aa398735111975aa recorded that a process deleted many files within a short interval. The event references principal-ff0116df6d90824b. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Repository audit on ENGINEERING-ASSET-501895f2c603da6f recorded that a user cloned several source repositories. The event references principal-08a3df240a2c2acb. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Switch telemetry on SUPPORT-ASSET-8a0f455136f22cce recorded that an address mapping changed repeatedly on a local segment. The event references principal-598fd0cdb7a2c2dd. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-acfcc278816e explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Policy audit on LEGAL-ASSET-fdcb7612a4f13f67 recorded that an audit policy was changed to collect fewer event categories. The event references principal-3d26eee8b88bfb17. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Mail audit on SALES-ASSET-1d2f1acd8ca606b9 recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-eaa00c222951727e. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Security retest SEC-86bb448fc8e9 covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Kubernetes audit on PEOPLE-ASSET-36a1a728506cc2a7 recorded that a workload mounted a directory from its host filesystem. The event references principal-b1c8c5f8e9de87c2. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Switch telemetry on LEGAL-ASSET-1643dbdebba2d78d recorded that an address mapping changed repeatedly on a local segment. The event references principal-c39fe907de3611c7. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"File audit on SALES-ASSET-f0f53d618a5c2238 recorded that a process compressed files from several directories into an archive. The event references principal-a24a28fb5a9017a6. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Firewall audit on SALES-ASSET-67b90170bfed122f recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-2766646810a01a28. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Package registry audit on FINANCE-ASSET-39c7276454a893cc recorded that a principal published a new package version. The event references principal-9e718ff7956300e6. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Certificate audit on RESEARCH-ASSET-a52c58b217e48a75 recorded that a service certificate was replaced. The event references principal-8f17b08464430d9f. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Secret manager audit on SUPPORT-ASSET-c293b34ccf018f66 recorded that a workload read several secret versions. The event references principal-e464eb0ee46edc73. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Module audit on OPERATIONS-ASSET-da72125783fc7146 recorded that a process loaded a library from an application-local directory. The event references principal-88a37cd2d0222e86. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Driver audit on PROCUREMENT-ASSET-caa474ba78b6dce6 recorded that a kernel driver was loaded after a package installation. The event references principal-c43c37da7fba502b. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Kubernetes audit on ENGINEERING-ASSET-893d9de1f805e218 recorded that a cluster admission policy was changed. The event references principal-63fff86ce57d7e9d. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Mail audit on LEGAL-ASSET-2836d47d3aa0d5af recorded that an account received delegated access to a mailbox. The event references principal-e1699b7a3eeb56fc. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Dns server audit on SALES-ASSET-76b84b3e5488545e recorded that a client requested a DNS zone transfer. The event references principal-2d34f2bcf00115a7. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Kubernetes audit on ENGINEERING-ASSET-af728a774d91dcb8 recorded that a workload mounted a directory from its host filesystem. The event references principal-6a5b731d9f44ffa6. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Runtime audit on SALES-ASSET-65e80c7b6f9129ee recorded that a process connected to the container runtime socket. The event references principal-e74aec44693d5ee6. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Agent audit on PROCUREMENT-ASSET-92d810ab505277a2 recorded that a privileged session changed endpoint monitoring settings. The event references principal-ae67200926ed1d7a. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-2c31d9786760, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Ci audit on OPERATIONS-ASSET-3c47f8e04ce54395 recorded that a build pipeline definition gained a new execution step. The event references principal-4e3a0bcc0149b2b6. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"File audit on SALES-ASSET-8fef53d84dc3e73f recorded that a process deleted many files within a short interval. The event references principal-1dec5bfe36cba361. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Module audit on LEGAL-ASSET-2be7e49aaf02b41c recorded that a process loaded a library from an application-local directory. The event references principal-8d4bc02ab462cace. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-4d69547aa5b7, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Ssh audit on PEOPLE-ASSET-97ff8f8fa97fd164 recorded that an SSH session opened and requested elevated command execution. The event references principal-60b1e96c2c9d3478. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Assessment SEC-b3a24164fe36 explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Storage audit on RESEARCH-ASSET-6e2b243ec7d7a919 recorded that an object-storage access policy was broadened. The event references principal-262db57bffaea9f7. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Wmi audit on SALES-ASSET-54ac6fc961ae7d6a recorded that a management request started a process through WMI. The event references principal-08c8fa6d75a3b195. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Change CHG-d49c8129162e lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Macos launch audit on ENGINEERING-ASSET-20d414dac3bf58ed recorded that a launch agent definition was installed in a user context. The event references principal-9f713f5b46efadf7. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Ci audit on COMMUNICATIONS-ASSET-9c71cbe9ba5a6116 recorded that a build pipeline definition gained a new execution step. The event references principal-0b9701ae91042079. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Ssh audit on OPERATIONS-ASSET-324bfe1afe152ff0 recorded that an SSH session opened and requested elevated command execution. The event references principal-db6e14b705505251. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Identity audit on PEOPLE-ASSET-f09717db52bad024 recorded that an account password was reset through a recovery workflow. The event references principal-52a4edbb0422bb75. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Security retest SEC-76ddc8db8568 covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Dhcp telemetry on RESEARCH-ASSET-e4b53bee781b0891 recorded that a server issued DHCP offers on a monitored segment. The event references principal-7d24baa0336a4972. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Mfa audit on COMMUNICATIONS-ASSET-ce18db2b3211944f recorded that multiple MFA challenges were issued during a short interval. The event references principal-5c71c8caf74a8fa1. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Process audit on RESEARCH-ASSET-ff9cda8159f26be2 recorded that a remote-support application started an interactive session. The event references principal-c2840b0826e54ab4. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Kubernetes audit on LEGAL-ASSET-360df78a99aa884c recorded that a cluster admission policy was changed. The event references principal-fdbbb745932ee2f1. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Ssh audit on PROCUREMENT-ASSET-76513cf046529603 recorded that an SSH session opened and requested elevated command execution. The event references principal-5b3a8f0f85403c14. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Function audit on OPERATIONS-ASSET-7bf3d2cc7f955758 recorded that a serverless function package and execution settings were updated. The event references principal-2b7da48bc74786c4. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-262d0cbd3ca7 explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Package registry audit on ENGINEERING-ASSET-468e2f1736323150 recorded that a principal published a new package version. The event references principal-cbfd72c0328f2633. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Script audit on PEOPLE-ASSET-7674cfc3c8c8d12a recorded that a script interpreter decoded an encoded argument before execution. The event references principal-15233cc20a5664b0. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-f814a8150d9c specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Cloud control audit on SUPPORT-ASSET-50842d406b871613 recorded that a session deleted a group of cloud resources. The event references principal-5fa6a0bc38223f91. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Function audit on RESEARCH-ASSET-82ba6903f0ade88c recorded that a serverless function package and execution settings were updated. The event references principal-07c155fce40b0c1d. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Agent audit on OPERATIONS-ASSET-7f3ae95480df95bb recorded that a privileged session changed endpoint monitoring settings. The event references principal-2ff0c372aa7d7315. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Kerberos audit on LEGAL-ASSET-6ee4a0334d8b0730 recorded that an account requested service tickets for multiple services. The event references principal-2772005981d83d01. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Assessment SEC-8a7cb2fd4048 explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Module audit on LEGAL-ASSET-2be7e49aaf02b41c recorded that a process loaded a library from an application-local directory. The event references principal-8d4bc02ab462cace. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Cron audit on ENGINEERING-ASSET-0d57cc07ded38310 recorded that a recurring job definition was added to the system schedule. The event references principal-db05c7bee0f112c7. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-4ec013f0d813 match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Identity audit on OPERATIONS-ASSET-71fc600bd08a667f recorded that an account registered a new MFA method. The event references principal-717e0b47f1247c8b. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Policy audit on PEOPLE-ASSET-4626b13b6c89e82c recorded that an audit policy was changed to collect fewer event categories. The event references principal-dc47a10146c766ea. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Firewall audit on FINANCE-ASSET-d80ee8804a4ec6b6 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-b21644c32449b9a0. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-6eb8e5709a02, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Oauth audit on LEGAL-ASSET-00c7e53409190f35 recorded that an application received consent for additional account scopes. The event references principal-aa7e16ffa8e68220. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Winrm audit on OPERATIONS-ASSET-5123f251af3bff40 recorded that a remote management session invoked a command on a managed host. The event references principal-f7aa03e82682bdc9. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Gateway logs on ENGINEERING-ASSET-8864632089fd4c50 recorded that a client established a long-lived encapsulated network session. The event references principal-90ee640b3b5c5162. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-fbc3a2487e5e explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Policy audit on COMMUNICATIONS-ASSET-6bd03c52fee36269 recorded that an audit policy was changed to collect fewer event categories. The event references principal-89ce4ef5b0451d62. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-6393f49b2b84 specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Service audit on PEOPLE-ASSET-222cba6353f1d99f recorded that a new automatically started service was registered. The event references principal-e5172d8225074491. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Cloud identity audit on SUPPORT-ASSET-7e8f88bce8cfa9fc recorded that a principal received a policy granting additional permissions. The event references principal-02df9042c50f2455. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Service audit on COMMUNICATIONS-ASSET-9cb10b4818b88629 recorded that a remote service-control request created and started a temporary service. The event references principal-9f1825f9f69c7e5f. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-4ed8382c9c58 accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"File audit on RESEARCH-ASSET-29f4cb3c7a29beaf recorded that access permissions were broadened on a directory tree. The event references principal-9b108c0888253ab1. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Gateway logs on FINANCE-ASSET-0eba77ccb6dbdba6 recorded that a client established a long-lived encapsulated network session. The event references principal-5f89b733086ddfa5. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Dhcp telemetry on PEOPLE-ASSET-2fdf9f5c1cf8306c recorded that a server issued DHCP offers on a monitored segment. The event references principal-c81573ac45372a70. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Flow logs on RESEARCH-ASSET-6a2a326a382bb0b4 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-56d66c0e0a2c4463. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-c927e53599b4 match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Process audit on PROCUREMENT-ASSET-121cde9378adb9cf recorded that a JavaScript interpreter executed a local script. The event references principal-1a06985b864403e0. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Registry audit on SUPPORT-ASSET-3b0593850dd40f7b recorded that a registry logon-start entry was created. The event references principal-d3ff9c757ce4b24b. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Process audit on COMMUNICATIONS-ASSET-3540d4ca6c64eb07 recorded that a remote-support application started an interactive session. The event references principal-e3fe7b2bae9cee75. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-4205899ebb90 match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Share audit on ENGINEERING-ASSET-15ac20dc277a74c4 recorded that a new network file share was published. The event references principal-33c52b08167e103b. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-0abe726cfb4b, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Resolver logs on FINANCE-ASSET-702feb45e71dd31e recorded that a client requested many long, high-entropy DNS labels. The event references principal-219bc21f1d685857. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-6edb44fd6914 before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Mail audit on PEOPLE-ASSET-0dab505ef5721fa1 recorded that an account received delegated access to a mailbox. The event references principal-867e051f8d4b0f18. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-14d17e79f9ba, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Application audit on OPERATIONS-ASSET-82d2279115651372 recorded that an application read clipboard contents repeatedly. The event references principal-d93f4c8e19d295a8. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-49cd5ed18f81, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Kubernetes audit on SUPPORT-ASSET-99bd1381f9f84168 recorded that a pod was created with privileged execution enabled. The event references principal-4de29bd2a93d9674. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-3c9a3bbc2a6b before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Mfa audit on FINANCE-ASSET-77a6969db5ae1147 recorded that multiple MFA challenges were issued during a short interval. The event references principal-660a5b1395e78ef7. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Mail audit on PROCUREMENT-ASSET-d1aa07096744ffae recorded that an account received delegated access to a mailbox. The event references principal-77fb31a09163908c. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Process access audit on OPERATIONS-ASSET-a4047122fa1f8006 recorded that a process requested read access to another process memory space. The event references principal-b6f3ffe23361d9c9. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-0499e62c1d77 match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Kubernetes audit on RESEARCH-ASSET-7116d85c35ffeedd recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-5cfd10bdd7720813. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Runtime audit on RESEARCH-ASSET-1fdd4c74894a8860 recorded that a process connected to the container runtime socket. The event references principal-1fe12f7544607ca6. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Cloud control audit on OPERATIONS-ASSET-ba4ce4cf529ac35c recorded that a session deleted a group of cloud resources. The event references principal-2a7a606b1116d324. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-901d6d6611b0 accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Network control audit on LEGAL-ASSET-8a1d97d0c15ac118 recorded that a cloud security group gained a broad ingress rule. The event references principal-52d39a8366e69bf4. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Windows logon audit on PEOPLE-ASSET-45fa406199d2c14e recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-291516c4491afd57. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Mail audit on PROCUREMENT-ASSET-d1aa07096744ffae recorded that an account received delegated access to a mailbox. The event references principal-77fb31a09163908c. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Account audit on SUPPORT-ASSET-4f664bc059385d17 recorded that a local user account was created on a managed system. The event references principal-1db165dfba5895ba. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Key service audit on PEOPLE-ASSET-51157cbfcf0e7f8b recorded that a principal issued a burst of key-service decrypt requests. The event references principal-8c512aac8f2c3631. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Firewall audit on PROCUREMENT-ASSET-2bed3490436bbbc8 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-90a45122531200f3. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-9f4f8ffabc04 before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Kubernetes audit on SALES-ASSET-bd821e033a435876 recorded that a cluster admission policy was changed. The event references principal-57ab3d2d3751af5f. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Waf logs on PROCUREMENT-ASSET-be57d152ab66f42b recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-c19a63b81ac51b37. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Macos launch audit on PEOPLE-ASSET-f2ccd0993eb11ff9 recorded that a launch agent definition was installed in a user context. The event references principal-ff81666bc8b89437. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Process audit on COMMUNICATIONS-ASSET-5b837c3960f14bc6 recorded that a JavaScript interpreter executed a local script. The event references principal-f91a7e6de3b60959. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Egress flow logs on FINANCE-ASSET-6fc2f9679740efc1 recorded that a workload opened an encrypted connection to an external service. The event references principal-b6c8a10c3d36b1fc. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-6844b6db1c05, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Proxy logs on OPERATIONS-ASSET-63a9838a229b6bdc recorded that a client transferred a large payload to an external storage endpoint. The event references principal-1a271b9f4504e35e. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-d94746563278 specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Systemd audit on RESEARCH-ASSET-eeb116f31cbce82f recorded that a service unit file was changed and the unit reloaded. The event references principal-f39102d395b571c9. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-905bff863e09 before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Api gateway logs on ENGINEERING-ASSET-51721c37d612a2f5 recorded that a client issued a burst of API requests. The event references principal-b27ef27161423988. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Function audit on SALES-ASSET-461c1fc508bcc3ad recorded that a serverless function package and execution settings were updated. The event references principal-f88b3cc6828a81db. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Registry audit on RESEARCH-ASSET-73e0cbd02049afd1 recorded that a workload pulled a container image from a registry. The event references principal-34d7877cf1ae898f. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Script audit on OPERATIONS-ASSET-df5c95ab3d436943 recorded that a script interpreter decoded an encoded argument before execution. The event references principal-d244a19c467082bb. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-753940678453 specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Service audit on COMMUNICATIONS-ASSET-7e54b0ca38e553fe recorded that a new automatically started service was registered. The event references principal-7d549ca6bce506ce. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Compute audit on PROCUREMENT-ASSET-507dec859fa3003b recorded that a principal launched multiple compute instances. The event references principal-611c292a786d76ca. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Ci secret audit on LEGAL-ASSET-210117fa7f63e7fa recorded that a build job requested a protected pipeline secret. The event references principal-bafb03e4143599bb. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Certificate audit on PROCUREMENT-ASSET-90178e3809a5e39e recorded that a service certificate was replaced. The event references principal-4bfd3026e3966135. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Module audit on COMMUNICATIONS-ASSET-e298c38c58f7c346 recorded that a process loaded a library from an application-local directory. The event references principal-dd8d62077451bf1c. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-c2299d1302ea match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Cloud control audit on PROCUREMENT-ASSET-3d72a13549b9a584 recorded that resources were created in a region with little prior activity. The event references principal-a14765e1d71ea435. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Switch telemetry on SALES-ASSET-67150f5bd544c87a recorded that an address mapping changed repeatedly on a local segment. The event references principal-f4e3b1c2069d2a7e. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Configuration audit on PROCUREMENT-ASSET-8aac493103d32947 recorded that a client proxy setting was changed. The event references principal-5ba8d1fc71029290. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Cloud identity audit on SALES-ASSET-8e5fe4f751d14789 recorded that a new programmatic access key was issued to a principal. The event references principal-42ddd98f6ef91f59. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Security retest SEC-8aa5e90136c3 covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Dns control audit on SALES-ASSET-47a87d0c2fc4257b recorded that an authoritative DNS record was updated. The event references principal-3d712bbcbd3470d6. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-cb9306490a71, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Mail audit on PEOPLE-ASSET-0dab505ef5721fa1 recorded that an account received delegated access to a mailbox. The event references principal-867e051f8d4b0f18. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Wmi audit on SUPPORT-ASSET-3ffcf7de08c7ab9e recorded that a management request started a process through WMI. The event references principal-6bf936da5c9a2c76. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Browser audit on PEOPLE-ASSET-48ee486909d7e37c recorded that a browser extension with page-reading permissions was installed. The event references principal-0d329542446b1b23. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Systemd audit on SUPPORT-ASSET-38d3359b892c66ba recorded that a service unit file was changed and the unit reloaded. The event references principal-fbace7ec59135a92. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Code integrity audit on RESEARCH-ASSET-b23d57d440170815 recorded that an executable without a publisher signature started from a writable directory. The event references principal-a70693803f9dbb50. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"File audit on LEGAL-ASSET-4a73488ba2d33df6 recorded that a process rewrote multiple files into encrypted containers. The event references principal-9d7037ae8c34aa83. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Resolver logs on LEGAL-ASSET-3fa235a88f26dc9e recorded that a client requested many long, high-entropy DNS labels. The event references principal-1767397f4dd4b5b0. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Proxy logs on SUPPORT-ASSET-eadf40ef6aff627a recorded that a client transferred a large payload to an external storage endpoint. The event references principal-77e382cc165fce08. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Storage access logs on LEGAL-ASSET-6ac4fabec7ab5dad recorded that a principal downloaded many objects from a storage bucket. The event references principal-70ca2ffed3e11735. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Repository audit on SALES-ASSET-b9ab0defeef57d69 recorded that a user cloned several source repositories. The event references principal-0da3c44a52b416ce. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-5c81596a07c9 specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Driver audit on SALES-ASSET-74116b6362e956da recorded that a kernel driver was loaded after a package installation. The event references principal-9eaf8c722428f29b. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Registry audit on FINANCE-ASSET-7f731069af53e8e1 recorded that a workload pulled a container image from a registry. The event references principal-b80084fb240685bf. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Share audit on LEGAL-ASSET-f4d3a91d6248c724 recorded that a new network file share was published. The event references principal-9174cfcb163194b8. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Proxy logs on FINANCE-ASSET-f9b86d6f6b974e8f recorded that a client transferred a large payload to an external storage endpoint. The event references principal-252b9a9159e9be98. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Resolver logs on FINANCE-ASSET-702feb45e71dd31e recorded that a client requested many long, high-entropy DNS labels. The event references principal-219bc21f1d685857. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Mail flow logs on COMMUNICATIONS-ASSET-60efe7c42d543cb2 recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-6db1155a76f69a6b. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-33ab666c6bb5, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Identity audit on COMMUNICATIONS-ASSET-2afac15aebb6997b recorded that an account registered a new MFA method. The event references principal-48533b26142b2db4. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-1a39b489402c explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Resolver logs on OPERATIONS-ASSET-5135623224ddfa0b recorded that a client requested many long, high-entropy DNS labels. The event references principal-4817944b772fb8eb. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Identity audit on SUPPORT-ASSET-3fdea2c42e845651 recorded that a service account established an interactive session. The event references principal-6872260152bd6bd7. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Resolver logs on PEOPLE-ASSET-aa9ea5738fc3afe1 recorded that a client requested many long, high-entropy DNS labels. The event references principal-bd6f946855b371b5. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Windows logon audit on RESEARCH-ASSET-fcc9667f845ac430 recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-af2356cb5701209c. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Cloud identity audit on ENGINEERING-ASSET-02b155235f1959ea recorded that a principal received a policy granting additional permissions. The event references principal-d5dc51acc5293d03. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Api gateway logs on SUPPORT-ASSET-13bc954846049d2f recorded that a client issued a burst of API requests. The event references principal-d482be68e022a834. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-2b8ce66afaee specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Vpn audit on PEOPLE-ASSET-8b15c5e5fc77cfb3 recorded that a remote-access VPN session was established. The event references principal-61e8cff53a9f17ad. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Mail audit on SUPPORT-ASSET-af2380a8ab001950 recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-d2de6ff979b628f2. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Ci secret audit on OPERATIONS-ASSET-e1c6669f5f29a589 recorded that a build job requested a protected pipeline secret. The event references principal-e8010ec93fff4989. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Switch telemetry on COMMUNICATIONS-ASSET-bcb43f0616b1a470 recorded that an address mapping changed repeatedly on a local segment. The event references principal-ea5a7f0eef9db0e7. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-a1e9fc66b281 covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Driver audit on FINANCE-ASSET-4d3885b7e2a2eaaa recorded that a kernel driver was loaded after a package installation. The event references principal-93dddd296bcd4a0a. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Repository audit on SUPPORT-ASSET-fb6027084fb1957b recorded that a user cloned several source repositories. The event references principal-6318dd66af34e88b. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Winrm audit on PEOPLE-ASSET-f67c81ba2aebe0a8 recorded that a remote management session invoked a command on a managed host. The event references principal-380dff97d88676ce. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"File audit on ENGINEERING-ASSET-52718af8394d4c73 recorded that a shell startup profile gained an additional command. The event references principal-7fbddd513d8c8d82. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Directory audit on PROCUREMENT-ASSET-7b387a0e6a39eb7a recorded that a principal requested directory replication data. The event references principal-0b3c6bcdb6ea6190. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Key service audit on LEGAL-ASSET-c93c39a0bf6d5d2d recorded that a principal issued a burst of key-service decrypt requests. The event references principal-a9f8c5175e6aa291. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Mail audit on RESEARCH-ASSET-fad2d601f38f7cda recorded that an account received delegated access to a mailbox. The event references principal-b5e074cc28811f03. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Dhcp telemetry on ENGINEERING-ASSET-16a2bd6b5dab3cb6 recorded that a server issued DHCP offers on a monitored segment. The event references principal-d5a61a238fb861fb. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Dns server audit on LEGAL-ASSET-9a776b98cec96a9e recorded that a client requested a DNS zone transfer. The event references principal-b7047a9785be46d4. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Security retest SEC-007e0c335ceb covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Code integrity audit on SALES-ASSET-c410ab31c1f04772 recorded that an executable without a publisher signature started from a writable directory. The event references principal-9e4abca76b69be64. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-25cc4ae49bb3 accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Mail and proxy logs on PEOPLE-ASSET-73f46f787c3750bc recorded that a user opened a URL delivered in an email message. The event references principal-ae3654afd7401601. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Egress flow logs on LEGAL-ASSET-1a606b14eab96fee recorded that a workload opened an encrypted connection to an external service. The event references principal-d6bec1039eca165c. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-ad18bfe9fc04 match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Macos launch audit on COMMUNICATIONS-ASSET-a6af7f5427b7cdc8 recorded that a launch agent definition was installed in a user context. The event references principal-1aeb8103bbf51c1f. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Browser audit on OPERATIONS-ASSET-1696f264e915fdf5 recorded that a browser extension with page-reading permissions was installed. The event references principal-f101b193c2f738a3. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Mail flow logs on COMMUNICATIONS-ASSET-60efe7c42d543cb2 recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-6db1155a76f69a6b. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Systemd audit on PROCUREMENT-ASSET-e562e2af350db7c6 recorded that a service unit file was changed and the unit reloaded. The event references principal-a239fb376cfcf526. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Gateway logs on PROCUREMENT-ASSET-b0d37645a10d287b recorded that a client established a long-lived encapsulated network session. The event references principal-1cc47c7a352875b2. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"File audit on FINANCE-ASSET-a4971629c23d55d9 recorded that a process compressed files from several directories into an archive. The event references principal-c74fdddea36d843d. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Dhcp telemetry on FINANCE-ASSET-99d84bf5e5de071b recorded that a server issued DHCP offers on a monitored segment. The event references principal-e238480421ab2c07. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Federation audit on PROCUREMENT-ASSET-627d4b1e14d07688 recorded that a tenant federation setting was updated. The event references principal-be363e08050ad9ec. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-cc8678bd92a7 accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Kubernetes audit on PEOPLE-ASSET-3e58a2eca5c63a44 recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-8f985c1a713a28f2. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Mail and proxy logs on RESEARCH-ASSET-0d6948f11ee5b28e recorded that a user opened a URL delivered in an email message. The event references principal-fdb003c9c4c80093. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Switch telemetry on LEGAL-ASSET-1643dbdebba2d78d recorded that an address mapping changed repeatedly on a local segment. The event references principal-c39fe907de3611c7. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Change CHG-0c675dc87c93 lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Account audit on OPERATIONS-ASSET-ad56fc4183b7ca9d recorded that a local user account was created on a managed system. The event references principal-fe2941e164dbf1c4. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-37fdbbbb1f79 before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Identity audit on COMMUNICATIONS-ASSET-2afac15aebb6997b recorded that an account registered a new MFA method. The event references principal-48533b26142b2db4. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-1a39b489402c specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Device and file audit on ENGINEERING-ASSET-c9b77c2a506ace86 recorded that files were copied to a removable storage device. The event references principal-7078af09729168a5. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Directory audit on OPERATIONS-ASSET-f0615ba52c4fafcb recorded that a principal requested directory replication data. The event references principal-c94c73361a03e2ca. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Cloud control audit on SALES-ASSET-5ed8420ac6bfabb9 recorded that a session deleted a group of cloud resources. The event references principal-e108fb64fd38558b. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Flow logs on LEGAL-ASSET-bb14ef480a9f5aa0 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-343b8b6d62a9710b. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Cloud control audit on LEGAL-ASSET-428365c6643172ec recorded that a cloud logging destination was disabled. The event references principal-5fcf49df98dad6ed. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Identity audit on SUPPORT-ASSET-15695a645557b69f recorded that repeated failed sign-ins were recorded for an account. The event references principal-51d00d36a920ed83. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Registry audit on ENGINEERING-ASSET-bd489c9ae7fbc817 recorded that a workload pulled a container image from a registry. The event references principal-95061e15f3e7bbec. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Agent audit on PEOPLE-ASSET-145b133cd9883db8 recorded that a privileged session changed endpoint monitoring settings. The event references principal-3cdfd17f049efdd9. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-9749b3e190f3 before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Service audit on PROCUREMENT-ASSET-28254d89b1701083 recorded that a remote service-control request created and started a temporary service. The event references principal-cfe7f7b5911dcb16. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Firewall audit on SALES-ASSET-67b90170bfed122f recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-2766646810a01a28. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Code integrity audit on LEGAL-ASSET-f6d743064b804557 recorded that an executable without a publisher signature started from a writable directory. The event references principal-4ea2e2cfcda079aa. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Process access audit on FINANCE-ASSET-247c48e4c49c174e recorded that a process requested read access to another process memory space. The event references principal-601055cfd3a85372. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Process access audit on LEGAL-ASSET-60fd34b6e0203a0f recorded that a process requested read access to another process memory space. The event references principal-1e4fdc2f020fb533. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Dns server audit on RESEARCH-ASSET-ea10daa512b8b485 recorded that a client requested a DNS zone transfer. The event references principal-8e8e3e27caaa4cef. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Service audit on FINANCE-ASSET-d962ba7a33513380 recorded that a new automatically started service was registered. The event references principal-238acc934bc77540. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-a474b67a7281 match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"File audit on OPERATIONS-ASSET-a72fe66e9e140fe9 recorded that a process compressed files from several directories into an archive. The event references principal-41403cc0bff319ee. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-3e7e35cdc4df, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Gateway logs on OPERATIONS-ASSET-7599af3c268c4876 recorded that a client established a long-lived encapsulated network session. The event references principal-ba0168660aabc1f0. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-1b2acd78d056 specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Process audit on FINANCE-ASSET-db3968cef4c0b684 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-a71f596247827755. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Change CHG-c4e299a7a297 lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Service audit on LEGAL-ASSET-c576aa1679d54c28 recorded that a new automatically started service was registered. The event references principal-7b1165f4385ce850. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Switch telemetry on ENGINEERING-ASSET-271d6935661ca5b6 recorded that an address mapping changed repeatedly on a local segment. The event references principal-2aa672d045fc50f4. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-bca4c9b02578 specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Process audit on SUPPORT-ASSET-0577991db5a15090 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-d0dbfe56694e1edd. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Registry audit on OPERATIONS-ASSET-2d36b1b63d0c4ad6 recorded that a workload pulled a container image from a registry. The event references principal-1fdf41d42655dccc. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Oauth audit on LEGAL-ASSET-00c7e53409190f35 recorded that an application received consent for additional account scopes. The event references principal-aa7e16ffa8e68220. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-17942d82e1c5 before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Egress flow logs on RESEARCH-ASSET-33b44f93ed777432 recorded that a workload opened an encrypted connection to an external service. The event references principal-33501a4209ab69ba. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-2f34abd85ff6 before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Dns control audit on LEGAL-ASSET-b16c2ea371640162 recorded that an authoritative DNS record was updated. The event references principal-162d081f9776c04e. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Database audit on SALES-ASSET-849ddfe1a9053808 recorded that a session changed a database table definition. The event references principal-425b4fae9e8852ef. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Service audit on PROCUREMENT-ASSET-28254d89b1701083 recorded that a remote service-control request created and started a temporary service. The event references principal-cfe7f7b5911dcb16. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-5c3cc25513dc match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Event service audit on RESEARCH-ASSET-79d1b62714d14ec4 recorded that an event log was cleared by a privileged request. The event references principal-78e29e015c8aeb2f. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Macos launch audit on PROCUREMENT-ASSET-cefeabfcdbb75ff5 recorded that a launch agent definition was installed in a user context. The event references principal-61b165b4264637cc. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Process audit on OPERATIONS-ASSET-6a681893d2f34701 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-7a707bcde872789a. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Service audit on PEOPLE-ASSET-222cba6353f1d99f recorded that a new automatically started service was registered. The event references principal-e5172d8225074491. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-7c6be80fdd9d specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Dhcp telemetry on PEOPLE-ASSET-2fdf9f5c1cf8306c recorded that a server issued DHCP offers on a monitored segment. The event references principal-c81573ac45372a70. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Function audit on SUPPORT-ASSET-639b47faa57b7d52 recorded that a serverless function package and execution settings were updated. The event references principal-142321e2377f77dd. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Network control audit on SUPPORT-ASSET-badb98bf2185855c recorded that a cloud security group gained a broad ingress rule. The event references principal-1a508d07acbfb51b. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Package registry audit on PEOPLE-ASSET-63788b9d7987296c recorded that a principal published a new package version. The event references principal-1efd21efeb7b167e. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Security retest SEC-ad609ea87d3c covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Registry audit on ENGINEERING-ASSET-3288f3a3a57d4d49 recorded that a registry logon-start entry was created. The event references principal-ab71b58d6c6b1b8b. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-2e0e26e6e466 specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Flow logs on SUPPORT-ASSET-30ebec702fd5fb40 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-cc4ef6967d7bd3d5. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Mfa audit on LEGAL-ASSET-e69fa0a56ff82707 recorded that multiple MFA challenges were issued during a short interval. The event references principal-f4248a85a02aa075. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Process audit on LEGAL-ASSET-1d30eece58fd02aa recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-73ea530a0de82f6d. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Flow logs on SALES-ASSET-e03d7f92d970afc6 recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-7f74331f29d46d56. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Kubernetes audit on OPERATIONS-ASSET-e5571d0159c5e55b recorded that a pod was created with privileged execution enabled. The event references principal-4016297e67e67765. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-8d29f4726b22 before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Oauth audit on PROCUREMENT-ASSET-2f4aab546bd1bb38 recorded that an application received consent for additional account scopes. The event references principal-eef62ccd4ff2398c. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-01c2a5255461 specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Event service audit on COMMUNICATIONS-ASSET-a0753c1183185be8 recorded that an event log was cleared by a privileged request. The event references principal-3da9da5b32a84636. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Driver audit on COMMUNICATIONS-ASSET-b8154a780e8f0180 recorded that a kernel driver was loaded after a package installation. The event references principal-5b575ab65094c162. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Kubernetes audit on COMMUNICATIONS-ASSET-f76c1c782f04bc0e recorded that a workload mounted a directory from its host filesystem. The event references principal-ea22af4c35053180. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Process access audit on SALES-ASSET-0e0ff0d46dd9bdcc recorded that a process requested read access to another process memory space. The event references principal-a29d7cafdbef1526. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Macos launch audit on LEGAL-ASSET-924fcf03a30c9333 recorded that a launch agent definition was installed in a user context. The event references principal-188d4edbd5c47469. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Share audit on PEOPLE-ASSET-29ff2158775d3e8d recorded that a new network file share was published. The event references principal-d660d14bb1dc5e12. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Browser audit on SALES-ASSET-2c13db88f9fe11a1 recorded that a browser extension with page-reading permissions was installed. The event references principal-dfbfeb6ce6f75d60. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Runtime audit on SUPPORT-ASSET-70bd103925bca47e recorded that a process connected to the container runtime socket. The event references principal-cf65589a3d4ad7b6. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-a7210d088fbb before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Kubernetes audit on OPERATIONS-ASSET-e9cb557fa33c100a recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-d1c39d3b8db93b55. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Cloud control audit on PEOPLE-ASSET-a565fc161c06dbdd recorded that a cloud logging destination was disabled. The event references principal-b1342e9d7cf466d7. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-2bb8392ca81d specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Cloud control audit on OPERATIONS-ASSET-31b25a4a2bbf0f7e recorded that resources were created in a region with little prior activity. The event references principal-2043ac1bd7256aa6. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Process audit on PROCUREMENT-ASSET-3482b66b87c99633 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-a0877a981b03e4e2. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-67ece2db4354 match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Function audit on ENGINEERING-ASSET-1db2f1c877763b47 recorded that a serverless function package and execution settings were updated. The event references principal-79d1bb9e5af18d47. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Switch telemetry on COMMUNICATIONS-ASSET-bcb43f0616b1a470 recorded that an address mapping changed repeatedly on a local segment. The event references principal-ea5a7f0eef9db0e7. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Wmi audit on FINANCE-ASSET-9fd34fa594551e66 recorded that a management request started a process through WMI. The event references principal-1f38151c7990e366. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Process access audit on RESEARCH-ASSET-d44095e784b89a49 recorded that a process requested read access to another process memory space. The event references principal-961efc1f116f534c. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Event service audit on PEOPLE-ASSET-3e7af42f465f079f recorded that an event log was cleared by a privileged request. The event references principal-7e44d019c9f83317. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Database audit on COMMUNICATIONS-ASSET-4fefa2aaca8d930a recorded that a session changed a database table definition. The event references principal-257c7d24c9971d35. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Script audit on LEGAL-ASSET-38bacff4f7d252bf recorded that a script interpreter decoded an encoded argument before execution. The event references principal-0e6d8e54a19c536c. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"File audit on SALES-ASSET-a4a69365dce2152a recorded that a shell startup profile gained an additional command. The event references principal-3637027719cb9240. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Group audit on PROCUREMENT-ASSET-b50d9791f482d6f4 recorded that an account was added to a privileged local group. The event references principal-c07c3b076842f6c0. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Process audit on FINANCE-ASSET-7c0fff41e30d4380 recorded that a JavaScript interpreter executed a local script. The event references principal-5ba5da6cfca5af4e. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Code integrity audit on FINANCE-ASSET-17d7fd3ccdbe7a13 recorded that an executable without a publisher signature started from a writable directory. The event references principal-8715ecce18f6c074. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Dns control audit on RESEARCH-ASSET-f829e9e9bed9564b recorded that an authoritative DNS record was updated. The event references principal-9fdc73540b6a06a8. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Kubernetes audit on SUPPORT-ASSET-46e0923b16c1de93 recorded that a cluster admission policy was changed. The event references principal-eb0f85c559534d98. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Smb audit on ENGINEERING-ASSET-167b039744d858de recorded that a session enumerated a file share and read multiple files. The event references principal-dae2d90d16568727. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Kubernetes audit on SALES-ASSET-3af15ceafaf37a50 recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-4e40a79e1d1cac1f. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Mfa audit on PROCUREMENT-ASSET-9ec036de13de448d recorded that multiple MFA challenges were issued during a short interval. The event references principal-906c50bf72cf0c69. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Identity audit on FINANCE-ASSET-5eeb4551c8b1c0e3 recorded that an account registered a new MFA method. The event references principal-0a574aaa6eaa69b8. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-a79dfaae3330 accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Smb audit on SUPPORT-ASSET-e1998cccd3abd998 recorded that a session enumerated a file share and read multiple files. The event references principal-3be2aaf5e58c794d. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-c55b3433a235 before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"File audit on ENGINEERING-ASSET-52718af8394d4c73 recorded that a shell startup profile gained an additional command. The event references principal-7fbddd513d8c8d82. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Directory audit on SUPPORT-ASSET-657351ecbd6ea04f recorded that a principal requested directory replication data. The event references principal-415e143ac445aa25. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-8e0ca2de5536 match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Mfa audit on LEGAL-ASSET-e69fa0a56ff82707 recorded that multiple MFA challenges were issued during a short interval. The event references principal-f4248a85a02aa075. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Security retest SEC-75e8a7b4c9af covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Network control audit on FINANCE-ASSET-93401772cf68a3aa recorded that a cloud security group gained a broad ingress rule. The event references principal-b7b99f534a1030f4. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-cdbe2fecad4a specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Directory audit on OPERATIONS-ASSET-f0615ba52c4fafcb recorded that a principal requested directory replication data. The event references principal-c94c73361a03e2ca. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"File audit on PROCUREMENT-ASSET-a3fde179ef5ff962 recorded that access permissions were broadened on a directory tree. The event references principal-bb1784cca8241c87. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Saas audit on PEOPLE-ASSET-5249110e05a8362d recorded that a user requested a bulk export from a business application. The event references principal-55b28360ed7bad44. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-93c1c5c35008 specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Api gateway logs on OPERATIONS-ASSET-5d940a8c3c4b311c recorded that a client issued a burst of API requests. The event references principal-9965146148dbdc29. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Kubernetes audit on FINANCE-ASSET-e06cf007729f9dbe recorded that a workload mounted a directory from its host filesystem. The event references principal-76bf38f3f96381c7. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Kerberos audit on RESEARCH-ASSET-add8a0192da6108f recorded that an account requested service tickets for multiple services. The event references principal-2289755f000d3a1a. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Event service audit on SALES-ASSET-c924bb512f8f20fd recorded that an event log was cleared by a privileged request. The event references principal-c440dcbeadedc4d2. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Database audit on OPERATIONS-ASSET-dec2bfd2d0808b67 recorded that a session changed a database table definition. The event references principal-0583f5a376c3e442. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Flow logs on PROCUREMENT-ASSET-6efd3fd7c57f6ea6 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-2f79b909f0a96c76. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-511018847469 before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Dns control audit on OPERATIONS-ASSET-d3932800e26302a2 recorded that an authoritative DNS record was updated. The event references principal-acc181df5bf7ded9. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-151c76255ba5 explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Identity audit on LEGAL-ASSET-943053d6267ac572 recorded that a service account established an interactive session. The event references principal-158c8b7f105115ea. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Gateway logs on SUPPORT-ASSET-bfcdc7fd12a63ce3 recorded that a client established a long-lived encapsulated network session. The event references principal-076e693836d2e9e9. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"File audit on FINANCE-ASSET-d2b45ac726791f9b recorded that a process deleted many files within a short interval. The event references principal-e041b8a80436a62f. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Egress flow logs on SALES-ASSET-a811cdcc9969f943 recorded that a workload opened an encrypted connection to an external service. The event references principal-17514c019150a73d. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Kubernetes audit on FINANCE-ASSET-8c8a0667d1ab346c recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-8cde8f18db765ef8. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Assessment SEC-f8cb3bcf80f0 explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Kubernetes audit on OPERATIONS-ASSET-e9cb557fa33c100a recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-d1c39d3b8db93b55. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-fe4f3d7c33ec accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Function audit on LEGAL-ASSET-a808b2dbcafaf1de recorded that a serverless function package and execution settings were updated. The event references principal-d18e2930c59bbade. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Assessment SEC-fafde95d18dc explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Account audit on SALES-ASSET-b02113ff8562d223 recorded that a local user account was created on a managed system. The event references principal-3cbed1cc8fc2d897. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Smb audit on OPERATIONS-ASSET-903799bcbb7f90a6 recorded that a session enumerated a file share and read multiple files. The event references principal-b3bfcfbe522db4bd. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Policy audit on SALES-ASSET-8b2e5805c0958f81 recorded that an audit policy was changed to collect fewer event categories. The event references principal-55b368edee8e470a. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-d327962a3c85 before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Storage access logs on ENGINEERING-ASSET-cfa9edf25dbd11b0 recorded that a principal downloaded many objects from a storage bucket. The event references principal-9a3a0f64a8f2a35d. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-2413fe523ec4, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Ci secret audit on RESEARCH-ASSET-d46af760b3fcf2d7 recorded that a build job requested a protected pipeline secret. The event references principal-60fe7cbc94a757b5. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-8df5b8ef971a specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Process audit on COMMUNICATIONS-ASSET-3540d4ca6c64eb07 recorded that a remote-support application started an interactive session. The event references principal-e3fe7b2bae9cee75. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Kubernetes audit on SALES-ASSET-ffd4e9bc10275050 recorded that a pod was created with privileged execution enabled. The event references principal-02bcfaa51dffcded. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Application audit on SALES-ASSET-9a8acf9f0cbf6165 recorded that an application read clipboard contents repeatedly. The event references principal-114c22ed14b6a3d7. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Kubernetes audit on FINANCE-ASSET-4f8f4d9f800ab9a6 recorded that a cluster admission policy was changed. The event references principal-0f727ece26b623bd. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Application audit on SALES-ASSET-5a207e0d30dc6722 recorded that an application requested repeated screen captures. The event references principal-e579eecfc7c0f733. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-e2dae95873d2 before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Mfa audit on PEOPLE-ASSET-e45fffd30cf466e9 recorded that multiple MFA challenges were issued during a short interval. The event references principal-3cbfe5aa85664020. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"File audit on ENGINEERING-ASSET-34a8ce1c539d9368 recorded that a process deleted many files within a short interval. The event references principal-c1c689ef96642a7c. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Api gateway logs on PEOPLE-ASSET-010de515bde4832b recorded that a client issued a burst of API requests. The event references principal-828fabb7c52c8ecb. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-fd7dac0ee493 match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Session audit on SALES-ASSET-e0e65cd3109e663e recorded that the same session token appeared from different client addresses. The event references principal-b32690205f2a72fc. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Process audit on COMMUNICATIONS-ASSET-332afb2165aa1448 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-afe5b84c8ef31787. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Process audit on COMMUNICATIONS-ASSET-332afb2165aa1448 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-afe5b84c8ef31787. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Service audit on PEOPLE-ASSET-7556bd332c3c0972 recorded that a remote service-control request created and started a temporary service. The event references principal-40ab931ed8bd0b59. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Egress flow logs on SUPPORT-ASSET-ff3badb46e903585 recorded that a workload opened an encrypted connection to an external service. The event references principal-ef7dbc8f1e7b6a52. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Driver audit on COMMUNICATIONS-ASSET-b8154a780e8f0180 recorded that a kernel driver was loaded after a package installation. The event references principal-5b575ab65094c162. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Key service audit on COMMUNICATIONS-ASSET-5437588d51522a99 recorded that a principal issued a burst of key-service decrypt requests. The event references principal-f88907eb1e848f20. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-0523046703ba explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Kubernetes audit on PEOPLE-ASSET-fb423ebd814658c2 recorded that a role binding granted a principal additional cluster permissions. The event references principal-1e6683e3ee80066c. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Database audit on LEGAL-ASSET-3632866debb967ca recorded that a session changed a database table definition. The event references principal-862aa2954135f309. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Mail audit on FINANCE-ASSET-c2947168e63669b0 recorded that an account received delegated access to a mailbox. The event references principal-33d9797e6b81280e. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Resolver logs on SALES-ASSET-17cdfcbdaddd4989 recorded that a client requested many long, high-entropy DNS labels. The event references principal-fddd379e6737bcc0. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-b2e64229228f explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Process audit on PEOPLE-ASSET-534c3950a47d5a64 recorded that a JavaScript interpreter executed a local script. The event references principal-8170f0f562dc21d2. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Process audit on PROCUREMENT-ASSET-4c9b1e536ca1f43f recorded that a Python interpreter loaded a script and contacted a service. The event references principal-f1d7ec01883c26bc. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Process audit on SUPPORT-ASSET-6869d2722a21fd5c recorded that a Python interpreter loaded a script and contacted a service. The event references principal-f677ab6a5a1c21d4. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-b938cc1adc67 match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Process audit on RESEARCH-ASSET-4c23face5574e971 recorded that a JavaScript interpreter executed a local script. The event references principal-4325acfa278d2f70. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Driver audit on OPERATIONS-ASSET-16afbb03ee82c54d recorded that a kernel driver was loaded after a package installation. The event references principal-32362e7a45f17c8f. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Policy audit on SUPPORT-ASSET-6952fff6cd8e7039 recorded that an audit policy was changed to collect fewer event categories. The event references principal-c6ab36fb929298bf. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Dhcp telemetry on RESEARCH-ASSET-e4b53bee781b0891 recorded that a server issued DHCP offers on a monitored segment. The event references principal-7d24baa0336a4972. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Driver audit on PEOPLE-ASSET-9e9f7519775a6002 recorded that a kernel driver was loaded after a package installation. The event references principal-4bafb24bfe647837. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Process audit on LEGAL-ASSET-ffdcc64fc856fa3d recorded that a JavaScript interpreter executed a local script. The event references principal-a45f3b91beb56205. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Macos launch audit on RESEARCH-ASSET-76ee756c91d53577 recorded that a launch agent definition was installed in a user context. The event references principal-cd202933651b57f9. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Identity audit on FINANCE-ASSET-5eeb4551c8b1c0e3 recorded that an account registered a new MFA method. The event references principal-0a574aaa6eaa69b8. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Dhcp telemetry on ENGINEERING-ASSET-16a2bd6b5dab3cb6 recorded that a server issued DHCP offers on a monitored segment. The event references principal-d5a61a238fb861fb. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Secret manager audit on FINANCE-ASSET-848c4b906d36b1f9 recorded that a workload read several secret versions. The event references principal-2d99961e29099c47. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Service audit on FINANCE-ASSET-271527485b0e477e recorded that a remote service-control request created and started a temporary service. The event references principal-31971ac078081c89. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Application audit on COMMUNICATIONS-ASSET-365eaf894be6367d recorded that an application read clipboard contents repeatedly. The event references principal-c9d903188ad53746. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Device and file audit on RESEARCH-ASSET-6da8ae6d7bfc1fd2 recorded that files were copied to a removable storage device. The event references principal-6e75da4e311027c4. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Secret manager audit on OPERATIONS-ASSET-9fccf4aa5cb6d2fb recorded that a workload read several secret versions. The event references principal-67a3ab465380b229. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-d1aed61cc26c match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Task scheduler audit on COMMUNICATIONS-ASSET-3b8f70e54b109a07 recorded that a scheduled task was registered to execute a program at logon. The event references principal-ea7b65d7a85105ed. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-a6f827999475 match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Oauth audit on ENGINEERING-ASSET-6abd006369fb2ea6 recorded that an application received consent for additional account scopes. The event references principal-7b515ef2be2fa58b. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Vpn audit on SUPPORT-ASSET-e419f3a293f3417a recorded that a remote-access VPN session was established. The event references principal-09df6291fa9e8663. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Process access audit on COMMUNICATIONS-ASSET-5d86ffc7f1150e70 recorded that a process requested read access to another process memory space. The event references principal-4279d106b274e43e. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Cloud identity audit on SALES-ASSET-97a28d40051be12b recorded that a principal received a policy granting additional permissions. The event references principal-e45a694b7e0b8b49. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Windows logon audit on PEOPLE-ASSET-45fa406199d2c14e recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-291516c4491afd57. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Winrm audit on PEOPLE-ASSET-f67c81ba2aebe0a8 recorded that a remote management session invoked a command on a managed host. The event references principal-380dff97d88676ce. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-ccd1f98e04ad accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Certificate audit on SUPPORT-ASSET-bf2e59d8cf05d409 recorded that a service certificate was replaced. The event references principal-3f10d0f128334232. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Mfa audit on OPERATIONS-ASSET-60e8646a52166a20 recorded that multiple MFA challenges were issued during a short interval. The event references principal-db3cac7564325f27. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Waf logs on FINANCE-ASSET-2688c7caaa5c3540 recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-fa0ae08c81b790e0. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Cloud control audit on SUPPORT-ASSET-e66fe35db626a7f0 recorded that resources were created in a region with little prior activity. The event references principal-84f7c4bc4b40ce6e. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Egress flow logs on RESEARCH-ASSET-33b44f93ed777432 recorded that a workload opened an encrypted connection to an external service. The event references principal-33501a4209ab69ba. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Storage access logs on LEGAL-ASSET-6ac4fabec7ab5dad recorded that a principal downloaded many objects from a storage bucket. The event references principal-70ca2ffed3e11735. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-7f38b88b6d36 match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"File audit on COMMUNICATIONS-ASSET-4e97ae367849b7ff recorded that a process deleted many files within a short interval. The event references principal-0d2d1e13b6f37e28. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Registry audit on RESEARCH-ASSET-e5e233361fd38697 recorded that a registry logon-start entry was created. The event references principal-83333208692c8fd1. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-55ecbf101a68, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Federation audit on LEGAL-ASSET-81a8982089dddbeb recorded that a tenant federation setting was updated. The event references principal-c29fe59344f3b4d5. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Assessment SEC-38bf7086c8b9 explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Storage audit on OPERATIONS-ASSET-07e77010a446667b recorded that a session deleted several storage snapshots. The event references principal-fc81340c87f20845. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Identity audit on OPERATIONS-ASSET-775dd42bd2b2e216 recorded that repeated failed sign-ins were recorded for an account. The event references principal-2f8b852f1ede3573. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-c16aa050fbd5 explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Wmi audit on COMMUNICATIONS-ASSET-03aadd8a551fef8d recorded that a management request started a process through WMI. The event references principal-1c1aa32fcc8fde6b. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Vpn audit on PEOPLE-ASSET-8b15c5e5fc77cfb3 recorded that a remote-access VPN session was established. The event references principal-61e8cff53a9f17ad. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Identity audit on LEGAL-ASSET-3e81b75ec6767272 recorded that repeated failed sign-ins were recorded for an account. The event references principal-4e9f85f638a1922a. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-4cadd9e49db7 accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Storage access logs on FINANCE-ASSET-c07c58461c3886b7 recorded that a principal downloaded many objects from a storage bucket. The event references principal-636661caf69ea2cc. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Flow logs on PEOPLE-ASSET-48ed1d716acee890 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-d5ba1580babde1ed. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"File audit on FINANCE-ASSET-2a7828c17a1b3f24 recorded that a shell startup profile gained an additional command. The event references principal-4b7e3cd5eb46c9e6. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Backup audit on OPERATIONS-ASSET-b26fa319d3d0ce69 recorded that a backup retention policy was shortened. The event references principal-428102206d771c95. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Storage audit on FINANCE-ASSET-768fdc22d9585f23 recorded that an object-storage access policy was broadened. The event references principal-18ac2fe076b447b0. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Ci audit on LEGAL-ASSET-307a1ab2be77fe5f recorded that a build pipeline definition gained a new execution step. The event references principal-362aa0b8c3b22688. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Cloud identity audit on PROCUREMENT-ASSET-cb3bd3ac326cf3b2 recorded that a principal assumed a role in another account. The event references principal-131a52eaecf4978f. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Kubernetes audit on PEOPLE-ASSET-46959b0322e15f66 recorded that a pod was created with privileged execution enabled. The event references principal-8e6c04f200191e81. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Identity audit on ENGINEERING-ASSET-17f1d906d8c35962 recorded that a service account established an interactive session. The event references principal-4e2ae7344e474fce. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-6823b059a3f0 accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Api gateway logs on ENGINEERING-ASSET-51721c37d612a2f5 recorded that a client issued a burst of API requests. The event references principal-b27ef27161423988. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-dbfcc2e040b6 before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Storage audit on SUPPORT-ASSET-519ebc03fcafbccd recorded that a session deleted several storage snapshots. The event references principal-1671f42126c1c5f8. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Flow logs on FINANCE-ASSET-b04c464556b8fa8d recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-4fa1efc3a212390d. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Task scheduler audit on OPERATIONS-ASSET-0c0ccf4949e6876b recorded that a scheduled task was registered to execute a program at logon. The event references principal-6b1b6724d1e28e1c. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"File audit on OPERATIONS-ASSET-a77dace88afed479 recorded that a process rewrote multiple files into encrypted containers. The event references principal-9bd0bfba4bc5c80f. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Mail audit on FINANCE-ASSET-ea1b6c24422b456d recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-44026a910bd0b4c9. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-e8304a8f42c5 explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Registry audit on FINANCE-ASSET-7f731069af53e8e1 recorded that a workload pulled a container image from a registry. The event references principal-b80084fb240685bf. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Change CHG-a2e202aef390 lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Kubernetes audit on RESEARCH-ASSET-d1f7ab9c3de5615d recorded that a cluster admission policy was changed. The event references principal-bc8aec70f878822d. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Repository audit on ENGINEERING-ASSET-501895f2c603da6f recorded that a user cloned several source repositories. The event references principal-08a3df240a2c2acb. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-c02e94fec34e before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Mail audit on COMMUNICATIONS-ASSET-cf30ec21588a2145 recorded that an account received delegated access to a mailbox. The event references principal-a11312ab2e69f315. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-47cf25683cbd specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Smb audit on OPERATIONS-ASSET-903799bcbb7f90a6 recorded that a session enumerated a file share and read multiple files. The event references principal-b3bfcfbe522db4bd. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Cloud control audit on COMMUNICATIONS-ASSET-c7835ea641b313a9 recorded that a session deleted a group of cloud resources. The event references principal-5e2ab493e683591c. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-e11f66c3baf1 specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Kubernetes audit on LEGAL-ASSET-82e9dc780e2f0fb0 recorded that a pod was created with privileged execution enabled. The event references principal-7d1067f1bf4b8bd0. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Configuration audit on ENGINEERING-ASSET-05746d5c7e76781e recorded that a client proxy setting was changed. The event references principal-f4f857793a1cd276. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-a34f9c2d6782 match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Package registry audit on FINANCE-ASSET-39c7276454a893cc recorded that a principal published a new package version. The event references principal-9e718ff7956300e6. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Change CHG-9032d3d3edb0 lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Gateway logs on PEOPLE-ASSET-755d4ede711826a7 recorded that a client established a long-lived encapsulated network session. The event references principal-3095e007e6941bdd. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-b80092782ec0 match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Ci audit on FINANCE-ASSET-5cdbdad4be0dcfbd recorded that a build pipeline definition gained a new execution step. The event references principal-248c78edaf5546c1. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Smb audit on PEOPLE-ASSET-d3a371e9da6189cb recorded that a session enumerated a file share and read multiple files. The event references principal-4aae8f7eba9ba686. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Waf logs on FINANCE-ASSET-2688c7caaa5c3540 recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-fa0ae08c81b790e0. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Ci audit on ENGINEERING-ASSET-2c0d231544308107 recorded that a build pipeline definition gained a new execution step. The event references principal-aba5ed9cc375c5ec. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"File audit on PROCUREMENT-ASSET-f66c7d2cd9a00208 recorded that a process compressed files from several directories into an archive. The event references principal-1608ac7a92b15a7f. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-7e87fe2aa5e2 match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Package registry audit on FINANCE-ASSET-39c7276454a893cc recorded that a principal published a new package version. The event references principal-9e718ff7956300e6. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Module audit on RESEARCH-ASSET-49e502fa5df5f407 recorded that a process loaded a library from an application-local directory. The event references principal-52065da876a99294. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Office audit on RESEARCH-ASSET-b8dbacd37bf5b2aa recorded that a document macro launched a child interpreter. The event references principal-fd35021fb1b91014. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Kubernetes audit on FINANCE-ASSET-e06cf007729f9dbe recorded that a workload mounted a directory from its host filesystem. The event references principal-76bf38f3f96381c7. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Identity audit on ENGINEERING-ASSET-f3a5e6ca5f4810c3 recorded that an account registered a new MFA method. The event references principal-a81b0853166bb0e5. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-695a4bab7436 match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Database audit on RESEARCH-ASSET-d8c71a5a44c49e60 recorded that a session changed a database table definition. The event references principal-355812fdc0609439. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Session audit on PROCUREMENT-ASSET-375b33e301ac9b62 recorded that the same session token appeared from different client addresses. The event references principal-c5f1efc48ec3f681. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Mail and proxy logs on COMMUNICATIONS-ASSET-48a9f26bd10054b4 recorded that a user opened a URL delivered in an email message. The event references principal-0e84a6c758769248. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-69a5a2b22fab specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Identity audit on PROCUREMENT-ASSET-3df9ef7ebe927a33 recorded that an account registered a new MFA method. The event references principal-8231b7a1d02ca56c. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Process audit on PROCUREMENT-ASSET-3482b66b87c99633 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-a0877a981b03e4e2. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-67ece2db4354 match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Resolver logs on RESEARCH-ASSET-abc39d656b9d30aa recorded that a client requested many long, high-entropy DNS labels. The event references principal-5aebc86024ffc2a8. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Kerberos audit on OPERATIONS-ASSET-15b32c4f5f91cc11 recorded that an account requested service tickets for multiple services. The event references principal-86eb3dff1abf1690. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Repository audit on LEGAL-ASSET-d4c7f3d667dee146 recorded that a user cloned several source repositories. The event references principal-0ab147f1f9481604. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Identity audit on SUPPORT-ASSET-3fdea2c42e845651 recorded that a service account established an interactive session. The event references principal-6872260152bd6bd7. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Ci audit on OPERATIONS-ASSET-3c47f8e04ce54395 recorded that a build pipeline definition gained a new execution step. The event references principal-4e3a0bcc0149b2b6. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Change CHG-a33374a731f6 lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Systemd audit on PEOPLE-ASSET-e24082f3c52d3f39 recorded that a service unit file was changed and the unit reloaded. The event references principal-b49269ba3a97e459. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Storage access logs on PROCUREMENT-ASSET-8beb52fc6c4219bf recorded that a principal downloaded many objects from a storage bucket. The event references principal-de077f5f8d45beed. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Group audit on SUPPORT-ASSET-32af0f049b4169a7 recorded that an account was added to a privileged local group. The event references principal-b75a2d708106954b. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Process audit on SUPPORT-ASSET-9f8775e0a67ff6e2 recorded that a remote-support application started an interactive session. The event references principal-342d9605d5b86694. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-82f02a56cbad accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Mail and proxy logs on SUPPORT-ASSET-79dbee71e86c40be recorded that a user opened a URL delivered in an email message. The event references principal-1603764c68a231e0. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Cloud identity audit on LEGAL-ASSET-be33ff15ebf5e263 recorded that a principal assumed a role in another account. The event references principal-a89c01a9848a96c2. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Windows logon audit on PROCUREMENT-ASSET-6de9173566128253 recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-1e31ae283e3821b5. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Mail and proxy logs on LEGAL-ASSET-bdb95e0606dac9b6 recorded that a user opened a URL delivered in an email message. The event references principal-5ab74a82bf3ac244. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Macos launch audit on PROCUREMENT-ASSET-cefeabfcdbb75ff5 recorded that a launch agent definition was installed in a user context. The event references principal-61b165b4264637cc. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Assessment SEC-aed54b153bee explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Registry audit on SALES-ASSET-797a3ae487efd18f recorded that a workload pulled a container image from a registry. The event references principal-6df652f7e41389ab. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Task scheduler audit on ENGINEERING-ASSET-03b8a656580bfb25 recorded that a scheduled task was registered to execute a program at logon. The event references principal-2a3a3ccb2ea52460. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Group audit on PROCUREMENT-ASSET-b50d9791f482d6f4 recorded that an account was added to a privileged local group. The event references principal-c07c3b076842f6c0. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Application audit on PEOPLE-ASSET-fcad7cf3be4e4115 recorded that a runtime configuration setting was updated. The event references principal-1c596d52504e0c0f. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Storage access logs on FINANCE-ASSET-c07c58461c3886b7 recorded that a principal downloaded many objects from a storage bucket. The event references principal-636661caf69ea2cc. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Code integrity audit on SUPPORT-ASSET-d243663dca87b63a recorded that an executable without a publisher signature started from a writable directory. The event references principal-ac7fc8d288d921e2. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Certificate audit on PROCUREMENT-ASSET-90178e3809a5e39e recorded that a service certificate was replaced. The event references principal-4bfd3026e3966135. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Database audit on PROCUREMENT-ASSET-e086d2946f81e9d3 recorded that a session read several tables and exported the query result. The event references principal-6283c0702f8c752e. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-1f6dc4343f4f, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Mail audit on SUPPORT-ASSET-d04332aa87461fec recorded that an account received delegated access to a mailbox. The event references principal-4bd49edb0535ebaf. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Code integrity audit on SALES-ASSET-c410ab31c1f04772 recorded that an executable without a publisher signature started from a writable directory. The event references principal-9e4abca76b69be64. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Process audit on ENGINEERING-ASSET-254e39c6de0e65b8 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-b4a1f0cd4cef32ed. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-a98c1c4288f0 explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Ci audit on PEOPLE-ASSET-ea14ad85e984ee1f recorded that a build pipeline definition gained a new execution step. The event references principal-02ee8abd42195e24. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Runtime audit on OPERATIONS-ASSET-b6b114583f048adf recorded that a process connected to the container runtime socket. The event references principal-2a53a47b4b50aacf. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Ssh audit on SUPPORT-ASSET-842f8e08ea10f95b recorded that an SSH session opened and requested elevated command execution. The event references principal-3779cc64299d1a95. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Session audit on PEOPLE-ASSET-2f7cb210c1411ef5 recorded that the same session token appeared from different client addresses. The event references principal-254fb3d8a50b95f2. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-e489c8bec6f5 specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Policy audit on SALES-ASSET-8b2e5805c0958f81 recorded that an audit policy was changed to collect fewer event categories. The event references principal-55b368edee8e470a. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Winrm audit on COMMUNICATIONS-ASSET-2bb6a89a28755b1e recorded that a remote management session invoked a command on a managed host. The event references principal-2ae22aaef9849f17. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-e0d2e81a8544 specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Storage audit on COMMUNICATIONS-ASSET-4c8d4447eef18c17 recorded that an object-storage access policy was broadened. The event references principal-2ee0983ecf5d6d25. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Process audit on OPERATIONS-ASSET-4be1d9f7adca7d10 recorded that a remote-support application started an interactive session. The event references principal-85052a5f25abdf7a. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Process audit on COMMUNICATIONS-ASSET-32e7de18e8d35e66 recorded that a Python interpreter loaded a script and contacted a service. The event references principal-2424b5e4e4370c09. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Dns server audit on PEOPLE-ASSET-9dfdc0288f418b98 recorded that a client requested a DNS zone transfer. The event references principal-fb173264d38aac45. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Oauth audit on PEOPLE-ASSET-f620f4cfac01530c recorded that an application received consent for additional account scopes. The event references principal-0999bb32ee8823f5. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Network control audit on SUPPORT-ASSET-badb98bf2185855c recorded that a cloud security group gained a broad ingress rule. The event references principal-1a508d07acbfb51b. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Database audit on OPERATIONS-ASSET-dec2bfd2d0808b67 recorded that a session changed a database table definition. The event references principal-0583f5a376c3e442. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Firewall audit on RESEARCH-ASSET-0236b24f6c7b0e03 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-582ef1b1560e6fc6. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-0011b4ba16f5 match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Directory audit on SALES-ASSET-59c719c0c63878b3 recorded that a principal requested directory replication data. The event references principal-cb15573feb355e86. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Storage access logs on OPERATIONS-ASSET-4a7bbac68a963680 recorded that a principal downloaded many objects from a storage bucket. The event references principal-9881a91f6d808755. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Policy audit on RESEARCH-ASSET-9236351eaaf332af recorded that an audit policy was changed to collect fewer event categories. The event references principal-9505995ed7eba439. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Device and file audit on SALES-ASSET-3b11bf4bc19f47f9 recorded that files were copied to a removable storage device. The event references principal-342176cf658025b8. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-50caf84a4b1e accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"File audit on SALES-ASSET-8fef53d84dc3e73f recorded that a process deleted many files within a short interval. The event references principal-1dec5bfe36cba361. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-4b9c9c9cf569, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Identity audit on RESEARCH-ASSET-855e969e96eb06ea recorded that an account password was reset through a recovery workflow. The event references principal-811400d02da15e41. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Identity audit on FINANCE-ASSET-5eeb4551c8b1c0e3 recorded that an account registered a new MFA method. The event references principal-0a574aaa6eaa69b8. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Process audit on PROCUREMENT-ASSET-4c9b1e536ca1f43f recorded that a Python interpreter loaded a script and contacted a service. The event references principal-f1d7ec01883c26bc. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-e9f62c742a74 specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Key service audit on RESEARCH-ASSET-fa35f918dce61e29 recorded that a principal issued a burst of key-service decrypt requests. The event references principal-139260250781ca0e. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-c4bb7faa6a50, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Kerberos audit on FINANCE-ASSET-0b0adcb58a633d21 recorded that an account requested service tickets for multiple services. The event references principal-bbbe909c0396acf3. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Security retest SEC-82ac9c31262c covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Kubernetes audit on COMMUNICATIONS-ASSET-a5023ab9f641c1cb recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-8da42e51a76b5b34. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Gateway logs on SALES-ASSET-712c30d2818c912a recorded that a client established a long-lived encapsulated network session. The event references principal-0cbf398f28282f6a. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"File audit on SUPPORT-ASSET-96c72864072032c8 recorded that a process deleted many files within a short interval. The event references principal-7a907f6a20c3a4ff. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Storage audit on LEGAL-ASSET-5cc263cd7974e410 recorded that a session deleted several storage snapshots. The event references principal-548b73b08858de12. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Cloud identity audit on COMMUNICATIONS-ASSET-a2643d4e14311066 recorded that a principal assumed a role in another account. The event references principal-3ce172a931fefefa. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-e5661f32334d specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Code integrity audit on ENGINEERING-ASSET-bc88477a091db102 recorded that an executable without a publisher signature started from a writable directory. The event references principal-26a79bf54e5ed1d5. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Api gateway logs on ENGINEERING-ASSET-51721c37d612a2f5 recorded that a client issued a burst of API requests. The event references principal-b27ef27161423988. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Service audit on COMMUNICATIONS-ASSET-9cb10b4818b88629 recorded that a remote service-control request created and started a temporary service. The event references principal-9f1825f9f69c7e5f. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"File audit on LEGAL-ASSET-b2789a781837a87b recorded that a shell startup profile gained an additional command. The event references principal-d7a3487fce82090e. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Assessment SEC-ca7ee9399ebf explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Process audit on PEOPLE-ASSET-534c3950a47d5a64 recorded that a JavaScript interpreter executed a local script. The event references principal-8170f0f562dc21d2. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Group audit on FINANCE-ASSET-df066dc7583c9589 recorded that an account was added to a privileged local group. The event references principal-91bee423e82eb7d5. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Group audit on FINANCE-ASSET-df066dc7583c9589 recorded that an account was added to a privileged local group. The event references principal-91bee423e82eb7d5. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Winrm audit on SALES-ASSET-53a0ec06a529813d recorded that a remote management session invoked a command on a managed host. The event references principal-d315b25d4a3677cf. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-9835fb0c25d2 match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Windows logon audit on PEOPLE-ASSET-45fa406199d2c14e recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-291516c4491afd57. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-2c2c32878172 match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Process audit on SALES-ASSET-c1342eb6176b4ffa recorded that a Python interpreter loaded a script and contacted a service. The event references principal-e11956d74b8d7b52. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-406221714bb0 before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Cloud control audit on OPERATIONS-ASSET-31b25a4a2bbf0f7e recorded that resources were created in a region with little prior activity. The event references principal-2043ac1bd7256aa6. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Compute audit on SALES-ASSET-4b3abc50600feeb3 recorded that a principal launched multiple compute instances. The event references principal-a87c3d065d8ee0b1. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Share audit on RESEARCH-ASSET-f2c54bce84c236d2 recorded that a new network file share was published. The event references principal-0e202f3a7615eefc. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Application audit on LEGAL-ASSET-235dadbbfdbe7d33 recorded that an application requested repeated screen captures. The event references principal-31391eee810ce402. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Application audit on OPERATIONS-ASSET-cf2679e9708fa36f recorded that a runtime configuration setting was updated. The event references principal-3db05afeebe1db89. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Process audit on SALES-ASSET-96ce257e2204a8a5 recorded that a remote-support application started an interactive session. The event references principal-ae9cce396ea567fe. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Office audit on FINANCE-ASSET-611546d095704224 recorded that a document macro launched a child interpreter. The event references principal-07f2af237b2ad540. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Network control audit on SUPPORT-ASSET-badb98bf2185855c recorded that a cloud security group gained a broad ingress rule. The event references principal-1a508d07acbfb51b. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-26f3682d8277 covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"File audit on SUPPORT-ASSET-a93f88cca8d4a8b9 recorded that a process rewrote multiple files into encrypted containers. The event references principal-ae3578564d0163ba. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-c48cc454f864 before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Dns control audit on SUPPORT-ASSET-daac2768071affbb recorded that an authoritative DNS record was updated. The event references principal-004b930761f504d4. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Driver audit on SUPPORT-ASSET-19c2a39ea2af2cbe recorded that a kernel driver was loaded after a package installation. The event references principal-f5704bc0d4a6300d. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-f38e63c8dd96 match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Resolver logs on OPERATIONS-ASSET-5135623224ddfa0b recorded that a client requested many long, high-entropy DNS labels. The event references principal-4817944b772fb8eb. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Cron audit on RESEARCH-ASSET-25e2f241c7b3849f recorded that a recurring job definition was added to the system schedule. The event references principal-2a055f75f46408a1. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Vpn audit on SALES-ASSET-09dd168451b4fb60 recorded that a remote-access VPN session was established. The event references principal-732980774243feef. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Federation audit on SALES-ASSET-88538f554d17e7e6 recorded that a tenant federation setting was updated. The event references principal-caaf0b98849ffd32. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Application audit on SUPPORT-ASSET-bc02457e5d2c9364 recorded that an application read clipboard contents repeatedly. The event references principal-5b5cc7cba3470ef8. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Waf logs on LEGAL-ASSET-558884e90876ee10 recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-3ea85690224829da. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-202d9da9b815 match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Federation audit on SUPPORT-ASSET-9d7cd1e21b7e712c recorded that a tenant federation setting was updated. The event references principal-1761e65ce57d1289. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-fe762b786166 explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Script audit on OPERATIONS-ASSET-df5c95ab3d436943 recorded that a script interpreter decoded an encoded argument before execution. The event references principal-d244a19c467082bb. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-753940678453 before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Flow logs on OPERATIONS-ASSET-498d986f9a323163 recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-921d661770eeeb14. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Cloud control audit on FINANCE-ASSET-874d671033c104d1 recorded that a cloud logging destination was disabled. The event references principal-b52f94a7d99dc7bf. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Device and file audit on SUPPORT-ASSET-05bbaad00af727ab recorded that files were copied to a removable storage device. The event references principal-dedda897251ae8fc. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Process audit on FINANCE-ASSET-7c0fff41e30d4380 recorded that a JavaScript interpreter executed a local script. The event references principal-5ba5da6cfca5af4e. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Compute audit on RESEARCH-ASSET-d341eca93691633b recorded that a principal launched multiple compute instances. The event references principal-cf04d4cb340e6373. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-e0312841dcdd match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Kubernetes audit on OPERATIONS-ASSET-e9cb557fa33c100a recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-d1c39d3b8db93b55. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-fe4f3d7c33ec match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Repository audit on OPERATIONS-ASSET-2cc6b5c22c3989e5 recorded that a user cloned several source repositories. The event references principal-e45f970cca2e32b9. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Saas audit on OPERATIONS-ASSET-f4bc429edd233279 recorded that a user requested a bulk export from a business application. The event references principal-0d93bc3cb85c4be3. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Session audit on ENGINEERING-ASSET-bc4c94aa37fb4f60 recorded that the same session token appeared from different client addresses. The event references principal-821aec91dc2aa8b4. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-07c90d496034 covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Dns server audit on PROCUREMENT-ASSET-e8eb2bcb15a480a1 recorded that a client requested a DNS zone transfer. The event references principal-937daedbc93fd7dd. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Cloud control audit on ENGINEERING-ASSET-bbf96ebe3618813b recorded that a cloud logging destination was disabled. The event references principal-7942b0cb0edc33ed. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-11504240fcc5 specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Database audit on OPERATIONS-ASSET-302e0f5dfef6781b recorded that a session read several tables and exported the query result. The event references principal-22fca2204489e9a2. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-da610f6a0c49 explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Session audit on LEGAL-ASSET-a93d2c4f4ac53314 recorded that the same session token appeared from different client addresses. The event references principal-4ff9816ed8758404. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Package registry audit on RESEARCH-ASSET-b42ad559dc38cada recorded that a principal published a new package version. The event references principal-ae25582585615c9e. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-31662ff04498 match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Flow logs on OPERATIONS-ASSET-edf434a71b109006 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-16d324cd052a6682. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-bd109364c1f5 accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Kubernetes audit on PEOPLE-ASSET-95c9822ffcf4a444 recorded that a cluster admission policy was changed. The event references principal-e51b094fe6b69872. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-248b8608da22 match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Federation audit on SUPPORT-ASSET-9d7cd1e21b7e712c recorded that a tenant federation setting was updated. The event references principal-1761e65ce57d1289. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Change CHG-fe762b786166 lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Cloud identity audit on SUPPORT-ASSET-7e8f88bce8cfa9fc recorded that a principal received a policy granting additional permissions. The event references principal-02df9042c50f2455. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-3018f02f2280 accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Cloud identity audit on RESEARCH-ASSET-39f1c4acdb98407c recorded that a new programmatic access key was issued to a principal. The event references principal-16f1be9653031bee. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Key service audit on PEOPLE-ASSET-51157cbfcf0e7f8b recorded that a principal issued a burst of key-service decrypt requests. The event references principal-8c512aac8f2c3631. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Application audit on SUPPORT-ASSET-bc02457e5d2c9364 recorded that an application read clipboard contents repeatedly. The event references principal-5b5cc7cba3470ef8. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-759600e2d74a, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Cloud identity audit on COMMUNICATIONS-ASSET-8660c1612914f6bd recorded that a principal received a policy granting additional permissions. The event references principal-796bfc42ecc484c7. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Device and file audit on ENGINEERING-ASSET-c9b77c2a506ace86 recorded that files were copied to a removable storage device. The event references principal-7078af09729168a5. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Cron audit on SALES-ASSET-34715d088f9c8c11 recorded that a recurring job definition was added to the system schedule. The event references principal-69300e7147cdfbd9. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Oauth audit on SUPPORT-ASSET-f8746b96a88e1b30 recorded that an application received consent for additional account scopes. The event references principal-7f165276ca2b480a. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Browser audit on LEGAL-ASSET-df49de2f96b43b40 recorded that a browser extension with page-reading permissions was installed. The event references principal-010a6a482ee1c838. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-35b1871e430b, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Macos launch audit on SUPPORT-ASSET-650496733d825be0 recorded that a launch agent definition was installed in a user context. The event references principal-0735ac9998e5203b. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Kerberos audit on ENGINEERING-ASSET-ca968191bd4b09c5 recorded that an account requested service tickets for multiple services. The event references principal-48c928131e4a9922. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Session audit on PEOPLE-ASSET-2f7cb210c1411ef5 recorded that the same session token appeared from different client addresses. The event references principal-254fb3d8a50b95f2. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Change CHG-e489c8bec6f5 lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Mail flow logs on SUPPORT-ASSET-4fe85cf52fa083ac recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-b1c48571a99cb1b2. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Compute audit on LEGAL-ASSET-4cc59a71aa46b3a9 recorded that a principal launched multiple compute instances. The event references principal-662e807a43fa7c2b. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Agent audit on FINANCE-ASSET-9e83a9427493fb22 recorded that a privileged session changed endpoint monitoring settings. The event references principal-456dd0970fc81a4c. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Firewall audit on SUPPORT-ASSET-e85c56705ce7aa30 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-9b678cb3b90b393c. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Repository audit on FINANCE-ASSET-107bba51318f26e9 recorded that a user cloned several source repositories. The event references principal-f147d2a9dbf7d7a7. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Kubernetes audit on COMMUNICATIONS-ASSET-f76c1c782f04bc0e recorded that a workload mounted a directory from its host filesystem. The event references principal-ea22af4c35053180. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-12e23152a940, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"File audit on SUPPORT-ASSET-a93f88cca8d4a8b9 recorded that a process rewrote multiple files into encrypted containers. The event references principal-ae3578564d0163ba. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Kubernetes audit on PROCUREMENT-ASSET-2f62998057d28724 recorded that a role binding granted a principal additional cluster permissions. The event references principal-4457a8d289298830. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Package registry audit on OPERATIONS-ASSET-b20136404dfc240b recorded that a principal published a new package version. The event references principal-97ed055b6e1a57e6. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Database audit on RESEARCH-ASSET-d8c71a5a44c49e60 recorded that a session changed a database table definition. The event references principal-355812fdc0609439. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-290478f04a76 accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Process audit on RESEARCH-ASSET-ff9cda8159f26be2 recorded that a remote-support application started an interactive session. The event references principal-c2840b0826e54ab4. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Process audit on PEOPLE-ASSET-534c3950a47d5a64 recorded that a JavaScript interpreter executed a local script. The event references principal-8170f0f562dc21d2. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Identity audit on RESEARCH-ASSET-855e969e96eb06ea recorded that an account password was reset through a recovery workflow. The event references principal-811400d02da15e41. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Cloud control audit on PEOPLE-ASSET-a565fc161c06dbdd recorded that a cloud logging destination was disabled. The event references principal-b1342e9d7cf466d7. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-2bb8392ca81d explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Repository audit on PROCUREMENT-ASSET-032fc4cf1761029e recorded that a repository collaborator received elevated permissions. The event references principal-c9c8d15f73a824e8. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Resolver logs on PROCUREMENT-ASSET-217f3e17146574de recorded that a client requested many long, high-entropy DNS labels. The event references principal-c25feb34aea9c3bd. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Cloud identity audit on LEGAL-ASSET-7e0cfa13cd7f5efc recorded that a new programmatic access key was issued to a principal. The event references principal-578071150bb49966. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Kerberos audit on LEGAL-ASSET-6ee4a0334d8b0730 recorded that an account requested service tickets for multiple services. The event references principal-2772005981d83d01. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Dhcp telemetry on LEGAL-ASSET-5112544cfce28921 recorded that a server issued DHCP offers on a monitored segment. The event references principal-176187e9b5662d2e. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-88bb7a6fa7e3 accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Agent audit on SUPPORT-ASSET-9325bde68edaa545 recorded that a privileged session changed endpoint monitoring settings. The event references principal-1641f4bad60d9f93. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Mail and proxy logs on PEOPLE-ASSET-73f46f787c3750bc recorded that a user opened a URL delivered in an email message. The event references principal-ae3654afd7401601. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Application audit on FINANCE-ASSET-be2eeaec3ad85eb4 recorded that a runtime configuration setting was updated. The event references principal-1d937b1c297b00f3. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Flow logs on COMMUNICATIONS-ASSET-d5fd0288e752f79f recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-fd4faa7e0445166d. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Configuration audit on ENGINEERING-ASSET-05746d5c7e76781e recorded that a client proxy setting was changed. The event references principal-f4f857793a1cd276. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Mail audit on PEOPLE-ASSET-0dab505ef5721fa1 recorded that an account received delegated access to a mailbox. The event references principal-867e051f8d4b0f18. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Mail and proxy logs on ENGINEERING-ASSET-d6ab66ae0acf6c7d recorded that a user opened a URL delivered in an email message. The event references principal-0a6867792e03bc3b. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-349b494b1581 accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Kubernetes audit on PEOPLE-ASSET-fb423ebd814658c2 recorded that a role binding granted a principal additional cluster permissions. The event references principal-1e6683e3ee80066c. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Registry audit on PROCUREMENT-ASSET-623aa42bae025131 recorded that a registry logon-start entry was created. The event references principal-9f2c57eab5b3cfda. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-e26a9b3192d3, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Storage access logs on COMMUNICATIONS-ASSET-560f077b5b32381f recorded that a principal downloaded many objects from a storage bucket. The event references principal-2c20310dc28bca65. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Certificate audit on SUPPORT-ASSET-bf2e59d8cf05d409 recorded that a service certificate was replaced. The event references principal-3f10d0f128334232. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Process access audit on PROCUREMENT-ASSET-a371e419fb9da077 recorded that a process requested read access to another process memory space. The event references principal-47b9eca6b126bee7. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Security retest SEC-411a11d421e2 covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Process audit on PROCUREMENT-ASSET-e094a3806b86f26f recorded that a remote-support application started an interactive session. The event references principal-0e21b55912ebea78. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-c24f1a08e5ff match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Api gateway logs on COMMUNICATIONS-ASSET-25487240e8c2e247 recorded that a client issued a burst of API requests. The event references principal-23ca7dbb4aa37ade. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Compute audit on LEGAL-ASSET-4cc59a71aa46b3a9 recorded that a principal launched multiple compute instances. The event references principal-662e807a43fa7c2b. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Cloud identity audit on FINANCE-ASSET-e7ffd7ca6e67a506 recorded that a principal assumed a role in another account. The event references principal-9b4f65d2a19e9629. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Identity audit on ENGINEERING-ASSET-7b28b0fa9a166d69 recorded that repeated failed sign-ins were recorded for an account. The event references principal-1962d3f4c712b2c7. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Storage audit on FINANCE-ASSET-47f72b6b10bf47c7 recorded that a session deleted several storage snapshots. The event references principal-6ce8e4c42cc80c2d. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Kubernetes audit on COMMUNICATIONS-ASSET-396281c213cbfe7d recorded that a role binding granted a principal additional cluster permissions. The event references principal-490795a3fa64d894. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Dns control audit on OPERATIONS-ASSET-d3932800e26302a2 recorded that an authoritative DNS record was updated. The event references principal-acc181df5bf7ded9. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-151c76255ba5, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Service audit on PROCUREMENT-ASSET-7131a22a8a5e3488 recorded that a new automatically started service was registered. The event references principal-7eed072979ca83fe. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"File audit on COMMUNICATIONS-ASSET-20dd539a3853169a recorded that a shell startup profile gained an additional command. The event references principal-c281969fbd0779dd. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Mail audit on FINANCE-ASSET-ea1b6c24422b456d recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-44026a910bd0b4c9. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Ssh audit on RESEARCH-ASSET-a4cfbeae0c987bb8 recorded that an SSH session opened and requested elevated command execution. The event references principal-f224386eb3a1c8ae. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Cloud identity audit on LEGAL-ASSET-7e0cfa13cd7f5efc recorded that a new programmatic access key was issued to a principal. The event references principal-578071150bb49966. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Database audit on FINANCE-ASSET-f03ba1a6a369cf03 recorded that a session read several tables and exported the query result. The event references principal-f892103a2793bbab. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-8a9f9fb5c9bc before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Mail audit on COMMUNICATIONS-ASSET-dece9873e2e03f6f recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-3d08b8fe271ddda1. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Directory audit on PROCUREMENT-ASSET-7b387a0e6a39eb7a recorded that a principal requested directory replication data. The event references principal-0b3c6bcdb6ea6190. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Script audit on PEOPLE-ASSET-7674cfc3c8c8d12a recorded that a script interpreter decoded an encoded argument before execution. The event references principal-15233cc20a5664b0. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-f814a8150d9c before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Account audit on COMMUNICATIONS-ASSET-9a834b6edbe1b57f recorded that a local user account was created on a managed system. The event references principal-57644d2a7475e5ae. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-faa95bc1daf3 specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Event service audit on SUPPORT-ASSET-2b5c6ab4e8f6f174 recorded that an event log was cleared by a privileged request. The event references principal-2294144a09bcf573. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Cloud identity audit on LEGAL-ASSET-a018d5a0c035a322 recorded that a principal received a policy granting additional permissions. The event references principal-e37ce5811af67681. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Egress flow logs on ENGINEERING-ASSET-244beee7b921f878 recorded that a workload opened an encrypted connection to an external service. The event references principal-0a5b130156e24d17. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Winrm audit on RESEARCH-ASSET-35584f0a53bc209b recorded that a remote management session invoked a command on a managed host. The event references principal-7b703d1f8c94aba9. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Smb audit on PROCUREMENT-ASSET-663a220061cd4095 recorded that a session enumerated a file share and read multiple files. The event references principal-ae5de00ea82776e7. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Winrm audit on PROCUREMENT-ASSET-98512f6cba9a2651 recorded that a remote management session invoked a command on a managed host. The event references principal-e3d261d10a11f3f9. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Backup audit on RESEARCH-ASSET-d7ec84ee273e258c recorded that a backup retention policy was shortened. The event references principal-46e3d9bc6deb6418. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-34994969d29e accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Certificate audit on PROCUREMENT-ASSET-90178e3809a5e39e recorded that a service certificate was replaced. The event references principal-4bfd3026e3966135. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Security retest SEC-392cc2b82945 covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Macos launch audit on SALES-ASSET-9700c4adcf12629e recorded that a launch agent definition was installed in a user context. The event references principal-fd31ea054fd63d39. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Kubernetes audit on LEGAL-ASSET-a4bb453a13c05590 recorded that a role binding granted a principal additional cluster permissions. The event references principal-f6d0dcce5ee82a68. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Firewall audit on PEOPLE-ASSET-957a449c8e927512 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-3d550d011d922017. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Firewall audit on ENGINEERING-ASSET-4346eb459a11971a recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-62f6e1ae625e9e27. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Vpn audit on SUPPORT-ASSET-e419f3a293f3417a recorded that a remote-access VPN session was established. The event references principal-09df6291fa9e8663. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Storage access logs on SUPPORT-ASSET-467cdf660d5e57c4 recorded that a principal downloaded many objects from a storage bucket. The event references principal-83eeaee20b7f40f8. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Device and file audit on SUPPORT-ASSET-05bbaad00af727ab recorded that files were copied to a removable storage device. The event references principal-dedda897251ae8fc. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Dhcp telemetry on OPERATIONS-ASSET-495d89e0df4422f6 recorded that a server issued DHCP offers on a monitored segment. The event references principal-ad2763e8b3d1fe71. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Storage audit on ENGINEERING-ASSET-b38bdd9cc61bbac2 recorded that an object-storage access policy was broadened. The event references principal-8585f4d7b4e61651. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Saas audit on PROCUREMENT-ASSET-94508e8090c4e3fa recorded that a user requested a bulk export from a business application. The event references principal-d0cfd5ec7d96061d. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Mail audit on OPERATIONS-ASSET-3a9ba1a13acae41d recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-458bdf5d7e7a4b20. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Cloud control audit on LEGAL-ASSET-152843552545f6c2 recorded that a session deleted a group of cloud resources. The event references principal-441348e944e96c5c. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-30e36caa1c81 before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Switch telemetry on SALES-ASSET-67150f5bd544c87a recorded that an address mapping changed repeatedly on a local segment. The event references principal-f4e3b1c2069d2a7e. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Code integrity audit on ENGINEERING-ASSET-bc88477a091db102 recorded that an executable without a publisher signature started from a writable directory. The event references principal-26a79bf54e5ed1d5. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Smb audit on FINANCE-ASSET-c99a2728b7b98f2b recorded that a session enumerated a file share and read multiple files. The event references principal-40d6614472abce2d. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-76653a681f72 match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Cloud control audit on ENGINEERING-ASSET-1c2668b46715bf02 recorded that resources were created in a region with little prior activity. The event references principal-974cef6dad8360ab. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Vpn audit on SUPPORT-ASSET-e419f3a293f3417a recorded that a remote-access VPN session was established. The event references principal-09df6291fa9e8663. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Process audit on SALES-ASSET-c1342eb6176b4ffa recorded that a Python interpreter loaded a script and contacted a service. The event references principal-e11956d74b8d7b52. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"File audit on ENGINEERING-ASSET-e53845b276f34712 recorded that a process rewrote multiple files into encrypted containers. The event references principal-f651e132a9d111e2. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Proxy logs on ENGINEERING-ASSET-55fbfe9ce1b9adb6 recorded that a client transferred a large payload to an external storage endpoint. The event references principal-9db93a1b04a04fcd. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-5a18336b0f80 specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Registry audit on SALES-ASSET-797a3ae487efd18f recorded that a workload pulled a container image from a registry. The event references principal-6df652f7e41389ab. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Storage audit on RESEARCH-ASSET-6e2b243ec7d7a919 recorded that an object-storage access policy was broadened. The event references principal-262db57bffaea9f7. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Ci secret audit on RESEARCH-ASSET-d46af760b3fcf2d7 recorded that a build job requested a protected pipeline secret. The event references principal-60fe7cbc94a757b5. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-8df5b8ef971a explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Group audit on ENGINEERING-ASSET-d30b74960b951b72 recorded that an account was added to a privileged local group. The event references principal-81526d7aed4e1797. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Ci audit on LEGAL-ASSET-307a1ab2be77fe5f recorded that a build pipeline definition gained a new execution step. The event references principal-362aa0b8c3b22688. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-d39ecfcfcf4d, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Waf logs on SUPPORT-ASSET-e0ebcdef3dfa8416 recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-3a687906c9bbefbc. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Share audit on COMMUNICATIONS-ASSET-155e7e0f58a0bc23 recorded that a new network file share was published. The event references principal-91339ef7c416f6ed. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-6e2f071b38a7 accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"File audit on PEOPLE-ASSET-572ab49b4fda25fd recorded that access permissions were broadened on a directory tree. The event references principal-892e9ce9179f90fe. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Smb audit on ENGINEERING-ASSET-167b039744d858de recorded that a session enumerated a file share and read multiple files. The event references principal-dae2d90d16568727. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Systemd audit on RESEARCH-ASSET-eeb116f31cbce82f recorded that a service unit file was changed and the unit reloaded. The event references principal-f39102d395b571c9. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Process audit on ENGINEERING-ASSET-254e39c6de0e65b8 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-b4a1f0cd4cef32ed. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Function audit on OPERATIONS-ASSET-7bf3d2cc7f955758 recorded that a serverless function package and execution settings were updated. The event references principal-2b7da48bc74786c4. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Key service audit on LEGAL-ASSET-c93c39a0bf6d5d2d recorded that a principal issued a burst of key-service decrypt requests. The event references principal-a9f8c5175e6aa291. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"File audit on COMMUNICATIONS-ASSET-23cdf3c51f4342c4 recorded that access permissions were broadened on a directory tree. The event references principal-fb51510da2f10fbb. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-177563af3c0f explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Registry audit on LEGAL-ASSET-d0480e188fd31f60 recorded that a workload pulled a container image from a registry. The event references principal-160b2d0cefee47e2. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Flow logs on LEGAL-ASSET-fa7ff1fc0a223203 recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-1ef2548f2594a804. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Process audit on FINANCE-ASSET-565f2ed301684671 recorded that a remote-support application started an interactive session. The event references principal-a4a07392170d1084. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Change CHG-c7ce772c93d9 lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Ci secret audit on ENGINEERING-ASSET-2fc72026491758e8 recorded that a build job requested a protected pipeline secret. The event references principal-ef329c66a1330a2f. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-2760c17646f8 before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Storage audit on ENGINEERING-ASSET-b38bdd9cc61bbac2 recorded that an object-storage access policy was broadened. The event references principal-8585f4d7b4e61651. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"File access audit on FINANCE-ASSET-334508df57fe9f23 recorded that a process opened a local credential-store file. The event references principal-0966351ff7c24bff. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Function audit on SALES-ASSET-461c1fc508bcc3ad recorded that a serverless function package and execution settings were updated. The event references principal-f88b3cc6828a81db. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Security retest SEC-58c8c86bddba covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Account audit on PEOPLE-ASSET-aaae6542cf112eee recorded that a local user account was created on a managed system. The event references principal-0953004be50ca69d. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Task scheduler audit on SALES-ASSET-14a4b633fa3add9a recorded that a scheduled task was registered to execute a program at logon. The event references principal-bc7f1b7e6f9cd150. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-6fd3c4345233 match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"File audit on OPERATIONS-ASSET-aa398735111975aa recorded that a process deleted many files within a short interval. The event references principal-ff0116df6d90824b. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Device and file audit on COMMUNICATIONS-ASSET-f491a02c80ff7ee4 recorded that files were copied to a removable storage device. The event references principal-b586401867cc7a49. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Pki audit on COMMUNICATIONS-ASSET-a88e156f33159899 recorded that a principal requested a certificate using an authentication template. The event references principal-0a19afbf9253f4fc. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Federation audit on RESEARCH-ASSET-85e9941ba25e96bb recorded that a tenant federation setting was updated. The event references principal-863b72c786eda302. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Dhcp telemetry on FINANCE-ASSET-99d84bf5e5de071b recorded that a server issued DHCP offers on a monitored segment. The event references principal-e238480421ab2c07. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Egress flow logs on OPERATIONS-ASSET-2513c8d77423854c recorded that a workload opened an encrypted connection to an external service. The event references principal-ec2152640ea901f5. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-7b05bf9df85f match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"File audit on FINANCE-ASSET-2004b1d4a03fd309 recorded that a process rewrote multiple files into encrypted containers. The event references principal-9560a602e126689a. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-4c175dda522b match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Vpn audit on RESEARCH-ASSET-f104c6cff8b4f120 recorded that a remote-access VPN session was established. The event references principal-18bc30314e242812. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Cloud identity audit on OPERATIONS-ASSET-e9ea023dcfe573c8 recorded that a principal assumed a role in another account. The event references principal-33e2cf770673f137. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"File access audit on LEGAL-ASSET-c0436d9a797b6aac recorded that a process opened a local credential-store file. The event references principal-8f957f68f520d591. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Package registry audit on SUPPORT-ASSET-ad8575a16b60726c recorded that a principal published a new package version. The event references principal-b9b60013a399b75b. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Database audit on LEGAL-ASSET-1c120ddc82665e7a recorded that a session read several tables and exported the query result. The event references principal-4636f85408e4dae9. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Api gateway logs on PROCUREMENT-ASSET-1c1b6a1c5f9b9bd8 recorded that a client issued a burst of API requests. The event references principal-257e72e6a629f939. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Identity audit on LEGAL-ASSET-10052cae7e6f5c6e recorded that an account password was reset through a recovery workflow. The event references principal-69df9c6ec5ef584b. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Kubernetes audit on PEOPLE-ASSET-36a1a728506cc2a7 recorded that a workload mounted a directory from its host filesystem. The event references principal-b1c8c5f8e9de87c2. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Share audit on OPERATIONS-ASSET-a9f5766b40361ce4 recorded that a new network file share was published. The event references principal-e591af365aeb634a. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Storage access logs on SUPPORT-ASSET-467cdf660d5e57c4 recorded that a principal downloaded many objects from a storage bucket. The event references principal-83eeaee20b7f40f8. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-0269a1028b3e match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Task scheduler audit on FINANCE-ASSET-ee3bbbf183a6aaf2 recorded that a scheduled task was registered to execute a program at logon. The event references principal-6b358d24fc67440c. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Office audit on COMMUNICATIONS-ASSET-9792dd26544328c7 recorded that a document macro launched a child interpreter. The event references principal-794c3f6a93ed6b1f. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Process audit on LEGAL-ASSET-523d2840aded9f3a recorded that a remote-support application started an interactive session. The event references principal-d733a0ecd691110d. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-cdbf29e6de41 match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Ssh audit on COMMUNICATIONS-ASSET-c7c949ba2f23f6e5 recorded that an SSH session opened and requested elevated command execution. The event references principal-3a7b389506fbf3c1. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Mail audit on LEGAL-ASSET-131d8c518786695c recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-3bea6da72e330e1b. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Change CHG-d902b810ce66 lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Compute audit on SUPPORT-ASSET-723f94949265b3d7 recorded that a principal launched multiple compute instances. The event references principal-1d5de0b683f369a9. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Cloud control audit on ENGINEERING-ASSET-1c2668b46715bf02 recorded that resources were created in a region with little prior activity. The event references principal-974cef6dad8360ab. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Process audit on RESEARCH-ASSET-ff9cda8159f26be2 recorded that a remote-support application started an interactive session. The event references principal-c2840b0826e54ab4. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Ci audit on SALES-ASSET-58f9b0d2c10b53d7 recorded that a build pipeline definition gained a new execution step. The event references principal-db424878959459e6. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Key service audit on OPERATIONS-ASSET-a2b77b051a5e88ca recorded that a principal issued a burst of key-service decrypt requests. The event references principal-2d26323a698b32c1. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Kubernetes audit on SUPPORT-ASSET-70672b7c7f3d80de recorded that a workload mounted a directory from its host filesystem. The event references principal-bb9a9a5a1ac32931. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Cloud control audit on COMMUNICATIONS-ASSET-6f90d32e2d49796b recorded that resources were created in a region with little prior activity. The event references principal-f5034ed11bd41e3e. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-0febd6f3bccc before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Identity audit on SALES-ASSET-08c0f29601b74bfa recorded that an account registered a new MFA method. The event references principal-4c8bc42872a0ca65. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-5d3b41f11c2a match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Service audit on ENGINEERING-ASSET-5be63ef6d4ef079d recorded that a remote service-control request created and started a temporary service. The event references principal-bd2813d9252e7fbb. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Flow logs on ENGINEERING-ASSET-eb2e69d274ba28c2 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-95a534f7e0b0cad5. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Database audit on SUPPORT-ASSET-a2d3ef51f6508fc5 recorded that a session read several tables and exported the query result. The event references principal-fc443d6fe94147f2. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Database audit on OPERATIONS-ASSET-dec2bfd2d0808b67 recorded that a session changed a database table definition. The event references principal-0583f5a376c3e442. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Smb audit on OPERATIONS-ASSET-903799bcbb7f90a6 recorded that a session enumerated a file share and read multiple files. The event references principal-b3bfcfbe522db4bd. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Gateway logs on SUPPORT-ASSET-bfcdc7fd12a63ce3 recorded that a client established a long-lived encapsulated network session. The event references principal-076e693836d2e9e9. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Storage audit on OPERATIONS-ASSET-07e77010a446667b recorded that a session deleted several storage snapshots. The event references principal-fc81340c87f20845. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Smb audit on SUPPORT-ASSET-e1998cccd3abd998 recorded that a session enumerated a file share and read multiple files. The event references principal-3be2aaf5e58c794d. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Systemd audit on OPERATIONS-ASSET-42dd1f251b2cefd5 recorded that a service unit file was changed and the unit reloaded. The event references principal-27edc61f63f1f31a. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Directory audit on PROCUREMENT-ASSET-7b387a0e6a39eb7a recorded that a principal requested directory replication data. The event references principal-0b3c6bcdb6ea6190. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Application audit on SALES-ASSET-9a8acf9f0cbf6165 recorded that an application read clipboard contents repeatedly. The event references principal-114c22ed14b6a3d7. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Policy audit on COMMUNICATIONS-ASSET-6bd03c52fee36269 recorded that an audit policy was changed to collect fewer event categories. The event references principal-89ce4ef5b0451d62. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-6393f49b2b84 explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Kubernetes audit on ENGINEERING-ASSET-af728a774d91dcb8 recorded that a workload mounted a directory from its host filesystem. The event references principal-6a5b731d9f44ffa6. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Database audit on ENGINEERING-ASSET-5b5cb77077baa64c recorded that a session changed a database table definition. The event references principal-6bfe365bf3961695. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-b0767feee0f0 explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Function audit on SALES-ASSET-461c1fc508bcc3ad recorded that a serverless function package and execution settings were updated. The event references principal-f88b3cc6828a81db. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Egress flow logs on COMMUNICATIONS-ASSET-1fa62ed57f8d2679 recorded that a workload opened an encrypted connection to an external service. The event references principal-297491ec275675d7. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Application audit on OPERATIONS-ASSET-09e59732382536e3 recorded that an application requested repeated screen captures. The event references principal-a45fb9f4a0a7c7be. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-b9a719c3d578 match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Application audit on FINANCE-ASSET-92ef4a42892b1789 recorded that an application read clipboard contents repeatedly. The event references principal-13f5550b59519bb2. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Storage access logs on OPERATIONS-ASSET-4a7bbac68a963680 recorded that a principal downloaded many objects from a storage bucket. The event references principal-9881a91f6d808755. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Kubernetes audit on PEOPLE-ASSET-3e58a2eca5c63a44 recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-8f985c1a713a28f2. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"File audit on PROCUREMENT-ASSET-4eb226a25712a501 recorded that a process rewrote multiple files into encrypted containers. The event references principal-6dcdfe5a31b0546b. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"File access audit on PROCUREMENT-ASSET-0b755d0602adf157 recorded that a process opened a local credential-store file. The event references principal-7e6f29a9069cca6a. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Identity audit on COMMUNICATIONS-ASSET-cdebef5d9dc25fc4 recorded that a service account established an interactive session. The event references principal-ecbde67b88dd7d93. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Secret manager audit on PROCUREMENT-ASSET-b6e8aa184c246f29 recorded that a workload read several secret versions. The event references principal-3c8c2cffa7cd4de8. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-31852c6dbce5 before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Cron audit on FINANCE-ASSET-3836d6a68d057960 recorded that a recurring job definition was added to the system schedule. The event references principal-c8b819a1d7d4650c. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-9eb2f25c5e6c match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Identity audit on FINANCE-ASSET-a32c9481137674af recorded that an account password was reset through a recovery workflow. The event references principal-b0dec7cad50c7fe1. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Security retest SEC-54982c6df719 covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Application audit on RESEARCH-ASSET-21c212dc3255aa17 recorded that an application read clipboard contents repeatedly. The event references principal-8f2a965b2d84c102. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Agent audit on COMMUNICATIONS-ASSET-7f32c685e6e40f0f recorded that a privileged session changed endpoint monitoring settings. The event references principal-ce4504f33247e9eb. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"File audit on OPERATIONS-ASSET-f5bfac37e0e6e52e recorded that access permissions were broadened on a directory tree. The event references principal-c5603af4c6f0f506. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-7bb2afdb4fe1 match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Session audit on FINANCE-ASSET-15bdb8a9163b0abc recorded that the same session token appeared from different client addresses. The event references principal-ce316de1911fbf84. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Application audit on ENGINEERING-ASSET-0a500e9acaab2792 recorded that an application requested repeated screen captures. The event references principal-f9139e2001fef8f3. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Systemd audit on SUPPORT-ASSET-38d3359b892c66ba recorded that a service unit file was changed and the unit reloaded. The event references principal-fbace7ec59135a92. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Flow logs on FINANCE-ASSET-a52520aa18fc5145 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-d9480c5f3eeb0f53. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Kubernetes audit on ENGINEERING-ASSET-af728a774d91dcb8 recorded that a workload mounted a directory from its host filesystem. The event references principal-6a5b731d9f44ffa6. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Change CHG-a53e117836c2 lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Agent audit on COMMUNICATIONS-ASSET-7f32c685e6e40f0f recorded that a privileged session changed endpoint monitoring settings. The event references principal-ce4504f33247e9eb. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Office audit on PROCUREMENT-ASSET-9c9a63eb958fdaa6 recorded that a document macro launched a child interpreter. The event references principal-40d050ba88a97331. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Ci secret audit on PEOPLE-ASSET-50143023c0d694b1 recorded that a build job requested a protected pipeline secret. The event references principal-236f39206994ec5b. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Service audit on RESEARCH-ASSET-83637b2bf6e44350 recorded that a new automatically started service was registered. The event references principal-9f4043a1a42fcc90. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Function audit on LEGAL-ASSET-a808b2dbcafaf1de recorded that a serverless function package and execution settings were updated. The event references principal-d18e2930c59bbade. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Cloud control audit on PEOPLE-ASSET-357f734fad0406df recorded that a session deleted a group of cloud resources. The event references principal-50a694af17f32a70. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-bc4a1bf9be57 match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Cloud identity audit on PROCUREMENT-ASSET-e334c75ea7c7bbae recorded that a new programmatic access key was issued to a principal. The event references principal-754b76246081ca60. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Application audit on ENGINEERING-ASSET-c6a3af2b55d88d84 recorded that a runtime configuration setting was updated. The event references principal-67b63805e0368323. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Cloud control audit on PEOPLE-ASSET-12878cc06ce2eeff recorded that resources were created in a region with little prior activity. The event references principal-504d0a8a24feb6ee. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Egress flow logs on ENGINEERING-ASSET-244beee7b921f878 recorded that a workload opened an encrypted connection to an external service. The event references principal-0a5b130156e24d17. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Process access audit on SALES-ASSET-0e0ff0d46dd9bdcc recorded that a process requested read access to another process memory space. The event references principal-a29d7cafdbef1526. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-9ba321c8e338 before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"File audit on PROCUREMENT-ASSET-de47614145685908 recorded that a shell startup profile gained an additional command. The event references principal-602bb5bc7aad1155. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-f26448347623 accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Repository audit on SALES-ASSET-b9ab0defeef57d69 recorded that a user cloned several source repositories. The event references principal-0da3c44a52b416ce. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Storage audit on PROCUREMENT-ASSET-f524c33b819a1663 recorded that an object-storage access policy was broadened. The event references principal-daeee49ee65928ba. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Firewall audit on RESEARCH-ASSET-0236b24f6c7b0e03 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-582ef1b1560e6fc6. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Waf logs on PEOPLE-ASSET-b68587853256629c recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-a0a816963fae146a. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-bdeb019a371d accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Winrm audit on COMMUNICATIONS-ASSET-2bb6a89a28755b1e recorded that a remote management session invoked a command on a managed host. The event references principal-2ae22aaef9849f17. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Federation audit on LEGAL-ASSET-81a8982089dddbeb recorded that a tenant federation setting was updated. The event references principal-c29fe59344f3b4d5. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Runtime audit on ENGINEERING-ASSET-275c1751b3b56ff6 recorded that a process connected to the container runtime socket. The event references principal-560134bf0a39e092. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-4a568df92172 match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Task scheduler audit on PROCUREMENT-ASSET-bd3697f2e2b8950e recorded that a scheduled task was registered to execute a program at logon. The event references principal-1483881099fae9be. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Pki audit on SALES-ASSET-34ed542c065cfc50 recorded that a principal requested a certificate using an authentication template. The event references principal-bd8f51ad03539dfb. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"File audit on SUPPORT-ASSET-5e6185480b7124c6 recorded that a shell startup profile gained an additional command. The event references principal-51f94e540bbb4321. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Change CHG-911a704b6979 lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Secret manager audit on PROCUREMENT-ASSET-b6e8aa184c246f29 recorded that a workload read several secret versions. The event references principal-3c8c2cffa7cd4de8. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Firewall audit on COMMUNICATIONS-ASSET-4f1cc73dbbdce003 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-3c942f0a8856cd1e. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-ae2eb5fa3a35 match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Mail flow logs on LEGAL-ASSET-692e1a748d08a501 recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-527175c687849d2d. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Wmi audit on ENGINEERING-ASSET-9642a3ef1a26edcb recorded that a management request started a process through WMI. The event references principal-4a2b4bdee8c5d199. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Ssh audit on PEOPLE-ASSET-97ff8f8fa97fd164 recorded that an SSH session opened and requested elevated command execution. The event references principal-60b1e96c2c9d3478. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Wmi audit on LEGAL-ASSET-a70f3384c72ee597 recorded that a management request started a process through WMI. The event references principal-d9be46a6c47bd578. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Flow logs on RESEARCH-ASSET-36f3e51101dc72ca recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-4148cfbbdb30636d. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Kubernetes audit on SALES-ASSET-ffd4e9bc10275050 recorded that a pod was created with privileged execution enabled. The event references principal-02bcfaa51dffcded. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"File access audit on PEOPLE-ASSET-4246817b50ce1d24 recorded that a process opened a local credential-store file. The event references principal-69567a3aa8e45657. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Process audit on SUPPORT-ASSET-9f8775e0a67ff6e2 recorded that a remote-support application started an interactive session. The event references principal-342d9605d5b86694. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Browser audit on PROCUREMENT-ASSET-50d8010904173019 recorded that a browser extension with page-reading permissions was installed. The event references principal-8e2e0553f52a5216. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Secret manager audit on PROCUREMENT-ASSET-b6e8aa184c246f29 recorded that a workload read several secret versions. The event references principal-3c8c2cffa7cd4de8. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-31852c6dbce5 specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"File audit on PROCUREMENT-ASSET-5c83620233b8b110 recorded that a process deleted many files within a short interval. The event references principal-eb86b20544a85de9. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Waf logs on RESEARCH-ASSET-f279330020f0e645 recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-a38184b376034ec2. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-bee285300fd3 match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Switch telemetry on PROCUREMENT-ASSET-c13f623edc6be72c recorded that an address mapping changed repeatedly on a local segment. The event references principal-464589d30bf27aee. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Kubernetes audit on ENGINEERING-ASSET-03ff797dc0608058 recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-84d60009e20971fc. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Identity audit on PROCUREMENT-ASSET-847c16861843d993 recorded that repeated failed sign-ins were recorded for an account. The event references principal-177e5d83a23e0f5b. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-c8c98151ab84 match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Ci audit on PROCUREMENT-ASSET-51d14292a906982f recorded that a build pipeline definition gained a new execution step. The event references principal-776e5e2e9ad695a2. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Secret manager audit on SUPPORT-ASSET-c293b34ccf018f66 recorded that a workload read several secret versions. The event references principal-e464eb0ee46edc73. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-3bfb39551997 match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Waf logs on SUPPORT-ASSET-e0ebcdef3dfa8416 recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-3a687906c9bbefbc. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Process audit on RESEARCH-ASSET-701eef6083bb4949 recorded that a Python interpreter loaded a script and contacted a service. The event references principal-9ed7f8cc72bbc316. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Process audit on LEGAL-ASSET-8a212c2ca8ae49ba recorded that a Python interpreter loaded a script and contacted a service. The event references principal-a6319754fd6d1b91. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Cloud identity audit on COMMUNICATIONS-ASSET-8660c1612914f6bd recorded that a principal received a policy granting additional permissions. The event references principal-796bfc42ecc484c7. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Application audit on PEOPLE-ASSET-b6c838eeab685d8f recorded that an application requested repeated screen captures. The event references principal-22d369aeea462cc7. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-3f3f917b83ae match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Kubernetes audit on LEGAL-ASSET-360df78a99aa884c recorded that a cluster admission policy was changed. The event references principal-fdbbb745932ee2f1. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Browser audit on OPERATIONS-ASSET-1696f264e915fdf5 recorded that a browser extension with page-reading permissions was installed. The event references principal-f101b193c2f738a3. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Change CHG-51606e334fc1 lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Cloud control audit on COMMUNICATIONS-ASSET-53a6ecae622bccee recorded that a cloud logging destination was disabled. The event references principal-cf25374694280e00. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-b83adf576de2 explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Cloud control audit on PEOPLE-ASSET-12878cc06ce2eeff recorded that resources were created in a region with little prior activity. The event references principal-504d0a8a24feb6ee. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Assessment SEC-d9f6f475ea91 explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Package registry audit on SUPPORT-ASSET-ad8575a16b60726c recorded that a principal published a new package version. The event references principal-b9b60013a399b75b. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Cron audit on ENGINEERING-ASSET-0d57cc07ded38310 recorded that a recurring job definition was added to the system schedule. The event references principal-db05c7bee0f112c7. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Vpn audit on FINANCE-ASSET-5b805daa08de83aa recorded that a remote-access VPN session was established. The event references principal-cc88ce7b51f0aa37. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"File audit on SUPPORT-ASSET-0129618ced8fc8ec recorded that a process compressed files from several directories into an archive. The event references principal-8432d907b9ba200c. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-5658fe247542 match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Winrm audit on ENGINEERING-ASSET-6e5e1ed61987467a recorded that a remote management session invoked a command on a managed host. The event references principal-c372b39c0d58be55. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Database audit on OPERATIONS-ASSET-302e0f5dfef6781b recorded that a session read several tables and exported the query result. The event references principal-22fca2204489e9a2. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Secret manager audit on SUPPORT-ASSET-c293b34ccf018f66 recorded that a workload read several secret versions. The event references principal-e464eb0ee46edc73. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Cloud control audit on PEOPLE-ASSET-a565fc161c06dbdd recorded that a cloud logging destination was disabled. The event references principal-b1342e9d7cf466d7. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Identity audit on COMMUNICATIONS-ASSET-4abec775a52c95c2 recorded that repeated failed sign-ins were recorded for an account. The event references principal-a42f44848e926187. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Directory audit on SALES-ASSET-59c719c0c63878b3 recorded that a principal requested directory replication data. The event references principal-cb15573feb355e86. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-342730cb2714 before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Code integrity audit on FINANCE-ASSET-17d7fd3ccdbe7a13 recorded that an executable without a publisher signature started from a writable directory. The event references principal-8715ecce18f6c074. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Change CHG-c7967f3297eb lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Driver audit on RESEARCH-ASSET-5b972011692602fc recorded that a kernel driver was loaded after a package installation. The event references principal-71a994ae28cc3c7a. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Key service audit on SALES-ASSET-4796409e71ec7ec0 recorded that a principal issued a burst of key-service decrypt requests. The event references principal-e868bdfcec891314. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Dns control audit on SALES-ASSET-47a87d0c2fc4257b recorded that an authoritative DNS record was updated. The event references principal-3d712bbcbd3470d6. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"File audit on COMMUNICATIONS-ASSET-aa99d2f314263fcc recorded that a process compressed files from several directories into an archive. The event references principal-f14ddee6e5692d20. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-028690f81adb before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Kerberos audit on SUPPORT-ASSET-cee89b8c79f8f807 recorded that an account requested service tickets for multiple services. The event references principal-ba01468b28096ded. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-fad7d4246cc1 explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Cloud identity audit on COMMUNICATIONS-ASSET-8660c1612914f6bd recorded that a principal received a policy granting additional permissions. The event references principal-796bfc42ecc484c7. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Ci secret audit on OPERATIONS-ASSET-e1c6669f5f29a589 recorded that a build job requested a protected pipeline secret. The event references principal-e8010ec93fff4989. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Process audit on FINANCE-ASSET-9d45d520b4a54280 recorded that a Python interpreter loaded a script and contacted a service. The event references principal-d052a3f1c4010987. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-698189598bcc, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Cloud control audit on COMMUNICATIONS-ASSET-53a6ecae622bccee recorded that a cloud logging destination was disabled. The event references principal-cf25374694280e00. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"File access audit on OPERATIONS-ASSET-1494559c806dea5d recorded that a process opened a local credential-store file. The event references principal-c4b1fa13e42018fb. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Federation audit on SUPPORT-ASSET-9d7cd1e21b7e712c recorded that a tenant federation setting was updated. The event references principal-1761e65ce57d1289. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Process audit on FINANCE-ASSET-565f2ed301684671 recorded that a remote-support application started an interactive session. The event references principal-a4a07392170d1084. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Key service audit on COMMUNICATIONS-ASSET-5437588d51522a99 recorded that a principal issued a burst of key-service decrypt requests. The event references principal-f88907eb1e848f20. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Mail and proxy logs on LEGAL-ASSET-bdb95e0606dac9b6 recorded that a user opened a URL delivered in an email message. The event references principal-5ab74a82bf3ac244. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Gateway logs on SUPPORT-ASSET-bfcdc7fd12a63ce3 recorded that a client established a long-lived encapsulated network session. The event references principal-076e693836d2e9e9. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Kubernetes audit on COMMUNICATIONS-ASSET-4eb386b59cd197fa recorded that a cluster admission policy was changed. The event references principal-6713342ad2d170de. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Egress flow logs on COMMUNICATIONS-ASSET-1fa62ed57f8d2679 recorded that a workload opened an encrypted connection to an external service. The event references principal-297491ec275675d7. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Module audit on PROCUREMENT-ASSET-234ebd90da532d08 recorded that a process loaded a library from an application-local directory. The event references principal-2bfaedc31b23b886. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-0de44bec4994 accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Application audit on ENGINEERING-ASSET-c6a3af2b55d88d84 recorded that a runtime configuration setting was updated. The event references principal-67b63805e0368323. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Process access audit on PEOPLE-ASSET-e69cbb53fe5c9e6a recorded that a process requested read access to another process memory space. The event references principal-b9eeb1db9d8c686f. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Event service audit on RESEARCH-ASSET-79d1b62714d14ec4 recorded that an event log was cleared by a privileged request. The event references principal-78e29e015c8aeb2f. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Policy audit on OPERATIONS-ASSET-bb5aff052239026f recorded that an audit policy was changed to collect fewer event categories. The event references principal-08ce997b82328b8f. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-782c0856ed53 match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Process audit on PROCUREMENT-ASSET-4c9b1e536ca1f43f recorded that a Python interpreter loaded a script and contacted a service. The event references principal-f1d7ec01883c26bc. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-e9f62c742a74 before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Kubernetes audit on FINANCE-ASSET-d7b2da83577ab38d recorded that a pod was created with privileged execution enabled. The event references principal-5177d7ecbc348aa2. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Policy audit on OPERATIONS-ASSET-bb5aff052239026f recorded that an audit policy was changed to collect fewer event categories. The event references principal-08ce997b82328b8f. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Dns control audit on ENGINEERING-ASSET-62a2603633015b4a recorded that an authoritative DNS record was updated. The event references principal-38391a49d25a310a. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Wmi audit on COMMUNICATIONS-ASSET-03aadd8a551fef8d recorded that a management request started a process through WMI. The event references principal-1c1aa32fcc8fde6b. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Directory audit on LEGAL-ASSET-e41057b50163ec62 recorded that a principal requested directory replication data. The event references principal-27103a43ea428bc2. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Policy audit on FINANCE-ASSET-e464a7dfab1a5a08 recorded that an audit policy was changed to collect fewer event categories. The event references principal-88be6dc1340765a4. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Cron audit on SALES-ASSET-34715d088f9c8c11 recorded that a recurring job definition was added to the system schedule. The event references principal-69300e7147cdfbd9. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Cron audit on SALES-ASSET-34715d088f9c8c11 recorded that a recurring job definition was added to the system schedule. The event references principal-69300e7147cdfbd9. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-ce1afd00b60c before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Wmi audit on LEGAL-ASSET-a70f3384c72ee597 recorded that a management request started a process through WMI. The event references principal-d9be46a6c47bd578. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Flow logs on COMMUNICATIONS-ASSET-9213739a917e9a5d recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-fd59ae210210a351. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Cron audit on PROCUREMENT-ASSET-ccd7b77f6fbe55e6 recorded that a recurring job definition was added to the system schedule. The event references principal-ff6d598ce8d74f2d. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Function audit on FINANCE-ASSET-715a47edf7141497 recorded that a serverless function package and execution settings were updated. The event references principal-e1d12cf425ed5c27. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Device and file audit on FINANCE-ASSET-95133e3350d50213 recorded that files were copied to a removable storage device. The event references principal-3a08b3fa9560c2b5. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Session audit on SALES-ASSET-e0e65cd3109e663e recorded that the same session token appeared from different client addresses. The event references principal-b32690205f2a72fc. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Registry audit on LEGAL-ASSET-d0480e188fd31f60 recorded that a workload pulled a container image from a registry. The event references principal-160b2d0cefee47e2. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Process audit on COMMUNICATIONS-ASSET-5b837c3960f14bc6 recorded that a JavaScript interpreter executed a local script. The event references principal-f91a7e6de3b60959. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-5fd09b881748, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Repository audit on COMMUNICATIONS-ASSET-fc7d932dec68a3a4 recorded that a user cloned several source repositories. The event references principal-f9163c8da3ccc09a. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Application audit on ENGINEERING-ASSET-83152a55ea1c27b8 recorded that an application read clipboard contents repeatedly. The event references principal-d08677bd055caebe. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Group audit on SUPPORT-ASSET-32af0f049b4169a7 recorded that an account was added to a privileged local group. The event references principal-b75a2d708106954b. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Dns server audit on ENGINEERING-ASSET-aec07c525ec55aac recorded that a client requested a DNS zone transfer. The event references principal-4c0d05a21a35e460. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Smb audit on LEGAL-ASSET-cbd503b9d9dce0b4 recorded that a session enumerated a file share and read multiple files. The event references principal-308281e8cf667587. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Macos launch audit on LEGAL-ASSET-924fcf03a30c9333 recorded that a launch agent definition was installed in a user context. The event references principal-188d4edbd5c47469. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Assessment SEC-5924701f7b2a explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Macos launch audit on SUPPORT-ASSET-650496733d825be0 recorded that a launch agent definition was installed in a user context. The event references principal-0735ac9998e5203b. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-1de867c35341 explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Identity audit on ENGINEERING-ASSET-ce4355624d538400 recorded that an account password was reset through a recovery workflow. The event references principal-8d13b23a4098f36d. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Switch telemetry on SALES-ASSET-67150f5bd544c87a recorded that an address mapping changed repeatedly on a local segment. The event references principal-f4e3b1c2069d2a7e. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Certificate audit on PEOPLE-ASSET-4d0259660c317b95 recorded that a service certificate was replaced. The event references principal-f191ea3a323e48f8. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-499c7cd8a4bb match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Application audit on PROCUREMENT-ASSET-0b973fc190e51fb9 recorded that an application requested repeated screen captures. The event references principal-6d7c52f4e39422b1. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Task scheduler audit on COMMUNICATIONS-ASSET-3b8f70e54b109a07 recorded that a scheduled task was registered to execute a program at logon. The event references principal-ea7b65d7a85105ed. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Database audit on ENGINEERING-ASSET-5b5cb77077baa64c recorded that a session changed a database table definition. The event references principal-6bfe365bf3961695. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Change CHG-b0767feee0f0 lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Kubernetes audit on LEGAL-ASSET-a4bb453a13c05590 recorded that a role binding granted a principal additional cluster permissions. The event references principal-f6d0dcce5ee82a68. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Certificate audit on COMMUNICATIONS-ASSET-f4321cc57d6f7080 recorded that a service certificate was replaced. The event references principal-790bc3cf91a2a094. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Certificate audit on LEGAL-ASSET-028cc6c15478424c recorded that a service certificate was replaced. The event references principal-ab2a10d3b09a07d5. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Security retest SEC-9e81ade63526 covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Policy audit on RESEARCH-ASSET-9236351eaaf332af recorded that an audit policy was changed to collect fewer event categories. The event references principal-9505995ed7eba439. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-96d5eb2240cf explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Function audit on FINANCE-ASSET-715a47edf7141497 recorded that a serverless function package and execution settings were updated. The event references principal-e1d12cf425ed5c27. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-830680725f89 before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Application audit on RESEARCH-ASSET-21c212dc3255aa17 recorded that an application read clipboard contents repeatedly. The event references principal-8f2a965b2d84c102. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Service audit on PEOPLE-ASSET-222cba6353f1d99f recorded that a new automatically started service was registered. The event references principal-e5172d8225074491. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-7c6be80fdd9d before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Process audit on OPERATIONS-ASSET-a738dad8c83d20bb recorded that a JavaScript interpreter executed a local script. The event references principal-ba7460ce51b6b106. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Api gateway logs on RESEARCH-ASSET-43a3327a7670f557 recorded that a client issued a burst of API requests. The event references principal-19db88a740f22c57. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Browser audit on SUPPORT-ASSET-089bd1e438aae68a recorded that a browser extension with page-reading permissions was installed. The event references principal-05dd057e76f4173e. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Event service audit on RESEARCH-ASSET-79d1b62714d14ec4 recorded that an event log was cleared by a privileged request. The event references principal-78e29e015c8aeb2f. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-fc0d5f8dfb40 match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Share audit on LEGAL-ASSET-f4d3a91d6248c724 recorded that a new network file share was published. The event references principal-9174cfcb163194b8. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Mail audit on SUPPORT-ASSET-d04332aa87461fec recorded that an account received delegated access to a mailbox. The event references principal-4bd49edb0535ebaf. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Repository audit on LEGAL-ASSET-d4c7f3d667dee146 recorded that a user cloned several source repositories. The event references principal-0ab147f1f9481604. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Package registry audit on PEOPLE-ASSET-63788b9d7987296c recorded that a principal published a new package version. The event references principal-1efd21efeb7b167e. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Kubernetes audit on SUPPORT-ASSET-95dbeaaf93770ec1 recorded that a role binding granted a principal additional cluster permissions. The event references principal-fae5a1331ea1b683. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Application audit on LEGAL-ASSET-235dadbbfdbe7d33 recorded that an application requested repeated screen captures. The event references principal-31391eee810ce402. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Policy audit on FINANCE-ASSET-e464a7dfab1a5a08 recorded that an audit policy was changed to collect fewer event categories. The event references principal-88be6dc1340765a4. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Dhcp telemetry on SUPPORT-ASSET-ea5b723e111a60c0 recorded that a server issued DHCP offers on a monitored segment. The event references principal-f0fe04f7d6936857. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-fc0db5de02db match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Systemd audit on FINANCE-ASSET-2646ce4052597344 recorded that a service unit file was changed and the unit reloaded. The event references principal-38069415a5ef6919. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-25e04f2148c8 match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Cloud identity audit on FINANCE-ASSET-b948d8305372c015 recorded that a new programmatic access key was issued to a principal. The event references principal-68bd58abfea31389. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Application audit on FINANCE-ASSET-5311585386f59d86 recorded that an application requested repeated screen captures. The event references principal-6f04a55a0eba4c05. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Mail and proxy logs on FINANCE-ASSET-75c33a0daf443282 recorded that a user opened a URL delivered in an email message. The event references principal-4da288c1eb5d26af. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-40811f7a8c47 accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Group audit on PEOPLE-ASSET-f5ce370c9062d00a recorded that an account was added to a privileged local group. The event references principal-a4fe590d9388b8ea. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Identity audit on SALES-ASSET-880860857ffcd92f recorded that a service account established an interactive session. The event references principal-6480886757402cfa. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"File access audit on PEOPLE-ASSET-4246817b50ce1d24 recorded that a process opened a local credential-store file. The event references principal-69567a3aa8e45657. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Process audit on RESEARCH-ASSET-a06368c20e1f1761 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-c27d38810eca0fcd. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-324089110a6a accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Runtime audit on RESEARCH-ASSET-1fdd4c74894a8860 recorded that a process connected to the container runtime socket. The event references principal-1fe12f7544607ca6. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Switch telemetry on SALES-ASSET-67150f5bd544c87a recorded that an address mapping changed repeatedly on a local segment. The event references principal-f4e3b1c2069d2a7e. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-88ef29e55952 specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Secret manager audit on ENGINEERING-ASSET-c96b6e8c112e5ab0 recorded that a workload read several secret versions. The event references principal-24b9130cfaf6e9ca. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Configuration audit on ENGINEERING-ASSET-05746d5c7e76781e recorded that a client proxy setting was changed. The event references principal-f4f857793a1cd276. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Mail and proxy logs on FINANCE-ASSET-75c33a0daf443282 recorded that a user opened a URL delivered in an email message. The event references principal-4da288c1eb5d26af. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Kubernetes audit on COMMUNICATIONS-ASSET-4eb386b59cd197fa recorded that a cluster admission policy was changed. The event references principal-6713342ad2d170de. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Session audit on COMMUNICATIONS-ASSET-9a4f765d7218bb33 recorded that the same session token appeared from different client addresses. The event references principal-961620617e88f850. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Kubernetes audit on LEGAL-ASSET-d5c1c420f1077ded recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-1d6426e1ff1f69c4. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Dns server audit on LEGAL-ASSET-9a776b98cec96a9e recorded that a client requested a DNS zone transfer. The event references principal-b7047a9785be46d4. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Firewall audit on LEGAL-ASSET-a8345e2e1a01ff48 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-74a2c9033c8d23b7. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Repository audit on SUPPORT-ASSET-fb6027084fb1957b recorded that a user cloned several source repositories. The event references principal-6318dd66af34e88b. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Wmi audit on COMMUNICATIONS-ASSET-03aadd8a551fef8d recorded that a management request started a process through WMI. The event references principal-1c1aa32fcc8fde6b. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-cc971669889f, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Switch telemetry on PROCUREMENT-ASSET-c13f623edc6be72c recorded that an address mapping changed repeatedly on a local segment. The event references principal-464589d30bf27aee. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Mail flow logs on FINANCE-ASSET-05268a477e8094f0 recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-ab4f2f7ab1b6ae29. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Secret manager audit on LEGAL-ASSET-473919a6141fb4d1 recorded that a workload read several secret versions. The event references principal-be429b8818a2a6bf. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-aa48520ea135 match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Identity audit on RESEARCH-ASSET-88e52266f5af4a21 recorded that a service account established an interactive session. The event references principal-d08379cdebfa5913. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-145968eea008 before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Ci audit on ENGINEERING-ASSET-2c0d231544308107 recorded that a build pipeline definition gained a new execution step. The event references principal-aba5ed9cc375c5ec. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Mail audit on COMMUNICATIONS-ASSET-dece9873e2e03f6f recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-3d08b8fe271ddda1. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-0daab88dffdd, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Agent audit on ENGINEERING-ASSET-d4aa23315bb70413 recorded that a privileged session changed endpoint monitoring settings. The event references principal-2e08cdbbea0a15c2. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Certificate audit on SALES-ASSET-d2e9e0997da46974 recorded that a service certificate was replaced. The event references principal-0e407d6273aa8758. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Gateway logs on OPERATIONS-ASSET-7599af3c268c4876 recorded that a client established a long-lived encapsulated network session. The event references principal-ba0168660aabc1f0. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Event service audit on COMMUNICATIONS-ASSET-a0753c1183185be8 recorded that an event log was cleared by a privileged request. The event references principal-3da9da5b32a84636. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-c5c2736f82fd accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Directory audit on SALES-ASSET-59c719c0c63878b3 recorded that a principal requested directory replication data. The event references principal-cb15573feb355e86. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Api gateway logs on PROCUREMENT-ASSET-1c1b6a1c5f9b9bd8 recorded that a client issued a burst of API requests. The event references principal-257e72e6a629f939. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Resolver logs on COMMUNICATIONS-ASSET-064116140685fdd2 recorded that a client requested many long, high-entropy DNS labels. The event references principal-a53098877c1921c0. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-77c2d4b208c9 covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Application audit on OPERATIONS-ASSET-cf2679e9708fa36f recorded that a runtime configuration setting was updated. The event references principal-3db05afeebe1db89. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-53fd9a25d116 specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Cloud control audit on ENGINEERING-ASSET-1c2668b46715bf02 recorded that resources were created in a region with little prior activity. The event references principal-974cef6dad8360ab. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-c8171b4c58bf match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Identity audit on SUPPORT-ASSET-f9b39e12fc139ef0 recorded that an account registered a new MFA method. The event references principal-3c523bf81b3a031f. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Account audit on PROCUREMENT-ASSET-6b3dfabb9fc718fa recorded that a local user account was created on a managed system. The event references principal-67628d1182b40e07. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Driver audit on ENGINEERING-ASSET-aa761eb37a133a6c recorded that a kernel driver was loaded after a package installation. The event references principal-b792fcefc38ccc53. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"File audit on OPERATIONS-ASSET-aa398735111975aa recorded that a process deleted many files within a short interval. The event references principal-ff0116df6d90824b. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Change CHG-1411f03ebbf1 lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Gateway logs on COMMUNICATIONS-ASSET-01bdebe9cfb40e2b recorded that a client established a long-lived encapsulated network session. The event references principal-298b7f8258456986. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Backup audit on OPERATIONS-ASSET-b26fa319d3d0ce69 recorded that a backup retention policy was shortened. The event references principal-428102206d771c95. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Flow logs on PROCUREMENT-ASSET-cd965c50b19b4b1f recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-3abc068e3f191445. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Change CHG-e9f5d88049ad lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Oauth audit on LEGAL-ASSET-00c7e53409190f35 recorded that an application received consent for additional account scopes. The event references principal-aa7e16ffa8e68220. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Device and file audit on COMMUNICATIONS-ASSET-f491a02c80ff7ee4 recorded that files were copied to a removable storage device. The event references principal-b586401867cc7a49. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-fdc1a6d4b075 match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Storage audit on COMMUNICATIONS-ASSET-4c8d4447eef18c17 recorded that an object-storage access policy was broadened. The event references principal-2ee0983ecf5d6d25. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Saas audit on LEGAL-ASSET-febb39399ce8713a recorded that a user requested a bulk export from a business application. The event references principal-56038be98666605f. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Browser audit on RESEARCH-ASSET-b0be4ff24f6a9c7d recorded that a browser extension with page-reading permissions was installed. The event references principal-c445644ab42572e7. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"File audit on SUPPORT-ASSET-96c72864072032c8 recorded that a process deleted many files within a short interval. The event references principal-7a907f6a20c3a4ff. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-843fa6d9974c explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Network control audit on PEOPLE-ASSET-30b5158319199c4f recorded that a cloud security group gained a broad ingress rule. The event references principal-4d55ccd8cef6e438. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Mail audit on SUPPORT-ASSET-af2380a8ab001950 recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-d2de6ff979b628f2. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Flow logs on PEOPLE-ASSET-48ed1d716acee890 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-d5ba1580babde1ed. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-6f9e41634fe3, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Repository audit on ENGINEERING-ASSET-501895f2c603da6f recorded that a user cloned several source repositories. The event references principal-08a3df240a2c2acb. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Application audit on OPERATIONS-ASSET-09e59732382536e3 recorded that an application requested repeated screen captures. The event references principal-a45fb9f4a0a7c7be. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Database audit on SALES-ASSET-849ddfe1a9053808 recorded that a session changed a database table definition. The event references principal-425b4fae9e8852ef. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-f7c1fff050cc accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Device and file audit on COMMUNICATIONS-ASSET-f491a02c80ff7ee4 recorded that files were copied to a removable storage device. The event references principal-b586401867cc7a49. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Backup audit on SALES-ASSET-6933f79c2a57f98c recorded that a backup retention policy was shortened. The event references principal-9b63e3d52602597e. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Group audit on SALES-ASSET-0d02096325648024 recorded that an account was added to a privileged local group. The event references principal-2cfc43945d846816. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Mail flow logs on PEOPLE-ASSET-9ba2c53dc33b0530 recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-5b015560df1e299f. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-781d418d8cd9 specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Process audit on PEOPLE-ASSET-f75719ff0e53a895 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-b17a106beae4504c. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Account audit on SALES-ASSET-b02113ff8562d223 recorded that a local user account was created on a managed system. The event references principal-3cbed1cc8fc2d897. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Agent audit on PEOPLE-ASSET-145b133cd9883db8 recorded that a privileged session changed endpoint monitoring settings. The event references principal-3cdfd17f049efdd9. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Process audit on LEGAL-ASSET-523d2840aded9f3a recorded that a remote-support application started an interactive session. The event references principal-d733a0ecd691110d. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Function audit on OPERATIONS-ASSET-7bf3d2cc7f955758 recorded that a serverless function package and execution settings were updated. The event references principal-2b7da48bc74786c4. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-262d0cbd3ca7 specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Identity audit on FINANCE-ASSET-17a7d4bc3e0dfc99 recorded that a service account established an interactive session. The event references principal-ba443b5f7751e8bc. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Identity audit on ENGINEERING-ASSET-f3a5e6ca5f4810c3 recorded that an account registered a new MFA method. The event references principal-a81b0853166bb0e5. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Network control audit on RESEARCH-ASSET-e48fcfb18287d725 recorded that a cloud security group gained a broad ingress rule. The event references principal-0f1496ca8a6383fd. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Database audit on PEOPLE-ASSET-5fce356081bdb526 recorded that a session read several tables and exported the query result. The event references principal-b90846a958bd885f. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Package registry audit on LEGAL-ASSET-904ec76dbb996774 recorded that a principal published a new package version. The event references principal-3920a37e9b8e2b42. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Function audit on LEGAL-ASSET-a808b2dbcafaf1de recorded that a serverless function package and execution settings were updated. The event references principal-d18e2930c59bbade. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"File audit on RESEARCH-ASSET-08266be3d48a0589 recorded that a process compressed files from several directories into an archive. The event references principal-ba2e548a2cd0e827. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Browser audit on ENGINEERING-ASSET-f6edb397c93f1bb4 recorded that a browser extension with page-reading permissions was installed. The event references principal-bf7a3feca21483cd. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Process audit on ENGINEERING-ASSET-254e39c6de0e65b8 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-b4a1f0cd4cef32ed. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Change CHG-a98c1c4288f0 lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Account audit on COMMUNICATIONS-ASSET-9a834b6edbe1b57f recorded that a local user account was created on a managed system. The event references principal-57644d2a7475e5ae. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Group audit on COMMUNICATIONS-ASSET-c7bad2289a06229c recorded that an account was added to a privileged local group. The event references principal-45633364c2ed091b. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-11e022798a72 accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Kubernetes audit on FINANCE-ASSET-915256a7e7a6d4a6 recorded that a role binding granted a principal additional cluster permissions. The event references principal-49e34ed22123229a. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Office audit on ENGINEERING-ASSET-8b497889760890b7 recorded that a document macro launched a child interpreter. The event references principal-348623c716d723c6. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Cloud identity audit on SALES-ASSET-97a28d40051be12b recorded that a principal received a policy granting additional permissions. The event references principal-e45a694b7e0b8b49. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Kubernetes audit on RESEARCH-ASSET-d1f7ab9c3de5615d recorded that a cluster admission policy was changed. The event references principal-bc8aec70f878822d. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-bc0f90c3602a specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Service audit on LEGAL-ASSET-c27c6fe8739fc291 recorded that a remote service-control request created and started a temporary service. The event references principal-473978dbe47e2846. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Policy audit on PEOPLE-ASSET-4626b13b6c89e82c recorded that an audit policy was changed to collect fewer event categories. The event references principal-dc47a10146c766ea. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Storage audit on LEGAL-ASSET-5cc263cd7974e410 recorded that a session deleted several storage snapshots. The event references principal-548b73b08858de12. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Switch telemetry on FINANCE-ASSET-c82eb7bf49c6713c recorded that an address mapping changed repeatedly on a local segment. The event references principal-24aa90be68c12c8b. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-fa6408a5a93d specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Api gateway logs on COMMUNICATIONS-ASSET-25487240e8c2e247 recorded that a client issued a burst of API requests. The event references principal-23ca7dbb4aa37ade. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-b49a46b46aa4 explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Dns control audit on FINANCE-ASSET-84a7d1044449f1a8 recorded that an authoritative DNS record was updated. The event references principal-f7395e7a5d189597. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Windows logon audit on COMMUNICATIONS-ASSET-6f9244839c2eca95 recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-263d3b9d1be1a7e1. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-0c0e042bf95b explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Module audit on SALES-ASSET-0a5edb66b7d6ecd7 recorded that a process loaded a library from an application-local directory. The event references principal-adbbffe7727b888c. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-9b8631afa010, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"File audit on OPERATIONS-ASSET-f5bfac37e0e6e52e recorded that access permissions were broadened on a directory tree. The event references principal-c5603af4c6f0f506. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"File audit on COMMUNICATIONS-ASSET-4e97ae367849b7ff recorded that a process deleted many files within a short interval. The event references principal-0d2d1e13b6f37e28. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Macos launch audit on SUPPORT-ASSET-650496733d825be0 recorded that a launch agent definition was installed in a user context. The event references principal-0735ac9998e5203b. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Account audit on FINANCE-ASSET-00ff9ecf71797cc7 recorded that a local user account was created on a managed system. The event references principal-a4700d3ad9f008de. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Mail flow logs on LEGAL-ASSET-692e1a748d08a501 recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-527175c687849d2d. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Assessment SEC-5569ad92fc3d explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Process audit on RESEARCH-ASSET-a06368c20e1f1761 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-c27d38810eca0fcd. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"File audit on OPERATIONS-ASSET-a72fe66e9e140fe9 recorded that a process compressed files from several directories into an archive. The event references principal-41403cc0bff319ee. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Resolver logs on PROCUREMENT-ASSET-217f3e17146574de recorded that a client requested many long, high-entropy DNS labels. The event references principal-c25feb34aea9c3bd. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Identity audit on OPERATIONS-ASSET-bc3d71283010bd0f recorded that an account password was reset through a recovery workflow. The event references principal-65a355a045f94503. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Change CHG-643745179126 lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Cloud control audit on SUPPORT-ASSET-e66fe35db626a7f0 recorded that resources were created in a region with little prior activity. The event references principal-84f7c4bc4b40ce6e. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Saas audit on FINANCE-ASSET-7dbfabaebbf506b5 recorded that a user requested a bulk export from a business application. The event references principal-147dd62c19db648c. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"File audit on LEGAL-ASSET-bda990f3a65f05d4 recorded that a process compressed files from several directories into an archive. The event references principal-e0bfbf7c864c739b. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Module audit on PEOPLE-ASSET-4e7e86d1ce25eca1 recorded that a process loaded a library from an application-local directory. The event references principal-32a2611884a3eb03. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Registry audit on FINANCE-ASSET-7f731069af53e8e1 recorded that a workload pulled a container image from a registry. The event references principal-b80084fb240685bf. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Agent audit on PROCUREMENT-ASSET-92d810ab505277a2 recorded that a privileged session changed endpoint monitoring settings. The event references principal-ae67200926ed1d7a. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Vpn audit on FINANCE-ASSET-5b805daa08de83aa recorded that a remote-access VPN session was established. The event references principal-cc88ce7b51f0aa37. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-531033a2d786, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"File access audit on LEGAL-ASSET-c0436d9a797b6aac recorded that a process opened a local credential-store file. The event references principal-8f957f68f520d591. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Process audit on OPERATIONS-ASSET-a738dad8c83d20bb recorded that a JavaScript interpreter executed a local script. The event references principal-ba7460ce51b6b106. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Change CHG-322d754f8409 lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Macos launch audit on SUPPORT-ASSET-650496733d825be0 recorded that a launch agent definition was installed in a user context. The event references principal-0735ac9998e5203b. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-1de867c35341, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Browser audit on OPERATIONS-ASSET-1696f264e915fdf5 recorded that a browser extension with page-reading permissions was installed. The event references principal-f101b193c2f738a3. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Ci secret audit on SUPPORT-ASSET-d5ed18de3905520f recorded that a build job requested a protected pipeline secret. The event references principal-7efbed86c5e71c09. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Process audit on PEOPLE-ASSET-f75719ff0e53a895 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-b17a106beae4504c. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Process audit on SUPPORT-ASSET-0577991db5a15090 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-d0dbfe56694e1edd. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Mail and proxy logs on LEGAL-ASSET-bdb95e0606dac9b6 recorded that a user opened a URL delivered in an email message. The event references principal-5ab74a82bf3ac244. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-3a9cee23a0aa before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Smb audit on SALES-ASSET-f9e0160f65640ecb recorded that a session enumerated a file share and read multiple files. The event references principal-5b93bfe2ff3ce2df. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-3a5017e11fe5 explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Task scheduler audit on PEOPLE-ASSET-967b5df7e748b2ff recorded that a scheduled task was registered to execute a program at logon. The event references principal-80092436d4633e85. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Assessment SEC-870835598d02 explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Event service audit on LEGAL-ASSET-1725494bd06479c8 recorded that an event log was cleared by a privileged request. The event references principal-2d006b9d45394524. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-d02dc959ec2a match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Dns control audit on SALES-ASSET-47a87d0c2fc4257b recorded that an authoritative DNS record was updated. The event references principal-3d712bbcbd3470d6. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-cb9306490a71 accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Saas audit on RESEARCH-ASSET-b155eac613e67224 recorded that a user requested a bulk export from a business application. The event references principal-5a3ba2a9838be78e. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Application audit on SUPPORT-ASSET-bc02457e5d2c9364 recorded that an application read clipboard contents repeatedly. The event references principal-5b5cc7cba3470ef8. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Gateway logs on PROCUREMENT-ASSET-b0d37645a10d287b recorded that a client established a long-lived encapsulated network session. The event references principal-1cc47c7a352875b2. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Kubernetes audit on LEGAL-ASSET-3c1eaaf59969b766 recorded that a workload mounted a directory from its host filesystem. The event references principal-a5edc19c7aca724f. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Device and file audit on SALES-ASSET-3b11bf4bc19f47f9 recorded that files were copied to a removable storage device. The event references principal-342176cf658025b8. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Macos launch audit on ENGINEERING-ASSET-20d414dac3bf58ed recorded that a launch agent definition was installed in a user context. The event references principal-9f713f5b46efadf7. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Group audit on PROCUREMENT-ASSET-b50d9791f482d6f4 recorded that an account was added to a privileged local group. The event references principal-c07c3b076842f6c0. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Backup audit on OPERATIONS-ASSET-b26fa319d3d0ce69 recorded that a backup retention policy was shortened. The event references principal-428102206d771c95. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Group audit on SUPPORT-ASSET-32af0f049b4169a7 recorded that an account was added to a privileged local group. The event references principal-b75a2d708106954b. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Dns control audit on PEOPLE-ASSET-4210d86f84839a74 recorded that an authoritative DNS record was updated. The event references principal-92f6f8227c610f96. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Flow logs on COMMUNICATIONS-ASSET-9213739a917e9a5d recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-fd59ae210210a351. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Office audit on SUPPORT-ASSET-b861b71047f83874 recorded that a document macro launched a child interpreter. The event references principal-41f626db101e0b15. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Driver audit on PEOPLE-ASSET-9e9f7519775a6002 recorded that a kernel driver was loaded after a package installation. The event references principal-4bafb24bfe647837. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-cc5acd342ca5 match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Module audit on PEOPLE-ASSET-4e7e86d1ce25eca1 recorded that a process loaded a library from an application-local directory. The event references principal-32a2611884a3eb03. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"File access audit on SALES-ASSET-da211711ae9c0eb7 recorded that a process opened a local credential-store file. The event references principal-d1b0980809a9edd2. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Assessment SEC-98cae1f2ef09 explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Waf logs on PEOPLE-ASSET-b68587853256629c recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-a0a816963fae146a. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-bdeb019a371d, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Cloud identity audit on COMMUNICATIONS-ASSET-a2643d4e14311066 recorded that a principal assumed a role in another account. The event references principal-3ce172a931fefefa. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Code integrity audit on PEOPLE-ASSET-4048dcb975a46f2e recorded that an executable without a publisher signature started from a writable directory. The event references principal-d449d23aa96125e6. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Key service audit on COMMUNICATIONS-ASSET-5437588d51522a99 recorded that a principal issued a burst of key-service decrypt requests. The event references principal-f88907eb1e848f20. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Macos launch audit on COMMUNICATIONS-ASSET-a6af7f5427b7cdc8 recorded that a launch agent definition was installed in a user context. The event references principal-1aeb8103bbf51c1f. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"File audit on SALES-ASSET-f0f53d618a5c2238 recorded that a process compressed files from several directories into an archive. The event references principal-a24a28fb5a9017a6. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-ff09ced7b153 accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Saas audit on SUPPORT-ASSET-2e07b9359e958267 recorded that a user requested a bulk export from a business application. The event references principal-b7211075b62be127. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Cloud control audit on LEGAL-ASSET-428365c6643172ec recorded that a cloud logging destination was disabled. The event references principal-5fcf49df98dad6ed. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Security retest SEC-01b7b218bcc6 covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Flow logs on PEOPLE-ASSET-48ed1d716acee890 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-d5ba1580babde1ed. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-6f9e41634fe3 accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Network control audit on SALES-ASSET-bd4a95d925024567 recorded that a cloud security group gained a broad ingress rule. The event references principal-2e1769cecef25401. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Change CHG-29db28979de6 lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Federation audit on SUPPORT-ASSET-9d7cd1e21b7e712c recorded that a tenant federation setting was updated. The event references principal-1761e65ce57d1289. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"File audit on PEOPLE-ASSET-df8464b337d342a5 recorded that a process deleted many files within a short interval. The event references principal-f13400db0397fece. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Flow logs on FINANCE-ASSET-a52520aa18fc5145 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-d9480c5f3eeb0f53. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Storage access logs on RESEARCH-ASSET-59340bda9ea1f273 recorded that a principal downloaded many objects from a storage bucket. The event references principal-516ae6385fac5df9. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Identity audit on COMMUNICATIONS-ASSET-cdebef5d9dc25fc4 recorded that a service account established an interactive session. The event references principal-ecbde67b88dd7d93. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Configuration audit on PROCUREMENT-ASSET-8aac493103d32947 recorded that a client proxy setting was changed. The event references principal-5ba8d1fc71029290. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Change CHG-221ec117bac6 lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Resolver logs on PROCUREMENT-ASSET-217f3e17146574de recorded that a client requested many long, high-entropy DNS labels. The event references principal-c25feb34aea9c3bd. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Registry audit on RESEARCH-ASSET-73e0cbd02049afd1 recorded that a workload pulled a container image from a registry. The event references principal-34d7877cf1ae898f. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Policy audit on ENGINEERING-ASSET-691918f61c7ec7b2 recorded that an audit policy was changed to collect fewer event categories. The event references principal-86d0e35aa5d8e487. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Registry audit on ENGINEERING-ASSET-3288f3a3a57d4d49 recorded that a registry logon-start entry was created. The event references principal-ab71b58d6c6b1b8b. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Secret manager audit on ENGINEERING-ASSET-c96b6e8c112e5ab0 recorded that a workload read several secret versions. The event references principal-24b9130cfaf6e9ca. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Process audit on SUPPORT-ASSET-6869d2722a21fd5c recorded that a Python interpreter loaded a script and contacted a service. The event references principal-f677ab6a5a1c21d4. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Ssh audit on SUPPORT-ASSET-842f8e08ea10f95b recorded that an SSH session opened and requested elevated command execution. The event references principal-3779cc64299d1a95. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Mail audit on PROCUREMENT-ASSET-57a43dc80cfc93ed recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-40142beb1db7ce4d. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Mail flow logs on ENGINEERING-ASSET-b3fe8e13b124582a recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-4618a2ddb02b8454. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Service audit on PROCUREMENT-ASSET-28254d89b1701083 recorded that a remote service-control request created and started a temporary service. The event references principal-cfe7f7b5911dcb16. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Flow logs on COMMUNICATIONS-ASSET-d5fd0288e752f79f recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-fd4faa7e0445166d. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-83c4a3292156 covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Dns control audit on RESEARCH-ASSET-f829e9e9bed9564b recorded that an authoritative DNS record was updated. The event references principal-9fdc73540b6a06a8. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Kubernetes audit on RESEARCH-ASSET-200dc8ad3542be6e recorded that a role binding granted a principal additional cluster permissions. The event references principal-b8023dd958201bec. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Assessment SEC-d1e325c5e4a7 explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Key service audit on FINANCE-ASSET-57ca74510903ebd4 recorded that a principal issued a burst of key-service decrypt requests. The event references principal-79b7e5a3aa2edd24. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Cloud identity audit on COMMUNICATIONS-ASSET-e9dda7a9ac4613e3 recorded that a new programmatic access key was issued to a principal. The event references principal-b50a9e7363974da3. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Script audit on PROCUREMENT-ASSET-d3383e3f3b9c4acb recorded that a script interpreter decoded an encoded argument before execution. The event references principal-b7570e0e965cd679. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Assessment SEC-db0a659d6762 explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Registry audit on OPERATIONS-ASSET-2d36b1b63d0c4ad6 recorded that a workload pulled a container image from a registry. The event references principal-1fdf41d42655dccc. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Secret manager audit on PROCUREMENT-ASSET-b6e8aa184c246f29 recorded that a workload read several secret versions. The event references principal-3c8c2cffa7cd4de8. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Event service audit on PROCUREMENT-ASSET-1656ac96cf7e6b6f recorded that an event log was cleared by a privileged request. The event references principal-994f7078cfaa2558. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Account audit on LEGAL-ASSET-00d4a961cd35ae5d recorded that a local user account was created on a managed system. The event references principal-ffacf4516ce71040. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Kubernetes audit on LEGAL-ASSET-d5c1c420f1077ded recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-1d6426e1ff1f69c4. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Kubernetes audit on SUPPORT-ASSET-ea9a39224859df23 recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-c986eaa5cd9383cb. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-8b69d70a8f85 match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Runtime audit on SUPPORT-ASSET-70bd103925bca47e recorded that a process connected to the container runtime socket. The event references principal-cf65589a3d4ad7b6. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-a7210d088fbb match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Api gateway logs on SUPPORT-ASSET-13bc954846049d2f recorded that a client issued a burst of API requests. The event references principal-d482be68e022a834. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Identity audit on COMMUNICATIONS-ASSET-ae1258c834d83e6f recorded that an account password was reset through a recovery workflow. The event references principal-98f97f4d1c43e756. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"File audit on RESEARCH-ASSET-29f4cb3c7a29beaf recorded that access permissions were broadened on a directory tree. The event references principal-9b108c0888253ab1. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Mail flow logs on ENGINEERING-ASSET-b3fe8e13b124582a recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-4618a2ddb02b8454. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Windows logon audit on SUPPORT-ASSET-b7addff92f67af33 recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-5b8a266b76f35fee. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Process access audit on COMMUNICATIONS-ASSET-5d86ffc7f1150e70 recorded that a process requested read access to another process memory space. The event references principal-4279d106b274e43e. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Process audit on COMMUNICATIONS-ASSET-32e7de18e8d35e66 recorded that a Python interpreter loaded a script and contacted a service. The event references principal-2424b5e4e4370c09. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Office audit on PROCUREMENT-ASSET-9c9a63eb958fdaa6 recorded that a document macro launched a child interpreter. The event references principal-40d050ba88a97331. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Agent audit on COMMUNICATIONS-ASSET-7f32c685e6e40f0f recorded that a privileged session changed endpoint monitoring settings. The event references principal-ce4504f33247e9eb. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Database audit on PEOPLE-ASSET-5fce356081bdb526 recorded that a session read several tables and exported the query result. The event references principal-b90846a958bd885f. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-e091dd0f8285 before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Cloud control audit on FINANCE-ASSET-b563459bb8af8f48 recorded that a session deleted a group of cloud resources. The event references principal-a8340a0f60620156. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"File audit on SUPPORT-ASSET-5e6185480b7124c6 recorded that a shell startup profile gained an additional command. The event references principal-51f94e540bbb4321. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Resolver logs on FINANCE-ASSET-702feb45e71dd31e recorded that a client requested many long, high-entropy DNS labels. The event references principal-219bc21f1d685857. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Dns control audit on PEOPLE-ASSET-4210d86f84839a74 recorded that an authoritative DNS record was updated. The event references principal-92f6f8227c610f96. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Assessment SEC-9824847b8c55 explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Waf logs on PEOPLE-ASSET-b68587853256629c recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-a0a816963fae146a. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Winrm audit on PROCUREMENT-ASSET-98512f6cba9a2651 recorded that a remote management session invoked a command on a managed host. The event references principal-e3d261d10a11f3f9. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-7f4e3d83c00a specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Kubernetes audit on OPERATIONS-ASSET-bc31964912cf4d1d recorded that a cluster admission policy was changed. The event references principal-c0a0ee553024f5ef. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Pki audit on FINANCE-ASSET-3748aa367e539143 recorded that a principal requested a certificate using an authentication template. The event references principal-d4df29576d1acbb5. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Ci audit on COMMUNICATIONS-ASSET-9c71cbe9ba5a6116 recorded that a build pipeline definition gained a new execution step. The event references principal-0b9701ae91042079. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Storage audit on COMMUNICATIONS-ASSET-80a867850d28c413 recorded that a session deleted several storage snapshots. The event references principal-fab18c6abd30f04e. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Account audit on PROCUREMENT-ASSET-6b3dfabb9fc718fa recorded that a local user account was created on a managed system. The event references principal-67628d1182b40e07. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-7771a9778540 specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Configuration audit on LEGAL-ASSET-654fecba9ad263c2 recorded that a client proxy setting was changed. The event references principal-40cdbd7119e49afd. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-2a6a4a5f2790 specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Repository audit on OPERATIONS-ASSET-d75290e6ed1a6d85 recorded that a repository collaborator received elevated permissions. The event references principal-b26cea051978a58c. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Directory audit on RESEARCH-ASSET-717c1ed36129eee9 recorded that a principal requested directory replication data. The event references principal-71255b0539b4ae1e. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Cloud identity audit on SUPPORT-ASSET-7e8f88bce8cfa9fc recorded that a principal received a policy granting additional permissions. The event references principal-02df9042c50f2455. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Application audit on PEOPLE-ASSET-16eca898293194f8 recorded that an application read clipboard contents repeatedly. The event references principal-9ece0c292d6cf355. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Change CHG-fcab3fdf29c0 lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"File audit on ENGINEERING-ASSET-52718af8394d4c73 recorded that a shell startup profile gained an additional command. The event references principal-7fbddd513d8c8d82. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Account audit on PEOPLE-ASSET-aaae6542cf112eee recorded that a local user account was created on a managed system. The event references principal-0953004be50ca69d. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-d8719312ac46 before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Service audit on SALES-ASSET-ee4f4ed67afc3eae recorded that a new automatically started service was registered. The event references principal-ae21c97b6a858bb0. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Task scheduler audit on ENGINEERING-ASSET-03b8a656580bfb25 recorded that a scheduled task was registered to execute a program at logon. The event references principal-2a3a3ccb2ea52460. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Process audit on FINANCE-ASSET-db3968cef4c0b684 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-a71f596247827755. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Application audit on LEGAL-ASSET-988ab05a6aaafddb recorded that a runtime configuration setting was updated. The event references principal-2cc56950de78c750. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-9fce6ada3217 explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Cloud identity audit on SUPPORT-ASSET-0acaf32cb86c9787 recorded that a new programmatic access key was issued to a principal. The event references principal-f4c6ed272feaab73. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Directory audit on PROCUREMENT-ASSET-7b387a0e6a39eb7a recorded that a principal requested directory replication data. The event references principal-0b3c6bcdb6ea6190. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-fa68664355b7 specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Session audit on PROCUREMENT-ASSET-375b33e301ac9b62 recorded that the same session token appeared from different client addresses. The event references principal-c5f1efc48ec3f681. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-13d721df8d28 match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Process access audit on LEGAL-ASSET-60fd34b6e0203a0f recorded that a process requested read access to another process memory space. The event references principal-1e4fdc2f020fb533. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-b4b7c3895d8c before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Identity audit on ENGINEERING-ASSET-7b28b0fa9a166d69 recorded that repeated failed sign-ins were recorded for an account. The event references principal-1962d3f4c712b2c7. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Backup audit on ENGINEERING-ASSET-e13f2ff83c899d5b recorded that a backup retention policy was shortened. The event references principal-31afc311e47df634. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Configuration audit on SUPPORT-ASSET-75f85e5b495f1222 recorded that a client proxy setting was changed. The event references principal-02061922c2bafcd3. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-e8c97c3680f9 specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Switch telemetry on SUPPORT-ASSET-8a0f455136f22cce recorded that an address mapping changed repeatedly on a local segment. The event references principal-598fd0cdb7a2c2dd. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Backup audit on SALES-ASSET-6933f79c2a57f98c recorded that a backup retention policy was shortened. The event references principal-9b63e3d52602597e. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Gateway logs on RESEARCH-ASSET-6dcd3c5959922161 recorded that a client established a long-lived encapsulated network session. The event references principal-d901ab75b47ec726. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Security retest SEC-68d8428b390d covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Browser audit on OPERATIONS-ASSET-1696f264e915fdf5 recorded that a browser extension with page-reading permissions was installed. The event references principal-f101b193c2f738a3. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-51606e334fc1 covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Group audit on OPERATIONS-ASSET-0c05abbcb3b78111 recorded that an account was added to a privileged local group. The event references principal-67db77b910dcd61e. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Kubernetes audit on PROCUREMENT-ASSET-a846eefa75a51312 recorded that a workload mounted a directory from its host filesystem. The event references principal-0cd6474c03a53052. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Identity audit on PROCUREMENT-ASSET-595810a122b584e8 recorded that a service account established an interactive session. The event references principal-786fe31fade4e850. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Compute audit on OPERATIONS-ASSET-ac6d22bf5640da77 recorded that a principal launched multiple compute instances. The event references principal-dec83605ca771167. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-616b0bdb3487 accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"File audit on OPERATIONS-ASSET-53ad24c9deb5d645 recorded that a shell startup profile gained an additional command. The event references principal-6049aaff0c8fe538. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Change CHG-59a78391fb4b lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Cloud control audit on ENGINEERING-ASSET-bbf96ebe3618813b recorded that a cloud logging destination was disabled. The event references principal-7942b0cb0edc33ed. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Repository audit on PEOPLE-ASSET-ab514f2b7cf1ca44 recorded that a repository collaborator received elevated permissions. The event references principal-49f43d9a0cf7b13c. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"File audit on COMMUNICATIONS-ASSET-aa99d2f314263fcc recorded that a process compressed files from several directories into an archive. The event references principal-f14ddee6e5692d20. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Browser audit on SUPPORT-ASSET-089bd1e438aae68a recorded that a browser extension with page-reading permissions was installed. The event references principal-05dd057e76f4173e. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Change CHG-816145c4da62 lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Database audit on PROCUREMENT-ASSET-e086d2946f81e9d3 recorded that a session read several tables and exported the query result. The event references principal-6283c0702f8c752e. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Code integrity audit on OPERATIONS-ASSET-06f732c807773233 recorded that an executable without a publisher signature started from a writable directory. The event references principal-28681a2e3d3ce90b. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Identity audit on SALES-ASSET-2f253fe8393025e1 recorded that an account password was reset through a recovery workflow. The event references principal-95366adc4199c0a7. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Saas audit on PEOPLE-ASSET-5249110e05a8362d recorded that a user requested a bulk export from a business application. The event references principal-55b28360ed7bad44. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Mfa audit on COMMUNICATIONS-ASSET-ce18db2b3211944f recorded that multiple MFA challenges were issued during a short interval. The event references principal-5c71c8caf74a8fa1. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-ff52d6dc5801 explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Office audit on OPERATIONS-ASSET-a21bbd8f65591dc7 recorded that a document macro launched a child interpreter. The event references principal-640ebd4004779cca. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-02c16ac8ab97 specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Function audit on LEGAL-ASSET-a808b2dbcafaf1de recorded that a serverless function package and execution settings were updated. The event references principal-d18e2930c59bbade. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Kerberos audit on ENGINEERING-ASSET-ca968191bd4b09c5 recorded that an account requested service tickets for multiple services. The event references principal-48c928131e4a9922. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Process access audit on SALES-ASSET-0e0ff0d46dd9bdcc recorded that a process requested read access to another process memory space. The event references principal-a29d7cafdbef1526. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Cloud identity audit on ENGINEERING-ASSET-af1e93943ab29f9c recorded that a new programmatic access key was issued to a principal. The event references principal-44b79fe1a6fcf9a1. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Oauth audit on PEOPLE-ASSET-f620f4cfac01530c recorded that an application received consent for additional account scopes. The event references principal-0999bb32ee8823f5. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-da3ec5cac05c accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Vpn audit on OPERATIONS-ASSET-3b10a040384bc85b recorded that a remote-access VPN session was established. The event references principal-e69c38b8397d46ff. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-d0578b5b8597 explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Code integrity audit on OPERATIONS-ASSET-06f732c807773233 recorded that an executable without a publisher signature started from a writable directory. The event references principal-28681a2e3d3ce90b. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"File audit on LEGAL-ASSET-fdae576414dd7376 recorded that a process deleted many files within a short interval. The event references principal-a6b7ec4e30bafd95. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Mail audit on COMMUNICATIONS-ASSET-cf30ec21588a2145 recorded that an account received delegated access to a mailbox. The event references principal-a11312ab2e69f315. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Resolver logs on COMMUNICATIONS-ASSET-064116140685fdd2 recorded that a client requested many long, high-entropy DNS labels. The event references principal-a53098877c1921c0. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Mail and proxy logs on PEOPLE-ASSET-73f46f787c3750bc recorded that a user opened a URL delivered in an email message. The event references principal-ae3654afd7401601. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Mail flow logs on OPERATIONS-ASSET-b187da0291cabbc9 recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-3df241ac15d172ff. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-54539ebdf474 covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"File access audit on COMMUNICATIONS-ASSET-5eb665c77394105b recorded that a process opened a local credential-store file. The event references principal-a9229a1030eb8134. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-27b06aed4bdc match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Process audit on SALES-ASSET-96ce257e2204a8a5 recorded that a remote-support application started an interactive session. The event references principal-ae9cce396ea567fe. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"File audit on SUPPORT-ASSET-528c23bdb207b71c recorded that access permissions were broadened on a directory tree. The event references principal-f1bdbe7329a336ab. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-0a43b3b46982 before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"File audit on COMMUNICATIONS-ASSET-23cdf3c51f4342c4 recorded that access permissions were broadened on a directory tree. The event references principal-fb51510da2f10fbb. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Key service audit on ENGINEERING-ASSET-a77dccd54b04aa48 recorded that a principal issued a burst of key-service decrypt requests. The event references principal-627115d6ce1d6169. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Application audit on OPERATIONS-ASSET-82d2279115651372 recorded that an application read clipboard contents repeatedly. The event references principal-d93f4c8e19d295a8. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Mfa audit on PROCUREMENT-ASSET-9ec036de13de448d recorded that multiple MFA challenges were issued during a short interval. The event references principal-906c50bf72cf0c69. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Change CHG-d2c9c51ac007 lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Account audit on SUPPORT-ASSET-4f664bc059385d17 recorded that a local user account was created on a managed system. The event references principal-1db165dfba5895ba. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-6fd850aa9f83 before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"File audit on LEGAL-ASSET-b2789a781837a87b recorded that a shell startup profile gained an additional command. The event references principal-d7a3487fce82090e. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Identity audit on SALES-ASSET-880860857ffcd92f recorded that a service account established an interactive session. The event references principal-6480886757402cfa. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-e91d3fcd08eb match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Cron audit on LEGAL-ASSET-fa5ca79bc164009d recorded that a recurring job definition was added to the system schedule. The event references principal-07e12ac009730cba. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-0ae107386894 before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Registry audit on COMMUNICATIONS-ASSET-bfd346cad4d024a4 recorded that a registry logon-start entry was created. The event references principal-74f1b84012bd604a. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-b96fb69d2b86 explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Dns control audit on PEOPLE-ASSET-4210d86f84839a74 recorded that an authoritative DNS record was updated. The event references principal-92f6f8227c610f96. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Change CHG-9824847b8c55 lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Account audit on ENGINEERING-ASSET-bce5c50695a23c43 recorded that a local user account was created on a managed system. The event references principal-1a94579d85980de4. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Wmi audit on COMMUNICATIONS-ASSET-03aadd8a551fef8d recorded that a management request started a process through WMI. The event references principal-1c1aa32fcc8fde6b. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-cc971669889f explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Account audit on RESEARCH-ASSET-a444b46456cd6186 recorded that a local user account was created on a managed system. The event references principal-dd1721a44a27272f. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Proxy logs on SALES-ASSET-c3dbe91c60733c60 recorded that a client transferred a large payload to an external storage endpoint. The event references principal-fbf3a8a302b7a6c9. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-c2d0f4a645dc explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Storage audit on SUPPORT-ASSET-4d8e24bcff05f227 recorded that an object-storage access policy was broadened. The event references principal-5112ec3a6a51c1b1. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-ed17c7cfa2d2 covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Mail audit on ENGINEERING-ASSET-0ca0b75c929f5305 recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-0a0bb31756158aab. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Process audit on COMMUNICATIONS-ASSET-5b837c3960f14bc6 recorded that a JavaScript interpreter executed a local script. The event references principal-f91a7e6de3b60959. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Process audit on SALES-ASSET-796c322bf9ce4051 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-eb12aa9934f163d5. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-f5fec0df3509, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Function audit on SALES-ASSET-461c1fc508bcc3ad recorded that a serverless function package and execution settings were updated. The event references principal-f88b3cc6828a81db. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Dns server audit on ENGINEERING-ASSET-aec07c525ec55aac recorded that a client requested a DNS zone transfer. The event references principal-4c0d05a21a35e460. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Cloud identity audit on SUPPORT-ASSET-7e8f88bce8cfa9fc recorded that a principal received a policy granting additional permissions. The event references principal-02df9042c50f2455. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Application audit on SALES-ASSET-a8b331f6bbbdf2ee recorded that a runtime configuration setting was updated. The event references principal-21cb8dcf748912e9. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-75383426559b explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"File audit on SALES-ASSET-a4a69365dce2152a recorded that a shell startup profile gained an additional command. The event references principal-3637027719cb9240. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Change CHG-d4cb1fb9a4dc lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Storage audit on OPERATIONS-ASSET-29e0421fa3b9bb88 recorded that an object-storage access policy was broadened. The event references principal-e4fd29cc648a5ac6. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-4648242cc648 explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"File audit on RESEARCH-ASSET-e7317bc73d028b83 recorded that a process deleted many files within a short interval. The event references principal-2ba5ba91bd6bd5b8. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-67b1b0c0ed83 accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Ci secret audit on LEGAL-ASSET-210117fa7f63e7fa recorded that a build job requested a protected pipeline secret. The event references principal-bafb03e4143599bb. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Smb audit on FINANCE-ASSET-c99a2728b7b98f2b recorded that a session enumerated a file share and read multiple files. The event references principal-40d6614472abce2d. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Task scheduler audit on SALES-ASSET-14a4b633fa3add9a recorded that a scheduled task was registered to execute a program at logon. The event references principal-bc7f1b7e6f9cd150. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-6fd3c4345233 accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Cloud control audit on RESEARCH-ASSET-2bdeaeb6bfb8b9b8 recorded that a cloud logging destination was disabled. The event references principal-00477aa276d23b17. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-032161856f78, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Firewall audit on SALES-ASSET-67b90170bfed122f recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-2766646810a01a28. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Cloud control audit on PEOPLE-ASSET-12878cc06ce2eeff recorded that resources were created in a region with little prior activity. The event references principal-504d0a8a24feb6ee. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Wmi audit on LEGAL-ASSET-a70f3384c72ee597 recorded that a management request started a process through WMI. The event references principal-d9be46a6c47bd578. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Kubernetes audit on OPERATIONS-ASSET-bc31964912cf4d1d recorded that a cluster admission policy was changed. The event references principal-c0a0ee553024f5ef. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-d896b10e7e0d before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Certificate audit on PROCUREMENT-ASSET-90178e3809a5e39e recorded that a service certificate was replaced. The event references principal-4bfd3026e3966135. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Dhcp telemetry on SUPPORT-ASSET-ea5b723e111a60c0 recorded that a server issued DHCP offers on a monitored segment. The event references principal-f0fe04f7d6936857. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Pki audit on ENGINEERING-ASSET-1be9c96304b0e927 recorded that a principal requested a certificate using an authentication template. The event references principal-86425f445bb7386e. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Oauth audit on OPERATIONS-ASSET-1d059cb4cf3d2fe1 recorded that an application received consent for additional account scopes. The event references principal-68400bad9534528c. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Federation audit on ENGINEERING-ASSET-ed48b05a54cba0b4 recorded that a tenant federation setting was updated. The event references principal-7dac1305cd5fd7e7. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-3639b66d5187 covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Policy audit on PROCUREMENT-ASSET-f2878461512a2696 recorded that an audit policy was changed to collect fewer event categories. The event references principal-2bb61efdeda82dac. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Proxy logs on OPERATIONS-ASSET-63a9838a229b6bdc recorded that a client transferred a large payload to an external storage endpoint. The event references principal-1a271b9f4504e35e. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Process audit on RESEARCH-ASSET-4c23face5574e971 recorded that a JavaScript interpreter executed a local script. The event references principal-4325acfa278d2f70. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Assessment SEC-f059629d83f7 explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Process audit on PEOPLE-ASSET-b5f000212e4e1683 recorded that a Python interpreter loaded a script and contacted a service. The event references principal-364f40722069431e. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Directory audit on COMMUNICATIONS-ASSET-014161d1ab75992f recorded that a principal requested directory replication data. The event references principal-06ff5e4392c8395e. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Session audit on COMMUNICATIONS-ASSET-9a4f765d7218bb33 recorded that the same session token appeared from different client addresses. The event references principal-961620617e88f850. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-50393256c8e7 accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Directory audit on LEGAL-ASSET-e41057b50163ec62 recorded that a principal requested directory replication data. The event references principal-27103a43ea428bc2. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"File audit on PEOPLE-ASSET-df8464b337d342a5 recorded that a process deleted many files within a short interval. The event references principal-f13400db0397fece. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Event service audit on PEOPLE-ASSET-3e7af42f465f079f recorded that an event log was cleared by a privileged request. The event references principal-7e44d019c9f83317. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-49d281fc1c3c, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Service audit on COMMUNICATIONS-ASSET-7e54b0ca38e553fe recorded that a new automatically started service was registered. The event references principal-7d549ca6bce506ce. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Key service audit on ENGINEERING-ASSET-a77dccd54b04aa48 recorded that a principal issued a burst of key-service decrypt requests. The event references principal-627115d6ce1d6169. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-ded893ef2d9a explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Package registry audit on OPERATIONS-ASSET-b20136404dfc240b recorded that a principal published a new package version. The event references principal-97ed055b6e1a57e6. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-3c87bebd62b4 explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Vpn audit on LEGAL-ASSET-89bfbe721ce26047 recorded that a remote-access VPN session was established. The event references principal-2ac6b6b7ff50c84a. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Application audit on SALES-ASSET-9a8acf9f0cbf6165 recorded that an application read clipboard contents repeatedly. The event references principal-114c22ed14b6a3d7. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Kubernetes audit on LEGAL-ASSET-3c1eaaf59969b766 recorded that a workload mounted a directory from its host filesystem. The event references principal-a5edc19c7aca724f. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"File audit on SALES-ASSET-8fef53d84dc3e73f recorded that a process deleted many files within a short interval. The event references principal-1dec5bfe36cba361. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Assessment SEC-4b9c9c9cf569 explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Compute audit on LEGAL-ASSET-4cc59a71aa46b3a9 recorded that a principal launched multiple compute instances. The event references principal-662e807a43fa7c2b. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-a7ad9d6d2fbc match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Package registry audit on COMMUNICATIONS-ASSET-7fd940c9dbda3462 recorded that a principal published a new package version. The event references principal-07091e1d888fa67d. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Mail audit on SALES-ASSET-bd6fcb0d83d6d9d8 recorded that an account received delegated access to a mailbox. The event references principal-44c7b65ec7f1b04b. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Process access audit on LEGAL-ASSET-60fd34b6e0203a0f recorded that a process requested read access to another process memory space. The event references principal-1e4fdc2f020fb533. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-b4b7c3895d8c specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Kubernetes audit on PEOPLE-ASSET-95c9822ffcf4a444 recorded that a cluster admission policy was changed. The event references principal-e51b094fe6b69872. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Mail and proxy logs on SUPPORT-ASSET-79dbee71e86c40be recorded that a user opened a URL delivered in an email message. The event references principal-1603764c68a231e0. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-ff5c235103eb match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Package registry audit on RESEARCH-ASSET-b42ad559dc38cada recorded that a principal published a new package version. The event references principal-ae25582585615c9e. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Ssh audit on RESEARCH-ASSET-a4cfbeae0c987bb8 recorded that an SSH session opened and requested elevated command execution. The event references principal-f224386eb3a1c8ae. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Firewall audit on ENGINEERING-ASSET-4346eb459a11971a recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-62f6e1ae625e9e27. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-329131c1f97a, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Network control audit on ENGINEERING-ASSET-2d4a799851b7227b recorded that a cloud security group gained a broad ingress rule. The event references principal-5b7cb16d420fdcdc. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Mail audit on RESEARCH-ASSET-0a4e5d836144a737 recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-3b98b2ee8f80fa29. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Mail audit on RESEARCH-ASSET-0a4e5d836144a737 recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-3b98b2ee8f80fa29. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Assessment SEC-021bb3123f73 explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Mail audit on LEGAL-ASSET-2836d47d3aa0d5af recorded that an account received delegated access to a mailbox. The event references principal-e1699b7a3eeb56fc. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-4a9a13f802d8 match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Service audit on SUPPORT-ASSET-bed8c4ced0655fc1 recorded that a remote service-control request created and started a temporary service. The event references principal-74bec1dcad5113eb. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Macos launch audit on OPERATIONS-ASSET-26bdf3f25161f2be recorded that a launch agent definition was installed in a user context. The event references principal-707a961a9c8924fd. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Change CHG-5e747af4f14d lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Service audit on SUPPORT-ASSET-bed8c4ced0655fc1 recorded that a remote service-control request created and started a temporary service. The event references principal-74bec1dcad5113eb. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Device and file audit on PEOPLE-ASSET-6b2be688c0738ea2 recorded that files were copied to a removable storage device. The event references principal-cb796dfd2a52dfa6. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"File audit on PROCUREMENT-ASSET-de47614145685908 recorded that a shell startup profile gained an additional command. The event references principal-602bb5bc7aad1155. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-f26448347623, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Smb audit on RESEARCH-ASSET-130b1b37c48e2c18 recorded that a session enumerated a file share and read multiple files. The event references principal-143930e21a998c01. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Security retest SEC-e158a5ccd9e6 covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Federation audit on FINANCE-ASSET-834ce73eb8e2d5f1 recorded that a tenant federation setting was updated. The event references principal-b4c9940f6c199e33. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Agent audit on SALES-ASSET-4f0c6ee9e7bb90ab recorded that a privileged session changed endpoint monitoring settings. The event references principal-b547aa127479e0eb. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Proxy logs on PROCUREMENT-ASSET-a90cefc8840eb875 recorded that a client transferred a large payload to an external storage endpoint. The event references principal-58357f3106f790fd. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Application audit on ENGINEERING-ASSET-83152a55ea1c27b8 recorded that an application read clipboard contents repeatedly. The event references principal-d08677bd055caebe. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Policy audit on FINANCE-ASSET-e464a7dfab1a5a08 recorded that an audit policy was changed to collect fewer event categories. The event references principal-88be6dc1340765a4. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-2c504e5aed3f before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"File audit on OPERATIONS-ASSET-aa398735111975aa recorded that a process deleted many files within a short interval. The event references principal-ff0116df6d90824b. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-1411f03ebbf1 explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Dhcp telemetry on PROCUREMENT-ASSET-40822febba29ea21 recorded that a server issued DHCP offers on a monitored segment. The event references principal-140fc1a13a173a5d. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-b24e2fbed3da match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Process audit on LEGAL-ASSET-523d2840aded9f3a recorded that a remote-support application started an interactive session. The event references principal-d733a0ecd691110d. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-cdbf29e6de41 match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Identity audit on OPERATIONS-ASSET-71fc600bd08a667f recorded that an account registered a new MFA method. The event references principal-717e0b47f1247c8b. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"File audit on RESEARCH-ASSET-e98c7e7ef8b5bfbe recorded that a process rewrote multiple files into encrypted containers. The event references principal-b60fe0e57ed46b9d. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-916f92af06bc specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Group audit on PEOPLE-ASSET-f5ce370c9062d00a recorded that an account was added to a privileged local group. The event references principal-a4fe590d9388b8ea. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Security retest SEC-c7bf292129fd covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Kubernetes audit on ENGINEERING-ASSET-03ff797dc0608058 recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-84d60009e20971fc. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Identity audit on PROCUREMENT-ASSET-3df9ef7ebe927a33 recorded that an account registered a new MFA method. The event references principal-8231b7a1d02ca56c. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Secret manager audit on PEOPLE-ASSET-406b99330a23361c recorded that a workload read several secret versions. The event references principal-c3699eaad53ba8ba. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"File audit on RESEARCH-ASSET-29f4cb3c7a29beaf recorded that access permissions were broadened on a directory tree. The event references principal-9b108c0888253ab1. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Runtime audit on COMMUNICATIONS-ASSET-da48b46f34e4599d recorded that a process connected to the container runtime socket. The event references principal-3deaf11c55ba9307. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Gateway logs on PROCUREMENT-ASSET-b0d37645a10d287b recorded that a client established a long-lived encapsulated network session. The event references principal-1cc47c7a352875b2. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Flow logs on LEGAL-ASSET-bb14ef480a9f5aa0 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-343b8b6d62a9710b. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-0b0992a46df5 match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Pki audit on PEOPLE-ASSET-3dbf336f859282fe recorded that a principal requested a certificate using an authentication template. The event references principal-bc62db6b4c821f23. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Cron audit on FINANCE-ASSET-3836d6a68d057960 recorded that a recurring job definition was added to the system schedule. The event references principal-c8b819a1d7d4650c. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Configuration audit on SUPPORT-ASSET-75f85e5b495f1222 recorded that a client proxy setting was changed. The event references principal-02061922c2bafcd3. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Proxy logs on RESEARCH-ASSET-2d6466dd3f8c1f6b recorded that a client transferred a large payload to an external storage endpoint. The event references principal-136b3bcae45dcdcd. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Storage audit on RESEARCH-ASSET-6e2b243ec7d7a919 recorded that an object-storage access policy was broadened. The event references principal-262db57bffaea9f7. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Cloud identity audit on ENGINEERING-ASSET-02b155235f1959ea recorded that a principal received a policy granting additional permissions. The event references principal-d5dc51acc5293d03. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Network control audit on PEOPLE-ASSET-30b5158319199c4f recorded that a cloud security group gained a broad ingress rule. The event references principal-4d55ccd8cef6e438. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"File audit on SALES-ASSET-f998f822d677efcd recorded that a process rewrote multiple files into encrypted containers. The event references principal-354f7ba2d1c31de7. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Oauth audit on SALES-ASSET-8a294b7f6b4fb5ec recorded that an application received consent for additional account scopes. The event references principal-4be7952cadd1c600. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Account audit on OPERATIONS-ASSET-ad56fc4183b7ca9d recorded that a local user account was created on a managed system. The event references principal-fe2941e164dbf1c4. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Device and file audit on RESEARCH-ASSET-6da8ae6d7bfc1fd2 recorded that files were copied to a removable storage device. The event references principal-6e75da4e311027c4. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Repository audit on PEOPLE-ASSET-e8dfe6d75dbb8e1e recorded that a user cloned several source repositories. The event references principal-e971d955c552fbff. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-4726f754575f match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Script audit on OPERATIONS-ASSET-df5c95ab3d436943 recorded that a script interpreter decoded an encoded argument before execution. The event references principal-d244a19c467082bb. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Kubernetes audit on FINANCE-ASSET-e06cf007729f9dbe recorded that a workload mounted a directory from its host filesystem. The event references principal-76bf38f3f96381c7. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Gateway logs on FINANCE-ASSET-0eba77ccb6dbdba6 recorded that a client established a long-lived encapsulated network session. The event references principal-5f89b733086ddfa5. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Repository audit on FINANCE-ASSET-107bba51318f26e9 recorded that a user cloned several source repositories. The event references principal-f147d2a9dbf7d7a7. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Identity audit on PROCUREMENT-ASSET-b4ae6e9e4fb445a9 recorded that an account password was reset through a recovery workflow. The event references principal-b2c1bc21d87bb7c1. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Storage audit on ENGINEERING-ASSET-cd853382d1a0a281 recorded that a session deleted several storage snapshots. The event references principal-39dd7d8e5cbb8cc6. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Certificate audit on COMMUNICATIONS-ASSET-f4321cc57d6f7080 recorded that a service certificate was replaced. The event references principal-790bc3cf91a2a094. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Macos launch audit on ENGINEERING-ASSET-20d414dac3bf58ed recorded that a launch agent definition was installed in a user context. The event references principal-9f713f5b46efadf7. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Resolver logs on RESEARCH-ASSET-abc39d656b9d30aa recorded that a client requested many long, high-entropy DNS labels. The event references principal-5aebc86024ffc2a8. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Network control audit on PROCUREMENT-ASSET-296ab163f292467f recorded that a cloud security group gained a broad ingress rule. The event references principal-485bf1fa128db935. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Assessment SEC-dd7838ed7efc explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Repository audit on PROCUREMENT-ASSET-032fc4cf1761029e recorded that a repository collaborator received elevated permissions. The event references principal-c9c8d15f73a824e8. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Dhcp telemetry on PROCUREMENT-ASSET-40822febba29ea21 recorded that a server issued DHCP offers on a monitored segment. The event references principal-140fc1a13a173a5d. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Task scheduler audit on SUPPORT-ASSET-fe6538271f60c593 recorded that a scheduled task was registered to execute a program at logon. The event references principal-a844a2602a6529d6. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Office audit on FINANCE-ASSET-611546d095704224 recorded that a document macro launched a child interpreter. The event references principal-07f2af237b2ad540. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"File access audit on SUPPORT-ASSET-701fe361a48ad8d6 recorded that a process opened a local credential-store file. The event references principal-0923914a571f26a3. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Backup audit on RESEARCH-ASSET-d7ec84ee273e258c recorded that a backup retention policy was shortened. The event references principal-46e3d9bc6deb6418. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Identity audit on SUPPORT-ASSET-3fdea2c42e845651 recorded that a service account established an interactive session. The event references principal-6872260152bd6bd7. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Account audit on LEGAL-ASSET-00d4a961cd35ae5d recorded that a local user account was created on a managed system. The event references principal-ffacf4516ce71040. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-896193a1dcc8 specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Storage audit on PEOPLE-ASSET-4b18ae09e42fe01b recorded that an object-storage access policy was broadened. The event references principal-7721904d8c389cbb. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-6a5c131edbe9 specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Kubernetes audit on COMMUNICATIONS-ASSET-4eb386b59cd197fa recorded that a cluster admission policy was changed. The event references principal-6713342ad2d170de. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Change CHG-42ef1b68e5bb lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Mfa audit on PEOPLE-ASSET-e45fffd30cf466e9 recorded that multiple MFA challenges were issued during a short interval. The event references principal-3cbfe5aa85664020. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Key service audit on FINANCE-ASSET-57ca74510903ebd4 recorded that a principal issued a burst of key-service decrypt requests. The event references principal-79b7e5a3aa2edd24. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Mfa audit on COMMUNICATIONS-ASSET-ce18db2b3211944f recorded that multiple MFA challenges were issued during a short interval. The event references principal-5c71c8caf74a8fa1. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Identity audit on FINANCE-ASSET-8c4f9dd18c643b5e recorded that repeated failed sign-ins were recorded for an account. The event references principal-e15b307c4e5bf156. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Process audit on ENGINEERING-ASSET-254e39c6de0e65b8 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-b4a1f0cd4cef32ed. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Task scheduler audit on FINANCE-ASSET-ee3bbbf183a6aaf2 recorded that a scheduled task was registered to execute a program at logon. The event references principal-6b358d24fc67440c. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Group audit on COMMUNICATIONS-ASSET-c7bad2289a06229c recorded that an account was added to a privileged local group. The event references principal-45633364c2ed091b. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Runtime audit on RESEARCH-ASSET-1fdd4c74894a8860 recorded that a process connected to the container runtime socket. The event references principal-1fe12f7544607ca6. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Ci audit on LEGAL-ASSET-307a1ab2be77fe5f recorded that a build pipeline definition gained a new execution step. The event references principal-362aa0b8c3b22688. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Identity audit on PROCUREMENT-ASSET-b4ae6e9e4fb445a9 recorded that an account password was reset through a recovery workflow. The event references principal-b2c1bc21d87bb7c1. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"File audit on PROCUREMENT-ASSET-5c83620233b8b110 recorded that a process deleted many files within a short interval. The event references principal-eb86b20544a85de9. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-cf813f421a48 accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Group audit on PEOPLE-ASSET-f5ce370c9062d00a recorded that an account was added to a privileged local group. The event references principal-a4fe590d9388b8ea. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Cloud control audit on RESEARCH-ASSET-2cbe7527ba09f822 recorded that resources were created in a region with little prior activity. The event references principal-3490db46f4cacc07. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Cloud control audit on RESEARCH-ASSET-2bdeaeb6bfb8b9b8 recorded that a cloud logging destination was disabled. The event references principal-00477aa276d23b17. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Pki audit on OPERATIONS-ASSET-075517e7328277d9 recorded that a principal requested a certificate using an authentication template. The event references principal-c9b353c364fde4c3. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-d6828c1ea27c match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Ssh audit on SUPPORT-ASSET-842f8e08ea10f95b recorded that an SSH session opened and requested elevated command execution. The event references principal-3779cc64299d1a95. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Key service audit on ENGINEERING-ASSET-a77dccd54b04aa48 recorded that a principal issued a burst of key-service decrypt requests. The event references principal-627115d6ce1d6169. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Mail and proxy logs on COMMUNICATIONS-ASSET-48a9f26bd10054b4 recorded that a user opened a URL delivered in an email message. The event references principal-0e84a6c758769248. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Smb audit on SALES-ASSET-f9e0160f65640ecb recorded that a session enumerated a file share and read multiple files. The event references principal-5b93bfe2ff3ce2df. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Identity audit on COMMUNICATIONS-ASSET-cdebef5d9dc25fc4 recorded that a service account established an interactive session. The event references principal-ecbde67b88dd7d93. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-bebfff361ebf specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Cloud control audit on PROCUREMENT-ASSET-1ca061884feb0239 recorded that a session deleted a group of cloud resources. The event references principal-bde2c278c233490d. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Application audit on SALES-ASSET-9a8acf9f0cbf6165 recorded that an application read clipboard contents repeatedly. The event references principal-114c22ed14b6a3d7. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-cce14d23c2d9 accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Certificate audit on COMMUNICATIONS-ASSET-f4321cc57d6f7080 recorded that a service certificate was replaced. The event references principal-790bc3cf91a2a094. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Kubernetes audit on LEGAL-ASSET-82e9dc780e2f0fb0 recorded that a pod was created with privileged execution enabled. The event references principal-7d1067f1bf4b8bd0. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-c21babb0ee65 specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Database audit on FINANCE-ASSET-7b5f1daa45ffd071 recorded that a session changed a database table definition. The event references principal-eec005bb1596cf1c. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Change CHG-9d822db8d5d7 lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Office audit on LEGAL-ASSET-7baa0b7a7bcbd13a recorded that a document macro launched a child interpreter. The event references principal-4d965a283abc96ce. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Repository audit on RESEARCH-ASSET-ddfa89ff412603e8 recorded that a user cloned several source repositories. The event references principal-a086fb65d451cd31. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-704824135431 explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Device and file audit on FINANCE-ASSET-95133e3350d50213 recorded that files were copied to a removable storage device. The event references principal-3a08b3fa9560c2b5. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Backup audit on ENGINEERING-ASSET-e13f2ff83c899d5b recorded that a backup retention policy was shortened. The event references principal-31afc311e47df634. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Egress flow logs on OPERATIONS-ASSET-2513c8d77423854c recorded that a workload opened an encrypted connection to an external service. The event references principal-ec2152640ea901f5. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Code integrity audit on PROCUREMENT-ASSET-3f90b9195fa39dc7 recorded that an executable without a publisher signature started from a writable directory. The event references principal-f1b547470e053c8b. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Cron audit on ENGINEERING-ASSET-0d57cc07ded38310 recorded that a recurring job definition was added to the system schedule. The event references principal-db05c7bee0f112c7. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Browser audit on OPERATIONS-ASSET-1696f264e915fdf5 recorded that a browser extension with page-reading permissions was installed. The event references principal-f101b193c2f738a3. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Office audit on SUPPORT-ASSET-b861b71047f83874 recorded that a document macro launched a child interpreter. The event references principal-41f626db101e0b15. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Gateway logs on PROCUREMENT-ASSET-b0d37645a10d287b recorded that a client established a long-lived encapsulated network session. The event references principal-1cc47c7a352875b2. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Proxy logs on SUPPORT-ASSET-eadf40ef6aff627a recorded that a client transferred a large payload to an external storage endpoint. The event references principal-77e382cc165fce08. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Backup audit on PROCUREMENT-ASSET-8055bd5873ef3941 recorded that a backup retention policy was shortened. The event references principal-ab63e55288bca196. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-94e5889ec9ed match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Cloud control audit on LEGAL-ASSET-428365c6643172ec recorded that a cloud logging destination was disabled. The event references principal-5fcf49df98dad6ed. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Cloud control audit on LEGAL-ASSET-152843552545f6c2 recorded that a session deleted a group of cloud resources. The event references principal-441348e944e96c5c. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Module audit on PEOPLE-ASSET-4e7e86d1ce25eca1 recorded that a process loaded a library from an application-local directory. The event references principal-32a2611884a3eb03. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Mail flow logs on PEOPLE-ASSET-9ba2c53dc33b0530 recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-5b015560df1e299f. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Key service audit on PEOPLE-ASSET-51157cbfcf0e7f8b recorded that a principal issued a burst of key-service decrypt requests. The event references principal-8c512aac8f2c3631. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Wmi audit on PROCUREMENT-ASSET-fda18a4350cff1b3 recorded that a management request started a process through WMI. The event references principal-cba091012017387e. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Service audit on LEGAL-ASSET-c576aa1679d54c28 recorded that a new automatically started service was registered. The event references principal-7b1165f4385ce850. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Assessment SEC-9acb38da322f explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Runtime audit on ENGINEERING-ASSET-275c1751b3b56ff6 recorded that a process connected to the container runtime socket. The event references principal-560134bf0a39e092. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Service audit on SALES-ASSET-ee4f4ed67afc3eae recorded that a new automatically started service was registered. The event references principal-ae21c97b6a858bb0. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Certificate audit on LEGAL-ASSET-028cc6c15478424c recorded that a service certificate was replaced. The event references principal-ab2a10d3b09a07d5. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-9e81ade63526 explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Certificate audit on FINANCE-ASSET-e16767dd715979b6 recorded that a service certificate was replaced. The event references principal-f8a1311de5964c87. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Mfa audit on RESEARCH-ASSET-900be36a816445ab recorded that multiple MFA challenges were issued during a short interval. The event references principal-fdb4d3be95b990c6. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Driver audit on SALES-ASSET-74116b6362e956da recorded that a kernel driver was loaded after a package installation. The event references principal-9eaf8c722428f29b. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Kubernetes audit on SUPPORT-ASSET-95dbeaaf93770ec1 recorded that a role binding granted a principal additional cluster permissions. The event references principal-fae5a1331ea1b683. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Runtime audit on OPERATIONS-ASSET-b6b114583f048adf recorded that a process connected to the container runtime socket. The event references principal-2a53a47b4b50aacf. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-6dc1dce0e28e match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Identity audit on SALES-ASSET-08c0f29601b74bfa recorded that an account registered a new MFA method. The event references principal-4c8bc42872a0ca65. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Flow logs on SALES-ASSET-60c136594edf1098 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-a5e562da0b238c72. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Key service audit on SALES-ASSET-4796409e71ec7ec0 recorded that a principal issued a burst of key-service decrypt requests. The event references principal-e868bdfcec891314. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Change CHG-3172b3f5e4dc lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"File access audit on SUPPORT-ASSET-701fe361a48ad8d6 recorded that a process opened a local credential-store file. The event references principal-0923914a571f26a3. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Switch telemetry on COMMUNICATIONS-ASSET-bcb43f0616b1a470 recorded that an address mapping changed repeatedly on a local segment. The event references principal-ea5a7f0eef9db0e7. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Session audit on OPERATIONS-ASSET-650805187004af92 recorded that the same session token appeared from different client addresses. The event references principal-fe1f7195dd801273. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Office audit on PEOPLE-ASSET-d75bb0ba4ef1bfaf recorded that a document macro launched a child interpreter. The event references principal-882202a717331e69. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Windows logon audit on OPERATIONS-ASSET-4a019c17c7542e6c recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-dd10cd046f3074f7. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Firewall audit on PEOPLE-ASSET-957a449c8e927512 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-3d550d011d922017. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Script audit on ENGINEERING-ASSET-e2ddc97a2c3f555e recorded that a script interpreter decoded an encoded argument before execution. The event references principal-f5db620bfae68583. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Windows logon audit on RESEARCH-ASSET-fcc9667f845ac430 recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-af2356cb5701209c. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Key service audit on SUPPORT-ASSET-32d985d5324796c4 recorded that a principal issued a burst of key-service decrypt requests. The event references principal-82b70d458957b545. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Dns control audit on PROCUREMENT-ASSET-a2a68c2dd932f661 recorded that an authoritative DNS record was updated. The event references principal-d6b239df277e509a. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Certificate audit on COMMUNICATIONS-ASSET-f4321cc57d6f7080 recorded that a service certificate was replaced. The event references principal-790bc3cf91a2a094. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-c03a8230e3f7 explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Mail audit on ENGINEERING-ASSET-784f3c782f3ac855 recorded that an account received delegated access to a mailbox. The event references principal-2080f4d9197e7c3e. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Secret manager audit on PEOPLE-ASSET-406b99330a23361c recorded that a workload read several secret versions. The event references principal-c3699eaad53ba8ba. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-3d775aaef186, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Storage audit on ENGINEERING-ASSET-b38bdd9cc61bbac2 recorded that an object-storage access policy was broadened. The event references principal-8585f4d7b4e61651. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Driver audit on FINANCE-ASSET-4d3885b7e2a2eaaa recorded that a kernel driver was loaded after a package installation. The event references principal-93dddd296bcd4a0a. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Vpn audit on SALES-ASSET-09dd168451b4fb60 recorded that a remote-access VPN session was established. The event references principal-732980774243feef. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-da0b9c7fa7b2 accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Account audit on SUPPORT-ASSET-4f664bc059385d17 recorded that a local user account was created on a managed system. The event references principal-1db165dfba5895ba. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Mfa audit on FINANCE-ASSET-77a6969db5ae1147 recorded that multiple MFA challenges were issued during a short interval. The event references principal-660a5b1395e78ef7. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Device and file audit on PROCUREMENT-ASSET-804fb2eb4bbf7ddf recorded that files were copied to a removable storage device. The event references principal-25d93f161d21c79f. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Process audit on PEOPLE-ASSET-2c32b67a1236291b recorded that a remote-support application started an interactive session. The event references principal-3d51474c05227a94. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Assessment SEC-9cd07794a880 explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Flow logs on PEOPLE-ASSET-747d1cebe72c1281 recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-d7e614d288290a88. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Cloud identity audit on OPERATIONS-ASSET-04350815f02c233e recorded that a new programmatic access key was issued to a principal. The event references principal-3f0b6fed7f9bbd92. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Task scheduler audit on SUPPORT-ASSET-fe6538271f60c593 recorded that a scheduled task was registered to execute a program at logon. The event references principal-a844a2602a6529d6. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Secret manager audit on LEGAL-ASSET-473919a6141fb4d1 recorded that a workload read several secret versions. The event references principal-be429b8818a2a6bf. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Gateway logs on OPERATIONS-ASSET-7599af3c268c4876 recorded that a client established a long-lived encapsulated network session. The event references principal-ba0168660aabc1f0. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Module audit on SUPPORT-ASSET-75579d877216839e recorded that a process loaded a library from an application-local directory. The event references principal-bf9534edb641c536. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Change CHG-3cab5fb4058d lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Kerberos audit on PEOPLE-ASSET-4ee9a55c8fd9d93a recorded that an account requested service tickets for multiple services. The event references principal-0978a46d6664fc2a. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Proxy logs on FINANCE-ASSET-f9b86d6f6b974e8f recorded that a client transferred a large payload to an external storage endpoint. The event references principal-252b9a9159e9be98. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Ssh audit on LEGAL-ASSET-97358e826a1337d7 recorded that an SSH session opened and requested elevated command execution. The event references principal-713d0f7027f2d117. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Proxy logs on PEOPLE-ASSET-47b1cfa33ae643a0 recorded that a client transferred a large payload to an external storage endpoint. The event references principal-eefc70a315bcfb3b. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Code integrity audit on PROCUREMENT-ASSET-3f90b9195fa39dc7 recorded that an executable without a publisher signature started from a writable directory. The event references principal-f1b547470e053c8b. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-b54e9f76caef match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Saas audit on PROCUREMENT-ASSET-94508e8090c4e3fa recorded that a user requested a bulk export from a business application. The event references principal-d0cfd5ec7d96061d. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Event service audit on PROCUREMENT-ASSET-1656ac96cf7e6b6f recorded that an event log was cleared by a privileged request. The event references principal-994f7078cfaa2558. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Key service audit on PROCUREMENT-ASSET-97184c5c539ee822 recorded that a principal issued a burst of key-service decrypt requests. The event references principal-d47010910e744f5c. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Kerberos audit on SUPPORT-ASSET-cee89b8c79f8f807 recorded that an account requested service tickets for multiple services. The event references principal-ba01468b28096ded. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Identity audit on SALES-ASSET-2f253fe8393025e1 recorded that an account password was reset through a recovery workflow. The event references principal-95366adc4199c0a7. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Share audit on SUPPORT-ASSET-642a0478e0fea4be recorded that a new network file share was published. The event references principal-d39d2cce091886dd. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"File audit on SUPPORT-ASSET-96c72864072032c8 recorded that a process deleted many files within a short interval. The event references principal-7a907f6a20c3a4ff. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Compute audit on SALES-ASSET-4b3abc50600feeb3 recorded that a principal launched multiple compute instances. The event references principal-a87c3d065d8ee0b1. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Repository audit on LEGAL-ASSET-d4c7f3d667dee146 recorded that a user cloned several source repositories. The event references principal-0ab147f1f9481604. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Cloud control audit on SALES-ASSET-5ed8420ac6bfabb9 recorded that a session deleted a group of cloud resources. The event references principal-e108fb64fd38558b. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Cloud control audit on SALES-ASSET-bfb02fef7d44a1a0 recorded that a cloud logging destination was disabled. The event references principal-cabdd3811f019647. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Identity audit on ENGINEERING-ASSET-17f1d906d8c35962 recorded that a service account established an interactive session. The event references principal-4e2ae7344e474fce. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Certificate audit on COMMUNICATIONS-ASSET-f4321cc57d6f7080 recorded that a service certificate was replaced. The event references principal-790bc3cf91a2a094. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Change CHG-c03a8230e3f7 lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Identity audit on RESEARCH-ASSET-855e969e96eb06ea recorded that an account password was reset through a recovery workflow. The event references principal-811400d02da15e41. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-242ca9ec4188, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Application audit on PEOPLE-ASSET-fcad7cf3be4e4115 recorded that a runtime configuration setting was updated. The event references principal-1c596d52504e0c0f. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-33992d4d43f9 specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Process audit on ENGINEERING-ASSET-b8d24c4e39635b0b recorded that a Python interpreter loaded a script and contacted a service. The event references principal-59e5008660f946a5. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-86c7139b136c accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Package registry audit on OPERATIONS-ASSET-b20136404dfc240b recorded that a principal published a new package version. The event references principal-97ed055b6e1a57e6. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Switch telemetry on OPERATIONS-ASSET-30a277f008dd59f9 recorded that an address mapping changed repeatedly on a local segment. The event references principal-f95a18784ccda07e. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Process audit on RESEARCH-ASSET-a06368c20e1f1761 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-c27d38810eca0fcd. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Pki audit on RESEARCH-ASSET-5892d31dbb5ae49e recorded that a principal requested a certificate using an authentication template. The event references principal-5044ec496f46d2cd. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Mfa audit on FINANCE-ASSET-77a6969db5ae1147 recorded that multiple MFA challenges were issued during a short interval. The event references principal-660a5b1395e78ef7. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-40574d3299a4 match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Device and file audit on OPERATIONS-ASSET-e188a7d05dfbf7ee recorded that files were copied to a removable storage device. The event references principal-4cd6803b897580b7. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-ad228d0094d2, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Kubernetes audit on FINANCE-ASSET-8c8a0667d1ab346c recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-8cde8f18db765ef8. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-f8cb3bcf80f0 match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Mfa audit on COMMUNICATIONS-ASSET-ce18db2b3211944f recorded that multiple MFA challenges were issued during a short interval. The event references principal-5c71c8caf74a8fa1. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Change CHG-ff52d6dc5801 lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Cron audit on SALES-ASSET-34715d088f9c8c11 recorded that a recurring job definition was added to the system schedule. The event references principal-69300e7147cdfbd9. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Identity audit on ENGINEERING-ASSET-ce4355624d538400 recorded that an account password was reset through a recovery workflow. The event references principal-8d13b23a4098f36d. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Egress flow logs on PROCUREMENT-ASSET-dec31bc9d60afefc recorded that a workload opened an encrypted connection to an external service. The event references principal-552eff98281f8ed1. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Mail audit on ENGINEERING-ASSET-784f3c782f3ac855 recorded that an account received delegated access to a mailbox. The event references principal-2080f4d9197e7c3e. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-4dbfd768c1f2 match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"File audit on OPERATIONS-ASSET-53ad24c9deb5d645 recorded that a shell startup profile gained an additional command. The event references principal-6049aaff0c8fe538. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"File audit on PEOPLE-ASSET-2821cb52cece6fb9 recorded that a shell startup profile gained an additional command. The event references principal-6665fccc697a255b. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-213f4b894287 explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Storage audit on LEGAL-ASSET-2e9a3d1f59ced5f4 recorded that an object-storage access policy was broadened. The event references principal-aece214cd9523226. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Policy audit on LEGAL-ASSET-fdcb7612a4f13f67 recorded that an audit policy was changed to collect fewer event categories. The event references principal-3d26eee8b88bfb17. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Waf logs on PEOPLE-ASSET-b68587853256629c recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-a0a816963fae146a. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Process audit on COMMUNICATIONS-ASSET-3540d4ca6c64eb07 recorded that a remote-support application started an interactive session. The event references principal-e3fe7b2bae9cee75. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Dns control audit on COMMUNICATIONS-ASSET-9ae5b908b35b63ef recorded that an authoritative DNS record was updated. The event references principal-b17631352023456c. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Identity audit on COMMUNICATIONS-ASSET-ae1258c834d83e6f recorded that an account password was reset through a recovery workflow. The event references principal-98f97f4d1c43e756. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Flow logs on SALES-ASSET-60c136594edf1098 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-a5e562da0b238c72. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Policy audit on ENGINEERING-ASSET-691918f61c7ec7b2 recorded that an audit policy was changed to collect fewer event categories. The event references principal-86d0e35aa5d8e487. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-13d4083175bf before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Federation audit on FINANCE-ASSET-834ce73eb8e2d5f1 recorded that a tenant federation setting was updated. The event references principal-b4c9940f6c199e33. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-d7bed0598eb7 specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Proxy logs on SUPPORT-ASSET-eadf40ef6aff627a recorded that a client transferred a large payload to an external storage endpoint. The event references principal-77e382cc165fce08. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Resolver logs on OPERATIONS-ASSET-5135623224ddfa0b recorded that a client requested many long, high-entropy DNS labels. The event references principal-4817944b772fb8eb. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Service audit on ENGINEERING-ASSET-5be63ef6d4ef079d recorded that a remote service-control request created and started a temporary service. The event references principal-bd2813d9252e7fbb. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Dns server audit on LEGAL-ASSET-9a776b98cec96a9e recorded that a client requested a DNS zone transfer. The event references principal-b7047a9785be46d4. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Change CHG-007e0c335ceb lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Kubernetes audit on SALES-ASSET-ffd4e9bc10275050 recorded that a pod was created with privileged execution enabled. The event references principal-02bcfaa51dffcded. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Office audit on LEGAL-ASSET-7baa0b7a7bcbd13a recorded that a document macro launched a child interpreter. The event references principal-4d965a283abc96ce. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Dns control audit on FINANCE-ASSET-84a7d1044449f1a8 recorded that an authoritative DNS record was updated. The event references principal-f7395e7a5d189597. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Waf logs on LEGAL-ASSET-558884e90876ee10 recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-3ea85690224829da. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Systemd audit on COMMUNICATIONS-ASSET-83d44af530d70e5a recorded that a service unit file was changed and the unit reloaded. The event references principal-fef91c85181668d1. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-5df54cd4592a specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Registry audit on SALES-ASSET-2cd7195afaa340c4 recorded that a registry logon-start entry was created. The event references principal-4dafe2d9d91101fd. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Application audit on OPERATIONS-ASSET-09e59732382536e3 recorded that an application requested repeated screen captures. The event references principal-a45fb9f4a0a7c7be. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Directory audit on ENGINEERING-ASSET-74de670cde6f3c91 recorded that a principal requested directory replication data. The event references principal-2491cc3af8b17009. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Identity audit on PEOPLE-ASSET-5f5eb7d500371474 recorded that an account registered a new MFA method. The event references principal-7c9584053a66a813. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Federation audit on LEGAL-ASSET-81a8982089dddbeb recorded that a tenant federation setting was updated. The event references principal-c29fe59344f3b4d5. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Repository audit on COMMUNICATIONS-ASSET-fc7d932dec68a3a4 recorded that a user cloned several source repositories. The event references principal-f9163c8da3ccc09a. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Office audit on PEOPLE-ASSET-d75bb0ba4ef1bfaf recorded that a document macro launched a child interpreter. The event references principal-882202a717331e69. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-c0aeb06e72fd specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Directory audit on SUPPORT-ASSET-657351ecbd6ea04f recorded that a principal requested directory replication data. The event references principal-415e143ac445aa25. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Mail flow logs on PROCUREMENT-ASSET-992b1e99dffe114d recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-ffd659ab57383ff2. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Flow logs on SUPPORT-ASSET-103a412104563dae recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-a1ca47883deef1d3. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Process audit on SUPPORT-ASSET-6a54632d13cc3523 recorded that a JavaScript interpreter executed a local script. The event references principal-5989897ff7bc53ab. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Ci secret audit on LEGAL-ASSET-210117fa7f63e7fa recorded that a build job requested a protected pipeline secret. The event references principal-bafb03e4143599bb. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Identity audit on ENGINEERING-ASSET-ce4355624d538400 recorded that an account password was reset through a recovery workflow. The event references principal-8d13b23a4098f36d. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Registry audit on PEOPLE-ASSET-493d3bd95ab44b29 recorded that a registry logon-start entry was created. The event references principal-b4c380fe3bd5d692. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-0fd356e7c337 explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Runtime audit on SALES-ASSET-65e80c7b6f9129ee recorded that a process connected to the container runtime socket. The event references principal-e74aec44693d5ee6. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Kubernetes audit on SALES-ASSET-3af15ceafaf37a50 recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-4e40a79e1d1cac1f. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Repository audit on OPERATIONS-ASSET-d75290e6ed1a6d85 recorded that a repository collaborator received elevated permissions. The event references principal-b26cea051978a58c. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-abae77a7202e explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Pki audit on PROCUREMENT-ASSET-4fa9108f30037594 recorded that a principal requested a certificate using an authentication template. The event references principal-7c9716b1c94aea0e. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Cloud control audit on OPERATIONS-ASSET-ba4ce4cf529ac35c recorded that a session deleted a group of cloud resources. The event references principal-2a7a606b1116d324. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Kubernetes audit on ENGINEERING-ASSET-893d9de1f805e218 recorded that a cluster admission policy was changed. The event references principal-63fff86ce57d7e9d. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-715af2fa1178 match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Group audit on SUPPORT-ASSET-32af0f049b4169a7 recorded that an account was added to a privileged local group. The event references principal-b75a2d708106954b. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Key service audit on RESEARCH-ASSET-fa35f918dce61e29 recorded that a principal issued a burst of key-service decrypt requests. The event references principal-139260250781ca0e. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Assessment SEC-c4bb7faa6a50 explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Switch telemetry on RESEARCH-ASSET-39ecead5bf809d8c recorded that an address mapping changed repeatedly on a local segment. The event references principal-78520d727e00f06a. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Cloud identity audit on LEGAL-ASSET-a018d5a0c035a322 recorded that a principal received a policy granting additional permissions. The event references principal-e37ce5811af67681. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-147c915a5591 match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Identity audit on SUPPORT-ASSET-15695a645557b69f recorded that repeated failed sign-ins were recorded for an account. The event references principal-51d00d36a920ed83. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-0475eea1e04d accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"File audit on RESEARCH-ASSET-e98c7e7ef8b5bfbe recorded that a process rewrote multiple files into encrypted containers. The event references principal-b60fe0e57ed46b9d. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Firewall audit on OPERATIONS-ASSET-f066243659fb5412 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-9b3165faa785f1a5. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Cloud identity audit on FINANCE-ASSET-44723c4a98b3d8ba recorded that a principal received a policy granting additional permissions. The event references principal-ddbfe461888a8cb6. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Script audit on SUPPORT-ASSET-1db9fff8dffdd6e2 recorded that a script interpreter decoded an encoded argument before execution. The event references principal-cddc3f00bf167947. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Configuration audit on PROCUREMENT-ASSET-8aac493103d32947 recorded that a client proxy setting was changed. The event references principal-5ba8d1fc71029290. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Registry audit on RESEARCH-ASSET-73e0cbd02049afd1 recorded that a workload pulled a container image from a registry. The event references principal-34d7877cf1ae898f. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Assessment SEC-f3348301fd45 explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Registry audit on LEGAL-ASSET-d0480e188fd31f60 recorded that a workload pulled a container image from a registry. The event references principal-160b2d0cefee47e2. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Event service audit on LEGAL-ASSET-1725494bd06479c8 recorded that an event log was cleared by a privileged request. The event references principal-2d006b9d45394524. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Identity audit on PROCUREMENT-ASSET-3df9ef7ebe927a33 recorded that an account registered a new MFA method. The event references principal-8231b7a1d02ca56c. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Storage access logs on PEOPLE-ASSET-c7aae9977fa123ac recorded that a principal downloaded many objects from a storage bucket. The event references principal-8d5cca2185bede9c. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Runtime audit on COMMUNICATIONS-ASSET-da48b46f34e4599d recorded that a process connected to the container runtime socket. The event references principal-3deaf11c55ba9307. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"File audit on SALES-ASSET-8fef53d84dc3e73f recorded that a process deleted many files within a short interval. The event references principal-1dec5bfe36cba361. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Secret manager audit on ENGINEERING-ASSET-c96b6e8c112e5ab0 recorded that a workload read several secret versions. The event references principal-24b9130cfaf6e9ca. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Event service audit on PROCUREMENT-ASSET-1656ac96cf7e6b6f recorded that an event log was cleared by a privileged request. The event references principal-994f7078cfaa2558. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-4d88ef476f7b accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Kubernetes audit on RESEARCH-ASSET-e5b9e413bdef9d8d recorded that a pod was created with privileged execution enabled. The event references principal-74b8c2bcccc76ba0. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"File audit on ENGINEERING-ASSET-b0203944931a2946 recorded that a process compressed files from several directories into an archive. The event references principal-c59c85332aba5a32. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Network control audit on FINANCE-ASSET-93401772cf68a3aa recorded that a cloud security group gained a broad ingress rule. The event references principal-b7b99f534a1030f4. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-cdbe2fecad4a before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Database audit on SALES-ASSET-849ddfe1a9053808 recorded that a session changed a database table definition. The event references principal-425b4fae9e8852ef. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-f7c1fff050cc, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Winrm audit on SALES-ASSET-53a0ec06a529813d recorded that a remote management session invoked a command on a managed host. The event references principal-d315b25d4a3677cf. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Script audit on FINANCE-ASSET-8f7a7c5dae3d75b5 recorded that a script interpreter decoded an encoded argument before execution. The event references principal-7a6a17f9162097f1. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Configuration audit on COMMUNICATIONS-ASSET-6d0a4b6d77bc51b5 recorded that a client proxy setting was changed. The event references principal-096d695d5dfbc71f. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Cloud identity audit on COMMUNICATIONS-ASSET-e9dda7a9ac4613e3 recorded that a new programmatic access key was issued to a principal. The event references principal-b50a9e7363974da3. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Winrm audit on RESEARCH-ASSET-35584f0a53bc209b recorded that a remote management session invoked a command on a managed host. The event references principal-7b703d1f8c94aba9. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Cloud control audit on FINANCE-ASSET-b563459bb8af8f48 recorded that a session deleted a group of cloud resources. The event references principal-a8340a0f60620156. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Assessment SEC-d5ee7f1c850d explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Proxy logs on COMMUNICATIONS-ASSET-5a2ac13c8b310540 recorded that a client transferred a large payload to an external storage endpoint. The event references principal-d735b0162330748a. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Registry audit on ENGINEERING-ASSET-bd489c9ae7fbc817 recorded that a workload pulled a container image from a registry. The event references principal-95061e15f3e7bbec. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Change CHG-4ff0a6f52482 lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Kubernetes audit on FINANCE-ASSET-8c8a0667d1ab346c recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-8cde8f18db765ef8. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Cloud control audit on FINANCE-ASSET-874d671033c104d1 recorded that a cloud logging destination was disabled. The event references principal-b52f94a7d99dc7bf. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Identity audit on FINANCE-ASSET-a32c9481137674af recorded that an account password was reset through a recovery workflow. The event references principal-b0dec7cad50c7fe1. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Waf logs on LEGAL-ASSET-558884e90876ee10 recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-3ea85690224829da. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Macos launch audit on OPERATIONS-ASSET-26bdf3f25161f2be recorded that a launch agent definition was installed in a user context. The event references principal-707a961a9c8924fd. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Secret manager audit on OPERATIONS-ASSET-9fccf4aa5cb6d2fb recorded that a workload read several secret versions. The event references principal-67a3ab465380b229. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Kerberos audit on PEOPLE-ASSET-4ee9a55c8fd9d93a recorded that an account requested service tickets for multiple services. The event references principal-0978a46d6664fc2a. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-b181e8f064fa explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Account audit on ENGINEERING-ASSET-bce5c50695a23c43 recorded that a local user account was created on a managed system. The event references principal-1a94579d85980de4. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Identity audit on PROCUREMENT-ASSET-b4ae6e9e4fb445a9 recorded that an account password was reset through a recovery workflow. The event references principal-b2c1bc21d87bb7c1. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-c7e2a0d168d1, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Identity audit on RESEARCH-ASSET-77b0ab4459df7f50 recorded that repeated failed sign-ins were recorded for an account. The event references principal-ef9a3ac0fa7044a5. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-189c1f550f6d match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Identity audit on FINANCE-ASSET-8c4f9dd18c643b5e recorded that repeated failed sign-ins were recorded for an account. The event references principal-e15b307c4e5bf156. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Group audit on SALES-ASSET-0d02096325648024 recorded that an account was added to a privileged local group. The event references principal-2cfc43945d846816. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Policy audit on LEGAL-ASSET-fdcb7612a4f13f67 recorded that an audit policy was changed to collect fewer event categories. The event references principal-3d26eee8b88bfb17. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Kubernetes audit on ENGINEERING-ASSET-cad5b32322e2d059 recorded that a pod was created with privileged execution enabled. The event references principal-b5a63a5d1fffe886. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Cron audit on OPERATIONS-ASSET-837b3c551a9b50e7 recorded that a recurring job definition was added to the system schedule. The event references principal-96fb058b67291144. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Configuration audit on FINANCE-ASSET-74d3e5b9407ece66 recorded that a client proxy setting was changed. The event references principal-00bf9f3d44fd549a. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-2b5f924f6293 match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Backup audit on FINANCE-ASSET-7d6385ebfb9a8a83 recorded that a backup retention policy was shortened. The event references principal-87f1c31296aed897. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Identity audit on SALES-ASSET-880860857ffcd92f recorded that a service account established an interactive session. The event references principal-6480886757402cfa. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-e91d3fcd08eb before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"File audit on SUPPORT-ASSET-96c72864072032c8 recorded that a process deleted many files within a short interval. The event references principal-7a907f6a20c3a4ff. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Office audit on ENGINEERING-ASSET-8b497889760890b7 recorded that a document macro launched a child interpreter. The event references principal-348623c716d723c6. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Application audit on PROCUREMENT-ASSET-4c611d31ce0dab93 recorded that an application read clipboard contents repeatedly. The event references principal-8af1d70f167ed8d6. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Cloud identity audit on ENGINEERING-ASSET-00c2f8de5ff4a52c recorded that a principal assumed a role in another account. The event references principal-4cb5db7ee766c0fa. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-67dbd4556ef3 accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Cloud control audit on FINANCE-ASSET-f3ec32c70b0e59d9 recorded that resources were created in a region with little prior activity. The event references principal-8d633cfbda070abb. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Saas audit on RESEARCH-ASSET-b155eac613e67224 recorded that a user requested a bulk export from a business application. The event references principal-5a3ba2a9838be78e. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Service audit on RESEARCH-ASSET-83637b2bf6e44350 recorded that a new automatically started service was registered. The event references principal-9f4043a1a42fcc90. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Kubernetes audit on SUPPORT-ASSET-ea9a39224859df23 recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-c986eaa5cd9383cb. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Federation audit on PEOPLE-ASSET-307988f8a71d4999 recorded that a tenant federation setting was updated. The event references principal-c9e7767b005f5591. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-fa89ffb8990d explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Package registry audit on OPERATIONS-ASSET-b20136404dfc240b recorded that a principal published a new package version. The event references principal-97ed055b6e1a57e6. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Firewall audit on SUPPORT-ASSET-e85c56705ce7aa30 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-9b678cb3b90b393c. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-63a82982fd9f match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"File audit on ENGINEERING-ASSET-e53845b276f34712 recorded that a process rewrote multiple files into encrypted containers. The event references principal-f651e132a9d111e2. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-428e80a052ce match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Systemd audit on RESEARCH-ASSET-eeb116f31cbce82f recorded that a service unit file was changed and the unit reloaded. The event references principal-f39102d395b571c9. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Agent audit on COMMUNICATIONS-ASSET-7f32c685e6e40f0f recorded that a privileged session changed endpoint monitoring settings. The event references principal-ce4504f33247e9eb. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Database audit on ENGINEERING-ASSET-2c4914b84c80f08c recorded that a session read several tables and exported the query result. The event references principal-b17a9277af7e3124. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-c6483d7d243a explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Function audit on OPERATIONS-ASSET-7bf3d2cc7f955758 recorded that a serverless function package and execution settings were updated. The event references principal-2b7da48bc74786c4. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Runtime audit on SALES-ASSET-65e80c7b6f9129ee recorded that a process connected to the container runtime socket. The event references principal-e74aec44693d5ee6. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-21bd8a6d7a5b specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Ci audit on LEGAL-ASSET-307a1ab2be77fe5f recorded that a build pipeline definition gained a new execution step. The event references principal-362aa0b8c3b22688. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-d39ecfcfcf4d accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Process audit on OPERATIONS-ASSET-4be1d9f7adca7d10 recorded that a remote-support application started an interactive session. The event references principal-85052a5f25abdf7a. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Proxy logs on LEGAL-ASSET-11a1797ca70316c7 recorded that a client transferred a large payload to an external storage endpoint. The event references principal-0b83b39a8d8a6fb4. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Windows logon audit on RESEARCH-ASSET-fcc9667f845ac430 recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-af2356cb5701209c. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Ci audit on OPERATIONS-ASSET-3c47f8e04ce54395 recorded that a build pipeline definition gained a new execution step. The event references principal-4e3a0bcc0149b2b6. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-a33374a731f6 explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Driver audit on COMMUNICATIONS-ASSET-b8154a780e8f0180 recorded that a kernel driver was loaded after a package installation. The event references principal-5b575ab65094c162. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Waf logs on FINANCE-ASSET-2688c7caaa5c3540 recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-fa0ae08c81b790e0. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Vpn audit on COMMUNICATIONS-ASSET-cf88b5e111fdd1c4 recorded that a remote-access VPN session was established. The event references principal-323dccf79a1a961c. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Storage audit on COMMUNICATIONS-ASSET-4c8d4447eef18c17 recorded that an object-storage access policy was broadened. The event references principal-2ee0983ecf5d6d25. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Directory audit on SUPPORT-ASSET-657351ecbd6ea04f recorded that a principal requested directory replication data. The event references principal-415e143ac445aa25. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Cloud control audit on ENGINEERING-ASSET-2f0ebfbab41474df recorded that a session deleted a group of cloud resources. The event references principal-eab0d8cb49ca354d. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Identity audit on COMMUNICATIONS-ASSET-ae1258c834d83e6f recorded that an account password was reset through a recovery workflow. The event references principal-98f97f4d1c43e756. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Network control audit on SALES-ASSET-bd4a95d925024567 recorded that a cloud security group gained a broad ingress rule. The event references principal-2e1769cecef25401. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Repository audit on PEOPLE-ASSET-ab514f2b7cf1ca44 recorded that a repository collaborator received elevated permissions. The event references principal-49f43d9a0cf7b13c. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Cloud identity audit on OPERATIONS-ASSET-3155b7b471a38d4e recorded that a principal received a policy granting additional permissions. The event references principal-e51b01012b559bdf. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-d27f6ea5c71e, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Kubernetes audit on ENGINEERING-ASSET-03ff797dc0608058 recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-84d60009e20971fc. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Database audit on FINANCE-ASSET-7b5f1daa45ffd071 recorded that a session changed a database table definition. The event references principal-eec005bb1596cf1c. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Assessment SEC-9d822db8d5d7 explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Registry audit on RESEARCH-ASSET-e5e233361fd38697 recorded that a registry logon-start entry was created. The event references principal-83333208692c8fd1. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Session audit on ENGINEERING-ASSET-bc4c94aa37fb4f60 recorded that the same session token appeared from different client addresses. The event references principal-821aec91dc2aa8b4. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Agent audit on SUPPORT-ASSET-9325bde68edaa545 recorded that a privileged session changed endpoint monitoring settings. The event references principal-1641f4bad60d9f93. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Identity audit on RESEARCH-ASSET-855e969e96eb06ea recorded that an account password was reset through a recovery workflow. The event references principal-811400d02da15e41. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-242ca9ec4188 accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"File audit on OPERATIONS-ASSET-aa398735111975aa recorded that a process deleted many files within a short interval. The event references principal-ff0116df6d90824b. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Office audit on SALES-ASSET-bd4695abc7ff04ad recorded that a document macro launched a child interpreter. The event references principal-9bfaf02fa70a4f6b. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Smb audit on RESEARCH-ASSET-130b1b37c48e2c18 recorded that a session enumerated a file share and read multiple files. The event references principal-143930e21a998c01. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Change CHG-e158a5ccd9e6 lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Agent audit on ENGINEERING-ASSET-d4aa23315bb70413 recorded that a privileged session changed endpoint monitoring settings. The event references principal-2e08cdbbea0a15c2. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Task scheduler audit on RESEARCH-ASSET-21bf6f06fdc5117a recorded that a scheduled task was registered to execute a program at logon. The event references principal-0cdfb8ebb9ac46b3. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Device and file audit on COMMUNICATIONS-ASSET-f491a02c80ff7ee4 recorded that files were copied to a removable storage device. The event references principal-b586401867cc7a49. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-fdc1a6d4b075 match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Group audit on RESEARCH-ASSET-0d0aaf2292482822 recorded that an account was added to a privileged local group. The event references principal-5badc7c76a42d4b2. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-84ca6b796f2f, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Driver audit on ENGINEERING-ASSET-aa761eb37a133a6c recorded that a kernel driver was loaded after a package installation. The event references principal-b792fcefc38ccc53. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Function audit on ENGINEERING-ASSET-1db2f1c877763b47 recorded that a serverless function package and execution settings were updated. The event references principal-79d1bb9e5af18d47. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Directory audit on OPERATIONS-ASSET-f0615ba52c4fafcb recorded that a principal requested directory replication data. The event references principal-c94c73361a03e2ca. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-9986197c0c6a match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Saas audit on OPERATIONS-ASSET-f4bc429edd233279 recorded that a user requested a bulk export from a business application. The event references principal-0d93bc3cb85c4be3. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-aadce13d079c covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Storage audit on RESEARCH-ASSET-6e2b243ec7d7a919 recorded that an object-storage access policy was broadened. The event references principal-262db57bffaea9f7. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Change CHG-65c23636bdd2 lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Policy audit on FINANCE-ASSET-e464a7dfab1a5a08 recorded that an audit policy was changed to collect fewer event categories. The event references principal-88be6dc1340765a4. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Kubernetes audit on PEOPLE-ASSET-46959b0322e15f66 recorded that a pod was created with privileged execution enabled. The event references principal-8e6c04f200191e81. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Backup audit on PEOPLE-ASSET-90b00913ef4755f4 recorded that a backup retention policy was shortened. The event references principal-069c9474003b2644. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Assessment SEC-f767be67e841 explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Flow logs on SALES-ASSET-60c136594edf1098 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-a5e562da0b238c72. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Registry audit on OPERATIONS-ASSET-2d36b1b63d0c4ad6 recorded that a workload pulled a container image from a registry. The event references principal-1fdf41d42655dccc. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Mail flow logs on OPERATIONS-ASSET-b187da0291cabbc9 recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-3df241ac15d172ff. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Module audit on FINANCE-ASSET-6b165174917b5734 recorded that a process loaded a library from an application-local directory. The event references principal-ecca7e9b2841d1cc. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Repository audit on ENGINEERING-ASSET-19fede4e07d7366c recorded that a repository collaborator received elevated permissions. The event references principal-22c3a4b3adce2401. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Group audit on OPERATIONS-ASSET-0c05abbcb3b78111 recorded that an account was added to a privileged local group. The event references principal-67db77b910dcd61e. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Waf logs on SALES-ASSET-8a0f506e8e518bc0 recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-eb2ba7446fb1565a. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Ci audit on RESEARCH-ASSET-1bb40eb620dce13c recorded that a build pipeline definition gained a new execution step. The event references principal-1e7493e87ff48bbe. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-7f835b5a85ad accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Repository audit on PROCUREMENT-ASSET-7cc2509e9eb69ebb recorded that a user cloned several source repositories. The event references principal-39fa91ed4065a325. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Share audit on PROCUREMENT-ASSET-d3ee6d1f094d6ce0 recorded that a new network file share was published. The event references principal-9978a814a123a526. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Dhcp telemetry on FINANCE-ASSET-99d84bf5e5de071b recorded that a server issued DHCP offers on a monitored segment. The event references principal-e238480421ab2c07. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-5c42053a6603, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Cloud control audit on SALES-ASSET-5ed8420ac6bfabb9 recorded that a session deleted a group of cloud resources. The event references principal-e108fb64fd38558b. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Ci audit on PEOPLE-ASSET-ea14ad85e984ee1f recorded that a build pipeline definition gained a new execution step. The event references principal-02ee8abd42195e24. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Change CHG-83102cd2a5b2 lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Module audit on OPERATIONS-ASSET-da72125783fc7146 recorded that a process loaded a library from an application-local directory. The event references principal-88a37cd2d0222e86. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Secret manager audit on RESEARCH-ASSET-9ed518d17fe68d7a recorded that a workload read several secret versions. The event references principal-7f1b48c31f4c5822. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Winrm audit on RESEARCH-ASSET-35584f0a53bc209b recorded that a remote management session invoked a command on a managed host. The event references principal-7b703d1f8c94aba9. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Kubernetes audit on PROCUREMENT-ASSET-fa28de9adbfdddd4 recorded that a pod was created with privileged execution enabled. The event references principal-c0583fecec986fcd. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-4afcaed70f26 specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"File audit on LEGAL-ASSET-fdae576414dd7376 recorded that a process deleted many files within a short interval. The event references principal-a6b7ec4e30bafd95. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Driver audit on OPERATIONS-ASSET-16afbb03ee82c54d recorded that a kernel driver was loaded after a package installation. The event references principal-32362e7a45f17c8f. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-dc77a030325b match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Session audit on OPERATIONS-ASSET-650805187004af92 recorded that the same session token appeared from different client addresses. The event references principal-fe1f7195dd801273. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Change CHG-d440b2eba275 lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"File audit on SUPPORT-ASSET-0129618ced8fc8ec recorded that a process compressed files from several directories into an archive. The event references principal-8432d907b9ba200c. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-5658fe247542 accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Identity audit on SALES-ASSET-17bd921cea441a1f recorded that repeated failed sign-ins were recorded for an account. The event references principal-d02e40aae87e9ff0. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Application audit on FINANCE-ASSET-5311585386f59d86 recorded that an application requested repeated screen captures. The event references principal-6f04a55a0eba4c05. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Process audit on SALES-ASSET-96ce257e2204a8a5 recorded that a remote-support application started an interactive session. The event references principal-ae9cce396ea567fe. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Storage audit on PROCUREMENT-ASSET-f524c33b819a1663 recorded that an object-storage access policy was broadened. The event references principal-daeee49ee65928ba. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Kubernetes audit on SUPPORT-ASSET-95dbeaaf93770ec1 recorded that a role binding granted a principal additional cluster permissions. The event references principal-fae5a1331ea1b683. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Identity audit on SUPPORT-ASSET-f9b39e12fc139ef0 recorded that an account registered a new MFA method. The event references principal-3c523bf81b3a031f. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Storage access logs on LEGAL-ASSET-6ac4fabec7ab5dad recorded that a principal downloaded many objects from a storage bucket. The event references principal-70ca2ffed3e11735. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Certificate audit on FINANCE-ASSET-e16767dd715979b6 recorded that a service certificate was replaced. The event references principal-f8a1311de5964c87. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-992d40111ef6 match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Firewall audit on RESEARCH-ASSET-0236b24f6c7b0e03 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-582ef1b1560e6fc6. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-0011b4ba16f5 before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Storage audit on PEOPLE-ASSET-4b18ae09e42fe01b recorded that an object-storage access policy was broadened. The event references principal-7721904d8c389cbb. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Task scheduler audit on PEOPLE-ASSET-967b5df7e748b2ff recorded that a scheduled task was registered to execute a program at logon. The event references principal-80092436d4633e85. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Module audit on SALES-ASSET-0a5edb66b7d6ecd7 recorded that a process loaded a library from an application-local directory. The event references principal-adbbffe7727b888c. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Assessment SEC-9b8631afa010 explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Ci secret audit on RESEARCH-ASSET-d46af760b3fcf2d7 recorded that a build job requested a protected pipeline secret. The event references principal-60fe7cbc94a757b5. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Identity audit on COMMUNICATIONS-ASSET-cdebef5d9dc25fc4 recorded that a service account established an interactive session. The event references principal-ecbde67b88dd7d93. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Flow logs on RESEARCH-ASSET-6a2a326a382bb0b4 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-56d66c0e0a2c4463. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Task scheduler audit on ENGINEERING-ASSET-03b8a656580bfb25 recorded that a scheduled task was registered to execute a program at logon. The event references principal-2a3a3ccb2ea52460. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-a3f8c9a20f72 match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Kubernetes audit on ENGINEERING-ASSET-74d13411d760b9a6 recorded that a role binding granted a principal additional cluster permissions. The event references principal-dbf4764de8118d40. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Configuration audit on OPERATIONS-ASSET-f3ed5a9b931a0951 recorded that a client proxy setting was changed. The event references principal-d8940d417fc4c9bd. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-b1a53ab76976 explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Mail and proxy logs on COMMUNICATIONS-ASSET-48a9f26bd10054b4 recorded that a user opened a URL delivered in an email message. The event references principal-0e84a6c758769248. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Kubernetes audit on PROCUREMENT-ASSET-8857c7021ba70cdd recorded that a cluster admission policy was changed. The event references principal-0637e683dcd7afbd. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-049772ba9b46 explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Switch telemetry on COMMUNICATIONS-ASSET-bcb43f0616b1a470 recorded that an address mapping changed repeatedly on a local segment. The event references principal-ea5a7f0eef9db0e7. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-a1e9fc66b281, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Proxy logs on PROCUREMENT-ASSET-a90cefc8840eb875 recorded that a client transferred a large payload to an external storage endpoint. The event references principal-58357f3106f790fd. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Waf logs on RESEARCH-ASSET-f279330020f0e645 recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-a38184b376034ec2. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"File audit on FINANCE-ASSET-d2b45ac726791f9b recorded that a process deleted many files within a short interval. The event references principal-e041b8a80436a62f. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Office audit on ENGINEERING-ASSET-8b497889760890b7 recorded that a document macro launched a child interpreter. The event references principal-348623c716d723c6. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Systemd audit on SUPPORT-ASSET-38d3359b892c66ba recorded that a service unit file was changed and the unit reloaded. The event references principal-fbace7ec59135a92. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Application audit on FINANCE-ASSET-5311585386f59d86 recorded that an application requested repeated screen captures. The event references principal-6f04a55a0eba4c05. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Module audit on OPERATIONS-ASSET-da72125783fc7146 recorded that a process loaded a library from an application-local directory. The event references principal-88a37cd2d0222e86. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Pki audit on COMMUNICATIONS-ASSET-a88e156f33159899 recorded that a principal requested a certificate using an authentication template. The event references principal-0a19afbf9253f4fc. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Gateway logs on OPERATIONS-ASSET-7599af3c268c4876 recorded that a client established a long-lived encapsulated network session. The event references principal-ba0168660aabc1f0. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Ssh audit on COMMUNICATIONS-ASSET-c7c949ba2f23f6e5 recorded that an SSH session opened and requested elevated command execution. The event references principal-3a7b389506fbf3c1. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-f244ef337f31 match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Egress flow logs on PROCUREMENT-ASSET-dec31bc9d60afefc recorded that a workload opened an encrypted connection to an external service. The event references principal-552eff98281f8ed1. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Mail audit on RESEARCH-ASSET-0a4e5d836144a737 recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-3b98b2ee8f80fa29. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"File access audit on PROCUREMENT-ASSET-0b755d0602adf157 recorded that a process opened a local credential-store file. The event references principal-7e6f29a9069cca6a. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Dns server audit on OPERATIONS-ASSET-77c8f7df02d0b548 recorded that a client requested a DNS zone transfer. The event references principal-de675342a884898f. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-2b9f155116a9 before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Mfa audit on FINANCE-ASSET-77a6969db5ae1147 recorded that multiple MFA challenges were issued during a short interval. The event references principal-660a5b1395e78ef7. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Task scheduler audit on SALES-ASSET-14a4b633fa3add9a recorded that a scheduled task was registered to execute a program at logon. The event references principal-bc7f1b7e6f9cd150. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Process audit on COMMUNICATIONS-ASSET-5b837c3960f14bc6 recorded that a JavaScript interpreter executed a local script. The event references principal-f91a7e6de3b60959. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"File audit on SALES-ASSET-f0f53d618a5c2238 recorded that a process compressed files from several directories into an archive. The event references principal-a24a28fb5a9017a6. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Script audit on FINANCE-ASSET-8f7a7c5dae3d75b5 recorded that a script interpreter decoded an encoded argument before execution. The event references principal-7a6a17f9162097f1. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Mail audit on FINANCE-ASSET-c2947168e63669b0 recorded that an account received delegated access to a mailbox. The event references principal-33d9797e6b81280e. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Assessment SEC-a9475594c02b explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Script audit on LEGAL-ASSET-38bacff4f7d252bf recorded that a script interpreter decoded an encoded argument before execution. The event references principal-0e6d8e54a19c536c. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Script audit on LEGAL-ASSET-38bacff4f7d252bf recorded that a script interpreter decoded an encoded argument before execution. The event references principal-0e6d8e54a19c536c. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Security retest SEC-a2f0efc521d5 covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Key service audit on LEGAL-ASSET-c93c39a0bf6d5d2d recorded that a principal issued a burst of key-service decrypt requests. The event references principal-a9f8c5175e6aa291. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Flow logs on FINANCE-ASSET-b04c464556b8fa8d recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-4fa1efc3a212390d. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Session audit on RESEARCH-ASSET-5cafc83fecebfc2d recorded that the same session token appeared from different client addresses. The event references principal-fe88f832c0c25c20. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Compute audit on PEOPLE-ASSET-fe0429fc4ead052f recorded that a principal launched multiple compute instances. The event references principal-4fe369a19d9b5bd1. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Session audit on FINANCE-ASSET-15bdb8a9163b0abc recorded that the same session token appeared from different client addresses. The event references principal-ce316de1911fbf84. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-17293d74a05e specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Process audit on SUPPORT-ASSET-6869d2722a21fd5c recorded that a Python interpreter loaded a script and contacted a service. The event references principal-f677ab6a5a1c21d4. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"File audit on ENGINEERING-ASSET-34a8ce1c539d9368 recorded that a process deleted many files within a short interval. The event references principal-c1c689ef96642a7c. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Change CHG-afb5c0e2c61d lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Network control audit on SALES-ASSET-bd4a95d925024567 recorded that a cloud security group gained a broad ingress rule. The event references principal-2e1769cecef25401. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Cloud control audit on FINANCE-ASSET-f3ec32c70b0e59d9 recorded that resources were created in a region with little prior activity. The event references principal-8d633cfbda070abb. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Federation audit on PROCUREMENT-ASSET-627d4b1e14d07688 recorded that a tenant federation setting was updated. The event references principal-be363e08050ad9ec. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Dns server audit on PEOPLE-ASSET-9dfdc0288f418b98 recorded that a client requested a DNS zone transfer. The event references principal-fb173264d38aac45. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"File audit on PROCUREMENT-ASSET-4eb226a25712a501 recorded that a process rewrote multiple files into encrypted containers. The event references principal-6dcdfe5a31b0546b. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Database audit on PEOPLE-ASSET-5fce356081bdb526 recorded that a session read several tables and exported the query result. The event references principal-b90846a958bd885f. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Database audit on FINANCE-ASSET-f03ba1a6a369cf03 recorded that a session read several tables and exported the query result. The event references principal-f892103a2793bbab. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-8a9f9fb5c9bc specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Proxy logs on PEOPLE-ASSET-47b1cfa33ae643a0 recorded that a client transferred a large payload to an external storage endpoint. The event references principal-eefc70a315bcfb3b. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Process audit on FINANCE-ASSET-9d45d520b4a54280 recorded that a Python interpreter loaded a script and contacted a service. The event references principal-d052a3f1c4010987. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Ssh audit on OPERATIONS-ASSET-324bfe1afe152ff0 recorded that an SSH session opened and requested elevated command execution. The event references principal-db6e14b705505251. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-e77b283c7fc4 explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Share audit on COMMUNICATIONS-ASSET-155e7e0f58a0bc23 recorded that a new network file share was published. The event references principal-91339ef7c416f6ed. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-6e2f071b38a7 before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Mail flow logs on SALES-ASSET-40ddb7fd75836262 recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-4279d4843faab477. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Change CHG-4242122066d2 lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Policy audit on RESEARCH-ASSET-9236351eaaf332af recorded that an audit policy was changed to collect fewer event categories. The event references principal-9505995ed7eba439. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-96d5eb2240cf specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Service audit on RESEARCH-ASSET-8d77d8342c20fbff recorded that a remote service-control request created and started a temporary service. The event references principal-211275ad14685644. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Mail flow logs on RESEARCH-ASSET-a506e0d5600d9442 recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-27bdbe6c899d3b5b. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Change CHG-973acca4a89b lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Process audit on FINANCE-ASSET-db3968cef4c0b684 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-a71f596247827755. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Assessment SEC-c4e299a7a297 explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Identity audit on COMMUNICATIONS-ASSET-4abec775a52c95c2 recorded that repeated failed sign-ins were recorded for an account. The event references principal-a42f44848e926187. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Kubernetes audit on SUPPORT-ASSET-ea9a39224859df23 recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-c986eaa5cd9383cb. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Process audit on SALES-ASSET-d7499e681a58affc recorded that a JavaScript interpreter executed a local script. The event references principal-ce0d21f659b72ac8. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Change CHG-978b0f77a1db lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Flow logs on SUPPORT-ASSET-30ebec702fd5fb40 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-cc4ef6967d7bd3d5. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Resolver logs on RESEARCH-ASSET-abc39d656b9d30aa recorded that a client requested many long, high-entropy DNS labels. The event references principal-5aebc86024ffc2a8. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Network control audit on ENGINEERING-ASSET-2d4a799851b7227b recorded that a cloud security group gained a broad ingress rule. The event references principal-5b7cb16d420fdcdc. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Pki audit on PEOPLE-ASSET-3dbf336f859282fe recorded that a principal requested a certificate using an authentication template. The event references principal-bc62db6b4c821f23. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-0bba12298ced match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Macos launch audit on LEGAL-ASSET-924fcf03a30c9333 recorded that a launch agent definition was installed in a user context. The event references principal-188d4edbd5c47469. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Application audit on COMMUNICATIONS-ASSET-349e251c3544c259 recorded that a runtime configuration setting was updated. The event references principal-f484d494a6adf949. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Ci audit on PROCUREMENT-ASSET-51d14292a906982f recorded that a build pipeline definition gained a new execution step. The event references principal-776e5e2e9ad695a2. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Saas audit on ENGINEERING-ASSET-0edd073ede2359c9 recorded that a user requested a bulk export from a business application. The event references principal-273e879f8b9e8512. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"File audit on ENGINEERING-ASSET-1a60a1286916ad01 recorded that access permissions were broadened on a directory tree. The event references principal-1a1a48bb1e529fb0. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Kubernetes audit on OPERATIONS-ASSET-914b85ff52bb152e recorded that a role binding granted a principal additional cluster permissions. The event references principal-23475897d2814771. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Resolver logs on SALES-ASSET-17cdfcbdaddd4989 recorded that a client requested many long, high-entropy DNS labels. The event references principal-fddd379e6737bcc0. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Session audit on RESEARCH-ASSET-5cafc83fecebfc2d recorded that the same session token appeared from different client addresses. The event references principal-fe88f832c0c25c20. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-bc59b3a43402, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Account audit on FINANCE-ASSET-00ff9ecf71797cc7 recorded that a local user account was created on a managed system. The event references principal-a4700d3ad9f008de. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-0217d5ba5458 match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Proxy logs on SALES-ASSET-c3dbe91c60733c60 recorded that a client transferred a large payload to an external storage endpoint. The event references principal-fbf3a8a302b7a6c9. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-c2d0f4a645dc specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"File audit on RESEARCH-ASSET-e98c7e7ef8b5bfbe recorded that a process rewrote multiple files into encrypted containers. The event references principal-b60fe0e57ed46b9d. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Identity audit on ENGINEERING-ASSET-17f1d906d8c35962 recorded that a service account established an interactive session. The event references principal-4e2ae7344e474fce. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"File audit on PEOPLE-ASSET-a99509e663c1444d recorded that a process rewrote multiple files into encrypted containers. The event references principal-dc7744cab585a5e1. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Office audit on OPERATIONS-ASSET-a21bbd8f65591dc7 recorded that a document macro launched a child interpreter. The event references principal-640ebd4004779cca. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Cloud identity audit on SALES-ASSET-6e863cbb874762df recorded that a principal assumed a role in another account. The event references principal-3f1f6f7b104b9c3f. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Share audit on SUPPORT-ASSET-642a0478e0fea4be recorded that a new network file share was published. The event references principal-d39d2cce091886dd. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Oauth audit on SUPPORT-ASSET-f8746b96a88e1b30 recorded that an application received consent for additional account scopes. The event references principal-7f165276ca2b480a. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-2324e45e66e6 match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Service audit on OPERATIONS-ASSET-fd16a6acf8f54a9a recorded that a new automatically started service was registered. The event references principal-c9af46ed7e55064b. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Macos launch audit on RESEARCH-ASSET-76ee756c91d53577 recorded that a launch agent definition was installed in a user context. The event references principal-cd202933651b57f9. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Resolver logs on PROCUREMENT-ASSET-217f3e17146574de recorded that a client requested many long, high-entropy DNS labels. The event references principal-c25feb34aea9c3bd. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"File access audit on COMMUNICATIONS-ASSET-5eb665c77394105b recorded that a process opened a local credential-store file. The event references principal-a9229a1030eb8134. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Storage access logs on LEGAL-ASSET-6ac4fabec7ab5dad recorded that a principal downloaded many objects from a storage bucket. The event references principal-70ca2ffed3e11735. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Cloud identity audit on SUPPORT-ASSET-0acaf32cb86c9787 recorded that a new programmatic access key was issued to a principal. The event references principal-f4c6ed272feaab73. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Kerberos audit on RESEARCH-ASSET-add8a0192da6108f recorded that an account requested service tickets for multiple services. The event references principal-2289755f000d3a1a. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Systemd audit on FINANCE-ASSET-2646ce4052597344 recorded that a service unit file was changed and the unit reloaded. The event references principal-38069415a5ef6919. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"File access audit on ENGINEERING-ASSET-9bb4a75d3491a9be recorded that a process opened a local credential-store file. The event references principal-f9c37bdee298aeea. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-ad734b015bad explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Gateway logs on FINANCE-ASSET-0eba77ccb6dbdba6 recorded that a client established a long-lived encapsulated network session. The event references principal-5f89b733086ddfa5. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Secret manager audit on FINANCE-ASSET-848c4b906d36b1f9 recorded that a workload read several secret versions. The event references principal-2d99961e29099c47. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-bb47fcc2ec94 accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Smb audit on ENGINEERING-ASSET-167b039744d858de recorded that a session enumerated a file share and read multiple files. The event references principal-dae2d90d16568727. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Kubernetes audit on COMMUNICATIONS-ASSET-4eb386b59cd197fa recorded that a cluster admission policy was changed. The event references principal-6713342ad2d170de. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-42ef1b68e5bb covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Package registry audit on RESEARCH-ASSET-b42ad559dc38cada recorded that a principal published a new package version. The event references principal-ae25582585615c9e. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Kubernetes audit on COMMUNICATIONS-ASSET-396281c213cbfe7d recorded that a role binding granted a principal additional cluster permissions. The event references principal-490795a3fa64d894. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Process audit on FINANCE-ASSET-7c0fff41e30d4380 recorded that a JavaScript interpreter executed a local script. The event references principal-5ba5da6cfca5af4e. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Gateway logs on COMMUNICATIONS-ASSET-01bdebe9cfb40e2b recorded that a client established a long-lived encapsulated network session. The event references principal-298b7f8258456986. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-f610a098f9a2 covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Kubernetes audit on FINANCE-ASSET-915256a7e7a6d4a6 recorded that a role binding granted a principal additional cluster permissions. The event references principal-49e34ed22123229a. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Dns server audit on FINANCE-ASSET-b5978ac018c6f58c recorded that a client requested a DNS zone transfer. The event references principal-eef8de7d2245f076. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-73e7d312daff match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Saas audit on LEGAL-ASSET-febb39399ce8713a recorded that a user requested a bulk export from a business application. The event references principal-56038be98666605f. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"File audit on RESEARCH-ASSET-e98c7e7ef8b5bfbe recorded that a process rewrote multiple files into encrypted containers. The event references principal-b60fe0e57ed46b9d. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Smb audit on OPERATIONS-ASSET-903799bcbb7f90a6 recorded that a session enumerated a file share and read multiple files. The event references principal-b3bfcfbe522db4bd. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-a084b14225b3 specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Api gateway logs on FINANCE-ASSET-7a64770a61e92e29 recorded that a client issued a burst of API requests. The event references principal-43cf908ee519b246. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Oauth audit on PROCUREMENT-ASSET-2f4aab546bd1bb38 recorded that an application received consent for additional account scopes. The event references principal-eef62ccd4ff2398c. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Mail audit on PROCUREMENT-ASSET-d1aa07096744ffae recorded that an account received delegated access to a mailbox. The event references principal-77fb31a09163908c. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-7606c6b51291 specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Network control audit on COMMUNICATIONS-ASSET-b93121e4b22b1a29 recorded that a cloud security group gained a broad ingress rule. The event references principal-8f16c182ac4bbc7f. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Process audit on COMMUNICATIONS-ASSET-332afb2165aa1448 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-afe5b84c8ef31787. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Kubernetes audit on FINANCE-ASSET-4f8f4d9f800ab9a6 recorded that a cluster admission policy was changed. The event references principal-0f727ece26b623bd. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-3a72ca142510 match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Systemd audit on COMMUNICATIONS-ASSET-83d44af530d70e5a recorded that a service unit file was changed and the unit reloaded. The event references principal-fef91c85181668d1. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Cloud control audit on SALES-ASSET-bfb02fef7d44a1a0 recorded that a cloud logging destination was disabled. The event references principal-cabdd3811f019647. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Switch telemetry on RESEARCH-ASSET-39ecead5bf809d8c recorded that an address mapping changed repeatedly on a local segment. The event references principal-78520d727e00f06a. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Storage access logs on ENGINEERING-ASSET-cfa9edf25dbd11b0 recorded that a principal downloaded many objects from a storage bucket. The event references principal-9a3a0f64a8f2a35d. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Driver audit on PROCUREMENT-ASSET-caa474ba78b6dce6 recorded that a kernel driver was loaded after a package installation. The event references principal-c43c37da7fba502b. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-1362f5d0e6fa specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Egress flow logs on ENGINEERING-ASSET-244beee7b921f878 recorded that a workload opened an encrypted connection to an external service. The event references principal-0a5b130156e24d17. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Application audit on SUPPORT-ASSET-0d07ed7bee9ce5d7 recorded that an application requested repeated screen captures. The event references principal-1f37918578f8f184. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Saas audit on OPERATIONS-ASSET-f4bc429edd233279 recorded that a user requested a bulk export from a business application. The event references principal-0d93bc3cb85c4be3. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Module audit on RESEARCH-ASSET-49e502fa5df5f407 recorded that a process loaded a library from an application-local directory. The event references principal-52065da876a99294. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-954b35b60dab accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Cloud identity audit on SALES-ASSET-8e5fe4f751d14789 recorded that a new programmatic access key was issued to a principal. The event references principal-42ddd98f6ef91f59. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-8aa5e90136c3 explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Federation audit on SALES-ASSET-88538f554d17e7e6 recorded that a tenant federation setting was updated. The event references principal-caaf0b98849ffd32. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Flow logs on ENGINEERING-ASSET-6ee9ce19d8b1f530 recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-5923ac86626d7de4. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Flow logs on ENGINEERING-ASSET-eb2e69d274ba28c2 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-95a534f7e0b0cad5. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Configuration audit on FINANCE-ASSET-74d3e5b9407ece66 recorded that a client proxy setting was changed. The event references principal-00bf9f3d44fd549a. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Ci audit on SALES-ASSET-58f9b0d2c10b53d7 recorded that a build pipeline definition gained a new execution step. The event references principal-db424878959459e6. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Process access audit on OPERATIONS-ASSET-a4047122fa1f8006 recorded that a process requested read access to another process memory space. The event references principal-b6f3ffe23361d9c9. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Device and file audit on SALES-ASSET-3b11bf4bc19f47f9 recorded that files were copied to a removable storage device. The event references principal-342176cf658025b8. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Device and file audit on LEGAL-ASSET-e36229f519715f46 recorded that files were copied to a removable storage device. The event references principal-ecac25dd7192fc25. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-4d76318bf5c5 match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Identity audit on LEGAL-ASSET-f678141e2b084a32 recorded that an account registered a new MFA method. The event references principal-500c71ca31b016a9. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Mfa audit on SALES-ASSET-413206c0391aae90 recorded that multiple MFA challenges were issued during a short interval. The event references principal-13b992911a08e483. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Storage audit on PEOPLE-ASSET-1ba8659c3031d7f0 recorded that a session deleted several storage snapshots. The event references principal-cf538081eb476d29. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Windows logon audit on COMMUNICATIONS-ASSET-6f9244839c2eca95 recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-263d3b9d1be1a7e1. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Ci audit on SALES-ASSET-58f9b0d2c10b53d7 recorded that a build pipeline definition gained a new execution step. The event references principal-db424878959459e6. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Runtime audit on PEOPLE-ASSET-616ef8f8f0889aaf recorded that a process connected to the container runtime socket. The event references principal-685ce977f92924b1. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-10cf20c53ae3 accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Kubernetes audit on SUPPORT-ASSET-70672b7c7f3d80de recorded that a workload mounted a directory from its host filesystem. The event references principal-bb9a9a5a1ac32931. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Network control audit on COMMUNICATIONS-ASSET-b93121e4b22b1a29 recorded that a cloud security group gained a broad ingress rule. The event references principal-8f16c182ac4bbc7f. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Process audit on FINANCE-ASSET-9d45d520b4a54280 recorded that a Python interpreter loaded a script and contacted a service. The event references principal-d052a3f1c4010987. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Kubernetes audit on OPERATIONS-ASSET-bc31964912cf4d1d recorded that a cluster admission policy was changed. The event references principal-c0a0ee553024f5ef. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Identity audit on OPERATIONS-ASSET-775dd42bd2b2e216 recorded that repeated failed sign-ins were recorded for an account. The event references principal-2f8b852f1ede3573. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Account audit on FINANCE-ASSET-00ff9ecf71797cc7 recorded that a local user account was created on a managed system. The event references principal-a4700d3ad9f008de. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Identity audit on ENGINEERING-ASSET-f3a5e6ca5f4810c3 recorded that an account registered a new MFA method. The event references principal-a81b0853166bb0e5. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Vpn audit on SALES-ASSET-09dd168451b4fb60 recorded that a remote-access VPN session was established. The event references principal-732980774243feef. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-da0b9c7fa7b2, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Wmi audit on RESEARCH-ASSET-ff750cc74100e1ac recorded that a management request started a process through WMI. The event references principal-2a6d4aeffc691fda. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Session audit on ENGINEERING-ASSET-bc4c94aa37fb4f60 recorded that the same session token appeared from different client addresses. The event references principal-821aec91dc2aa8b4. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Cron audit on PROCUREMENT-ASSET-ccd7b77f6fbe55e6 recorded that a recurring job definition was added to the system schedule. The event references principal-ff6d598ce8d74f2d. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Registry audit on LEGAL-ASSET-d0480e188fd31f60 recorded that a workload pulled a container image from a registry. The event references principal-160b2d0cefee47e2. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Kubernetes audit on RESEARCH-ASSET-d1f7ab9c3de5615d recorded that a cluster admission policy was changed. The event references principal-bc8aec70f878822d. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Secret manager audit on LEGAL-ASSET-473919a6141fb4d1 recorded that a workload read several secret versions. The event references principal-be429b8818a2a6bf. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-aa48520ea135 before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Resolver logs on PEOPLE-ASSET-aa9ea5738fc3afe1 recorded that a client requested many long, high-entropy DNS labels. The event references principal-bd6f946855b371b5. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Code integrity audit on PEOPLE-ASSET-4048dcb975a46f2e recorded that an executable without a publisher signature started from a writable directory. The event references principal-d449d23aa96125e6. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Ci audit on SUPPORT-ASSET-be888d94d309deab recorded that a build pipeline definition gained a new execution step. The event references principal-f55be257f884a1b4. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Dns control audit on FINANCE-ASSET-84a7d1044449f1a8 recorded that an authoritative DNS record was updated. The event references principal-f7395e7a5d189597. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Saas audit on ENGINEERING-ASSET-0edd073ede2359c9 recorded that a user requested a bulk export from a business application. The event references principal-273e879f8b9e8512. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Agent audit on OPERATIONS-ASSET-7f3ae95480df95bb recorded that a privileged session changed endpoint monitoring settings. The event references principal-2ff0c372aa7d7315. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-ece303c6c9a5 covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Kubernetes audit on RESEARCH-ASSET-d1f7ab9c3de5615d recorded that a cluster admission policy was changed. The event references principal-bc8aec70f878822d. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Runtime audit on RESEARCH-ASSET-1fdd4c74894a8860 recorded that a process connected to the container runtime socket. The event references principal-1fe12f7544607ca6. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Application audit on RESEARCH-ASSET-11f390ae672643c2 recorded that a runtime configuration setting was updated. The event references principal-1a691de3cb24648f. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Agent audit on PROCUREMENT-ASSET-92d810ab505277a2 recorded that a privileged session changed endpoint monitoring settings. The event references principal-ae67200926ed1d7a. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Assessment SEC-2c31d9786760 explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Office audit on COMMUNICATIONS-ASSET-9792dd26544328c7 recorded that a document macro launched a child interpreter. The event references principal-794c3f6a93ed6b1f. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Identity audit on SUPPORT-ASSET-9a791522c1b9c744 recorded that an account password was reset through a recovery workflow. The event references principal-bd3f8b10beb2211f. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"File access audit on SALES-ASSET-da211711ae9c0eb7 recorded that a process opened a local credential-store file. The event references principal-d1b0980809a9edd2. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Flow logs on PEOPLE-ASSET-48ed1d716acee890 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-d5ba1580babde1ed. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Mail audit on LEGAL-ASSET-131d8c518786695c recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-3bea6da72e330e1b. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Resolver logs on PEOPLE-ASSET-aa9ea5738fc3afe1 recorded that a client requested many long, high-entropy DNS labels. The event references principal-bd6f946855b371b5. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Process audit on RESEARCH-ASSET-4c23face5574e971 recorded that a JavaScript interpreter executed a local script. The event references principal-4325acfa278d2f70. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Identity audit on FINANCE-ASSET-17a7d4bc3e0dfc99 recorded that a service account established an interactive session. The event references principal-ba443b5f7751e8bc. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Smb audit on PEOPLE-ASSET-d3a371e9da6189cb recorded that a session enumerated a file share and read multiple files. The event references principal-4aae8f7eba9ba686. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Smb audit on PEOPLE-ASSET-d3a371e9da6189cb recorded that a session enumerated a file share and read multiple files. The event references principal-4aae8f7eba9ba686. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-40dac43dd55c before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Registry audit on RESEARCH-ASSET-e5e233361fd38697 recorded that a registry logon-start entry was created. The event references principal-83333208692c8fd1. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Flow logs on OPERATIONS-ASSET-498d986f9a323163 recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-921d661770eeeb14. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-63d72b693284 explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Registry audit on LEGAL-ASSET-27fcaf5b02ef0a74 recorded that a registry logon-start entry was created. The event references principal-b668661833835ee3. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Winrm audit on OPERATIONS-ASSET-5123f251af3bff40 recorded that a remote management session invoked a command on a managed host. The event references principal-f7aa03e82682bdc9. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-f3d2b22e1fef accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Process audit on PROCUREMENT-ASSET-121cde9378adb9cf recorded that a JavaScript interpreter executed a local script. The event references principal-1a06985b864403e0. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Proxy logs on LEGAL-ASSET-11a1797ca70316c7 recorded that a client transferred a large payload to an external storage endpoint. The event references principal-0b83b39a8d8a6fb4. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Flow logs on LEGAL-ASSET-bb14ef480a9f5aa0 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-343b8b6d62a9710b. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"File audit on SALES-ASSET-f998f822d677efcd recorded that a process rewrote multiple files into encrypted containers. The event references principal-354f7ba2d1c31de7. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Function audit on PROCUREMENT-ASSET-9b0e13d58a2188a8 recorded that a serverless function package and execution settings were updated. The event references principal-12b8d8e2191620d9. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Change CHG-a601f89844f7 lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Share audit on LEGAL-ASSET-f4d3a91d6248c724 recorded that a new network file share was published. The event references principal-9174cfcb163194b8. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Compute audit on SALES-ASSET-4b3abc50600feeb3 recorded that a principal launched multiple compute instances. The event references principal-a87c3d065d8ee0b1. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-dcc0817e74ac match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Kubernetes audit on SALES-ASSET-3af15ceafaf37a50 recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-4e40a79e1d1cac1f. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Database audit on SALES-ASSET-849ddfe1a9053808 recorded that a session changed a database table definition. The event references principal-425b4fae9e8852ef. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Egress flow logs on PROCUREMENT-ASSET-dec31bc9d60afefc recorded that a workload opened an encrypted connection to an external service. The event references principal-552eff98281f8ed1. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-a2951cdd9ad1 before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Ci audit on RESEARCH-ASSET-1bb40eb620dce13c recorded that a build pipeline definition gained a new execution step. The event references principal-1e7493e87ff48bbe. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Flow logs on SUPPORT-ASSET-30ebec702fd5fb40 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-cc4ef6967d7bd3d5. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-73834c1f3e05 accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Runtime audit on FINANCE-ASSET-f76f44e364cb49d4 recorded that a process connected to the container runtime socket. The event references principal-61088a6af6fdfeb5. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-578ddadc252b accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Gateway logs on LEGAL-ASSET-4deff653cf2694f9 recorded that a client established a long-lived encapsulated network session. The event references principal-76329b77e1b0e6b1. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Gateway logs on OPERATIONS-ASSET-7599af3c268c4876 recorded that a client established a long-lived encapsulated network session. The event references principal-ba0168660aabc1f0. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Cloud identity audit on LEGAL-ASSET-a018d5a0c035a322 recorded that a principal received a policy granting additional permissions. The event references principal-e37ce5811af67681. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Service audit on SUPPORT-ASSET-bed8c4ced0655fc1 recorded that a remote service-control request created and started a temporary service. The event references principal-74bec1dcad5113eb. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Dhcp telemetry on LEGAL-ASSET-5112544cfce28921 recorded that a server issued DHCP offers on a monitored segment. The event references principal-176187e9b5662d2e. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Saas audit on PEOPLE-ASSET-5249110e05a8362d recorded that a user requested a bulk export from a business application. The event references principal-55b28360ed7bad44. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"File audit on COMMUNICATIONS-ASSET-7174b9fee0b011b4 recorded that a process rewrote multiple files into encrypted containers. The event references principal-8e2fefcd77348cfa. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Group audit on PEOPLE-ASSET-f5ce370c9062d00a recorded that an account was added to a privileged local group. The event references principal-a4fe590d9388b8ea. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"File audit on PROCUREMENT-ASSET-a3fde179ef5ff962 recorded that access permissions were broadened on a directory tree. The event references principal-bb1784cca8241c87. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Federation audit on PEOPLE-ASSET-307988f8a71d4999 recorded that a tenant federation setting was updated. The event references principal-c9e7767b005f5591. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-fa89ffb8990d specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Application audit on LEGAL-ASSET-235dadbbfdbe7d33 recorded that an application requested repeated screen captures. The event references principal-31391eee810ce402. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Function audit on COMMUNICATIONS-ASSET-6eba6dd15491bb00 recorded that a serverless function package and execution settings were updated. The event references principal-a52d85256a55e315. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Configuration audit on RESEARCH-ASSET-c3d25c02edb1b375 recorded that a client proxy setting was changed. The event references principal-c2c0e84c38c559bb. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Saas audit on ENGINEERING-ASSET-0edd073ede2359c9 recorded that a user requested a bulk export from a business application. The event references principal-273e879f8b9e8512. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Change CHG-73af046f35a0 lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Windows logon audit on SUPPORT-ASSET-b7addff92f67af33 recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-5b8a266b76f35fee. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-d619d8c5e1d8 explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Repository audit on OPERATIONS-ASSET-2cc6b5c22c3989e5 recorded that a user cloned several source repositories. The event references principal-e45f970cca2e32b9. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Proxy logs on COMMUNICATIONS-ASSET-5a2ac13c8b310540 recorded that a client transferred a large payload to an external storage endpoint. The event references principal-d735b0162330748a. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Egress flow logs on COMMUNICATIONS-ASSET-1fa62ed57f8d2679 recorded that a workload opened an encrypted connection to an external service. The event references principal-297491ec275675d7. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Vpn audit on ENGINEERING-ASSET-10805fb79cd039f2 recorded that a remote-access VPN session was established. The event references principal-ee63fc11c18dbead. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Service audit on SUPPORT-ASSET-2eb791dfb1c8878d recorded that a new automatically started service was registered. The event references principal-7742e70843824b66. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Change CHG-2607dd9a16cd lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Process audit on LEGAL-ASSET-ffdcc64fc856fa3d recorded that a JavaScript interpreter executed a local script. The event references principal-a45f3b91beb56205. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Kubernetes audit on OPERATIONS-ASSET-bc31964912cf4d1d recorded that a cluster admission policy was changed. The event references principal-c0a0ee553024f5ef. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Repository audit on PEOPLE-ASSET-e8dfe6d75dbb8e1e recorded that a user cloned several source repositories. The event references principal-e971d955c552fbff. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Code integrity audit on ENGINEERING-ASSET-bc88477a091db102 recorded that an executable without a publisher signature started from a writable directory. The event references principal-26a79bf54e5ed1d5. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-426844adf496 accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Identity audit on OPERATIONS-ASSET-775dd42bd2b2e216 recorded that repeated failed sign-ins were recorded for an account. The event references principal-2f8b852f1ede3573. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Mail audit on OPERATIONS-ASSET-3a9ba1a13acae41d recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-458bdf5d7e7a4b20. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Agent audit on OPERATIONS-ASSET-7f3ae95480df95bb recorded that a privileged session changed endpoint monitoring settings. The event references principal-2ff0c372aa7d7315. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Function audit on FINANCE-ASSET-715a47edf7141497 recorded that a serverless function package and execution settings were updated. The event references principal-e1d12cf425ed5c27. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Cloud identity audit on PEOPLE-ASSET-f0da82528453fc68 recorded that a principal received a policy granting additional permissions. The event references principal-c5a646fec9c6789b. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Windows logon audit on LEGAL-ASSET-30d47fccd7c65f45 recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-5fc9e45b889f41d1. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Kubernetes audit on OPERATIONS-ASSET-e5571d0159c5e55b recorded that a pod was created with privileged execution enabled. The event references principal-4016297e67e67765. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Oauth audit on SALES-ASSET-8a294b7f6b4fb5ec recorded that an application received consent for additional account scopes. The event references principal-4be7952cadd1c600. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Cloud identity audit on OPERATIONS-ASSET-e9ea023dcfe573c8 recorded that a principal assumed a role in another account. The event references principal-33e2cf770673f137. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-a31063e63837, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Storage audit on LEGAL-ASSET-5cc263cd7974e410 recorded that a session deleted several storage snapshots. The event references principal-548b73b08858de12. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-8cde7188eaad explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Repository audit on FINANCE-ASSET-dc6e3bd56c8a0a87 recorded that a repository collaborator received elevated permissions. The event references principal-28c1f6e75f00c284. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Change CHG-77e5e3928a51 lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Firewall audit on PEOPLE-ASSET-957a449c8e927512 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-3d550d011d922017. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Backup audit on PEOPLE-ASSET-90b00913ef4755f4 recorded that a backup retention policy was shortened. The event references principal-069c9474003b2644. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Change CHG-f767be67e841 lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Oauth audit on FINANCE-ASSET-ab8c40ef4ea54ef3 recorded that an application received consent for additional account scopes. The event references principal-c6dc8dd297f2cce8. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Device and file audit on LEGAL-ASSET-e36229f519715f46 recorded that files were copied to a removable storage device. The event references principal-ecac25dd7192fc25. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Systemd audit on SALES-ASSET-4e41129f633ac17f recorded that a service unit file was changed and the unit reloaded. The event references principal-6e1812150b898dbc. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-ffa9ced26248 before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Key service audit on PEOPLE-ASSET-51157cbfcf0e7f8b recorded that a principal issued a burst of key-service decrypt requests. The event references principal-8c512aac8f2c3631. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Package registry audit on PEOPLE-ASSET-63788b9d7987296c recorded that a principal published a new package version. The event references principal-1efd21efeb7b167e. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Task scheduler audit on SALES-ASSET-14a4b633fa3add9a recorded that a scheduled task was registered to execute a program at logon. The event references principal-bc7f1b7e6f9cd150. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Dhcp telemetry on RESEARCH-ASSET-e4b53bee781b0891 recorded that a server issued DHCP offers on a monitored segment. The event references principal-7d24baa0336a4972. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Secret manager audit on SALES-ASSET-b73f8978ef6e4f27 recorded that a workload read several secret versions. The event references principal-d6b84c181926e6a9. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Ci audit on RESEARCH-ASSET-1bb40eb620dce13c recorded that a build pipeline definition gained a new execution step. The event references principal-1e7493e87ff48bbe. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Cloud control audit on RESEARCH-ASSET-7f111a5abf79c08a recorded that a session deleted a group of cloud resources. The event references principal-e374d397f062ff2d. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Service audit on PEOPLE-ASSET-7556bd332c3c0972 recorded that a remote service-control request created and started a temporary service. The event references principal-40ab931ed8bd0b59. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Waf logs on ENGINEERING-ASSET-155d31939b4a4ab3 recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-a5bfd2692d01cf27. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-8dcf77a70d4e, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Federation audit on ENGINEERING-ASSET-ed48b05a54cba0b4 recorded that a tenant federation setting was updated. The event references principal-7dac1305cd5fd7e7. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Repository audit on COMMUNICATIONS-ASSET-fc7d932dec68a3a4 recorded that a user cloned several source repositories. The event references principal-f9163c8da3ccc09a. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-e6e789e059aa specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Resolver logs on SUPPORT-ASSET-b02540e08d1a5e1b recorded that a client requested many long, high-entropy DNS labels. The event references principal-ac999136f4795cef. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Wmi audit on PROCUREMENT-ASSET-fda18a4350cff1b3 recorded that a management request started a process through WMI. The event references principal-cba091012017387e. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Service audit on PEOPLE-ASSET-222cba6353f1d99f recorded that a new automatically started service was registered. The event references principal-e5172d8225074491. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Device and file audit on SUPPORT-ASSET-05bbaad00af727ab recorded that files were copied to a removable storage device. The event references principal-dedda897251ae8fc. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-aae8c88a75e5, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Wmi audit on SUPPORT-ASSET-3ffcf7de08c7ab9e recorded that a management request started a process through WMI. The event references principal-6bf936da5c9a2c76. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Task scheduler audit on PROCUREMENT-ASSET-bd3697f2e2b8950e recorded that a scheduled task was registered to execute a program at logon. The event references principal-1483881099fae9be. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Process audit on RESEARCH-ASSET-701eef6083bb4949 recorded that a Python interpreter loaded a script and contacted a service. The event references principal-9ed7f8cc72bbc316. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-bc02905e9265 specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Driver audit on OPERATIONS-ASSET-16afbb03ee82c54d recorded that a kernel driver was loaded after a package installation. The event references principal-32362e7a45f17c8f. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Oauth audit on COMMUNICATIONS-ASSET-d085212f92517588 recorded that an application received consent for additional account scopes. The event references principal-410957c7717cf0fe. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Agent audit on LEGAL-ASSET-6d17adf81f6fe3af recorded that a privileged session changed endpoint monitoring settings. The event references principal-f72780533376e28a. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Change CHG-621e843eee55 lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Event service audit on FINANCE-ASSET-9334935a696bff2c recorded that an event log was cleared by a privileged request. The event references principal-f4f6381e73c7f8ed. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Ssh audit on FINANCE-ASSET-370d0df1776daaea recorded that an SSH session opened and requested elevated command execution. The event references principal-d8496f14d2489876. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-75ec249596ca, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Module audit on PROCUREMENT-ASSET-234ebd90da532d08 recorded that a process loaded a library from an application-local directory. The event references principal-2bfaedc31b23b886. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Cloud control audit on LEGAL-ASSET-57d9881033f6b349 recorded that resources were created in a region with little prior activity. The event references principal-3d1e3e3a52fd0eed. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Identity audit on SUPPORT-ASSET-9a791522c1b9c744 recorded that an account password was reset through a recovery workflow. The event references principal-bd3f8b10beb2211f. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-85f47412c6b8 explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Storage audit on OPERATIONS-ASSET-29e0421fa3b9bb88 recorded that an object-storage access policy was broadened. The event references principal-e4fd29cc648a5ac6. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Firewall audit on COMMUNICATIONS-ASSET-4f1cc73dbbdce003 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-3c942f0a8856cd1e. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-ae2eb5fa3a35 before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Kubernetes audit on COMMUNICATIONS-ASSET-789b240d08ec701b recorded that a pod was created with privileged execution enabled. The event references principal-bd54f828538e68ca. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-2e61af5c938d specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Ci secret audit on COMMUNICATIONS-ASSET-d9b1648a2cfcda09 recorded that a build job requested a protected pipeline secret. The event references principal-8fc1bbd9d306c19b. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-b3f8a019214e specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Windows logon audit on SALES-ASSET-6ef3ee3501c6fc3e recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-9c0f223e81092f12. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Repository audit on LEGAL-ASSET-d4c7f3d667dee146 recorded that a user cloned several source repositories. The event references principal-0ab147f1f9481604. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Event service audit on ENGINEERING-ASSET-93dff18c1d7d23e9 recorded that an event log was cleared by a privileged request. The event references principal-32227ffe2b6b23ca. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-cb676adb6697 explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Package registry audit on PEOPLE-ASSET-63788b9d7987296c recorded that a principal published a new package version. The event references principal-1efd21efeb7b167e. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-ad609ea87d3c, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Repository audit on PEOPLE-ASSET-ab514f2b7cf1ca44 recorded that a repository collaborator received elevated permissions. The event references principal-49f43d9a0cf7b13c. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Database audit on COMMUNICATIONS-ASSET-4fefa2aaca8d930a recorded that a session changed a database table definition. The event references principal-257c7d24c9971d35. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-42eab180e7df match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Process audit on SALES-ASSET-d7499e681a58affc recorded that a JavaScript interpreter executed a local script. The event references principal-ce0d21f659b72ac8. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Identity audit on LEGAL-ASSET-3e81b75ec6767272 recorded that repeated failed sign-ins were recorded for an account. The event references principal-4e9f85f638a1922a. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Share audit on SUPPORT-ASSET-642a0478e0fea4be recorded that a new network file share was published. The event references principal-d39d2cce091886dd. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Kubernetes audit on ENGINEERING-ASSET-cad5b32322e2d059 recorded that a pod was created with privileged execution enabled. The event references principal-b5a63a5d1fffe886. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Secret manager audit on ENGINEERING-ASSET-c96b6e8c112e5ab0 recorded that a workload read several secret versions. The event references principal-24b9130cfaf6e9ca. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Driver audit on SALES-ASSET-74116b6362e956da recorded that a kernel driver was loaded after a package installation. The event references principal-9eaf8c722428f29b. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-65b9697dae48 match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Configuration audit on COMMUNICATIONS-ASSET-6d0a4b6d77bc51b5 recorded that a client proxy setting was changed. The event references principal-096d695d5dfbc71f. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Oauth audit on RESEARCH-ASSET-0631ea2256cf662a recorded that an application received consent for additional account scopes. The event references principal-8da4697a549d31b3. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-97759d66f964 specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Winrm audit on LEGAL-ASSET-6240747fe412756f recorded that a remote management session invoked a command on a managed host. The event references principal-bff5de31e17ff348. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"File audit on SALES-ASSET-f998f822d677efcd recorded that a process rewrote multiple files into encrypted containers. The event references principal-354f7ba2d1c31de7. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Storage audit on SUPPORT-ASSET-4d8e24bcff05f227 recorded that an object-storage access policy was broadened. The event references principal-5112ec3a6a51c1b1. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Vpn audit on RESEARCH-ASSET-f104c6cff8b4f120 recorded that a remote-access VPN session was established. The event references principal-18bc30314e242812. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-42cb4b7d1811 accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Repository audit on PEOPLE-ASSET-e8dfe6d75dbb8e1e recorded that a user cloned several source repositories. The event references principal-e971d955c552fbff. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Cron audit on PEOPLE-ASSET-4b3199ab3c63dd2d recorded that a recurring job definition was added to the system schedule. The event references principal-f1110cbb064f6627. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Package registry audit on RESEARCH-ASSET-b42ad559dc38cada recorded that a principal published a new package version. The event references principal-ae25582585615c9e. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Kubernetes audit on PEOPLE-ASSET-95c9822ffcf4a444 recorded that a cluster admission policy was changed. The event references principal-e51b094fe6b69872. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Package registry audit on LEGAL-ASSET-904ec76dbb996774 recorded that a principal published a new package version. The event references principal-3920a37e9b8e2b42. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-ebff72a828ec match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Resolver logs on PEOPLE-ASSET-aa9ea5738fc3afe1 recorded that a client requested many long, high-entropy DNS labels. The event references principal-bd6f946855b371b5. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Registry audit on SUPPORT-ASSET-f57e1958aa803333 recorded that a workload pulled a container image from a registry. The event references principal-10cd1718e32b6b5f. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Package registry audit on SALES-ASSET-70769ae6745858de recorded that a principal published a new package version. The event references principal-06efaa74600c0f91. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Identity audit on PROCUREMENT-ASSET-847c16861843d993 recorded that repeated failed sign-ins were recorded for an account. The event references principal-177e5d83a23e0f5b. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Database audit on RESEARCH-ASSET-d8c71a5a44c49e60 recorded that a session changed a database table definition. The event references principal-355812fdc0609439. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Kubernetes audit on COMMUNICATIONS-ASSET-4eb386b59cd197fa recorded that a cluster admission policy was changed. The event references principal-6713342ad2d170de. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Service audit on ENGINEERING-ASSET-5be63ef6d4ef079d recorded that a remote service-control request created and started a temporary service. The event references principal-bd2813d9252e7fbb. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-b730e8e4f2a0 explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Event service audit on COMMUNICATIONS-ASSET-a0753c1183185be8 recorded that an event log was cleared by a privileged request. The event references principal-3da9da5b32a84636. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Cloud control audit on PEOPLE-ASSET-357f734fad0406df recorded that a session deleted a group of cloud resources. The event references principal-50a694af17f32a70. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Process audit on PEOPLE-ASSET-2c32b67a1236291b recorded that a remote-support application started an interactive session. The event references principal-3d51474c05227a94. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Repository audit on SUPPORT-ASSET-fb6027084fb1957b recorded that a user cloned several source repositories. The event references principal-6318dd66af34e88b. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Gateway logs on SALES-ASSET-712c30d2818c912a recorded that a client established a long-lived encapsulated network session. The event references principal-0cbf398f28282f6a. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-49ebbc930e0e explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Dns control audit on ENGINEERING-ASSET-62a2603633015b4a recorded that an authoritative DNS record was updated. The event references principal-38391a49d25a310a. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Application audit on ENGINEERING-ASSET-0a500e9acaab2792 recorded that an application requested repeated screen captures. The event references principal-f9139e2001fef8f3. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-81d378563639 before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Process audit on RESEARCH-ASSET-4c23face5574e971 recorded that a JavaScript interpreter executed a local script. The event references principal-4325acfa278d2f70. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Change CHG-f059629d83f7 lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Cloud identity audit on SUPPORT-ASSET-0acaf32cb86c9787 recorded that a new programmatic access key was issued to a principal. The event references principal-f4c6ed272feaab73. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-c5f9036f50dc specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Winrm audit on SALES-ASSET-53a0ec06a529813d recorded that a remote management session invoked a command on a managed host. The event references principal-d315b25d4a3677cf. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Identity audit on LEGAL-ASSET-f678141e2b084a32 recorded that an account registered a new MFA method. The event references principal-500c71ca31b016a9. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Driver audit on ENGINEERING-ASSET-aa761eb37a133a6c recorded that a kernel driver was loaded after a package installation. The event references principal-b792fcefc38ccc53. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Event service audit on LEGAL-ASSET-1725494bd06479c8 recorded that an event log was cleared by a privileged request. The event references principal-2d006b9d45394524. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Function audit on SUPPORT-ASSET-639b47faa57b7d52 recorded that a serverless function package and execution settings were updated. The event references principal-142321e2377f77dd. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Windows logon audit on LEGAL-ASSET-30d47fccd7c65f45 recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-5fc9e45b889f41d1. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"File audit on PEOPLE-ASSET-572ab49b4fda25fd recorded that access permissions were broadened on a directory tree. The event references principal-892e9ce9179f90fe. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-abbd48f2b350 match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"File audit on PEOPLE-ASSET-cc74b22d2c2ca8f7 recorded that a process compressed files from several directories into an archive. The event references principal-e9c54c5535050840. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Winrm audit on ENGINEERING-ASSET-6e5e1ed61987467a recorded that a remote management session invoked a command on a managed host. The event references principal-c372b39c0d58be55. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Module audit on COMMUNICATIONS-ASSET-e298c38c58f7c346 recorded that a process loaded a library from an application-local directory. The event references principal-dd8d62077451bf1c. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Repository audit on RESEARCH-ASSET-ddfa89ff412603e8 recorded that a user cloned several source repositories. The event references principal-a086fb65d451cd31. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"File audit on PEOPLE-ASSET-a99509e663c1444d recorded that a process rewrote multiple files into encrypted containers. The event references principal-dc7744cab585a5e1. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Event service audit on SALES-ASSET-c924bb512f8f20fd recorded that an event log was cleared by a privileged request. The event references principal-c440dcbeadedc4d2. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Cloud control audit on SUPPORT-ASSET-e66fe35db626a7f0 recorded that resources were created in a region with little prior activity. The event references principal-84f7c4bc4b40ce6e. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Proxy logs on OPERATIONS-ASSET-63a9838a229b6bdc recorded that a client transferred a large payload to an external storage endpoint. The event references principal-1a271b9f4504e35e. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Registry audit on OPERATIONS-ASSET-bb2e321557973238 recorded that a registry logon-start entry was created. The event references principal-48a0f7ab86053bfa. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Pki audit on SUPPORT-ASSET-70be4dd0be19b589 recorded that a principal requested a certificate using an authentication template. The event references principal-3490e3ca6541e91e. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Process audit on FINANCE-ASSET-565f2ed301684671 recorded that a remote-support application started an interactive session. The event references principal-a4a07392170d1084. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Cloud identity audit on OPERATIONS-ASSET-04350815f02c233e recorded that a new programmatic access key was issued to a principal. The event references principal-3f0b6fed7f9bbd92. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-e0988b378b33 specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Backup audit on PROCUREMENT-ASSET-8055bd5873ef3941 recorded that a backup retention policy was shortened. The event references principal-ab63e55288bca196. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Dns server audit on LEGAL-ASSET-9a776b98cec96a9e recorded that a client requested a DNS zone transfer. The event references principal-b7047a9785be46d4. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Firewall audit on SALES-ASSET-67b90170bfed122f recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-2766646810a01a28. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-5151656f7a11 accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Script audit on OPERATIONS-ASSET-df5c95ab3d436943 recorded that a script interpreter decoded an encoded argument before execution. The event references principal-d244a19c467082bb. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Repository audit on SALES-ASSET-b9ab0defeef57d69 recorded that a user cloned several source repositories. The event references principal-0da3c44a52b416ce. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Storage access logs on PROCUREMENT-ASSET-8beb52fc6c4219bf recorded that a principal downloaded many objects from a storage bucket. The event references principal-de077f5f8d45beed. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Process audit on SALES-ASSET-c1342eb6176b4ffa recorded that a Python interpreter loaded a script and contacted a service. The event references principal-e11956d74b8d7b52. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Api gateway logs on SALES-ASSET-67b00a7811823c9c recorded that a client issued a burst of API requests. The event references principal-0a02b6edf23f48b5. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Proxy logs on PEOPLE-ASSET-47b1cfa33ae643a0 recorded that a client transferred a large payload to an external storage endpoint. The event references principal-eefc70a315bcfb3b. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Firewall audit on PROCUREMENT-ASSET-2bed3490436bbbc8 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-90a45122531200f3. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Kerberos audit on ENGINEERING-ASSET-ca968191bd4b09c5 recorded that an account requested service tickets for multiple services. The event references principal-48c928131e4a9922. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Certificate audit on ENGINEERING-ASSET-9451d5f5fd9b7794 recorded that a service certificate was replaced. The event references principal-a6fab514c28c1ba9. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Switch telemetry on PEOPLE-ASSET-2fae865ac519b354 recorded that an address mapping changed repeatedly on a local segment. The event references principal-cadf13732271e411. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Kubernetes audit on LEGAL-ASSET-360df78a99aa884c recorded that a cluster admission policy was changed. The event references principal-fdbbb745932ee2f1. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-1c156e162697 explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Application audit on COMMUNICATIONS-ASSET-365eaf894be6367d recorded that an application read clipboard contents repeatedly. The event references principal-c9d903188ad53746. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Backup audit on SUPPORT-ASSET-cc26a0f722f080c9 recorded that a backup retention policy was shortened. The event references principal-d64cfde7265390a0. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"File audit on FINANCE-ASSET-2a7828c17a1b3f24 recorded that a shell startup profile gained an additional command. The event references principal-4b7e3cd5eb46c9e6. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Storage audit on LEGAL-ASSET-2e9a3d1f59ced5f4 recorded that an object-storage access policy was broadened. The event references principal-aece214cd9523226. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Runtime audit on OPERATIONS-ASSET-b6b114583f048adf recorded that a process connected to the container runtime socket. The event references principal-2a53a47b4b50aacf. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Database audit on PROCUREMENT-ASSET-e086d2946f81e9d3 recorded that a session read several tables and exported the query result. The event references principal-6283c0702f8c752e. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Assessment SEC-1f6dc4343f4f explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Waf logs on OPERATIONS-ASSET-b7ed82085f777d6d recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-82b5142e40756445. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-ecba602d6c78 accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Process audit on PROCUREMENT-ASSET-e094a3806b86f26f recorded that a remote-support application started an interactive session. The event references principal-0e21b55912ebea78. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-c24f1a08e5ff match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Service audit on OPERATIONS-ASSET-fd16a6acf8f54a9a recorded that a new automatically started service was registered. The event references principal-c9af46ed7e55064b. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Identity audit on PEOPLE-ASSET-d81992a54d0e0cd4 recorded that a service account established an interactive session. The event references principal-0bc399328dfcae48. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Repository audit on RESEARCH-ASSET-ddfa89ff412603e8 recorded that a user cloned several source repositories. The event references principal-a086fb65d451cd31. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Device and file audit on LEGAL-ASSET-e36229f519715f46 recorded that files were copied to a removable storage device. The event references principal-ecac25dd7192fc25. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Flow logs on FINANCE-ASSET-b04c464556b8fa8d recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-4fa1efc3a212390d. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-aec5cf47c772 before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Driver audit on PROCUREMENT-ASSET-caa474ba78b6dce6 recorded that a kernel driver was loaded after a package installation. The event references principal-c43c37da7fba502b. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Process audit on FINANCE-ASSET-9d45d520b4a54280 recorded that a Python interpreter loaded a script and contacted a service. The event references principal-d052a3f1c4010987. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-698189598bcc accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Cloud identity audit on RESEARCH-ASSET-39f1c4acdb98407c recorded that a new programmatic access key was issued to a principal. The event references principal-16f1be9653031bee. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Change CHG-5e8a904eb341 lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Mfa audit on LEGAL-ASSET-e69fa0a56ff82707 recorded that multiple MFA challenges were issued during a short interval. The event references principal-f4248a85a02aa075. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Change CHG-75e8a7b4c9af lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Switch telemetry on SUPPORT-ASSET-8a0f455136f22cce recorded that an address mapping changed repeatedly on a local segment. The event references principal-598fd0cdb7a2c2dd. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"File access audit on PROCUREMENT-ASSET-0b755d0602adf157 recorded that a process opened a local credential-store file. The event references principal-7e6f29a9069cca6a. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Cloud control audit on COMMUNICATIONS-ASSET-6f90d32e2d49796b recorded that resources were created in a region with little prior activity. The event references principal-f5034ed11bd41e3e. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-0febd6f3bccc match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Ci secret audit on FINANCE-ASSET-b6445d71bd651026 recorded that a build job requested a protected pipeline secret. The event references principal-634acd477e34564f. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-070a6600c827 match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Vpn audit on SUPPORT-ASSET-e419f3a293f3417a recorded that a remote-access VPN session was established. The event references principal-09df6291fa9e8663. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Windows logon audit on SALES-ASSET-6ef3ee3501c6fc3e recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-9c0f223e81092f12. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Compute audit on RESEARCH-ASSET-d341eca93691633b recorded that a principal launched multiple compute instances. The event references principal-cf04d4cb340e6373. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Kubernetes audit on PROCUREMENT-ASSET-8857c7021ba70cdd recorded that a cluster admission policy was changed. The event references principal-0637e683dcd7afbd. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Security retest SEC-049772ba9b46 covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Registry audit on PEOPLE-ASSET-2d7ca72857a14112 recorded that a workload pulled a container image from a registry. The event references principal-f31f9ebfd4a3d389. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Firewall audit on LEGAL-ASSET-a8345e2e1a01ff48 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-74a2c9033c8d23b7. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Service audit on FINANCE-ASSET-271527485b0e477e recorded that a remote service-control request created and started a temporary service. The event references principal-31971ac078081c89. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Change CHG-3ef78a9e1b77 lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Code integrity audit on COMMUNICATIONS-ASSET-ae65063c9a0dd2a0 recorded that an executable without a publisher signature started from a writable directory. The event references principal-32fc5fcb369ae6d2. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Backup audit on PROCUREMENT-ASSET-8055bd5873ef3941 recorded that a backup retention policy was shortened. The event references principal-ab63e55288bca196. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-94e5889ec9ed match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Mail and proxy logs on PROCUREMENT-ASSET-f73ebff8c2f46ccc recorded that a user opened a URL delivered in an email message. The event references principal-81190b386823c031. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Mail audit on FINANCE-ASSET-c2947168e63669b0 recorded that an account received delegated access to a mailbox. The event references principal-33d9797e6b81280e. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-a9475594c02b, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Cloud control audit on RESEARCH-ASSET-2cbe7527ba09f822 recorded that resources were created in a region with little prior activity. The event references principal-3490db46f4cacc07. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-b1257e937bb3 match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Group audit on ENGINEERING-ASSET-d30b74960b951b72 recorded that an account was added to a privileged local group. The event references principal-81526d7aed4e1797. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Driver audit on RESEARCH-ASSET-5b972011692602fc recorded that a kernel driver was loaded after a package installation. The event references principal-71a994ae28cc3c7a. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-334d91865b6f before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Cloud identity audit on OPERATIONS-ASSET-04350815f02c233e recorded that a new programmatic access key was issued to a principal. The event references principal-3f0b6fed7f9bbd92. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Office audit on SALES-ASSET-bd4695abc7ff04ad recorded that a document macro launched a child interpreter. The event references principal-9bfaf02fa70a4f6b. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-17e48eb573c0 explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Oauth audit on COMMUNICATIONS-ASSET-d085212f92517588 recorded that an application received consent for additional account scopes. The event references principal-410957c7717cf0fe. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Kubernetes audit on FINANCE-ASSET-d7b2da83577ab38d recorded that a pod was created with privileged execution enabled. The event references principal-5177d7ecbc348aa2. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-574fc4b59238 match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Storage audit on ENGINEERING-ASSET-cd853382d1a0a281 recorded that a session deleted several storage snapshots. The event references principal-39dd7d8e5cbb8cc6. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-835456d8a6ed match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Network control audit on OPERATIONS-ASSET-bd217021cb34aa91 recorded that a cloud security group gained a broad ingress rule. The event references principal-2dc6c3bb2730ad8e. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Task scheduler audit on RESEARCH-ASSET-21bf6f06fdc5117a recorded that a scheduled task was registered to execute a program at logon. The event references principal-0cdfb8ebb9ac46b3. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Federation audit on RESEARCH-ASSET-85e9941ba25e96bb recorded that a tenant federation setting was updated. The event references principal-863b72c786eda302. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Cloud identity audit on LEGAL-ASSET-7e0cfa13cd7f5efc recorded that a new programmatic access key was issued to a principal. The event references principal-578071150bb49966. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Security retest SEC-24b0ea50d97e covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Windows logon audit on PEOPLE-ASSET-45fa406199d2c14e recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-291516c4491afd57. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Driver audit on ENGINEERING-ASSET-aa761eb37a133a6c recorded that a kernel driver was loaded after a package installation. The event references principal-b792fcefc38ccc53. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Mail and proxy logs on RESEARCH-ASSET-0d6948f11ee5b28e recorded that a user opened a URL delivered in an email message. The event references principal-fdb003c9c4c80093. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Script audit on PROCUREMENT-ASSET-d3383e3f3b9c4acb recorded that a script interpreter decoded an encoded argument before execution. The event references principal-b7570e0e965cd679. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Cron audit on COMMUNICATIONS-ASSET-d8fc966dee08cb0c recorded that a recurring job definition was added to the system schedule. The event references principal-703666e706c43b5e. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-682a96c4ad02 explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Mail and proxy logs on OPERATIONS-ASSET-7ac4ed112230cbe5 recorded that a user opened a URL delivered in an email message. The event references principal-b1bb74d41be20948. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-60d3b9591751 match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Cloud identity audit on COMMUNICATIONS-ASSET-a2643d4e14311066 recorded that a principal assumed a role in another account. The event references principal-3ce172a931fefefa. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Identity audit on SUPPORT-ASSET-3fdea2c42e845651 recorded that a service account established an interactive session. The event references principal-6872260152bd6bd7. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Cloud control audit on FINANCE-ASSET-874d671033c104d1 recorded that a cloud logging destination was disabled. The event references principal-b52f94a7d99dc7bf. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Registry audit on FINANCE-ASSET-6f5ecd36af234140 recorded that a registry logon-start entry was created. The event references principal-ce9587e0dadb3215. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Federation audit on OPERATIONS-ASSET-d2752a593a5fec4b recorded that a tenant federation setting was updated. The event references principal-5f95a2859726a629. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Change CHG-5226f64d676d lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Cron audit on RESEARCH-ASSET-25e2f241c7b3849f recorded that a recurring job definition was added to the system schedule. The event references principal-2a055f75f46408a1. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-5d2a4fb54c81 before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"File audit on ENGINEERING-ASSET-b0203944931a2946 recorded that a process compressed files from several directories into an archive. The event references principal-c59c85332aba5a32. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-058df65fd991 explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Policy audit on SALES-ASSET-8b2e5805c0958f81 recorded that an audit policy was changed to collect fewer event categories. The event references principal-55b368edee8e470a. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-d327962a3c85 specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Dhcp telemetry on SALES-ASSET-b9c8816924ddc5c0 recorded that a server issued DHCP offers on a monitored segment. The event references principal-c2f4772a3b098c6c. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Directory audit on PEOPLE-ASSET-37791232d78efc05 recorded that a principal requested directory replication data. The event references principal-55f0d12673ae40b1. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Driver audit on RESEARCH-ASSET-5b972011692602fc recorded that a kernel driver was loaded after a package installation. The event references principal-71a994ae28cc3c7a. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Storage audit on FINANCE-ASSET-768fdc22d9585f23 recorded that an object-storage access policy was broadened. The event references principal-18ac2fe076b447b0. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Oauth audit on OPERATIONS-ASSET-1d059cb4cf3d2fe1 recorded that an application received consent for additional account scopes. The event references principal-68400bad9534528c. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-3068d84b0cac match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"File audit on FINANCE-ASSET-2004b1d4a03fd309 recorded that a process rewrote multiple files into encrypted containers. The event references principal-9560a602e126689a. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Registry audit on ENGINEERING-ASSET-bd489c9ae7fbc817 recorded that a workload pulled a container image from a registry. The event references principal-95061e15f3e7bbec. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-4ff0a6f52482 covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Windows logon audit on SUPPORT-ASSET-b7addff92f67af33 recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-5b8a266b76f35fee. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Driver audit on PEOPLE-ASSET-9e9f7519775a6002 recorded that a kernel driver was loaded after a package installation. The event references principal-4bafb24bfe647837. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Process audit on OPERATIONS-ASSET-495b246de141f994 recorded that a Python interpreter loaded a script and contacted a service. The event references principal-3264c9e681183a21. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Repository audit on LEGAL-ASSET-d4c7f3d667dee146 recorded that a user cloned several source repositories. The event references principal-0ab147f1f9481604. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Storage access logs on SUPPORT-ASSET-467cdf660d5e57c4 recorded that a principal downloaded many objects from a storage bucket. The event references principal-83eeaee20b7f40f8. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Mfa audit on FINANCE-ASSET-77a6969db5ae1147 recorded that multiple MFA challenges were issued during a short interval. The event references principal-660a5b1395e78ef7. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-40574d3299a4 match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Cloud identity audit on COMMUNICATIONS-ASSET-8660c1612914f6bd recorded that a principal received a policy granting additional permissions. The event references principal-796bfc42ecc484c7. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Mail audit on SUPPORT-ASSET-d04332aa87461fec recorded that an account received delegated access to a mailbox. The event references principal-4bd49edb0535ebaf. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-4502587df860 match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Waf logs on OPERATIONS-ASSET-b7ed82085f777d6d recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-82b5142e40756445. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-ecba602d6c78 match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Dhcp telemetry on FINANCE-ASSET-99d84bf5e5de071b recorded that a server issued DHCP offers on a monitored segment. The event references principal-e238480421ab2c07. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Assessment SEC-5c42053a6603 explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"File audit on FINANCE-ASSET-d2b45ac726791f9b recorded that a process deleted many files within a short interval. The event references principal-e041b8a80436a62f. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Repository audit on SUPPORT-ASSET-f2c722947f994337 recorded that a repository collaborator received elevated permissions. The event references principal-81983e01bdfb552d. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-a6357ab061c5, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"File audit on OPERATIONS-ASSET-f5bfac37e0e6e52e recorded that access permissions were broadened on a directory tree. The event references principal-c5603af4c6f0f506. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-7bb2afdb4fe1 before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Firewall audit on RESEARCH-ASSET-0236b24f6c7b0e03 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-582ef1b1560e6fc6. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Dhcp telemetry on SUPPORT-ASSET-ea5b723e111a60c0 recorded that a server issued DHCP offers on a monitored segment. The event references principal-f0fe04f7d6936857. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Systemd audit on SUPPORT-ASSET-38d3359b892c66ba recorded that a service unit file was changed and the unit reloaded. The event references principal-fbace7ec59135a92. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Mfa audit on SALES-ASSET-413206c0391aae90 recorded that multiple MFA challenges were issued during a short interval. The event references principal-13b992911a08e483. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-95a08f3af89a specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Flow logs on SALES-ASSET-e03d7f92d970afc6 recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-7f74331f29d46d56. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Database audit on SALES-ASSET-849ddfe1a9053808 recorded that a session changed a database table definition. The event references principal-425b4fae9e8852ef. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Pki audit on SALES-ASSET-34ed542c065cfc50 recorded that a principal requested a certificate using an authentication template. The event references principal-bd8f51ad03539dfb. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-9999de313145 before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"File access audit on SUPPORT-ASSET-701fe361a48ad8d6 recorded that a process opened a local credential-store file. The event references principal-0923914a571f26a3. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Change CHG-a74161f6314c lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Repository audit on PROCUREMENT-ASSET-032fc4cf1761029e recorded that a repository collaborator received elevated permissions. The event references principal-c9c8d15f73a824e8. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Identity audit on FINANCE-ASSET-5eeb4551c8b1c0e3 recorded that an account registered a new MFA method. The event references principal-0a574aaa6eaa69b8. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Share audit on LEGAL-ASSET-f4d3a91d6248c724 recorded that a new network file share was published. The event references principal-9174cfcb163194b8. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-89c133546cc1 match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Process access audit on PROCUREMENT-ASSET-a371e419fb9da077 recorded that a process requested read access to another process memory space. The event references principal-47b9eca6b126bee7. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Database audit on OPERATIONS-ASSET-302e0f5dfef6781b recorded that a session read several tables and exported the query result. The event references principal-22fca2204489e9a2. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Application audit on SUPPORT-ASSET-0d07ed7bee9ce5d7 recorded that an application requested repeated screen captures. The event references principal-1f37918578f8f184. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Firewall audit on FINANCE-ASSET-d80ee8804a4ec6b6 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-b21644c32449b9a0. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Compute audit on SUPPORT-ASSET-723f94949265b3d7 recorded that a principal launched multiple compute instances. The event references principal-1d5de0b683f369a9. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-9db8a9c3138c accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Smb audit on LEGAL-ASSET-cbd503b9d9dce0b4 recorded that a session enumerated a file share and read multiple files. The event references principal-308281e8cf667587. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"File audit on ENGINEERING-ASSET-34a8ce1c539d9368 recorded that a process deleted many files within a short interval. The event references principal-c1c689ef96642a7c. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Code integrity audit on ENGINEERING-ASSET-bc88477a091db102 recorded that an executable without a publisher signature started from a writable directory. The event references principal-26a79bf54e5ed1d5. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Kubernetes audit on RESEARCH-ASSET-7116d85c35ffeedd recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-5cfd10bdd7720813. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Kerberos audit on FINANCE-ASSET-0b0adcb58a633d21 recorded that an account requested service tickets for multiple services. The event references principal-bbbe909c0396acf3. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Dns server audit on RESEARCH-ASSET-ea10daa512b8b485 recorded that a client requested a DNS zone transfer. The event references principal-8e8e3e27caaa4cef. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Kubernetes audit on RESEARCH-ASSET-e5b9e413bdef9d8d recorded that a pod was created with privileged execution enabled. The event references principal-74b8c2bcccc76ba0. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-a34a6108dce2 explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Kubernetes audit on PROCUREMENT-ASSET-fa28de9adbfdddd4 recorded that a pod was created with privileged execution enabled. The event references principal-c0583fecec986fcd. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Change CHG-4afcaed70f26 lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Compute audit on SUPPORT-ASSET-723f94949265b3d7 recorded that a principal launched multiple compute instances. The event references principal-1d5de0b683f369a9. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Account audit on FINANCE-ASSET-00ff9ecf71797cc7 recorded that a local user account was created on a managed system. The event references principal-a4700d3ad9f008de. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-0217d5ba5458 accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Flow logs on LEGAL-ASSET-bb14ef480a9f5aa0 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-343b8b6d62a9710b. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"File audit on PEOPLE-ASSET-df8464b337d342a5 recorded that a process deleted many files within a short interval. The event references principal-f13400db0397fece. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Ci audit on ENGINEERING-ASSET-2c0d231544308107 recorded that a build pipeline definition gained a new execution step. The event references principal-aba5ed9cc375c5ec. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Federation audit on COMMUNICATIONS-ASSET-866384484e84ef96 recorded that a tenant federation setting was updated. The event references principal-e2dd8e40c0e17294. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"File audit on SUPPORT-ASSET-a93f88cca8d4a8b9 recorded that a process rewrote multiple files into encrypted containers. The event references principal-ae3578564d0163ba. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-c48cc454f864 match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"File audit on RESEARCH-ASSET-e7317bc73d028b83 recorded that a process deleted many files within a short interval. The event references principal-2ba5ba91bd6bd5b8. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-67b1b0c0ed83, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Runtime audit on SUPPORT-ASSET-70bd103925bca47e recorded that a process connected to the container runtime socket. The event references principal-cf65589a3d4ad7b6. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Agent audit on FINANCE-ASSET-9e83a9427493fb22 recorded that a privileged session changed endpoint monitoring settings. The event references principal-456dd0970fc81a4c. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Process audit on FINANCE-ASSET-7c0fff41e30d4380 recorded that a JavaScript interpreter executed a local script. The event references principal-5ba5da6cfca5af4e. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Event service audit on FINANCE-ASSET-9334935a696bff2c recorded that an event log was cleared by a privileged request. The event references principal-f4f6381e73c7f8ed. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Change CHG-aa1cb5a12cb4 lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Waf logs on FINANCE-ASSET-2688c7caaa5c3540 recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-fa0ae08c81b790e0. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Event service audit on FINANCE-ASSET-9334935a696bff2c recorded that an event log was cleared by a privileged request. The event references principal-f4f6381e73c7f8ed. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Session audit on SALES-ASSET-e0e65cd3109e663e recorded that the same session token appeared from different client addresses. The event references principal-b32690205f2a72fc. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Wmi audit on OPERATIONS-ASSET-c2921eb1d36d866a recorded that a management request started a process through WMI. The event references principal-1c1a48cb243f47fb. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Flow logs on RESEARCH-ASSET-36f3e51101dc72ca recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-4148cfbbdb30636d. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Change CHG-d4e59646f718 lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Api gateway logs on PROCUREMENT-ASSET-1c1b6a1c5f9b9bd8 recorded that a client issued a burst of API requests. The event references principal-257e72e6a629f939. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Kubernetes audit on COMMUNICATIONS-ASSET-a5023ab9f641c1cb recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-8da42e51a76b5b34. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"File audit on PEOPLE-ASSET-a99509e663c1444d recorded that a process rewrote multiple files into encrypted containers. The event references principal-dc7744cab585a5e1. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-e3f82a6b593a match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"File audit on FINANCE-ASSET-2a7828c17a1b3f24 recorded that a shell startup profile gained an additional command. The event references principal-4b7e3cd5eb46c9e6. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Process audit on COMMUNICATIONS-ASSET-32e7de18e8d35e66 recorded that a Python interpreter loaded a script and contacted a service. The event references principal-2424b5e4e4370c09. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Browser audit on RESEARCH-ASSET-b0be4ff24f6a9c7d recorded that a browser extension with page-reading permissions was installed. The event references principal-c445644ab42572e7. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Kubernetes audit on ENGINEERING-ASSET-af728a774d91dcb8 recorded that a workload mounted a directory from its host filesystem. The event references principal-6a5b731d9f44ffa6. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Switch telemetry on RESEARCH-ASSET-39ecead5bf809d8c recorded that an address mapping changed repeatedly on a local segment. The event references principal-78520d727e00f06a. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Script audit on COMMUNICATIONS-ASSET-ad52eab51d5bfbe3 recorded that a script interpreter decoded an encoded argument before execution. The event references principal-b20c6bb2ef5361bb. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Wmi audit on LEGAL-ASSET-a70f3384c72ee597 recorded that a management request started a process through WMI. The event references principal-d9be46a6c47bd578. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Network control audit on ENGINEERING-ASSET-2d4a799851b7227b recorded that a cloud security group gained a broad ingress rule. The event references principal-5b7cb16d420fdcdc. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-eaa47edc4689 explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Browser audit on LEGAL-ASSET-df49de2f96b43b40 recorded that a browser extension with page-reading permissions was installed. The event references principal-010a6a482ee1c838. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Saas audit on ENGINEERING-ASSET-0edd073ede2359c9 recorded that a user requested a bulk export from a business application. The event references principal-273e879f8b9e8512. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Ci audit on COMMUNICATIONS-ASSET-9c71cbe9ba5a6116 recorded that a build pipeline definition gained a new execution step. The event references principal-0b9701ae91042079. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Script audit on FINANCE-ASSET-8f7a7c5dae3d75b5 recorded that a script interpreter decoded an encoded argument before execution. The event references principal-7a6a17f9162097f1. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-1c375750846b match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Backup audit on LEGAL-ASSET-0b947a06b2f86efb recorded that a backup retention policy was shortened. The event references principal-ec8805dd5dc564d0. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Module audit on COMMUNICATIONS-ASSET-e298c38c58f7c346 recorded that a process loaded a library from an application-local directory. The event references principal-dd8d62077451bf1c. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Backup audit on ENGINEERING-ASSET-e13f2ff83c899d5b recorded that a backup retention policy was shortened. The event references principal-31afc311e47df634. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Cloud control audit on FINANCE-ASSET-f3ec32c70b0e59d9 recorded that resources were created in a region with little prior activity. The event references principal-8d633cfbda070abb. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-12f1b6c04336, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"File audit on OPERATIONS-ASSET-a77dace88afed479 recorded that a process rewrote multiple files into encrypted containers. The event references principal-9bd0bfba4bc5c80f. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Windows logon audit on COMMUNICATIONS-ASSET-6f9244839c2eca95 recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-263d3b9d1be1a7e1. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Configuration audit on OPERATIONS-ASSET-f3ed5a9b931a0951 recorded that a client proxy setting was changed. The event references principal-d8940d417fc4c9bd. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Repository audit on OPERATIONS-ASSET-d75290e6ed1a6d85 recorded that a repository collaborator received elevated permissions. The event references principal-b26cea051978a58c. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-abae77a7202e, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Registry audit on PROCUREMENT-ASSET-76d816b7b04f4b8f recorded that a workload pulled a container image from a registry. The event references principal-12ce95b5667b0630. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Identity audit on OPERATIONS-ASSET-0bbb0193ab08eb6e recorded that a service account established an interactive session. The event references principal-de6a7bc5c123923c. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Group audit on OPERATIONS-ASSET-0c05abbcb3b78111 recorded that an account was added to a privileged local group. The event references principal-67db77b910dcd61e. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Flow logs on PROCUREMENT-ASSET-cd965c50b19b4b1f recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-3abc068e3f191445. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Database audit on PROCUREMENT-ASSET-e086d2946f81e9d3 recorded that a session read several tables and exported the query result. The event references principal-6283c0702f8c752e. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Switch telemetry on PROCUREMENT-ASSET-c13f623edc6be72c recorded that an address mapping changed repeatedly on a local segment. The event references principal-464589d30bf27aee. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Identity audit on SALES-ASSET-2f253fe8393025e1 recorded that an account password was reset through a recovery workflow. The event references principal-95366adc4199c0a7. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Script audit on SALES-ASSET-5accd98a99abf46d recorded that a script interpreter decoded an encoded argument before execution. The event references principal-9d518b079e49f304. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-dbebbafd9030 explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Mfa audit on LEGAL-ASSET-e69fa0a56ff82707 recorded that multiple MFA challenges were issued during a short interval. The event references principal-f4248a85a02aa075. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Gateway logs on SUPPORT-ASSET-bfcdc7fd12a63ce3 recorded that a client established a long-lived encapsulated network session. The event references principal-076e693836d2e9e9. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Directory audit on PEOPLE-ASSET-37791232d78efc05 recorded that a principal requested directory replication data. The event references principal-55f0d12673ae40b1. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-99388695a32a match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Wmi audit on OPERATIONS-ASSET-c2921eb1d36d866a recorded that a management request started a process through WMI. The event references principal-1c1a48cb243f47fb. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Mail and proxy logs on OPERATIONS-ASSET-7ac4ed112230cbe5 recorded that a user opened a URL delivered in an email message. The event references principal-b1bb74d41be20948. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Storage audit on LEGAL-ASSET-2e9a3d1f59ced5f4 recorded that an object-storage access policy was broadened. The event references principal-aece214cd9523226. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Cloud identity audit on ENGINEERING-ASSET-02b155235f1959ea recorded that a principal received a policy granting additional permissions. The event references principal-d5dc51acc5293d03. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Share audit on SALES-ASSET-af32e6af472026fd recorded that a new network file share was published. The event references principal-f1240dad3caae0d8. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Firewall audit on SALES-ASSET-67b90170bfed122f recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-2766646810a01a28. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-5151656f7a11 match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Egress flow logs on PEOPLE-ASSET-9176797d1eb78aff recorded that a workload opened an encrypted connection to an external service. The event references principal-eeab4c2bc996daf9. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Assessment SEC-504c2df20702 explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Federation audit on OPERATIONS-ASSET-d2752a593a5fec4b recorded that a tenant federation setting was updated. The event references principal-5f95a2859726a629. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Pki audit on LEGAL-ASSET-06762de597c73d74 recorded that a principal requested a certificate using an authentication template. The event references principal-39b0053611d607fa. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Mail audit on RESEARCH-ASSET-fad2d601f38f7cda recorded that an account received delegated access to a mailbox. The event references principal-b5e074cc28811f03. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Storage audit on PROCUREMENT-ASSET-f524c33b819a1663 recorded that an object-storage access policy was broadened. The event references principal-daeee49ee65928ba. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Storage audit on COMMUNICATIONS-ASSET-80a867850d28c413 recorded that a session deleted several storage snapshots. The event references principal-fab18c6abd30f04e. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Change CHG-9cc28f996ca4 lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Mail audit on OPERATIONS-ASSET-3a9ba1a13acae41d recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-458bdf5d7e7a4b20. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Agent audit on FINANCE-ASSET-9e83a9427493fb22 recorded that a privileged session changed endpoint monitoring settings. The event references principal-456dd0970fc81a4c. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-4d68cfa77a26 specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Service audit on ENGINEERING-ASSET-ef233e13b4aa7209 recorded that a new automatically started service was registered. The event references principal-aa6e053019f9dc60. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-d54037b9d5d3 specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Backup audit on FINANCE-ASSET-7d6385ebfb9a8a83 recorded that a backup retention policy was shortened. The event references principal-87f1c31296aed897. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Network control audit on OPERATIONS-ASSET-bd217021cb34aa91 recorded that a cloud security group gained a broad ingress rule. The event references principal-2dc6c3bb2730ad8e. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Ci audit on PEOPLE-ASSET-ea14ad85e984ee1f recorded that a build pipeline definition gained a new execution step. The event references principal-02ee8abd42195e24. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Smb audit on LEGAL-ASSET-cbd503b9d9dce0b4 recorded that a session enumerated a file share and read multiple files. The event references principal-308281e8cf667587. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-f3853a780ee6 explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Service audit on ENGINEERING-ASSET-ef233e13b4aa7209 recorded that a new automatically started service was registered. The event references principal-aa6e053019f9dc60. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Runtime audit on PEOPLE-ASSET-616ef8f8f0889aaf recorded that a process connected to the container runtime socket. The event references principal-685ce977f92924b1. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Kubernetes audit on RESEARCH-ASSET-e5b9e413bdef9d8d recorded that a pod was created with privileged execution enabled. The event references principal-74b8c2bcccc76ba0. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Storage audit on LEGAL-ASSET-2e9a3d1f59ced5f4 recorded that an object-storage access policy was broadened. The event references principal-aece214cd9523226. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Change CHG-e06045924ece lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Ci audit on PEOPLE-ASSET-ea14ad85e984ee1f recorded that a build pipeline definition gained a new execution step. The event references principal-02ee8abd42195e24. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Assessment SEC-83102cd2a5b2 explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Dns server audit on SALES-ASSET-76b84b3e5488545e recorded that a client requested a DNS zone transfer. The event references principal-2d34f2bcf00115a7. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Kubernetes audit on OPERATIONS-ASSET-e5571d0159c5e55b recorded that a pod was created with privileged execution enabled. The event references principal-4016297e67e67765. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Ci audit on COMMUNICATIONS-ASSET-9c71cbe9ba5a6116 recorded that a build pipeline definition gained a new execution step. The event references principal-0b9701ae91042079. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Policy audit on SUPPORT-ASSET-6952fff6cd8e7039 recorded that an audit policy was changed to collect fewer event categories. The event references principal-c6ab36fb929298bf. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"File access audit on SALES-ASSET-da211711ae9c0eb7 recorded that a process opened a local credential-store file. The event references principal-d1b0980809a9edd2. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Package registry audit on COMMUNICATIONS-ASSET-7fd940c9dbda3462 recorded that a principal published a new package version. The event references principal-07091e1d888fa67d. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Wmi audit on SUPPORT-ASSET-3ffcf7de08c7ab9e recorded that a management request started a process through WMI. The event references principal-6bf936da5c9a2c76. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Process audit on LEGAL-ASSET-523d2840aded9f3a recorded that a remote-support application started an interactive session. The event references principal-d733a0ecd691110d. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Cron audit on RESEARCH-ASSET-25e2f241c7b3849f recorded that a recurring job definition was added to the system schedule. The event references principal-2a055f75f46408a1. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-5d2a4fb54c81 match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Ci secret audit on COMMUNICATIONS-ASSET-d9b1648a2cfcda09 recorded that a build job requested a protected pipeline secret. The event references principal-8fc1bbd9d306c19b. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Cloud identity audit on LEGAL-ASSET-7e0cfa13cd7f5efc recorded that a new programmatic access key was issued to a principal. The event references principal-578071150bb49966. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Proxy logs on ENGINEERING-ASSET-55fbfe9ce1b9adb6 recorded that a client transferred a large payload to an external storage endpoint. The event references principal-9db93a1b04a04fcd. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-5a18336b0f80 explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Dns server audit on SUPPORT-ASSET-99242b48e0f1290b recorded that a client requested a DNS zone transfer. The event references principal-c5b7de8a13a46984. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-ff24131b9a24 explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Process audit on OPERATIONS-ASSET-4be1d9f7adca7d10 recorded that a remote-support application started an interactive session. The event references principal-85052a5f25abdf7a. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-3503c46a3a3a, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Mail flow logs on SUPPORT-ASSET-4fe85cf52fa083ac recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-b1c48571a99cb1b2. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-636c3872a249 covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Kubernetes audit on PROCUREMENT-ASSET-a846eefa75a51312 recorded that a workload mounted a directory from its host filesystem. The event references principal-0cd6474c03a53052. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Storage audit on PEOPLE-ASSET-4b18ae09e42fe01b recorded that an object-storage access policy was broadened. The event references principal-7721904d8c389cbb. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Runtime audit on RESEARCH-ASSET-1fdd4c74894a8860 recorded that a process connected to the container runtime socket. The event references principal-1fe12f7544607ca6. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Registry audit on PROCUREMENT-ASSET-76d816b7b04f4b8f recorded that a workload pulled a container image from a registry. The event references principal-12ce95b5667b0630. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Smb audit on PEOPLE-ASSET-d3a371e9da6189cb recorded that a session enumerated a file share and read multiple files. The event references principal-4aae8f7eba9ba686. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-40dac43dd55c specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Resolver logs on COMMUNICATIONS-ASSET-064116140685fdd2 recorded that a client requested many long, high-entropy DNS labels. The event references principal-a53098877c1921c0. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Identity audit on SALES-ASSET-17bd921cea441a1f recorded that repeated failed sign-ins were recorded for an account. The event references principal-d02e40aae87e9ff0. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-f3a081c12b89 accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Secret manager audit on FINANCE-ASSET-848c4b906d36b1f9 recorded that a workload read several secret versions. The event references principal-2d99961e29099c47. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Configuration audit on ENGINEERING-ASSET-05746d5c7e76781e recorded that a client proxy setting was changed. The event references principal-f4f857793a1cd276. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Directory audit on COMMUNICATIONS-ASSET-014161d1ab75992f recorded that a principal requested directory replication data. The event references principal-06ff5e4392c8395e. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-0413191c606a before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Smb audit on LEGAL-ASSET-cbd503b9d9dce0b4 recorded that a session enumerated a file share and read multiple files. The event references principal-308281e8cf667587. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Security retest SEC-f3853a780ee6 covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Event service audit on PROCUREMENT-ASSET-1656ac96cf7e6b6f recorded that an event log was cleared by a privileged request. The event references principal-994f7078cfaa2558. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Ssh audit on RESEARCH-ASSET-a4cfbeae0c987bb8 recorded that an SSH session opened and requested elevated command execution. The event references principal-f224386eb3a1c8ae. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Flow logs on SALES-ASSET-60c136594edf1098 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-a5e562da0b238c72. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-3ecdc63d7bea match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Browser audit on FINANCE-ASSET-5beff27234a79da1 recorded that a browser extension with page-reading permissions was installed. The event references principal-f62be1e2c47a255f. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-a02b248736d8 explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Device and file audit on RESEARCH-ASSET-6da8ae6d7bfc1fd2 recorded that files were copied to a removable storage device. The event references principal-6e75da4e311027c4. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Cloud control audit on OPERATIONS-ASSET-ba4ce4cf529ac35c recorded that a session deleted a group of cloud resources. The event references principal-2a7a606b1116d324. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Switch telemetry on FINANCE-ASSET-c82eb7bf49c6713c recorded that an address mapping changed repeatedly on a local segment. The event references principal-24aa90be68c12c8b. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Smb audit on FINANCE-ASSET-c99a2728b7b98f2b recorded that a session enumerated a file share and read multiple files. The event references principal-40d6614472abce2d. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Package registry audit on PROCUREMENT-ASSET-742ad97982b567e2 recorded that a principal published a new package version. The event references principal-5921bb600425987a. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-66cc8f2d0c9f accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Registry audit on ENGINEERING-ASSET-bd489c9ae7fbc817 recorded that a workload pulled a container image from a registry. The event references principal-95061e15f3e7bbec. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Dhcp telemetry on ENGINEERING-ASSET-16a2bd6b5dab3cb6 recorded that a server issued DHCP offers on a monitored segment. The event references principal-d5a61a238fb861fb. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Code integrity audit on FINANCE-ASSET-17d7fd3ccdbe7a13 recorded that an executable without a publisher signature started from a writable directory. The event references principal-8715ecce18f6c074. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Assessment SEC-c7967f3297eb explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Identity audit on RESEARCH-ASSET-77b0ab4459df7f50 recorded that repeated failed sign-ins were recorded for an account. The event references principal-ef9a3ac0fa7044a5. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Script audit on RESEARCH-ASSET-a67da4eb1517ea03 recorded that a script interpreter decoded an encoded argument before execution. The event references principal-e606a4602bed6561. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Security retest SEC-901e29e5ee04 covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Backup audit on LEGAL-ASSET-0b947a06b2f86efb recorded that a backup retention policy was shortened. The event references principal-ec8805dd5dc564d0. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Gateway logs on SALES-ASSET-712c30d2818c912a recorded that a client established a long-lived encapsulated network session. The event references principal-0cbf398f28282f6a. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-49ebbc930e0e specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Kubernetes audit on SALES-ASSET-bd821e033a435876 recorded that a cluster admission policy was changed. The event references principal-57ab3d2d3751af5f. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Mail flow logs on COMMUNICATIONS-ASSET-60efe7c42d543cb2 recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-6db1155a76f69a6b. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Package registry audit on COMMUNICATIONS-ASSET-7fd940c9dbda3462 recorded that a principal published a new package version. The event references principal-07091e1d888fa67d. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Storage access logs on SALES-ASSET-9e32b40d91582c35 recorded that a principal downloaded many objects from a storage bucket. The event references principal-71bb68cca0a6547d. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Identity audit on COMMUNICATIONS-ASSET-2afac15aebb6997b recorded that an account registered a new MFA method. The event references principal-48533b26142b2db4. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Registry audit on OPERATIONS-ASSET-bb2e321557973238 recorded that a registry logon-start entry was created. The event references principal-48a0f7ab86053bfa. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Change CHG-31c8ab46ca2c lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Smb audit on ENGINEERING-ASSET-167b039744d858de recorded that a session enumerated a file share and read multiple files. The event references principal-dae2d90d16568727. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Storage audit on RESEARCH-ASSET-4fe3f3661fdb65de recorded that a session deleted several storage snapshots. The event references principal-c8575d45e94d3ebb. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-58e3441d3a28 specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Oauth audit on PEOPLE-ASSET-f620f4cfac01530c recorded that an application received consent for additional account scopes. The event references principal-0999bb32ee8823f5. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"File audit on ENGINEERING-ASSET-52718af8394d4c73 recorded that a shell startup profile gained an additional command. The event references principal-7fbddd513d8c8d82. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Ci audit on RESEARCH-ASSET-1bb40eb620dce13c recorded that a build pipeline definition gained a new execution step. The event references principal-1e7493e87ff48bbe. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-7f835b5a85ad match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Switch telemetry on ENGINEERING-ASSET-271d6935661ca5b6 recorded that an address mapping changed repeatedly on a local segment. The event references principal-2aa672d045fc50f4. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Storage audit on COMMUNICATIONS-ASSET-80a867850d28c413 recorded that a session deleted several storage snapshots. The event references principal-fab18c6abd30f04e. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-9cc28f996ca4 specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Application audit on COMMUNICATIONS-ASSET-c8d077447f8b8c1d recorded that an application requested repeated screen captures. The event references principal-062e1b2072504f50. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Windows logon audit on COMMUNICATIONS-ASSET-6f9244839c2eca95 recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-263d3b9d1be1a7e1. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Backup audit on OPERATIONS-ASSET-b26fa319d3d0ce69 recorded that a backup retention policy was shortened. The event references principal-428102206d771c95. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Change CHG-840fc1b5aa63 lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Code integrity audit on COMMUNICATIONS-ASSET-ae65063c9a0dd2a0 recorded that an executable without a publisher signature started from a writable directory. The event references principal-32fc5fcb369ae6d2. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-10c6da8b8abc specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Cron audit on PROCUREMENT-ASSET-ccd7b77f6fbe55e6 recorded that a recurring job definition was added to the system schedule. The event references principal-ff6d598ce8d74f2d. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Code integrity audit on LEGAL-ASSET-f6d743064b804557 recorded that an executable without a publisher signature started from a writable directory. The event references principal-4ea2e2cfcda079aa. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-7bbc131e5888 match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Process audit on SUPPORT-ASSET-6869d2722a21fd5c recorded that a Python interpreter loaded a script and contacted a service. The event references principal-f677ab6a5a1c21d4. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-b938cc1adc67 match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Macos launch audit on FINANCE-ASSET-050b0e8279760750 recorded that a launch agent definition was installed in a user context. The event references principal-7354e7b956585560. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"File audit on OPERATIONS-ASSET-f5bfac37e0e6e52e recorded that access permissions were broadened on a directory tree. The event references principal-c5603af4c6f0f506. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Mail audit on COMMUNICATIONS-ASSET-dece9873e2e03f6f recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-3d08b8fe271ddda1. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Share audit on OPERATIONS-ASSET-a9f5766b40361ce4 recorded that a new network file share was published. The event references principal-e591af365aeb634a. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Dns server audit on PROCUREMENT-ASSET-e8eb2bcb15a480a1 recorded that a client requested a DNS zone transfer. The event references principal-937daedbc93fd7dd. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Secret manager audit on RESEARCH-ASSET-9ed518d17fe68d7a recorded that a workload read several secret versions. The event references principal-7f1b48c31f4c5822. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Cron audit on COMMUNICATIONS-ASSET-d8fc966dee08cb0c recorded that a recurring job definition was added to the system schedule. The event references principal-703666e706c43b5e. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Kubernetes audit on SALES-ASSET-bd821e033a435876 recorded that a cluster admission policy was changed. The event references principal-57ab3d2d3751af5f. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-9a86594e8a12 before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Package registry audit on SUPPORT-ASSET-ad8575a16b60726c recorded that a principal published a new package version. The event references principal-b9b60013a399b75b. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-148b2809a01f, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Firewall audit on LEGAL-ASSET-a8345e2e1a01ff48 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-74a2c9033c8d23b7. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Session audit on RESEARCH-ASSET-5cafc83fecebfc2d recorded that the same session token appeared from different client addresses. The event references principal-fe88f832c0c25c20. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Driver audit on LEGAL-ASSET-1d7f06f84da720a0 recorded that a kernel driver was loaded after a package installation. The event references principal-419a1d9d514f9429. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Mfa audit on PEOPLE-ASSET-e45fffd30cf466e9 recorded that multiple MFA challenges were issued during a short interval. The event references principal-3cbfe5aa85664020. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Identity audit on PEOPLE-ASSET-ab714026bdcab67f recorded that repeated failed sign-ins were recorded for an account. The event references principal-b8f5dfca5dbf6b01. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Change CHG-fd425d2fe5a1 lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Identity audit on OPERATIONS-ASSET-0bbb0193ab08eb6e recorded that a service account established an interactive session. The event references principal-de6a7bc5c123923c. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Network control audit on PROCUREMENT-ASSET-296ab163f292467f recorded that a cloud security group gained a broad ingress rule. The event references principal-485bf1fa128db935. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Switch telemetry on FINANCE-ASSET-c82eb7bf49c6713c recorded that an address mapping changed repeatedly on a local segment. The event references principal-24aa90be68c12c8b. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-fa6408a5a93d before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"File audit on LEGAL-ASSET-bda990f3a65f05d4 recorded that a process compressed files from several directories into an archive. The event references principal-e0bfbf7c864c739b. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-1601231e62aa match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Cloud identity audit on COMMUNICATIONS-ASSET-8660c1612914f6bd recorded that a principal received a policy granting additional permissions. The event references principal-796bfc42ecc484c7. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Storage audit on LEGAL-ASSET-2e9a3d1f59ced5f4 recorded that an object-storage access policy was broadened. The event references principal-aece214cd9523226. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Assessment SEC-e06045924ece explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Ci secret audit on LEGAL-ASSET-210117fa7f63e7fa recorded that a build job requested a protected pipeline secret. The event references principal-bafb03e4143599bb. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-c22080670261 explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Cloud control audit on OPERATIONS-ASSET-e8aae5321595ab4e recorded that a cloud logging destination was disabled. The event references principal-a8271fb4edbdf45f. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"File audit on PROCUREMENT-ASSET-a3fde179ef5ff962 recorded that access permissions were broadened on a directory tree. The event references principal-bb1784cca8241c87. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-63b0d544f31e specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Wmi audit on RESEARCH-ASSET-ff750cc74100e1ac recorded that a management request started a process through WMI. The event references principal-2a6d4aeffc691fda. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Function audit on ENGINEERING-ASSET-1db2f1c877763b47 recorded that a serverless function package and execution settings were updated. The event references principal-79d1bb9e5af18d47. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-bdd718719c15 specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Secret manager audit on OPERATIONS-ASSET-9fccf4aa5cb6d2fb recorded that a workload read several secret versions. The event references principal-67a3ab465380b229. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-d1aed61cc26c match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Cloud identity audit on SUPPORT-ASSET-d4887989aac3f6e3 recorded that a principal assumed a role in another account. The event references principal-ccdf0cbbc01cef8e. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-ccb1da25e3a3 match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Service audit on ENGINEERING-ASSET-5be63ef6d4ef079d recorded that a remote service-control request created and started a temporary service. The event references principal-bd2813d9252e7fbb. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-b730e8e4f2a0, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Oauth audit on SUPPORT-ASSET-f8746b96a88e1b30 recorded that an application received consent for additional account scopes. The event references principal-7f165276ca2b480a. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-2324e45e66e6 match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Vpn audit on ENGINEERING-ASSET-10805fb79cd039f2 recorded that a remote-access VPN session was established. The event references principal-ee63fc11c18dbead. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-989e6473ce09 explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Browser audit on SALES-ASSET-2c13db88f9fe11a1 recorded that a browser extension with page-reading permissions was installed. The event references principal-dfbfeb6ce6f75d60. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Event service audit on COMMUNICATIONS-ASSET-a0753c1183185be8 recorded that an event log was cleared by a privileged request. The event references principal-3da9da5b32a84636. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Cloud identity audit on RESEARCH-ASSET-809fdc9f1154a3c8 recorded that a principal received a policy granting additional permissions. The event references principal-58f2cdd79c2b5788. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-226021384659 match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Backup audit on PEOPLE-ASSET-90b00913ef4755f4 recorded that a backup retention policy was shortened. The event references principal-069c9474003b2644. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Cloud identity audit on COMMUNICATIONS-ASSET-e9dda7a9ac4613e3 recorded that a new programmatic access key was issued to a principal. The event references principal-b50a9e7363974da3. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Change CHG-8ef8ec04042e lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Cloud identity audit on SALES-ASSET-6e863cbb874762df recorded that a principal assumed a role in another account. The event references principal-3f1f6f7b104b9c3f. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Cloud control audit on ENGINEERING-ASSET-bbf96ebe3618813b recorded that a cloud logging destination was disabled. The event references principal-7942b0cb0edc33ed. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Egress flow logs on LEGAL-ASSET-1a606b14eab96fee recorded that a workload opened an encrypted connection to an external service. The event references principal-d6bec1039eca165c. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-ad18bfe9fc04 accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"File audit on PROCUREMENT-ASSET-4eb226a25712a501 recorded that a process rewrote multiple files into encrypted containers. The event references principal-6dcdfe5a31b0546b. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-847512c4e883 explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Compute audit on SALES-ASSET-4b3abc50600feeb3 recorded that a principal launched multiple compute instances. The event references principal-a87c3d065d8ee0b1. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-dcc0817e74ac match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"File audit on LEGAL-ASSET-bda990f3a65f05d4 recorded that a process compressed files from several directories into an archive. The event references principal-e0bfbf7c864c739b. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Configuration audit on OPERATIONS-ASSET-f3ed5a9b931a0951 recorded that a client proxy setting was changed. The event references principal-d8940d417fc4c9bd. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-b1a53ab76976 specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Identity audit on OPERATIONS-ASSET-bc3d71283010bd0f recorded that an account password was reset through a recovery workflow. The event references principal-65a355a045f94503. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Configuration audit on SUPPORT-ASSET-75f85e5b495f1222 recorded that a client proxy setting was changed. The event references principal-02061922c2bafcd3. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-e8c97c3680f9 explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Dns control audit on ENGINEERING-ASSET-62a2603633015b4a recorded that an authoritative DNS record was updated. The event references principal-38391a49d25a310a. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"File audit on PEOPLE-ASSET-572ab49b4fda25fd recorded that access permissions were broadened on a directory tree. The event references principal-892e9ce9179f90fe. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-abbd48f2b350 accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Session audit on RESEARCH-ASSET-5cafc83fecebfc2d recorded that the same session token appeared from different client addresses. The event references principal-fe88f832c0c25c20. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Compute audit on COMMUNICATIONS-ASSET-36b3449238b8f470 recorded that a principal launched multiple compute instances. The event references principal-36e251f09c18691b. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Flow logs on OPERATIONS-ASSET-498d986f9a323163 recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-921d661770eeeb14. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Office audit on RESEARCH-ASSET-b8dbacd37bf5b2aa recorded that a document macro launched a child interpreter. The event references principal-fd35021fb1b91014. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Assessment SEC-09baecef883e explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Wmi audit on SALES-ASSET-54ac6fc961ae7d6a recorded that a management request started a process through WMI. The event references principal-08c8fa6d75a3b195. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Mail and proxy logs on OPERATIONS-ASSET-7ac4ed112230cbe5 recorded that a user opened a URL delivered in an email message. The event references principal-b1bb74d41be20948. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Configuration audit on LEGAL-ASSET-654fecba9ad263c2 recorded that a client proxy setting was changed. The event references principal-40cdbd7119e49afd. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Change CHG-2a6a4a5f2790 lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Network control audit on LEGAL-ASSET-8a1d97d0c15ac118 recorded that a cloud security group gained a broad ingress rule. The event references principal-52d39a8366e69bf4. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Change CHG-552a489c2d23 lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Process access audit on FINANCE-ASSET-247c48e4c49c174e recorded that a process requested read access to another process memory space. The event references principal-601055cfd3a85372. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Process audit on PROCUREMENT-ASSET-121cde9378adb9cf recorded that a JavaScript interpreter executed a local script. The event references principal-1a06985b864403e0. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Service audit on RESEARCH-ASSET-8d77d8342c20fbff recorded that a remote service-control request created and started a temporary service. The event references principal-211275ad14685644. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-c126ed25a361 accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"File access audit on RESEARCH-ASSET-41c0744f3eec824f recorded that a process opened a local credential-store file. The event references principal-22db2b4742c4cf72. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Storage access logs on LEGAL-ASSET-6ac4fabec7ab5dad recorded that a principal downloaded many objects from a storage bucket. The event references principal-70ca2ffed3e11735. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Identity audit on ENGINEERING-ASSET-ce4355624d538400 recorded that an account password was reset through a recovery workflow. The event references principal-8d13b23a4098f36d. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Pki audit on RESEARCH-ASSET-5892d31dbb5ae49e recorded that a principal requested a certificate using an authentication template. The event references principal-5044ec496f46d2cd. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Cloud control audit on RESEARCH-ASSET-2bdeaeb6bfb8b9b8 recorded that a cloud logging destination was disabled. The event references principal-00477aa276d23b17. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"File audit on LEGAL-ASSET-f437cecc468ccf1f recorded that access permissions were broadened on a directory tree. The event references principal-1d5f4386a802d873. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Database audit on ENGINEERING-ASSET-2c4914b84c80f08c recorded that a session read several tables and exported the query result. The event references principal-b17a9277af7e3124. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Group audit on RESEARCH-ASSET-0d0aaf2292482822 recorded that an account was added to a privileged local group. The event references principal-5badc7c76a42d4b2. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Application audit on OPERATIONS-ASSET-09e59732382536e3 recorded that an application requested repeated screen captures. The event references principal-a45fb9f4a0a7c7be. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-b9a719c3d578 before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Storage audit on COMMUNICATIONS-ASSET-80a867850d28c413 recorded that a session deleted several storage snapshots. The event references principal-fab18c6abd30f04e. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Process access audit on COMMUNICATIONS-ASSET-5d86ffc7f1150e70 recorded that a process requested read access to another process memory space. The event references principal-4279d106b274e43e. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Registry audit on OPERATIONS-ASSET-bb2e321557973238 recorded that a registry logon-start entry was created. The event references principal-48a0f7ab86053bfa. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-31c8ab46ca2c specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Storage audit on SALES-ASSET-54a03152e889d43f recorded that a session deleted several storage snapshots. The event references principal-69a5261a8cfb5a4d. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-b04f5b558551 specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Session audit on SALES-ASSET-e0e65cd3109e663e recorded that the same session token appeared from different client addresses. The event references principal-b32690205f2a72fc. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Function audit on RESEARCH-ASSET-82ba6903f0ade88c recorded that a serverless function package and execution settings were updated. The event references principal-07c155fce40b0c1d. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Oauth audit on COMMUNICATIONS-ASSET-d085212f92517588 recorded that an application received consent for additional account scopes. The event references principal-410957c7717cf0fe. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Egress flow logs on FINANCE-ASSET-6fc2f9679740efc1 recorded that a workload opened an encrypted connection to an external service. The event references principal-b6c8a10c3d36b1fc. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Macos launch audit on LEGAL-ASSET-924fcf03a30c9333 recorded that a launch agent definition was installed in a user context. The event references principal-188d4edbd5c47469. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Flow logs on COMMUNICATIONS-ASSET-9213739a917e9a5d recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-fd59ae210210a351. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Kerberos audit on SALES-ASSET-7d0683e2088779fa recorded that an account requested service tickets for multiple services. The event references principal-b437865450b6fb0e. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-05b02c1fb1ed, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Process audit on PEOPLE-ASSET-f75719ff0e53a895 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-b17a106beae4504c. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Wmi audit on OPERATIONS-ASSET-c2921eb1d36d866a recorded that a management request started a process through WMI. The event references principal-1c1a48cb243f47fb. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Storage access logs on FINANCE-ASSET-c07c58461c3886b7 recorded that a principal downloaded many objects from a storage bucket. The event references principal-636661caf69ea2cc. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-1a6a2bca6316 accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Network control audit on PEOPLE-ASSET-30b5158319199c4f recorded that a cloud security group gained a broad ingress rule. The event references principal-4d55ccd8cef6e438. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-66d1069abb01 before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Kubernetes audit on OPERATIONS-ASSET-e5571d0159c5e55b recorded that a pod was created with privileged execution enabled. The event references principal-4016297e67e67765. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Saas audit on OPERATIONS-ASSET-f4bc429edd233279 recorded that a user requested a bulk export from a business application. The event references principal-0d93bc3cb85c4be3. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Mail audit on COMMUNICATIONS-ASSET-cf30ec21588a2145 recorded that an account received delegated access to a mailbox. The event references principal-a11312ab2e69f315. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Waf logs on ENGINEERING-ASSET-155d31939b4a4ab3 recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-a5bfd2692d01cf27. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Driver audit on FINANCE-ASSET-4d3885b7e2a2eaaa recorded that a kernel driver was loaded after a package installation. The event references principal-93dddd296bcd4a0a. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Device and file audit on ENGINEERING-ASSET-c9b77c2a506ace86 recorded that files were copied to a removable storage device. The event references principal-7078af09729168a5. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Wmi audit on ENGINEERING-ASSET-9642a3ef1a26edcb recorded that a management request started a process through WMI. The event references principal-4a2b4bdee8c5d199. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Dns server audit on COMMUNICATIONS-ASSET-3ba853c8b87dee93 recorded that a client requested a DNS zone transfer. The event references principal-fbb1839d1793e373. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Change CHG-38a0e0ae5fd6 lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Systemd audit on PEOPLE-ASSET-e24082f3c52d3f39 recorded that a service unit file was changed and the unit reloaded. The event references principal-b49269ba3a97e459. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Session audit on ENGINEERING-ASSET-bc4c94aa37fb4f60 recorded that the same session token appeared from different client addresses. The event references principal-821aec91dc2aa8b4. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Windows logon audit on ENGINEERING-ASSET-9a2b7e9a3eb1704f recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-d502784167672763. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Cloud identity audit on ENGINEERING-ASSET-00c2f8de5ff4a52c recorded that a principal assumed a role in another account. The event references principal-4cb5db7ee766c0fa. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Ci secret audit on SUPPORT-ASSET-d5ed18de3905520f recorded that a build job requested a protected pipeline secret. The event references principal-7efbed86c5e71c09. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Vpn audit on COMMUNICATIONS-ASSET-cf88b5e111fdd1c4 recorded that a remote-access VPN session was established. The event references principal-323dccf79a1a961c. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Flow logs on RESEARCH-ASSET-36f3e51101dc72ca recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-4148cfbbdb30636d. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Dns control audit on PROCUREMENT-ASSET-a2a68c2dd932f661 recorded that an authoritative DNS record was updated. The event references principal-d6b239df277e509a. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-0a1a00f227ef match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Storage audit on OPERATIONS-ASSET-07e77010a446667b recorded that a session deleted several storage snapshots. The event references principal-fc81340c87f20845. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Ssh audit on LEGAL-ASSET-97358e826a1337d7 recorded that an SSH session opened and requested elevated command execution. The event references principal-713d0f7027f2d117. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Policy audit on PROCUREMENT-ASSET-f2878461512a2696 recorded that an audit policy was changed to collect fewer event categories. The event references principal-2bb61efdeda82dac. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Process audit on ENGINEERING-ASSET-db715ea0863774ba recorded that a remote-support application started an interactive session. The event references principal-ca4d1a946cc4272b. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Winrm audit on FINANCE-ASSET-f7f3ea9e3a52d83c recorded that a remote management session invoked a command on a managed host. The event references principal-13d8273b51b14066. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Share audit on RESEARCH-ASSET-f2c54bce84c236d2 recorded that a new network file share was published. The event references principal-0e202f3a7615eefc. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-f1bdfef82b8d match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Identity audit on SALES-ASSET-880860857ffcd92f recorded that a service account established an interactive session. The event references principal-6480886757402cfa. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Process audit on SUPPORT-ASSET-6869d2722a21fd5c recorded that a Python interpreter loaded a script and contacted a service. The event references principal-f677ab6a5a1c21d4. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Oauth audit on PROCUREMENT-ASSET-2f4aab546bd1bb38 recorded that an application received consent for additional account scopes. The event references principal-eef62ccd4ff2398c. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-01c2a5255461 before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Cloud identity audit on SUPPORT-ASSET-0acaf32cb86c9787 recorded that a new programmatic access key was issued to a principal. The event references principal-f4c6ed272feaab73. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Mail audit on PEOPLE-ASSET-23ff12ac4cce3df1 recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-210b267fe07fa398. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Mail and proxy logs on RESEARCH-ASSET-0d6948f11ee5b28e recorded that a user opened a URL delivered in an email message. The event references principal-fdb003c9c4c80093. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Application audit on SUPPORT-ASSET-0d07ed7bee9ce5d7 recorded that an application requested repeated screen captures. The event references principal-1f37918578f8f184. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Firewall audit on OPERATIONS-ASSET-f066243659fb5412 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-9b3165faa785f1a5. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Flow logs on RESEARCH-ASSET-36f3e51101dc72ca recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-4148cfbbdb30636d. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Database audit on OPERATIONS-ASSET-302e0f5dfef6781b recorded that a session read several tables and exported the query result. The event references principal-22fca2204489e9a2. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Code integrity audit on SUPPORT-ASSET-d243663dca87b63a recorded that an executable without a publisher signature started from a writable directory. The event references principal-ac7fc8d288d921e2. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-d890bf9aa7dd match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Kerberos audit on RESEARCH-ASSET-add8a0192da6108f recorded that an account requested service tickets for multiple services. The event references principal-2289755f000d3a1a. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Key service audit on SUPPORT-ASSET-32d985d5324796c4 recorded that a principal issued a burst of key-service decrypt requests. The event references principal-82b70d458957b545. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Registry audit on SALES-ASSET-797a3ae487efd18f recorded that a workload pulled a container image from a registry. The event references principal-6df652f7e41389ab. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-0e511c93bc22, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Browser audit on LEGAL-ASSET-df49de2f96b43b40 recorded that a browser extension with page-reading permissions was installed. The event references principal-010a6a482ee1c838. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Assessment SEC-35b1871e430b explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Pki audit on COMMUNICATIONS-ASSET-a88e156f33159899 recorded that a principal requested a certificate using an authentication template. The event references principal-0a19afbf9253f4fc. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Database audit on LEGAL-ASSET-1c120ddc82665e7a recorded that a session read several tables and exported the query result. The event references principal-4636f85408e4dae9. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Assessment SEC-07dfdeea5788 explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Storage audit on ENGINEERING-ASSET-cd853382d1a0a281 recorded that a session deleted several storage snapshots. The event references principal-39dd7d8e5cbb8cc6. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Cron audit on PEOPLE-ASSET-4b3199ab3c63dd2d recorded that a recurring job definition was added to the system schedule. The event references principal-f1110cbb064f6627. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Cloud control audit on PEOPLE-ASSET-357f734fad0406df recorded that a session deleted a group of cloud resources. The event references principal-50a694af17f32a70. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-bc4a1bf9be57 accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Cloud identity audit on FINANCE-ASSET-b948d8305372c015 recorded that a new programmatic access key was issued to a principal. The event references principal-68bd58abfea31389. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Directory audit on PEOPLE-ASSET-37791232d78efc05 recorded that a principal requested directory replication data. The event references principal-55f0d12673ae40b1. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-99388695a32a accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Ci secret audit on SALES-ASSET-ad09caa9a6596785 recorded that a build job requested a protected pipeline secret. The event references principal-5cac9dd38eee5122. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"File audit on SALES-ASSET-6ae931d0f4c709bb recorded that access permissions were broadened on a directory tree. The event references principal-d574e0d5ffd134ab. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Package registry audit on PROCUREMENT-ASSET-742ad97982b567e2 recorded that a principal published a new package version. The event references principal-5921bb600425987a. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Mail audit on COMMUNICATIONS-ASSET-cf30ec21588a2145 recorded that an account received delegated access to a mailbox. The event references principal-a11312ab2e69f315. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-47cf25683cbd before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Dhcp telemetry on OPERATIONS-ASSET-495d89e0df4422f6 recorded that a server issued DHCP offers on a monitored segment. The event references principal-ad2763e8b3d1fe71. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-6e9124f82719 match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Module audit on ENGINEERING-ASSET-ef21d634c2b3a94b recorded that a process loaded a library from an application-local directory. The event references principal-47653e2725b4086f. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Federation audit on COMMUNICATIONS-ASSET-866384484e84ef96 recorded that a tenant federation setting was updated. The event references principal-e2dd8e40c0e17294. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-3eff39a09fa7 accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Vpn audit on RESEARCH-ASSET-f104c6cff8b4f120 recorded that a remote-access VPN session was established. The event references principal-18bc30314e242812. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Kubernetes audit on PEOPLE-ASSET-36a1a728506cc2a7 recorded that a workload mounted a directory from its host filesystem. The event references principal-b1c8c5f8e9de87c2. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Ci secret audit on COMMUNICATIONS-ASSET-d9b1648a2cfcda09 recorded that a build job requested a protected pipeline secret. The event references principal-8fc1bbd9d306c19b. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Change CHG-b3f8a019214e lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Mail and proxy logs on SALES-ASSET-86e0136e86dcbb64 recorded that a user opened a URL delivered in an email message. The event references principal-090cc1db12274cd7. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-714b765147e2 match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Cloud identity audit on RESEARCH-ASSET-809fdc9f1154a3c8 recorded that a principal received a policy granting additional permissions. The event references principal-58f2cdd79c2b5788. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-226021384659 match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Process audit on PROCUREMENT-ASSET-121cde9378adb9cf recorded that a JavaScript interpreter executed a local script. The event references principal-1a06985b864403e0. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Application audit on SALES-ASSET-5a207e0d30dc6722 recorded that an application requested repeated screen captures. The event references principal-e579eecfc7c0f733. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Application audit on PROCUREMENT-ASSET-0b973fc190e51fb9 recorded that an application requested repeated screen captures. The event references principal-6d7c52f4e39422b1. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Security retest SEC-a3fe62ebef9c covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Policy audit on OPERATIONS-ASSET-bb5aff052239026f recorded that an audit policy was changed to collect fewer event categories. The event references principal-08ce997b82328b8f. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Pki audit on SUPPORT-ASSET-70be4dd0be19b589 recorded that a principal requested a certificate using an authentication template. The event references principal-3490e3ca6541e91e. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Cloud control audit on PROCUREMENT-ASSET-1ca061884feb0239 recorded that a session deleted a group of cloud resources. The event references principal-bde2c278c233490d. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Function audit on PROCUREMENT-ASSET-9b0e13d58a2188a8 recorded that a serverless function package and execution settings were updated. The event references principal-12b8d8e2191620d9. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Assessment SEC-a601f89844f7 explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Vpn audit on OPERATIONS-ASSET-3b10a040384bc85b recorded that a remote-access VPN session was established. The event references principal-e69c38b8397d46ff. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Identity audit on PEOPLE-ASSET-f09717db52bad024 recorded that an account password was reset through a recovery workflow. The event references principal-52a4edbb0422bb75. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Browser audit on ENGINEERING-ASSET-f6edb397c93f1bb4 recorded that a browser extension with page-reading permissions was installed. The event references principal-bf7a3feca21483cd. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Module audit on COMMUNICATIONS-ASSET-e298c38c58f7c346 recorded that a process loaded a library from an application-local directory. The event references principal-dd8d62077451bf1c. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-c2299d1302ea accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Device and file audit on FINANCE-ASSET-95133e3350d50213 recorded that files were copied to a removable storage device. The event references principal-3a08b3fa9560c2b5. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Assessment SEC-199328eb4f2d explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"File audit on FINANCE-ASSET-d2b45ac726791f9b recorded that a process deleted many files within a short interval. The event references principal-e041b8a80436a62f. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Api gateway logs on SUPPORT-ASSET-13bc954846049d2f recorded that a client issued a burst of API requests. The event references principal-d482be68e022a834. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Database audit on LEGAL-ASSET-3632866debb967ca recorded that a session changed a database table definition. The event references principal-862aa2954135f309. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Oauth audit on OPERATIONS-ASSET-1d059cb4cf3d2fe1 recorded that an application received consent for additional account scopes. The event references principal-68400bad9534528c. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-3068d84b0cac match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Dns control audit on LEGAL-ASSET-b16c2ea371640162 recorded that an authoritative DNS record was updated. The event references principal-162d081f9776c04e. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-3ead920901ff accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Kubernetes audit on SALES-ASSET-3af15ceafaf37a50 recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-4e40a79e1d1cac1f. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Storage access logs on OPERATIONS-ASSET-4a7bbac68a963680 recorded that a principal downloaded many objects from a storage bucket. The event references principal-9881a91f6d808755. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Cloud identity audit on PEOPLE-ASSET-db5bfc23857c8681 recorded that a principal assumed a role in another account. The event references principal-3e8604b26d44d800. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Device and file audit on FINANCE-ASSET-95133e3350d50213 recorded that files were copied to a removable storage device. The event references principal-3a08b3fa9560c2b5. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Change CHG-199328eb4f2d lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Cloud identity audit on RESEARCH-ASSET-39f1c4acdb98407c recorded that a new programmatic access key was issued to a principal. The event references principal-16f1be9653031bee. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Assessment SEC-5e8a904eb341 explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Waf logs on OPERATIONS-ASSET-b7ed82085f777d6d recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-82b5142e40756445. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Kubernetes audit on COMMUNICATIONS-ASSET-f76c1c782f04bc0e recorded that a workload mounted a directory from its host filesystem. The event references principal-ea22af4c35053180. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Systemd audit on COMMUNICATIONS-ASSET-83d44af530d70e5a recorded that a service unit file was changed and the unit reloaded. The event references principal-fef91c85181668d1. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Process audit on RESEARCH-ASSET-a06368c20e1f1761 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-c27d38810eca0fcd. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Function audit on PROCUREMENT-ASSET-9b0e13d58a2188a8 recorded that a serverless function package and execution settings were updated. The event references principal-12b8d8e2191620d9. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Mail audit on OPERATIONS-ASSET-3a9ba1a13acae41d recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-458bdf5d7e7a4b20. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Mail and proxy logs on SUPPORT-ASSET-79dbee71e86c40be recorded that a user opened a URL delivered in an email message. The event references principal-1603764c68a231e0. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Storage access logs on FINANCE-ASSET-c07c58461c3886b7 recorded that a principal downloaded many objects from a storage bucket. The event references principal-636661caf69ea2cc. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-1a6a2bca6316, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Firewall audit on RESEARCH-ASSET-0236b24f6c7b0e03 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-582ef1b1560e6fc6. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Kubernetes audit on PEOPLE-ASSET-46959b0322e15f66 recorded that a pod was created with privileged execution enabled. The event references principal-8e6c04f200191e81. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-72c5b4eaf3f3 before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Secret manager audit on SUPPORT-ASSET-c293b34ccf018f66 recorded that a workload read several secret versions. The event references principal-e464eb0ee46edc73. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-3bfb39551997 match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Pki audit on ENGINEERING-ASSET-1be9c96304b0e927 recorded that a principal requested a certificate using an authentication template. The event references principal-86425f445bb7386e. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Smb audit on SALES-ASSET-f9e0160f65640ecb recorded that a session enumerated a file share and read multiple files. The event references principal-5b93bfe2ff3ce2df. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Process access audit on SUPPORT-ASSET-a8d87f27cfdb843f recorded that a process requested read access to another process memory space. The event references principal-8eabe5478e5a2271. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Identity audit on PROCUREMENT-ASSET-595810a122b584e8 recorded that a service account established an interactive session. The event references principal-786fe31fade4e850. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Dns control audit on PROCUREMENT-ASSET-a2a68c2dd932f661 recorded that an authoritative DNS record was updated. The event references principal-d6b239df277e509a. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"File access audit on OPERATIONS-ASSET-1494559c806dea5d recorded that a process opened a local credential-store file. The event references principal-c4b1fa13e42018fb. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Network control audit on PEOPLE-ASSET-30b5158319199c4f recorded that a cloud security group gained a broad ingress rule. The event references principal-4d55ccd8cef6e438. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Service audit on OPERATIONS-ASSET-53e47c7270341ae1 recorded that a remote service-control request created and started a temporary service. The event references principal-ae8a8a74a000dff1. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Certificate audit on SALES-ASSET-d2e9e0997da46974 recorded that a service certificate was replaced. The event references principal-0e407d6273aa8758. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-33c47314ec0e specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Cloud identity audit on SALES-ASSET-97a28d40051be12b recorded that a principal received a policy granting additional permissions. The event references principal-e45a694b7e0b8b49. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Application audit on LEGAL-ASSET-988ab05a6aaafddb recorded that a runtime configuration setting was updated. The event references principal-2cc56950de78c750. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Security retest SEC-9fce6ada3217 covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Cloud identity audit on PEOPLE-ASSET-120c32cb226f1634 recorded that a new programmatic access key was issued to a principal. The event references principal-1aef76f9cfa1105d. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Database audit on PEOPLE-ASSET-aeb9e932203e4086 recorded that a session changed a database table definition. The event references principal-4c123413716680f3. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Change CHG-138a32b480e7 lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Cloud control audit on SALES-ASSET-c5ac5bf2061a85e1 recorded that resources were created in a region with little prior activity. The event references principal-213b93a3248e4777. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Systemd audit on PEOPLE-ASSET-e24082f3c52d3f39 recorded that a service unit file was changed and the unit reloaded. The event references principal-b49269ba3a97e459. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"File audit on LEGAL-ASSET-4a73488ba2d33df6 recorded that a process rewrote multiple files into encrypted containers. The event references principal-9d7037ae8c34aa83. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-fd853d056a66 specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Kubernetes audit on RESEARCH-ASSET-ca81e4dea7e4d440 recorded that a workload mounted a directory from its host filesystem. The event references principal-142014dd00377291. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"File access audit on FINANCE-ASSET-334508df57fe9f23 recorded that a process opened a local credential-store file. The event references principal-0966351ff7c24bff. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Security retest SEC-8320ed3b260f covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Dns server audit on ENGINEERING-ASSET-aec07c525ec55aac recorded that a client requested a DNS zone transfer. The event references principal-4c0d05a21a35e460. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-f3cc0f2a81fc before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Network control audit on PROCUREMENT-ASSET-296ab163f292467f recorded that a cloud security group gained a broad ingress rule. The event references principal-485bf1fa128db935. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Agent audit on SALES-ASSET-4f0c6ee9e7bb90ab recorded that a privileged session changed endpoint monitoring settings. The event references principal-b547aa127479e0eb. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Database audit on SUPPORT-ASSET-9310282a796b35af recorded that a session changed a database table definition. The event references principal-c009c7c60f3c400f. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Registry audit on SUPPORT-ASSET-f57e1958aa803333 recorded that a workload pulled a container image from a registry. The event references principal-10cd1718e32b6b5f. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Device and file audit on PROCUREMENT-ASSET-804fb2eb4bbf7ddf recorded that files were copied to a removable storage device. The event references principal-25d93f161d21c79f. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-00c4d0f69ad6 match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Kubernetes audit on FINANCE-ASSET-d7b2da83577ab38d recorded that a pod was created with privileged execution enabled. The event references principal-5177d7ecbc348aa2. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Session audit on LEGAL-ASSET-a93d2c4f4ac53314 recorded that the same session token appeared from different client addresses. The event references principal-4ff9816ed8758404. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Assessment SEC-565ec33c2b00 explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Cloud control audit on OPERATIONS-ASSET-e8aae5321595ab4e recorded that a cloud logging destination was disabled. The event references principal-a8271fb4edbdf45f. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Flow logs on COMMUNICATIONS-ASSET-9213739a917e9a5d recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-fd59ae210210a351. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Database audit on PEOPLE-ASSET-aeb9e932203e4086 recorded that a session changed a database table definition. The event references principal-4c123413716680f3. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Directory audit on PROCUREMENT-ASSET-7b387a0e6a39eb7a recorded that a principal requested directory replication data. The event references principal-0b3c6bcdb6ea6190. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Runtime audit on ENGINEERING-ASSET-275c1751b3b56ff6 recorded that a process connected to the container runtime socket. The event references principal-560134bf0a39e092. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-4a568df92172 match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Service audit on SUPPORT-ASSET-bed8c4ced0655fc1 recorded that a remote service-control request created and started a temporary service. The event references principal-74bec1dcad5113eb. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-f8d0f69fdff8, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Mail audit on FINANCE-ASSET-c2947168e63669b0 recorded that an account received delegated access to a mailbox. The event references principal-33d9797e6b81280e. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Macos launch audit on RESEARCH-ASSET-76ee756c91d53577 recorded that a launch agent definition was installed in a user context. The event references principal-cd202933651b57f9. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-f7305a1daaf8, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Repository audit on PROCUREMENT-ASSET-7cc2509e9eb69ebb recorded that a user cloned several source repositories. The event references principal-39fa91ed4065a325. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Federation audit on ENGINEERING-ASSET-ed48b05a54cba0b4 recorded that a tenant federation setting was updated. The event references principal-7dac1305cd5fd7e7. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Change CHG-3639b66d5187 lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Application audit on FINANCE-ASSET-be2eeaec3ad85eb4 recorded that a runtime configuration setting was updated. The event references principal-1d937b1c297b00f3. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Ci audit on SUPPORT-ASSET-be888d94d309deab recorded that a build pipeline definition gained a new execution step. The event references principal-f55be257f884a1b4. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Device and file audit on SALES-ASSET-3b11bf4bc19f47f9 recorded that files were copied to a removable storage device. The event references principal-342176cf658025b8. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-50caf84a4b1e, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Configuration audit on OPERATIONS-ASSET-f3ed5a9b931a0951 recorded that a client proxy setting was changed. The event references principal-d8940d417fc4c9bd. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Kubernetes audit on OPERATIONS-ASSET-f1f73c739188a298 recorded that a workload mounted a directory from its host filesystem. The event references principal-5a00d24e558e0ba4. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-c2b20252f060 explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Session audit on LEGAL-ASSET-a93d2c4f4ac53314 recorded that the same session token appeared from different client addresses. The event references principal-4ff9816ed8758404. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Saas audit on COMMUNICATIONS-ASSET-1937d1daec1efbd9 recorded that a user requested a bulk export from a business application. The event references principal-7aa0534f456ac613. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-b424c7e4107b, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Cloud control audit on FINANCE-ASSET-b563459bb8af8f48 recorded that a session deleted a group of cloud resources. The event references principal-a8340a0f60620156. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Firewall audit on SUPPORT-ASSET-e85c56705ce7aa30 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-9b678cb3b90b393c. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Ci secret audit on SUPPORT-ASSET-d5ed18de3905520f recorded that a build job requested a protected pipeline secret. The event references principal-7efbed86c5e71c09. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-70cb4f6bb6aa before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"File audit on ENGINEERING-ASSET-34a8ce1c539d9368 recorded that a process deleted many files within a short interval. The event references principal-c1c689ef96642a7c. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Cloud control audit on ENGINEERING-ASSET-2f0ebfbab41474df recorded that a session deleted a group of cloud resources. The event references principal-eab0d8cb49ca354d. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Storage audit on PROCUREMENT-ASSET-283ac93c3c2be26b recorded that a session deleted several storage snapshots. The event references principal-84f457c32ccdb7a6. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Cloud control audit on SALES-ASSET-c5ac5bf2061a85e1 recorded that resources were created in a region with little prior activity. The event references principal-213b93a3248e4777. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Code integrity audit on PEOPLE-ASSET-4048dcb975a46f2e recorded that an executable without a publisher signature started from a writable directory. The event references principal-d449d23aa96125e6. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-bde7d63bb866, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Registry audit on COMMUNICATIONS-ASSET-bfd346cad4d024a4 recorded that a registry logon-start entry was created. The event references principal-74f1b84012bd604a. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Office audit on RESEARCH-ASSET-b8dbacd37bf5b2aa recorded that a document macro launched a child interpreter. The event references principal-fd35021fb1b91014. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Kerberos audit on RESEARCH-ASSET-add8a0192da6108f recorded that an account requested service tickets for multiple services. The event references principal-2289755f000d3a1a. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-ad316d4d708d accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Identity audit on FINANCE-ASSET-a32c9481137674af recorded that an account password was reset through a recovery workflow. The event references principal-b0dec7cad50c7fe1. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Winrm audit on ENGINEERING-ASSET-6e5e1ed61987467a recorded that a remote management session invoked a command on a managed host. The event references principal-c372b39c0d58be55. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-e547a9053c51 accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Backup audit on SALES-ASSET-6933f79c2a57f98c recorded that a backup retention policy was shortened. The event references principal-9b63e3d52602597e. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-ca577d5075f0, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Module audit on PROCUREMENT-ASSET-234ebd90da532d08 recorded that a process loaded a library from an application-local directory. The event references principal-2bfaedc31b23b886. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Task scheduler audit on RESEARCH-ASSET-21bf6f06fdc5117a recorded that a scheduled task was registered to execute a program at logon. The event references principal-0cdfb8ebb9ac46b3. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-0f3ff901a1ab match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Process audit on ENGINEERING-ASSET-b8d24c4e39635b0b recorded that a Python interpreter loaded a script and contacted a service. The event references principal-59e5008660f946a5. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-86c7139b136c match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Code integrity audit on RESEARCH-ASSET-b23d57d440170815 recorded that an executable without a publisher signature started from a writable directory. The event references principal-a70693803f9dbb50. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Compute audit on ENGINEERING-ASSET-67df6013e7bda695 recorded that a principal launched multiple compute instances. The event references principal-d74238a9b43b1893. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Network control audit on SUPPORT-ASSET-badb98bf2185855c recorded that a cloud security group gained a broad ingress rule. The event references principal-1a508d07acbfb51b. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Change CHG-26f3682d8277 lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Certificate audit on PEOPLE-ASSET-4d0259660c317b95 recorded that a service certificate was replaced. The event references principal-f191ea3a323e48f8. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Database audit on RESEARCH-ASSET-d8c71a5a44c49e60 recorded that a session changed a database table definition. The event references principal-355812fdc0609439. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Vpn audit on PROCUREMENT-ASSET-af5dcb9896a63a8e recorded that a remote-access VPN session was established. The event references principal-29a685b020122aec. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Oauth audit on SALES-ASSET-8a294b7f6b4fb5ec recorded that an application received consent for additional account scopes. The event references principal-4be7952cadd1c600. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Vpn audit on RESEARCH-ASSET-f104c6cff8b4f120 recorded that a remote-access VPN session was established. The event references principal-18bc30314e242812. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-42cb4b7d1811 match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Proxy logs on PEOPLE-ASSET-47b1cfa33ae643a0 recorded that a client transferred a large payload to an external storage endpoint. The event references principal-eefc70a315bcfb3b. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Cloud identity audit on FINANCE-ASSET-b948d8305372c015 recorded that a new programmatic access key was issued to a principal. The event references principal-68bd58abfea31389. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Cloud control audit on COMMUNICATIONS-ASSET-53a6ecae622bccee recorded that a cloud logging destination was disabled. The event references principal-cf25374694280e00. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Resolver logs on ENGINEERING-ASSET-02301b26ed9cf1c5 recorded that a client requested many long, high-entropy DNS labels. The event references principal-8e3fc22d3aadc906. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Network control audit on FINANCE-ASSET-93401772cf68a3aa recorded that a cloud security group gained a broad ingress rule. The event references principal-b7b99f534a1030f4. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Network control audit on OPERATIONS-ASSET-bd217021cb34aa91 recorded that a cloud security group gained a broad ingress rule. The event references principal-2dc6c3bb2730ad8e. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Switch telemetry on ENGINEERING-ASSET-271d6935661ca5b6 recorded that an address mapping changed repeatedly on a local segment. The event references principal-2aa672d045fc50f4. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-bca4c9b02578 before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Repository audit on OPERATIONS-ASSET-d75290e6ed1a6d85 recorded that a repository collaborator received elevated permissions. The event references principal-b26cea051978a58c. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Mail audit on OPERATIONS-ASSET-3bd074cdd8f9b5e6 recorded that an account received delegated access to a mailbox. The event references principal-81775ab116c002d8. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-a01c89f46f72 match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Gateway logs on RESEARCH-ASSET-6dcd3c5959922161 recorded that a client established a long-lived encapsulated network session. The event references principal-d901ab75b47ec726. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Share audit on FINANCE-ASSET-689b8f41db9ab4f4 recorded that a new network file share was published. The event references principal-604eb4041d82448c. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Change CHG-e4c4b889b049 lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Session audit on OPERATIONS-ASSET-650805187004af92 recorded that the same session token appeared from different client addresses. The event references principal-fe1f7195dd801273. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Event service audit on LEGAL-ASSET-1725494bd06479c8 recorded that an event log was cleared by a privileged request. The event references principal-2d006b9d45394524. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-d02dc959ec2a accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Flow logs on FINANCE-ASSET-a52520aa18fc5145 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-d9480c5f3eeb0f53. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Assessment SEC-6ae64a6fb834 explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Mail flow logs on SALES-ASSET-40ddb7fd75836262 recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-4279d4843faab477. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Assessment SEC-4242122066d2 explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Registry audit on PROCUREMENT-ASSET-623aa42bae025131 recorded that a registry logon-start entry was created. The event references principal-9f2c57eab5b3cfda. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Assessment SEC-e26a9b3192d3 explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Identity audit on FINANCE-ASSET-a32c9481137674af recorded that an account password was reset through a recovery workflow. The event references principal-b0dec7cad50c7fe1. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Proxy logs on OPERATIONS-ASSET-63a9838a229b6bdc recorded that a client transferred a large payload to an external storage endpoint. The event references principal-1a271b9f4504e35e. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Federation audit on LEGAL-ASSET-81a8982089dddbeb recorded that a tenant federation setting was updated. The event references principal-c29fe59344f3b4d5. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Cloud identity audit on RESEARCH-ASSET-8d54a31e0957dabb recorded that a principal assumed a role in another account. The event references principal-8a3eb5c757201646. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Kubernetes audit on PEOPLE-ASSET-3e58a2eca5c63a44 recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-8f985c1a713a28f2. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-300a08b7dfb0 match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Database audit on FINANCE-ASSET-7b5f1daa45ffd071 recorded that a session changed a database table definition. The event references principal-eec005bb1596cf1c. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Share audit on SUPPORT-ASSET-642a0478e0fea4be recorded that a new network file share was published. The event references principal-d39d2cce091886dd. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Registry audit on COMMUNICATIONS-ASSET-c99d7ada90aece83 recorded that a workload pulled a container image from a registry. The event references principal-c5705a8b2e1e260b. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-c68351cddfd1, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Certificate audit on LEGAL-ASSET-028cc6c15478424c recorded that a service certificate was replaced. The event references principal-ab2a10d3b09a07d5. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Ssh audit on OPERATIONS-ASSET-324bfe1afe152ff0 recorded that an SSH session opened and requested elevated command execution. The event references principal-db6e14b705505251. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Script audit on COMMUNICATIONS-ASSET-ad52eab51d5bfbe3 recorded that a script interpreter decoded an encoded argument before execution. The event references principal-b20c6bb2ef5361bb. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Windows logon audit on PROCUREMENT-ASSET-6de9173566128253 recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-1e31ae283e3821b5. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"File audit on OPERATIONS-ASSET-53ad24c9deb5d645 recorded that a shell startup profile gained an additional command. The event references principal-6049aaff0c8fe538. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-59a78391fb4b explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Gateway logs on SALES-ASSET-712c30d2818c912a recorded that a client established a long-lived encapsulated network session. The event references principal-0cbf398f28282f6a. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Egress flow logs on PEOPLE-ASSET-9176797d1eb78aff recorded that a workload opened an encrypted connection to an external service. The event references principal-eeab4c2bc996daf9. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Secret manager audit on OPERATIONS-ASSET-9fccf4aa5cb6d2fb recorded that a workload read several secret versions. The event references principal-67a3ab465380b229. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Cloud control audit on ENGINEERING-ASSET-1c2668b46715bf02 recorded that resources were created in a region with little prior activity. The event references principal-974cef6dad8360ab. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Office audit on FINANCE-ASSET-611546d095704224 recorded that a document macro launched a child interpreter. The event references principal-07f2af237b2ad540. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Winrm audit on RESEARCH-ASSET-35584f0a53bc209b recorded that a remote management session invoked a command on a managed host. The event references principal-7b703d1f8c94aba9. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Script audit on RESEARCH-ASSET-a67da4eb1517ea03 recorded that a script interpreter decoded an encoded argument before execution. The event references principal-e606a4602bed6561. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Change CHG-901e29e5ee04 lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Network control audit on RESEARCH-ASSET-e48fcfb18287d725 recorded that a cloud security group gained a broad ingress rule. The event references principal-0f1496ca8a6383fd. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Ssh audit on LEGAL-ASSET-97358e826a1337d7 recorded that an SSH session opened and requested elevated command execution. The event references principal-713d0f7027f2d117. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"File audit on RESEARCH-ASSET-e40ef73f48b09e4f recorded that a shell startup profile gained an additional command. The event references principal-2434130e3913b6f0. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Repository audit on LEGAL-ASSET-f07ffc46adc231a4 recorded that a repository collaborator received elevated permissions. The event references principal-d071e326612f692d. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Event service audit on SALES-ASSET-c924bb512f8f20fd recorded that an event log was cleared by a privileged request. The event references principal-c440dcbeadedc4d2. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Kubernetes audit on SALES-ASSET-ffd4e9bc10275050 recorded that a pod was created with privileged execution enabled. The event references principal-02bcfaa51dffcded. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Mail and proxy logs on ENGINEERING-ASSET-d6ab66ae0acf6c7d recorded that a user opened a URL delivered in an email message. The event references principal-0a6867792e03bc3b. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Kubernetes audit on ENGINEERING-ASSET-03ff797dc0608058 recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-84d60009e20971fc. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Script audit on FINANCE-ASSET-8f7a7c5dae3d75b5 recorded that a script interpreter decoded an encoded argument before execution. The event references principal-7a6a17f9162097f1. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Key service audit on OPERATIONS-ASSET-a2b77b051a5e88ca recorded that a principal issued a burst of key-service decrypt requests. The event references principal-2d26323a698b32c1. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Share audit on OPERATIONS-ASSET-a9f5766b40361ce4 recorded that a new network file share was published. The event references principal-e591af365aeb634a. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Kerberos audit on SALES-ASSET-7d0683e2088779fa recorded that an account requested service tickets for multiple services. The event references principal-b437865450b6fb0e. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Storage audit on PEOPLE-ASSET-1ba8659c3031d7f0 recorded that a session deleted several storage snapshots. The event references principal-cf538081eb476d29. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Api gateway logs on FINANCE-ASSET-7a64770a61e92e29 recorded that a client issued a burst of API requests. The event references principal-43cf908ee519b246. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Code integrity audit on PROCUREMENT-ASSET-3f90b9195fa39dc7 recorded that an executable without a publisher signature started from a writable directory. The event references principal-f1b547470e053c8b. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Database audit on OPERATIONS-ASSET-302e0f5dfef6781b recorded that a session read several tables and exported the query result. The event references principal-22fca2204489e9a2. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Cron audit on SUPPORT-ASSET-0f143a13847207ad recorded that a recurring job definition was added to the system schedule. The event references principal-940a8e24d3cd68aa. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Process audit on FINANCE-ASSET-565f2ed301684671 recorded that a remote-support application started an interactive session. The event references principal-a4a07392170d1084. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Firewall audit on OPERATIONS-ASSET-f066243659fb5412 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-9b3165faa785f1a5. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Kubernetes audit on PROCUREMENT-ASSET-a7191d519031e89b recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-a4246f24c83acd17. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-b8898c3cb949 explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Application audit on PEOPLE-ASSET-b6c838eeab685d8f recorded that an application requested repeated screen captures. The event references principal-22d369aeea462cc7. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Kubernetes audit on RESEARCH-ASSET-200dc8ad3542be6e recorded that a role binding granted a principal additional cluster permissions. The event references principal-b8023dd958201bec. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-d1e325c5e4a7, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Backup audit on LEGAL-ASSET-0b947a06b2f86efb recorded that a backup retention policy was shortened. The event references principal-ec8805dd5dc564d0. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-878f9c1942c8, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Repository audit on COMMUNICATIONS-ASSET-74eb656a821bda53 recorded that a repository collaborator received elevated permissions. The event references principal-aeb807368ce77066. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-9ecd3f8c22a5 match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Api gateway logs on SALES-ASSET-67b00a7811823c9c recorded that a client issued a burst of API requests. The event references principal-0a02b6edf23f48b5. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Identity audit on PEOPLE-ASSET-f09717db52bad024 recorded that an account password was reset through a recovery workflow. The event references principal-52a4edbb0422bb75. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Mail flow logs on PEOPLE-ASSET-9ba2c53dc33b0530 recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-5b015560df1e299f. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-781d418d8cd9 explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Proxy logs on COMMUNICATIONS-ASSET-5a2ac13c8b310540 recorded that a client transferred a large payload to an external storage endpoint. The event references principal-d735b0162330748a. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-45e2d294c4ba covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Windows logon audit on FINANCE-ASSET-08f4600838c704c1 recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-9a25429fc1580f3b. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"File audit on SUPPORT-ASSET-a93f88cca8d4a8b9 recorded that a process rewrote multiple files into encrypted containers. The event references principal-ae3578564d0163ba. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Function audit on RESEARCH-ASSET-82ba6903f0ade88c recorded that a serverless function package and execution settings were updated. The event references principal-07c155fce40b0c1d. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Event service audit on SALES-ASSET-c924bb512f8f20fd recorded that an event log was cleared by a privileged request. The event references principal-c440dcbeadedc4d2. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Process access audit on FINANCE-ASSET-247c48e4c49c174e recorded that a process requested read access to another process memory space. The event references principal-601055cfd3a85372. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Process audit on RESEARCH-ASSET-701eef6083bb4949 recorded that a Python interpreter loaded a script and contacted a service. The event references principal-9ed7f8cc72bbc316. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Function audit on COMMUNICATIONS-ASSET-6eba6dd15491bb00 recorded that a serverless function package and execution settings were updated. The event references principal-a52d85256a55e315. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Cloud identity audit on FINANCE-ASSET-e7ffd7ca6e67a506 recorded that a principal assumed a role in another account. The event references principal-9b4f65d2a19e9629. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Assessment SEC-91f9474661ef explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Resolver logs on FINANCE-ASSET-702feb45e71dd31e recorded that a client requested many long, high-entropy DNS labels. The event references principal-219bc21f1d685857. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-6edb44fd6914 specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"File audit on PROCUREMENT-ASSET-4eb226a25712a501 recorded that a process rewrote multiple files into encrypted containers. The event references principal-6dcdfe5a31b0546b. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Security retest SEC-847512c4e883 covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Flow logs on LEGAL-ASSET-fa7ff1fc0a223203 recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-1ef2548f2594a804. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Change CHG-a168cec8cc2e lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Repository audit on SUPPORT-ASSET-f2c722947f994337 recorded that a repository collaborator received elevated permissions. The event references principal-81983e01bdfb552d. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Kubernetes audit on LEGAL-ASSET-a4bb453a13c05590 recorded that a role binding granted a principal additional cluster permissions. The event references principal-f6d0dcce5ee82a68. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Windows logon audit on ENGINEERING-ASSET-9a2b7e9a3eb1704f recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-d502784167672763. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Compute audit on ENGINEERING-ASSET-67df6013e7bda695 recorded that a principal launched multiple compute instances. The event references principal-d74238a9b43b1893. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Repository audit on COMMUNICATIONS-ASSET-74eb656a821bda53 recorded that a repository collaborator received elevated permissions. The event references principal-aeb807368ce77066. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Cloud control audit on PEOPLE-ASSET-357f734fad0406df recorded that a session deleted a group of cloud resources. The event references principal-50a694af17f32a70. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Cloud identity audit on RESEARCH-ASSET-39f1c4acdb98407c recorded that a new programmatic access key was issued to a principal. The event references principal-16f1be9653031bee. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Configuration audit on RESEARCH-ASSET-c3d25c02edb1b375 recorded that a client proxy setting was changed. The event references principal-c2c0e84c38c559bb. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Identity audit on SALES-ASSET-08c0f29601b74bfa recorded that an account registered a new MFA method. The event references principal-4c8bc42872a0ca65. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-5d3b41f11c2a before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Backup audit on COMMUNICATIONS-ASSET-34bf9b07e39c1f16 recorded that a backup retention policy was shortened. The event references principal-e0e79be492923c4a. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Cloud control audit on OPERATIONS-ASSET-e8aae5321595ab4e recorded that a cloud logging destination was disabled. The event references principal-a8271fb4edbdf45f. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Directory audit on OPERATIONS-ASSET-f0615ba52c4fafcb recorded that a principal requested directory replication data. The event references principal-c94c73361a03e2ca. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Service audit on ENGINEERING-ASSET-5be63ef6d4ef079d recorded that a remote service-control request created and started a temporary service. The event references principal-bd2813d9252e7fbb. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Policy audit on COMMUNICATIONS-ASSET-6bd03c52fee36269 recorded that an audit policy was changed to collect fewer event categories. The event references principal-89ce4ef5b0451d62. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Repository audit on PROCUREMENT-ASSET-032fc4cf1761029e recorded that a repository collaborator received elevated permissions. The event references principal-c9c8d15f73a824e8. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-145957eb0da9 accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Runtime audit on LEGAL-ASSET-67b364f8c09b4aef recorded that a process connected to the container runtime socket. The event references principal-a26c56705eacce84. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-6332c883839f before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Api gateway logs on SUPPORT-ASSET-13bc954846049d2f recorded that a client issued a burst of API requests. The event references principal-d482be68e022a834. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Runtime audit on OPERATIONS-ASSET-b6b114583f048adf recorded that a process connected to the container runtime socket. The event references principal-2a53a47b4b50aacf. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Kubernetes audit on SUPPORT-ASSET-70672b7c7f3d80de recorded that a workload mounted a directory from its host filesystem. The event references principal-bb9a9a5a1ac32931. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"File audit on PROCUREMENT-ASSET-4eb226a25712a501 recorded that a process rewrote multiple files into encrypted containers. The event references principal-6dcdfe5a31b0546b. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Session audit on COMMUNICATIONS-ASSET-9a4f765d7218bb33 recorded that the same session token appeared from different client addresses. The event references principal-961620617e88f850. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Wmi audit on OPERATIONS-ASSET-c2921eb1d36d866a recorded that a management request started a process through WMI. The event references principal-1c1a48cb243f47fb. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-b09b4b763588 covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Storage access logs on SUPPORT-ASSET-467cdf660d5e57c4 recorded that a principal downloaded many objects from a storage bucket. The event references principal-83eeaee20b7f40f8. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Database audit on COMMUNICATIONS-ASSET-b51d02175f1c9085 recorded that a session read several tables and exported the query result. The event references principal-61c8ab03c285a7c1. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Network control audit on SALES-ASSET-bd4a95d925024567 recorded that a cloud security group gained a broad ingress rule. The event references principal-2e1769cecef25401. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Kubernetes audit on FINANCE-ASSET-4f8f4d9f800ab9a6 recorded that a cluster admission policy was changed. The event references principal-0f727ece26b623bd. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Script audit on PEOPLE-ASSET-7674cfc3c8c8d12a recorded that a script interpreter decoded an encoded argument before execution. The event references principal-15233cc20a5664b0. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Mail audit on LEGAL-ASSET-131d8c518786695c recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-3bea6da72e330e1b. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Secret manager audit on PEOPLE-ASSET-406b99330a23361c recorded that a workload read several secret versions. The event references principal-c3699eaad53ba8ba. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Process audit on PEOPLE-ASSET-b5f000212e4e1683 recorded that a Python interpreter loaded a script and contacted a service. The event references principal-364f40722069431e. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Dhcp telemetry on RESEARCH-ASSET-e4b53bee781b0891 recorded that a server issued DHCP offers on a monitored segment. The event references principal-7d24baa0336a4972. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-f9635a124ed8 before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Federation audit on LEGAL-ASSET-81a8982089dddbeb recorded that a tenant federation setting was updated. The event references principal-c29fe59344f3b4d5. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-38bf7086c8b9, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Kerberos audit on PEOPLE-ASSET-4ee9a55c8fd9d93a recorded that an account requested service tickets for multiple services. The event references principal-0978a46d6664fc2a. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"File audit on ENGINEERING-ASSET-1a60a1286916ad01 recorded that access permissions were broadened on a directory tree. The event references principal-1a1a48bb1e529fb0. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-071b4999b07f match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Network control audit on LEGAL-ASSET-8a1d97d0c15ac118 recorded that a cloud security group gained a broad ingress rule. The event references principal-52d39a8366e69bf4. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Assessment SEC-552a489c2d23 explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Service audit on LEGAL-ASSET-c27c6fe8739fc291 recorded that a remote service-control request created and started a temporary service. The event references principal-473978dbe47e2846. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Kubernetes audit on COMMUNICATIONS-ASSET-396281c213cbfe7d recorded that a role binding granted a principal additional cluster permissions. The event references principal-490795a3fa64d894. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-483b62e36618 accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Federation audit on SUPPORT-ASSET-9d7cd1e21b7e712c recorded that a tenant federation setting was updated. The event references principal-1761e65ce57d1289. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Proxy logs on PROCUREMENT-ASSET-a90cefc8840eb875 recorded that a client transferred a large payload to an external storage endpoint. The event references principal-58357f3106f790fd. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Agent audit on PROCUREMENT-ASSET-92d810ab505277a2 recorded that a privileged session changed endpoint monitoring settings. The event references principal-ae67200926ed1d7a. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Cloud identity audit on COMMUNICATIONS-ASSET-a2643d4e14311066 recorded that a principal assumed a role in another account. The event references principal-3ce172a931fefefa. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-e5661f32334d before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Key service audit on SALES-ASSET-4796409e71ec7ec0 recorded that a principal issued a burst of key-service decrypt requests. The event references principal-e868bdfcec891314. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Security retest SEC-3172b3f5e4dc covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Event service audit on SALES-ASSET-c924bb512f8f20fd recorded that an event log was cleared by a privileged request. The event references principal-c440dcbeadedc4d2. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Storage audit on FINANCE-ASSET-768fdc22d9585f23 recorded that an object-storage access policy was broadened. The event references principal-18ac2fe076b447b0. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Cloud identity audit on PEOPLE-ASSET-f0da82528453fc68 recorded that a principal received a policy granting additional permissions. The event references principal-c5a646fec9c6789b. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Cron audit on PROCUREMENT-ASSET-ccd7b77f6fbe55e6 recorded that a recurring job definition was added to the system schedule. The event references principal-ff6d598ce8d74f2d. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Dns server audit on RESEARCH-ASSET-ea10daa512b8b485 recorded that a client requested a DNS zone transfer. The event references principal-8e8e3e27caaa4cef. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Browser audit on SUPPORT-ASSET-089bd1e438aae68a recorded that a browser extension with page-reading permissions was installed. The event references principal-05dd057e76f4173e. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Directory audit on COMMUNICATIONS-ASSET-014161d1ab75992f recorded that a principal requested directory replication data. The event references principal-06ff5e4392c8395e. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Browser audit on LEGAL-ASSET-df49de2f96b43b40 recorded that a browser extension with page-reading permissions was installed. The event references principal-010a6a482ee1c838. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Account audit on ENGINEERING-ASSET-bce5c50695a23c43 recorded that a local user account was created on a managed system. The event references principal-1a94579d85980de4. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Secret manager audit on COMMUNICATIONS-ASSET-0901e5043739c868 recorded that a workload read several secret versions. The event references principal-811d7f224d798eaf. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Code integrity audit on LEGAL-ASSET-f6d743064b804557 recorded that an executable without a publisher signature started from a writable directory. The event references principal-4ea2e2cfcda079aa. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-7bbc131e5888 match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Switch telemetry on PEOPLE-ASSET-2fae865ac519b354 recorded that an address mapping changed repeatedly on a local segment. The event references principal-cadf13732271e411. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Secret manager audit on COMMUNICATIONS-ASSET-0901e5043739c868 recorded that a workload read several secret versions. The event references principal-811d7f224d798eaf. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Package registry audit on SUPPORT-ASSET-ad8575a16b60726c recorded that a principal published a new package version. The event references principal-b9b60013a399b75b. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"File audit on COMMUNICATIONS-ASSET-4e97ae367849b7ff recorded that a process deleted many files within a short interval. The event references principal-0d2d1e13b6f37e28. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-92e6173d09bc, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Windows logon audit on PROCUREMENT-ASSET-6de9173566128253 recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-1e31ae283e3821b5. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Change CHG-fa1d27da50ac lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Code integrity audit on ENGINEERING-ASSET-bc88477a091db102 recorded that an executable without a publisher signature started from a writable directory. The event references principal-26a79bf54e5ed1d5. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-426844adf496, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Wmi audit on SALES-ASSET-54ac6fc961ae7d6a recorded that a management request started a process through WMI. The event references principal-08c8fa6d75a3b195. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Security retest SEC-d49c8129162e covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Storage audit on SUPPORT-ASSET-4d8e24bcff05f227 recorded that an object-storage access policy was broadened. The event references principal-5112ec3a6a51c1b1. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Dns control audit on LEGAL-ASSET-b16c2ea371640162 recorded that an authoritative DNS record was updated. The event references principal-162d081f9776c04e. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Share audit on COMMUNICATIONS-ASSET-155e7e0f58a0bc23 recorded that a new network file share was published. The event references principal-91339ef7c416f6ed. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Process audit on LEGAL-ASSET-1d30eece58fd02aa recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-73ea530a0de82f6d. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Wmi audit on ENGINEERING-ASSET-9642a3ef1a26edcb recorded that a management request started a process through WMI. The event references principal-4a2b4bdee8c5d199. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Change CHG-7450cb200a44 lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Registry audit on SUPPORT-ASSET-3b0593850dd40f7b recorded that a registry logon-start entry was created. The event references principal-d3ff9c757ce4b24b. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Flow logs on ENGINEERING-ASSET-6ee9ce19d8b1f530 recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-5923ac86626d7de4. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-6bb0b94c43dd match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Kubernetes audit on PROCUREMENT-ASSET-a7191d519031e89b recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-a4246f24c83acd17. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Systemd audit on COMMUNICATIONS-ASSET-83d44af530d70e5a recorded that a service unit file was changed and the unit reloaded. The event references principal-fef91c85181668d1. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Script audit on ENGINEERING-ASSET-e2ddc97a2c3f555e recorded that a script interpreter decoded an encoded argument before execution. The event references principal-f5db620bfae68583. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Dns server audit on SALES-ASSET-76b84b3e5488545e recorded that a client requested a DNS zone transfer. The event references principal-2d34f2bcf00115a7. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-2435de04b5c4 specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Repository audit on RESEARCH-ASSET-f2f0b485da92764a recorded that a repository collaborator received elevated permissions. The event references principal-883f23b0e04d7f14. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Process audit on SALES-ASSET-796c322bf9ce4051 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-eb12aa9934f163d5. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Application audit on COMMUNICATIONS-ASSET-365eaf894be6367d recorded that an application read clipboard contents repeatedly. The event references principal-c9d903188ad53746. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-9ea49b505462 match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Directory audit on SUPPORT-ASSET-657351ecbd6ea04f recorded that a principal requested directory replication data. The event references principal-415e143ac445aa25. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Firewall audit on PROCUREMENT-ASSET-2bed3490436bbbc8 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-90a45122531200f3. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Cloud control audit on LEGAL-ASSET-57d9881033f6b349 recorded that resources were created in a region with little prior activity. The event references principal-3d1e3e3a52fd0eed. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Cloud identity audit on FINANCE-ASSET-b948d8305372c015 recorded that a new programmatic access key was issued to a principal. The event references principal-68bd58abfea31389. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Kubernetes audit on RESEARCH-ASSET-200dc8ad3542be6e recorded that a role binding granted a principal additional cluster permissions. The event references principal-b8023dd958201bec. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"File audit on COMMUNICATIONS-ASSET-aa99d2f314263fcc recorded that a process compressed files from several directories into an archive. The event references principal-f14ddee6e5692d20. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-028690f81adb match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Mail and proxy logs on SUPPORT-ASSET-79dbee71e86c40be recorded that a user opened a URL delivered in an email message. The event references principal-1603764c68a231e0. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-ff5c235103eb match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Event service audit on RESEARCH-ASSET-79d1b62714d14ec4 recorded that an event log was cleared by a privileged request. The event references principal-78e29e015c8aeb2f. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Flow logs on COMMUNICATIONS-ASSET-d5fd0288e752f79f recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-fd4faa7e0445166d. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Pki audit on ENGINEERING-ASSET-1be9c96304b0e927 recorded that a principal requested a certificate using an authentication template. The event references principal-86425f445bb7386e. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Application audit on RESEARCH-ASSET-44de8cf55f1c805f recorded that an application requested repeated screen captures. The event references principal-17ee862a652063ef. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Backup audit on PROCUREMENT-ASSET-8055bd5873ef3941 recorded that a backup retention policy was shortened. The event references principal-ab63e55288bca196. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Cron audit on OPERATIONS-ASSET-837b3c551a9b50e7 recorded that a recurring job definition was added to the system schedule. The event references principal-96fb058b67291144. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Systemd audit on COMMUNICATIONS-ASSET-83d44af530d70e5a recorded that a service unit file was changed and the unit reloaded. The event references principal-fef91c85181668d1. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-5df54cd4592a before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Script audit on OPERATIONS-ASSET-df5c95ab3d436943 recorded that a script interpreter decoded an encoded argument before execution. The event references principal-d244a19c467082bb. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Smb audit on SUPPORT-ASSET-e1998cccd3abd998 recorded that a session enumerated a file share and read multiple files. The event references principal-3be2aaf5e58c794d. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Mfa audit on OPERATIONS-ASSET-60e8646a52166a20 recorded that multiple MFA challenges were issued during a short interval. The event references principal-db3cac7564325f27. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-fa58f86f4676 before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"File audit on COMMUNICATIONS-ASSET-7174b9fee0b011b4 recorded that a process rewrote multiple files into encrypted containers. The event references principal-8e2fefcd77348cfa. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-4ed2c68523fd covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Kerberos audit on PEOPLE-ASSET-4ee9a55c8fd9d93a recorded that an account requested service tickets for multiple services. The event references principal-0978a46d6664fc2a. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Vpn audit on PROCUREMENT-ASSET-af5dcb9896a63a8e recorded that a remote-access VPN session was established. The event references principal-29a685b020122aec. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Key service audit on ENGINEERING-ASSET-a77dccd54b04aa48 recorded that a principal issued a burst of key-service decrypt requests. The event references principal-627115d6ce1d6169. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-ded893ef2d9a covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Saas audit on RESEARCH-ASSET-b155eac613e67224 recorded that a user requested a bulk export from a business application. The event references principal-5a3ba2a9838be78e. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Assessment SEC-4cd3c2a0fbf7 explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Cloud control audit on SUPPORT-ASSET-50842d406b871613 recorded that a session deleted a group of cloud resources. The event references principal-5fa6a0bc38223f91. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Process audit on SUPPORT-ASSET-6a54632d13cc3523 recorded that a JavaScript interpreter executed a local script. The event references principal-5989897ff7bc53ab. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Pki audit on SUPPORT-ASSET-70be4dd0be19b589 recorded that a principal requested a certificate using an authentication template. The event references principal-3490e3ca6541e91e. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-3de4617f4158 specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Event service audit on OPERATIONS-ASSET-6bb0ff67f6f8dbd2 recorded that an event log was cleared by a privileged request. The event references principal-1c69ef2988f5b8db. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-f99060f953c4, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Module audit on SUPPORT-ASSET-75579d877216839e recorded that a process loaded a library from an application-local directory. The event references principal-bf9534edb641c536. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Storage audit on ENGINEERING-ASSET-b38bdd9cc61bbac2 recorded that an object-storage access policy was broadened. The event references principal-8585f4d7b4e61651. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Federation audit on SALES-ASSET-88538f554d17e7e6 recorded that a tenant federation setting was updated. The event references principal-caaf0b98849ffd32. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Assessment SEC-6dd74a2222ad explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Macos launch audit on SUPPORT-ASSET-650496733d825be0 recorded that a launch agent definition was installed in a user context. The event references principal-0735ac9998e5203b. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Script audit on SALES-ASSET-5accd98a99abf46d recorded that a script interpreter decoded an encoded argument before execution. The event references principal-9d518b079e49f304. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Systemd audit on SALES-ASSET-4e41129f633ac17f recorded that a service unit file was changed and the unit reloaded. The event references principal-6e1812150b898dbc. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Registry audit on FINANCE-ASSET-6f5ecd36af234140 recorded that a registry logon-start entry was created. The event references principal-ce9587e0dadb3215. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Oauth audit on FINANCE-ASSET-ab8c40ef4ea54ef3 recorded that an application received consent for additional account scopes. The event references principal-c6dc8dd297f2cce8. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Network control audit on PROCUREMENT-ASSET-296ab163f292467f recorded that a cloud security group gained a broad ingress rule. The event references principal-485bf1fa128db935. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-dd7838ed7efc, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Pki audit on FINANCE-ASSET-3748aa367e539143 recorded that a principal requested a certificate using an authentication template. The event references principal-d4df29576d1acbb5. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Office audit on ENGINEERING-ASSET-8b497889760890b7 recorded that a document macro launched a child interpreter. The event references principal-348623c716d723c6. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-b0d325a185be before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Wmi audit on SALES-ASSET-54ac6fc961ae7d6a recorded that a management request started a process through WMI. The event references principal-08c8fa6d75a3b195. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Group audit on OPERATIONS-ASSET-0c05abbcb3b78111 recorded that an account was added to a privileged local group. The event references principal-67db77b910dcd61e. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Mail flow logs on ENGINEERING-ASSET-b3fe8e13b124582a recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-4618a2ddb02b8454. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Mail flow logs on SALES-ASSET-40ddb7fd75836262 recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-4279d4843faab477. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Service audit on SALES-ASSET-ee4f4ed67afc3eae recorded that a new automatically started service was registered. The event references principal-ae21c97b6a858bb0. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Security retest SEC-25994e75c2ed covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Function audit on COMMUNICATIONS-ASSET-6eba6dd15491bb00 recorded that a serverless function package and execution settings were updated. The event references principal-a52d85256a55e315. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-6020a477f6fd explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Network control audit on FINANCE-ASSET-93401772cf68a3aa recorded that a cloud security group gained a broad ingress rule. The event references principal-b7b99f534a1030f4. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Application audit on ENGINEERING-ASSET-83152a55ea1c27b8 recorded that an application read clipboard contents repeatedly. The event references principal-d08677bd055caebe. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-5f849f943496 explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Process audit on COMMUNICATIONS-ASSET-3540d4ca6c64eb07 recorded that a remote-support application started an interactive session. The event references principal-e3fe7b2bae9cee75. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Identity audit on FINANCE-ASSET-8c4f9dd18c643b5e recorded that repeated failed sign-ins were recorded for an account. The event references principal-e15b307c4e5bf156. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Service audit on PROCUREMENT-ASSET-7131a22a8a5e3488 recorded that a new automatically started service was registered. The event references principal-7eed072979ca83fe. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Assessment SEC-56d95849e793 explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Cloud identity audit on RESEARCH-ASSET-8d54a31e0957dabb recorded that a principal assumed a role in another account. The event references principal-8a3eb5c757201646. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Systemd audit on RESEARCH-ASSET-eeb116f31cbce82f recorded that a service unit file was changed and the unit reloaded. The event references principal-f39102d395b571c9. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-905bff863e09 match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Service audit on PEOPLE-ASSET-7556bd332c3c0972 recorded that a remote service-control request created and started a temporary service. The event references principal-40ab931ed8bd0b59. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Database audit on SALES-ASSET-19142cf000a582b0 recorded that a session read several tables and exported the query result. The event references principal-5991e381a26e4376. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Security retest SEC-453705ad73a7 covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Service audit on SUPPORT-ASSET-bed8c4ced0655fc1 recorded that a remote service-control request created and started a temporary service. The event references principal-74bec1dcad5113eb. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"File audit on PEOPLE-ASSET-df8464b337d342a5 recorded that a process deleted many files within a short interval. The event references principal-f13400db0397fece. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Change CHG-6f2add6a40bc lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Identity audit on COMMUNICATIONS-ASSET-2afac15aebb6997b recorded that an account registered a new MFA method. The event references principal-48533b26142b2db4. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Share audit on COMMUNICATIONS-ASSET-155e7e0f58a0bc23 recorded that a new network file share was published. The event references principal-91339ef7c416f6ed. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Compute audit on COMMUNICATIONS-ASSET-36b3449238b8f470 recorded that a principal launched multiple compute instances. The event references principal-36e251f09c18691b. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-bd89d22266c8 before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Function audit on PEOPLE-ASSET-7a184783e26cf4b6 recorded that a serverless function package and execution settings were updated. The event references principal-20e08b043fa3eb3a. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-aea3da9ba3d2 before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Kubernetes audit on COMMUNICATIONS-ASSET-a5023ab9f641c1cb recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-8da42e51a76b5b34. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Registry audit on OPERATIONS-ASSET-2d36b1b63d0c4ad6 recorded that a workload pulled a container image from a registry. The event references principal-1fdf41d42655dccc. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-d18f0fb4db5e explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Macos launch audit on PEOPLE-ASSET-f2ccd0993eb11ff9 recorded that a launch agent definition was installed in a user context. The event references principal-ff81666bc8b89437. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-20b5cf30f87e specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Cloud control audit on FINANCE-ASSET-874d671033c104d1 recorded that a cloud logging destination was disabled. The event references principal-b52f94a7d99dc7bf. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-4f49c59dca50 match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Proxy logs on ENGINEERING-ASSET-55fbfe9ce1b9adb6 recorded that a client transferred a large payload to an external storage endpoint. The event references principal-9db93a1b04a04fcd. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Identity audit on COMMUNICATIONS-ASSET-4abec775a52c95c2 recorded that repeated failed sign-ins were recorded for an account. The event references principal-a42f44848e926187. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-c5fcc3ba5393 match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Directory audit on RESEARCH-ASSET-717c1ed36129eee9 recorded that a principal requested directory replication data. The event references principal-71255b0539b4ae1e. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-278977d61497 before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Mail audit on RESEARCH-ASSET-fad2d601f38f7cda recorded that an account received delegated access to a mailbox. The event references principal-b5e074cc28811f03. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Cloud identity audit on FINANCE-ASSET-44723c4a98b3d8ba recorded that a principal received a policy granting additional permissions. The event references principal-ddbfe461888a8cb6. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Service audit on OPERATIONS-ASSET-fd16a6acf8f54a9a recorded that a new automatically started service was registered. The event references principal-c9af46ed7e55064b. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-276f3164aa47 specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Browser audit on COMMUNICATIONS-ASSET-242d23ba4ad50b88 recorded that a browser extension with page-reading permissions was installed. The event references principal-c4eaf539de0f6aa8. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Windows logon audit on SUPPORT-ASSET-b7addff92f67af33 recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-5b8a266b76f35fee. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-d619d8c5e1d8 specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Cron audit on ENGINEERING-ASSET-0d57cc07ded38310 recorded that a recurring job definition was added to the system schedule. The event references principal-db05c7bee0f112c7. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-4ec013f0d813 match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Process audit on RESEARCH-ASSET-a06368c20e1f1761 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-c27d38810eca0fcd. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Windows logon audit on FINANCE-ASSET-08f4600838c704c1 recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-9a25429fc1580f3b. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-98e85f54a44d match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Code integrity audit on COMMUNICATIONS-ASSET-ae65063c9a0dd2a0 recorded that an executable without a publisher signature started from a writable directory. The event references principal-32fc5fcb369ae6d2. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-10c6da8b8abc before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"File audit on PEOPLE-ASSET-cc74b22d2c2ca8f7 recorded that a process compressed files from several directories into an archive. The event references principal-e9c54c5535050840. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Dns server audit on COMMUNICATIONS-ASSET-3ba853c8b87dee93 recorded that a client requested a DNS zone transfer. The event references principal-fbb1839d1793e373. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Identity audit on LEGAL-ASSET-10052cae7e6f5c6e recorded that an account password was reset through a recovery workflow. The event references principal-69df9c6ec5ef584b. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Assessment SEC-9420679a032c explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Cron audit on LEGAL-ASSET-fa5ca79bc164009d recorded that a recurring job definition was added to the system schedule. The event references principal-07e12ac009730cba. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Cloud identity audit on OPERATIONS-ASSET-e9ea023dcfe573c8 recorded that a principal assumed a role in another account. The event references principal-33e2cf770673f137. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Application audit on ENGINEERING-ASSET-c6a3af2b55d88d84 recorded that a runtime configuration setting was updated. The event references principal-67b63805e0368323. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Script audit on SALES-ASSET-5accd98a99abf46d recorded that a script interpreter decoded an encoded argument before execution. The event references principal-9d518b079e49f304. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Database audit on PROCUREMENT-ASSET-88d6e016f81704ea recorded that a session changed a database table definition. The event references principal-a7367e91f7bc0a1d. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Cloud identity audit on PROCUREMENT-ASSET-ec7ad16199b37527 recorded that a principal received a policy granting additional permissions. The event references principal-8b968a5cde5474fa. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-d1451a5b8b62 before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Event service audit on ENGINEERING-ASSET-93dff18c1d7d23e9 recorded that an event log was cleared by a privileged request. The event references principal-32227ffe2b6b23ca. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Cloud control audit on OPERATIONS-ASSET-31b25a4a2bbf0f7e recorded that resources were created in a region with little prior activity. The event references principal-2043ac1bd7256aa6. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-d4e73e19c5db accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Cloud control audit on PROCUREMENT-ASSET-1ca061884feb0239 recorded that a session deleted a group of cloud resources. The event references principal-bde2c278c233490d. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-5f3dacbc2df2 match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Session audit on ENGINEERING-ASSET-bc4c94aa37fb4f60 recorded that the same session token appeared from different client addresses. The event references principal-821aec91dc2aa8b4. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Api gateway logs on OPERATIONS-ASSET-5d940a8c3c4b311c recorded that a client issued a burst of API requests. The event references principal-9965146148dbdc29. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Mfa audit on PEOPLE-ASSET-e45fffd30cf466e9 recorded that multiple MFA challenges were issued during a short interval. The event references principal-3cbfe5aa85664020. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-ff6a44d07033 before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Storage access logs on RESEARCH-ASSET-59340bda9ea1f273 recorded that a principal downloaded many objects from a storage bucket. The event references principal-516ae6385fac5df9. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Network control audit on PROCUREMENT-ASSET-296ab163f292467f recorded that a cloud security group gained a broad ingress rule. The event references principal-485bf1fa128db935. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Process audit on OPERATIONS-ASSET-a738dad8c83d20bb recorded that a JavaScript interpreter executed a local script. The event references principal-ba7460ce51b6b106. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-322d754f8409 covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Resolver logs on COMMUNICATIONS-ASSET-064116140685fdd2 recorded that a client requested many long, high-entropy DNS labels. The event references principal-a53098877c1921c0. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Kubernetes audit on PROCUREMENT-ASSET-a7191d519031e89b recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-a4246f24c83acd17. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Task scheduler audit on COMMUNICATIONS-ASSET-3b8f70e54b109a07 recorded that a scheduled task was registered to execute a program at logon. The event references principal-ea7b65d7a85105ed. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-a6f827999475 before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Configuration audit on LEGAL-ASSET-654fecba9ad263c2 recorded that a client proxy setting was changed. The event references principal-40cdbd7119e49afd. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Firewall audit on ENGINEERING-ASSET-4346eb459a11971a recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-62f6e1ae625e9e27. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Task scheduler audit on PEOPLE-ASSET-967b5df7e748b2ff recorded that a scheduled task was registered to execute a program at logon. The event references principal-80092436d4633e85. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Application audit on SALES-ASSET-a8b331f6bbbdf2ee recorded that a runtime configuration setting was updated. The event references principal-21cb8dcf748912e9. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Identity audit on LEGAL-ASSET-3e81b75ec6767272 recorded that repeated failed sign-ins were recorded for an account. The event references principal-4e9f85f638a1922a. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Egress flow logs on SALES-ASSET-a811cdcc9969f943 recorded that a workload opened an encrypted connection to an external service. The event references principal-17514c019150a73d. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"File audit on OPERATIONS-ASSET-a77dace88afed479 recorded that a process rewrote multiple files into encrypted containers. The event references principal-9bd0bfba4bc5c80f. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-f27e311f439a before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Configuration audit on PEOPLE-ASSET-5afa9d0b44139e46 recorded that a client proxy setting was changed. The event references principal-c6f3609cd125d978. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Ci audit on SUPPORT-ASSET-be888d94d309deab recorded that a build pipeline definition gained a new execution step. The event references principal-f55be257f884a1b4. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Switch telemetry on SUPPORT-ASSET-8a0f455136f22cce recorded that an address mapping changed repeatedly on a local segment. The event references principal-598fd0cdb7a2c2dd. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Oauth audit on FINANCE-ASSET-ab8c40ef4ea54ef3 recorded that an application received consent for additional account scopes. The event references principal-c6dc8dd297f2cce8. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Agent audit on LEGAL-ASSET-6d17adf81f6fe3af recorded that a privileged session changed endpoint monitoring settings. The event references principal-f72780533376e28a. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Registry audit on SUPPORT-ASSET-3b0593850dd40f7b recorded that a registry logon-start entry was created. The event references principal-d3ff9c757ce4b24b. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-9dafe0e0a6a2 covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Vpn audit on LEGAL-ASSET-89bfbe721ce26047 recorded that a remote-access VPN session was established. The event references principal-2ac6b6b7ff50c84a. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Module audit on OPERATIONS-ASSET-da72125783fc7146 recorded that a process loaded a library from an application-local directory. The event references principal-88a37cd2d0222e86. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Backup audit on COMMUNICATIONS-ASSET-34bf9b07e39c1f16 recorded that a backup retention policy was shortened. The event references principal-e0e79be492923c4a. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Office audit on COMMUNICATIONS-ASSET-9792dd26544328c7 recorded that a document macro launched a child interpreter. The event references principal-794c3f6a93ed6b1f. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Mail audit on COMMUNICATIONS-ASSET-dece9873e2e03f6f recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-3d08b8fe271ddda1. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Cloud identity audit on PEOPLE-ASSET-120c32cb226f1634 recorded that a new programmatic access key was issued to a principal. The event references principal-1aef76f9cfa1105d. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"File audit on SUPPORT-ASSET-0129618ced8fc8ec recorded that a process compressed files from several directories into an archive. The event references principal-8432d907b9ba200c. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Certificate audit on PEOPLE-ASSET-4d0259660c317b95 recorded that a service certificate was replaced. The event references principal-f191ea3a323e48f8. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Kubernetes audit on RESEARCH-ASSET-ca81e4dea7e4d440 recorded that a workload mounted a directory from its host filesystem. The event references principal-142014dd00377291. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Runtime audit on SUPPORT-ASSET-70bd103925bca47e recorded that a process connected to the container runtime socket. The event references principal-cf65589a3d4ad7b6. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Flow logs on PROCUREMENT-ASSET-cd965c50b19b4b1f recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-3abc068e3f191445. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Agent audit on SUPPORT-ASSET-9325bde68edaa545 recorded that a privileged session changed endpoint monitoring settings. The event references principal-1641f4bad60d9f93. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-261579b999e9 covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Kubernetes audit on SUPPORT-ASSET-99bd1381f9f84168 recorded that a pod was created with privileged execution enabled. The event references principal-4de29bd2a93d9674. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Pki audit on FINANCE-ASSET-3748aa367e539143 recorded that a principal requested a certificate using an authentication template. The event references principal-d4df29576d1acbb5. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-fe3137163d44 match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Storage audit on SALES-ASSET-54a03152e889d43f recorded that a session deleted several storage snapshots. The event references principal-69a5261a8cfb5a4d. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Saas audit on FINANCE-ASSET-7dbfabaebbf506b5 recorded that a user requested a bulk export from a business application. The event references principal-147dd62c19db648c. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Registry audit on PEOPLE-ASSET-2d7ca72857a14112 recorded that a workload pulled a container image from a registry. The event references principal-f31f9ebfd4a3d389. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Database audit on SALES-ASSET-19142cf000a582b0 recorded that a session read several tables and exported the query result. The event references principal-5991e381a26e4376. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Database audit on ENGINEERING-ASSET-2c4914b84c80f08c recorded that a session read several tables and exported the query result. The event references principal-b17a9277af7e3124. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Script audit on ENGINEERING-ASSET-e2ddc97a2c3f555e recorded that a script interpreter decoded an encoded argument before execution. The event references principal-f5db620bfae68583. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Kubernetes audit on PEOPLE-ASSET-fb423ebd814658c2 recorded that a role binding granted a principal additional cluster permissions. The event references principal-1e6683e3ee80066c. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Configuration audit on FINANCE-ASSET-74d3e5b9407ece66 recorded that a client proxy setting was changed. The event references principal-00bf9f3d44fd549a. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Mfa audit on PROCUREMENT-ASSET-9ec036de13de448d recorded that multiple MFA challenges were issued during a short interval. The event references principal-906c50bf72cf0c69. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Group audit on PEOPLE-ASSET-f5ce370c9062d00a recorded that an account was added to a privileged local group. The event references principal-a4fe590d9388b8ea. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Cloud control audit on LEGAL-ASSET-428365c6643172ec recorded that a cloud logging destination was disabled. The event references principal-5fcf49df98dad6ed. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Resolver logs on OPERATIONS-ASSET-5135623224ddfa0b recorded that a client requested many long, high-entropy DNS labels. The event references principal-4817944b772fb8eb. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"File audit on COMMUNICATIONS-ASSET-7174b9fee0b011b4 recorded that a process rewrote multiple files into encrypted containers. The event references principal-8e2fefcd77348cfa. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Process audit on OPERATIONS-ASSET-6a681893d2f34701 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-7a707bcde872789a. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"File audit on SUPPORT-ASSET-0129618ced8fc8ec recorded that a process compressed files from several directories into an archive. The event references principal-8432d907b9ba200c. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Driver audit on RESEARCH-ASSET-5b972011692602fc recorded that a kernel driver was loaded after a package installation. The event references principal-71a994ae28cc3c7a. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-334d91865b6f specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Session audit on FINANCE-ASSET-15bdb8a9163b0abc recorded that the same session token appeared from different client addresses. The event references principal-ce316de1911fbf84. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Change CHG-17293d74a05e lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Agent audit on SALES-ASSET-4f0c6ee9e7bb90ab recorded that a privileged session changed endpoint monitoring settings. The event references principal-b547aa127479e0eb. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Repository audit on RESEARCH-ASSET-f2f0b485da92764a recorded that a repository collaborator received elevated permissions. The event references principal-883f23b0e04d7f14. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Agent audit on ENGINEERING-ASSET-d4aa23315bb70413 recorded that a privileged session changed endpoint monitoring settings. The event references principal-2e08cdbbea0a15c2. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Certificate audit on SALES-ASSET-d2e9e0997da46974 recorded that a service certificate was replaced. The event references principal-0e407d6273aa8758. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Firewall audit on OPERATIONS-ASSET-f066243659fb5412 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-9b3165faa785f1a5. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"File access audit on SALES-ASSET-da211711ae9c0eb7 recorded that a process opened a local credential-store file. The event references principal-d1b0980809a9edd2. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-98cae1f2ef09, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Service audit on RESEARCH-ASSET-8d77d8342c20fbff recorded that a remote service-control request created and started a temporary service. The event references principal-211275ad14685644. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-c126ed25a361 match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Runtime audit on PROCUREMENT-ASSET-ef2802409ab5a514 recorded that a process connected to the container runtime socket. The event references principal-81a676edf02534d4. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Identity audit on PROCUREMENT-ASSET-847c16861843d993 recorded that repeated failed sign-ins were recorded for an account. The event references principal-177e5d83a23e0f5b. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Macos launch audit on OPERATIONS-ASSET-26bdf3f25161f2be recorded that a launch agent definition was installed in a user context. The event references principal-707a961a9c8924fd. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Oauth audit on ENGINEERING-ASSET-6abd006369fb2ea6 recorded that an application received consent for additional account scopes. The event references principal-7b515ef2be2fa58b. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Waf logs on OPERATIONS-ASSET-b7ed82085f777d6d recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-82b5142e40756445. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Windows logon audit on PEOPLE-ASSET-45fa406199d2c14e recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-291516c4491afd57. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-2c2c32878172 before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Dhcp telemetry on SUPPORT-ASSET-ea5b723e111a60c0 recorded that a server issued DHCP offers on a monitored segment. The event references principal-f0fe04f7d6936857. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Database audit on PEOPLE-ASSET-aeb9e932203e4086 recorded that a session changed a database table definition. The event references principal-4c123413716680f3. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Mail audit on PEOPLE-ASSET-23ff12ac4cce3df1 recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-210b267fe07fa398. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Backup audit on SUPPORT-ASSET-cc26a0f722f080c9 recorded that a backup retention policy was shortened. The event references principal-d64cfde7265390a0. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-5f9ce19e951f accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Repository audit on RESEARCH-ASSET-ddfa89ff412603e8 recorded that a user cloned several source repositories. The event references principal-a086fb65d451cd31. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Browser audit on SALES-ASSET-2c13db88f9fe11a1 recorded that a browser extension with page-reading permissions was installed. The event references principal-dfbfeb6ce6f75d60. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Compute audit on ENGINEERING-ASSET-67df6013e7bda695 recorded that a principal launched multiple compute instances. The event references principal-d74238a9b43b1893. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-0f3075d23d22, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Firewall audit on PEOPLE-ASSET-957a449c8e927512 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-3d550d011d922017. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Process audit on PEOPLE-ASSET-b5f000212e4e1683 recorded that a Python interpreter loaded a script and contacted a service. The event references principal-364f40722069431e. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-57b2dea500bb, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Cron audit on OPERATIONS-ASSET-837b3c551a9b50e7 recorded that a recurring job definition was added to the system schedule. The event references principal-96fb058b67291144. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Code integrity audit on FINANCE-ASSET-17d7fd3ccdbe7a13 recorded that an executable without a publisher signature started from a writable directory. The event references principal-8715ecce18f6c074. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Registry audit on SALES-ASSET-2cd7195afaa340c4 recorded that a registry logon-start entry was created. The event references principal-4dafe2d9d91101fd. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Mail flow logs on LEGAL-ASSET-692e1a748d08a501 recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-527175c687849d2d. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Wmi audit on FINANCE-ASSET-9fd34fa594551e66 recorded that a management request started a process through WMI. The event references principal-1f38151c7990e366. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Egress flow logs on OPERATIONS-ASSET-2513c8d77423854c recorded that a workload opened an encrypted connection to an external service. The event references principal-ec2152640ea901f5. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-7b05bf9df85f accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"File access audit on PEOPLE-ASSET-4246817b50ce1d24 recorded that a process opened a local credential-store file. The event references principal-69567a3aa8e45657. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Browser audit on PEOPLE-ASSET-48ee486909d7e37c recorded that a browser extension with page-reading permissions was installed. The event references principal-0d329542446b1b23. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Storage access logs on SALES-ASSET-9e32b40d91582c35 recorded that a principal downloaded many objects from a storage bucket. The event references principal-71bb68cca0a6547d. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Secret manager audit on SUPPORT-ASSET-c293b34ccf018f66 recorded that a workload read several secret versions. The event references principal-e464eb0ee46edc73. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Kubernetes audit on PEOPLE-ASSET-46959b0322e15f66 recorded that a pod was created with privileged execution enabled. The event references principal-8e6c04f200191e81. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-72c5b4eaf3f3 accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Module audit on PEOPLE-ASSET-4e7e86d1ce25eca1 recorded that a process loaded a library from an application-local directory. The event references principal-32a2611884a3eb03. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-65a861d46792 explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Identity audit on RESEARCH-ASSET-88e52266f5af4a21 recorded that a service account established an interactive session. The event references principal-d08379cdebfa5913. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Process access audit on PROCUREMENT-ASSET-a371e419fb9da077 recorded that a process requested read access to another process memory space. The event references principal-47b9eca6b126bee7. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Cloud identity audit on OPERATIONS-ASSET-04350815f02c233e recorded that a new programmatic access key was issued to a principal. The event references principal-3f0b6fed7f9bbd92. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-e0988b378b33 explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Winrm audit on FINANCE-ASSET-f7f3ea9e3a52d83c recorded that a remote management session invoked a command on a managed host. The event references principal-13d8273b51b14066. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Kubernetes audit on SALES-ASSET-b7d7628f8816a948 recorded that a role binding granted a principal additional cluster permissions. The event references principal-76cb7e33983ecb6a. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-21d31f74927b, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Mail audit on SUPPORT-ASSET-d04332aa87461fec recorded that an account received delegated access to a mailbox. The event references principal-4bd49edb0535ebaf. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-4502587df860 match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Directory audit on ENGINEERING-ASSET-74de670cde6f3c91 recorded that a principal requested directory replication data. The event references principal-2491cc3af8b17009. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Process audit on ENGINEERING-ASSET-db715ea0863774ba recorded that a remote-support application started an interactive session. The event references principal-ca4d1a946cc4272b. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-5258746bdc6b explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"File audit on LEGAL-ASSET-bda990f3a65f05d4 recorded that a process compressed files from several directories into an archive. The event references principal-e0bfbf7c864c739b. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Dns control audit on PROCUREMENT-ASSET-a2a68c2dd932f661 recorded that an authoritative DNS record was updated. The event references principal-d6b239df277e509a. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Application audit on OPERATIONS-ASSET-82d2279115651372 recorded that an application read clipboard contents repeatedly. The event references principal-d93f4c8e19d295a8. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Cloud control audit on SUPPORT-ASSET-50842d406b871613 recorded that a session deleted a group of cloud resources. The event references principal-5fa6a0bc38223f91. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-2717e63b0352 match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Application audit on LEGAL-ASSET-988ab05a6aaafddb recorded that a runtime configuration setting was updated. The event references principal-2cc56950de78c750. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Browser audit on ENGINEERING-ASSET-f6edb397c93f1bb4 recorded that a browser extension with page-reading permissions was installed. The event references principal-bf7a3feca21483cd. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-67a0264d055b covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Database audit on FINANCE-ASSET-f03ba1a6a369cf03 recorded that a session read several tables and exported the query result. The event references principal-f892103a2793bbab. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Share audit on FINANCE-ASSET-689b8f41db9ab4f4 recorded that a new network file share was published. The event references principal-604eb4041d82448c. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"File access audit on PEOPLE-ASSET-4246817b50ce1d24 recorded that a process opened a local credential-store file. The event references principal-69567a3aa8e45657. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Waf logs on COMMUNICATIONS-ASSET-5ce6d959f09ef085 recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-ded293726939201b. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Repository audit on FINANCE-ASSET-107bba51318f26e9 recorded that a user cloned several source repositories. The event references principal-f147d2a9dbf7d7a7. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Mail audit on LEGAL-ASSET-2836d47d3aa0d5af recorded that an account received delegated access to a mailbox. The event references principal-e1699b7a3eeb56fc. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Vpn audit on SALES-ASSET-09dd168451b4fb60 recorded that a remote-access VPN session was established. The event references principal-732980774243feef. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Function audit on PROCUREMENT-ASSET-9b0e13d58a2188a8 recorded that a serverless function package and execution settings were updated. The event references principal-12b8d8e2191620d9. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Process audit on SUPPORT-ASSET-0577991db5a15090 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-d0dbfe56694e1edd. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-48f20570fc3e, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Kerberos audit on PROCUREMENT-ASSET-f07f0980cf620efa recorded that an account requested service tickets for multiple services. The event references principal-6dd83c14e2a9dd31. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-31a805cc0a9d accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"File audit on PEOPLE-ASSET-572ab49b4fda25fd recorded that access permissions were broadened on a directory tree. The event references principal-892e9ce9179f90fe. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Dns server audit on COMMUNICATIONS-ASSET-3ba853c8b87dee93 recorded that a client requested a DNS zone transfer. The event references principal-fbb1839d1793e373. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-38a0e0ae5fd6 explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Cloud control audit on COMMUNICATIONS-ASSET-6f90d32e2d49796b recorded that resources were created in a region with little prior activity. The event references principal-f5034ed11bd41e3e. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Mail and proxy logs on COMMUNICATIONS-ASSET-48a9f26bd10054b4 recorded that a user opened a URL delivered in an email message. The event references principal-0e84a6c758769248. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-69a5a2b22fab explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Api gateway logs on COMMUNICATIONS-ASSET-25487240e8c2e247 recorded that a client issued a burst of API requests. The event references principal-23ca7dbb4aa37ade. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Process access audit on FINANCE-ASSET-247c48e4c49c174e recorded that a process requested read access to another process memory space. The event references principal-601055cfd3a85372. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Mail audit on ENGINEERING-ASSET-784f3c782f3ac855 recorded that an account received delegated access to a mailbox. The event references principal-2080f4d9197e7c3e. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Cron audit on FINANCE-ASSET-3836d6a68d057960 recorded that a recurring job definition was added to the system schedule. The event references principal-c8b819a1d7d4650c. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-9eb2f25c5e6c accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Storage access logs on COMMUNICATIONS-ASSET-560f077b5b32381f recorded that a principal downloaded many objects from a storage bucket. The event references principal-2c20310dc28bca65. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Cloud identity audit on OPERATIONS-ASSET-3155b7b471a38d4e recorded that a principal received a policy granting additional permissions. The event references principal-e51b01012b559bdf. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Dns server audit on OPERATIONS-ASSET-77c8f7df02d0b548 recorded that a client requested a DNS zone transfer. The event references principal-de675342a884898f. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Certificate audit on FINANCE-ASSET-e16767dd715979b6 recorded that a service certificate was replaced. The event references principal-f8a1311de5964c87. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Registry audit on PROCUREMENT-ASSET-623aa42bae025131 recorded that a registry logon-start entry was created. The event references principal-9f2c57eab5b3cfda. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Registry audit on ENGINEERING-ASSET-3288f3a3a57d4d49 recorded that a registry logon-start entry was created. The event references principal-ab71b58d6c6b1b8b. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Wmi audit on SALES-ASSET-54ac6fc961ae7d6a recorded that a management request started a process through WMI. The event references principal-08c8fa6d75a3b195. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"File audit on OPERATIONS-ASSET-53ad24c9deb5d645 recorded that a shell startup profile gained an additional command. The event references principal-6049aaff0c8fe538. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Cloud control audit on LEGAL-ASSET-57d9881033f6b349 recorded that resources were created in a region with little prior activity. The event references principal-3d1e3e3a52fd0eed. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Mail audit on SALES-ASSET-bd6fcb0d83d6d9d8 recorded that an account received delegated access to a mailbox. The event references principal-44c7b65ec7f1b04b. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Kerberos audit on SUPPORT-ASSET-cee89b8c79f8f807 recorded that an account requested service tickets for multiple services. The event references principal-ba01468b28096ded. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Change CHG-fad7d4246cc1 lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Process audit on PEOPLE-ASSET-b5f000212e4e1683 recorded that a Python interpreter loaded a script and contacted a service. The event references principal-364f40722069431e. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Process audit on ENGINEERING-ASSET-db715ea0863774ba recorded that a remote-support application started an interactive session. The event references principal-ca4d1a946cc4272b. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-5258746bdc6b, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Repository audit on COMMUNICATIONS-ASSET-74eb656a821bda53 recorded that a repository collaborator received elevated permissions. The event references principal-aeb807368ce77066. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Cloud identity audit on RESEARCH-ASSET-8d54a31e0957dabb recorded that a principal assumed a role in another account. The event references principal-8a3eb5c757201646. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-827b7e69b5ce match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Certificate audit on OPERATIONS-ASSET-3ca9753ca5075c61 recorded that a service certificate was replaced. The event references principal-15f1c60782059a24. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-8b1493d8ccb3 before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Policy audit on COMMUNICATIONS-ASSET-6bd03c52fee36269 recorded that an audit policy was changed to collect fewer event categories. The event references principal-89ce4ef5b0451d62. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Storage audit on LEGAL-ASSET-5cc263cd7974e410 recorded that a session deleted several storage snapshots. The event references principal-548b73b08858de12. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Registry audit on RESEARCH-ASSET-e5e233361fd38697 recorded that a registry logon-start entry was created. The event references principal-83333208692c8fd1. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Database audit on COMMUNICATIONS-ASSET-b51d02175f1c9085 recorded that a session read several tables and exported the query result. The event references principal-61c8ab03c285a7c1. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Configuration audit on PROCUREMENT-ASSET-8aac493103d32947 recorded that a client proxy setting was changed. The event references principal-5ba8d1fc71029290. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Kubernetes audit on PEOPLE-ASSET-95c9822ffcf4a444 recorded that a cluster admission policy was changed. The event references principal-e51b094fe6b69872. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Application audit on RESEARCH-ASSET-44de8cf55f1c805f recorded that an application requested repeated screen captures. The event references principal-17ee862a652063ef. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-044385f0b4a6 explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Switch telemetry on PEOPLE-ASSET-2fae865ac519b354 recorded that an address mapping changed repeatedly on a local segment. The event references principal-cadf13732271e411. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Function audit on PEOPLE-ASSET-7a184783e26cf4b6 recorded that a serverless function package and execution settings were updated. The event references principal-20e08b043fa3eb3a. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Key service audit on ENGINEERING-ASSET-a77dccd54b04aa48 recorded that a principal issued a burst of key-service decrypt requests. The event references principal-627115d6ce1d6169. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Module audit on SUPPORT-ASSET-75579d877216839e recorded that a process loaded a library from an application-local directory. The event references principal-bf9534edb641c536. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-3cab5fb4058d explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Script audit on LEGAL-ASSET-38bacff4f7d252bf recorded that a script interpreter decoded an encoded argument before execution. The event references principal-0e6d8e54a19c536c. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-a2f0efc521d5 explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Function audit on COMMUNICATIONS-ASSET-6eba6dd15491bb00 recorded that a serverless function package and execution settings were updated. The event references principal-a52d85256a55e315. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Registry audit on COMMUNICATIONS-ASSET-bfd346cad4d024a4 recorded that a registry logon-start entry was created. The event references principal-74f1b84012bd604a. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Ci audit on FINANCE-ASSET-5cdbdad4be0dcfbd recorded that a build pipeline definition gained a new execution step. The event references principal-248c78edaf5546c1. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Script audit on PEOPLE-ASSET-7674cfc3c8c8d12a recorded that a script interpreter decoded an encoded argument before execution. The event references principal-15233cc20a5664b0. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Flow logs on SALES-ASSET-e03d7f92d970afc6 recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-7f74331f29d46d56. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Cloud control audit on LEGAL-ASSET-57d9881033f6b349 recorded that resources were created in a region with little prior activity. The event references principal-3d1e3e3a52fd0eed. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Browser audit on COMMUNICATIONS-ASSET-242d23ba4ad50b88 recorded that a browser extension with page-reading permissions was installed. The event references principal-c4eaf539de0f6aa8. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Certificate audit on ENGINEERING-ASSET-9451d5f5fd9b7794 recorded that a service certificate was replaced. The event references principal-a6fab514c28c1ba9. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-1c0a5e1f7844 match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Gateway logs on ENGINEERING-ASSET-8864632089fd4c50 recorded that a client established a long-lived encapsulated network session. The event references principal-90ee640b3b5c5162. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Browser audit on PEOPLE-ASSET-48ee486909d7e37c recorded that a browser extension with page-reading permissions was installed. The event references principal-0d329542446b1b23. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-1a5b6dff7c03 explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Process audit on LEGAL-ASSET-523d2840aded9f3a recorded that a remote-support application started an interactive session. The event references principal-d733a0ecd691110d. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Registry audit on COMMUNICATIONS-ASSET-c99d7ada90aece83 recorded that a workload pulled a container image from a registry. The event references principal-c5705a8b2e1e260b. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-c68351cddfd1 accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Identity audit on ENGINEERING-ASSET-17f1d906d8c35962 recorded that a service account established an interactive session. The event references principal-4e2ae7344e474fce. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"File audit on RESEARCH-ASSET-e40ef73f48b09e4f recorded that a shell startup profile gained an additional command. The event references principal-2434130e3913b6f0. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Process access audit on PROCUREMENT-ASSET-a371e419fb9da077 recorded that a process requested read access to another process memory space. The event references principal-47b9eca6b126bee7. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-411a11d421e2 explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Share audit on RESEARCH-ASSET-f2c54bce84c236d2 recorded that a new network file share was published. The event references principal-0e202f3a7615eefc. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-f1bdfef82b8d accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Windows logon audit on SALES-ASSET-6ef3ee3501c6fc3e recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-9c0f223e81092f12. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Kubernetes audit on SUPPORT-ASSET-ea9a39224859df23 recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-c986eaa5cd9383cb. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"File audit on PROCUREMENT-ASSET-de47614145685908 recorded that a shell startup profile gained an additional command. The event references principal-602bb5bc7aad1155. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Group audit on ENGINEERING-ASSET-d30b74960b951b72 recorded that an account was added to a privileged local group. The event references principal-81526d7aed4e1797. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Change CHG-d2487e1bf585 lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Repository audit on COMMUNICATIONS-ASSET-fc7d932dec68a3a4 recorded that a user cloned several source repositories. The event references principal-f9163c8da3ccc09a. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-e6e789e059aa explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Cloud control audit on ENGINEERING-ASSET-bbf96ebe3618813b recorded that a cloud logging destination was disabled. The event references principal-7942b0cb0edc33ed. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Ci secret audit on ENGINEERING-ASSET-2fc72026491758e8 recorded that a build job requested a protected pipeline secret. The event references principal-ef329c66a1330a2f. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-2760c17646f8 match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Application audit on COMMUNICATIONS-ASSET-c8d077447f8b8c1d recorded that an application requested repeated screen captures. The event references principal-062e1b2072504f50. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Database audit on PEOPLE-ASSET-5fce356081bdb526 recorded that a session read several tables and exported the query result. The event references principal-b90846a958bd885f. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Database audit on COMMUNICATIONS-ASSET-b51d02175f1c9085 recorded that a session read several tables and exported the query result. The event references principal-61c8ab03c285a7c1. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-68d6c9f266e6, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Ci secret audit on COMMUNICATIONS-ASSET-d9b1648a2cfcda09 recorded that a build job requested a protected pipeline secret. The event references principal-8fc1bbd9d306c19b. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Resolver logs on SUPPORT-ASSET-b02540e08d1a5e1b recorded that a client requested many long, high-entropy DNS labels. The event references principal-ac999136f4795cef. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Resolver logs on SALES-ASSET-17cdfcbdaddd4989 recorded that a client requested many long, high-entropy DNS labels. The event references principal-fddd379e6737bcc0. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Application audit on RESEARCH-ASSET-44de8cf55f1c805f recorded that an application requested repeated screen captures. The event references principal-17ee862a652063ef. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Cloud control audit on SALES-ASSET-5ed8420ac6bfabb9 recorded that a session deleted a group of cloud resources. The event references principal-e108fb64fd38558b. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Application audit on COMMUNICATIONS-ASSET-349e251c3544c259 recorded that a runtime configuration setting was updated. The event references principal-f484d494a6adf949. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Registry audit on PEOPLE-ASSET-2d7ca72857a14112 recorded that a workload pulled a container image from a registry. The event references principal-f31f9ebfd4a3d389. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Security retest SEC-585cea92789a covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Egress flow logs on LEGAL-ASSET-1a606b14eab96fee recorded that a workload opened an encrypted connection to an external service. The event references principal-d6bec1039eca165c. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Saas audit on COMMUNICATIONS-ASSET-1937d1daec1efbd9 recorded that a user requested a bulk export from a business application. The event references principal-7aa0534f456ac613. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"File access audit on ENGINEERING-ASSET-9bb4a75d3491a9be recorded that a process opened a local credential-store file. The event references principal-f9c37bdee298aeea. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Change CHG-ad734b015bad lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Egress flow logs on COMMUNICATIONS-ASSET-1fa62ed57f8d2679 recorded that a workload opened an encrypted connection to an external service. The event references principal-297491ec275675d7. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Application audit on FINANCE-ASSET-92ef4a42892b1789 recorded that an application read clipboard contents repeatedly. The event references principal-13f5550b59519bb2. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Mail flow logs on OPERATIONS-ASSET-b187da0291cabbc9 recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-3df241ac15d172ff. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"File audit on SALES-ASSET-a4a69365dce2152a recorded that a shell startup profile gained an additional command. The event references principal-3637027719cb9240. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Saas audit on COMMUNICATIONS-ASSET-1937d1daec1efbd9 recorded that a user requested a bulk export from a business application. The event references principal-7aa0534f456ac613. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Process access audit on SALES-ASSET-0e0ff0d46dd9bdcc recorded that a process requested read access to another process memory space. The event references principal-a29d7cafdbef1526. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Code integrity audit on PEOPLE-ASSET-4048dcb975a46f2e recorded that an executable without a publisher signature started from a writable directory. The event references principal-d449d23aa96125e6. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Storage access logs on PEOPLE-ASSET-c7aae9977fa123ac recorded that a principal downloaded many objects from a storage bucket. The event references principal-8d5cca2185bede9c. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Kubernetes audit on COMMUNICATIONS-ASSET-f76c1c782f04bc0e recorded that a workload mounted a directory from its host filesystem. The event references principal-ea22af4c35053180. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Proxy logs on PROCUREMENT-ASSET-a90cefc8840eb875 recorded that a client transferred a large payload to an external storage endpoint. The event references principal-58357f3106f790fd. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Session audit on SUPPORT-ASSET-39c9a292833723e5 recorded that the same session token appeared from different client addresses. The event references principal-a5ec7d156048f10f. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Ci audit on ENGINEERING-ASSET-2c0d231544308107 recorded that a build pipeline definition gained a new execution step. The event references principal-aba5ed9cc375c5ec. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Key service audit on COMMUNICATIONS-ASSET-5437588d51522a99 recorded that a principal issued a burst of key-service decrypt requests. The event references principal-f88907eb1e848f20. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Kubernetes audit on OPERATIONS-ASSET-f1f73c739188a298 recorded that a workload mounted a directory from its host filesystem. The event references principal-5a00d24e558e0ba4. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Database audit on PEOPLE-ASSET-5fce356081bdb526 recorded that a session read several tables and exported the query result. The event references principal-b90846a958bd885f. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Configuration audit on FINANCE-ASSET-74d3e5b9407ece66 recorded that a client proxy setting was changed. The event references principal-00bf9f3d44fd549a. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-2b5f924f6293 before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Runtime audit on SALES-ASSET-65e80c7b6f9129ee recorded that a process connected to the container runtime socket. The event references principal-e74aec44693d5ee6. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Winrm audit on PROCUREMENT-ASSET-98512f6cba9a2651 recorded that a remote management session invoked a command on a managed host. The event references principal-e3d261d10a11f3f9. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Script audit on RESEARCH-ASSET-a67da4eb1517ea03 recorded that a script interpreter decoded an encoded argument before execution. The event references principal-e606a4602bed6561. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Kerberos audit on FINANCE-ASSET-0b0adcb58a633d21 recorded that an account requested service tickets for multiple services. The event references principal-bbbe909c0396acf3. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"File audit on SUPPORT-ASSET-5e6185480b7124c6 recorded that a shell startup profile gained an additional command. The event references principal-51f94e540bbb4321. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-911a704b6979 explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Pki audit on OPERATIONS-ASSET-075517e7328277d9 recorded that a principal requested a certificate using an authentication template. The event references principal-c9b353c364fde4c3. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Storage audit on PROCUREMENT-ASSET-283ac93c3c2be26b recorded that a session deleted several storage snapshots. The event references principal-84f457c32ccdb7a6. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Cloud control audit on COMMUNICATIONS-ASSET-6f90d32e2d49796b recorded that resources were created in a region with little prior activity. The event references principal-f5034ed11bd41e3e. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Dns control audit on OPERATIONS-ASSET-d3932800e26302a2 recorded that an authoritative DNS record was updated. The event references principal-acc181df5bf7ded9. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Switch telemetry on OPERATIONS-ASSET-30a277f008dd59f9 recorded that an address mapping changed repeatedly on a local segment. The event references principal-f95a18784ccda07e. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Repository audit on ENGINEERING-ASSET-501895f2c603da6f recorded that a user cloned several source repositories. The event references principal-08a3df240a2c2acb. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Backup audit on ENGINEERING-ASSET-e13f2ff83c899d5b recorded that a backup retention policy was shortened. The event references principal-31afc311e47df634. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Driver audit on COMMUNICATIONS-ASSET-b8154a780e8f0180 recorded that a kernel driver was loaded after a package installation. The event references principal-5b575ab65094c162. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-ede433da697b before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Application audit on LEGAL-ASSET-2b053903e1a723bb recorded that an application read clipboard contents repeatedly. The event references principal-36dbf50d505a5d2a. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Ssh audit on COMMUNICATIONS-ASSET-c7c949ba2f23f6e5 recorded that an SSH session opened and requested elevated command execution. The event references principal-3a7b389506fbf3c1. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Saas audit on SUPPORT-ASSET-2e07b9359e958267 recorded that a user requested a bulk export from a business application. The event references principal-b7211075b62be127. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Application audit on RESEARCH-ASSET-21c212dc3255aa17 recorded that an application read clipboard contents repeatedly. The event references principal-8f2a965b2d84c102. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Session audit on OPERATIONS-ASSET-650805187004af92 recorded that the same session token appeared from different client addresses. The event references principal-fe1f7195dd801273. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-d440b2eba275 covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Firewall audit on FINANCE-ASSET-d80ee8804a4ec6b6 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-b21644c32449b9a0. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Agent audit on LEGAL-ASSET-6d17adf81f6fe3af recorded that a privileged session changed endpoint monitoring settings. The event references principal-f72780533376e28a. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Repository audit on RESEARCH-ASSET-f2f0b485da92764a recorded that a repository collaborator received elevated permissions. The event references principal-883f23b0e04d7f14. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Cloud identity audit on LEGAL-ASSET-a018d5a0c035a322 recorded that a principal received a policy granting additional permissions. The event references principal-e37ce5811af67681. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Mail audit on LEGAL-ASSET-131d8c518786695c recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-3bea6da72e330e1b. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Database audit on FINANCE-ASSET-7b5f1daa45ffd071 recorded that a session changed a database table definition. The event references principal-eec005bb1596cf1c. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Runtime audit on FINANCE-ASSET-f76f44e364cb49d4 recorded that a process connected to the container runtime socket. The event references principal-61088a6af6fdfeb5. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-578ddadc252b match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Identity audit on PEOPLE-ASSET-f09717db52bad024 recorded that an account password was reset through a recovery workflow. The event references principal-52a4edbb0422bb75. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Application audit on COMMUNICATIONS-ASSET-349e251c3544c259 recorded that a runtime configuration setting was updated. The event references principal-f484d494a6adf949. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Api gateway logs on RESEARCH-ASSET-43a3327a7670f557 recorded that a client issued a burst of API requests. The event references principal-19db88a740f22c57. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Share audit on OPERATIONS-ASSET-a9f5766b40361ce4 recorded that a new network file share was published. The event references principal-e591af365aeb634a. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"File audit on SALES-ASSET-f0f53d618a5c2238 recorded that a process compressed files from several directories into an archive. The event references principal-a24a28fb5a9017a6. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"File access audit on PROCUREMENT-ASSET-0b755d0602adf157 recorded that a process opened a local credential-store file. The event references principal-7e6f29a9069cca6a. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Browser audit on PROCUREMENT-ASSET-50d8010904173019 recorded that a browser extension with page-reading permissions was installed. The event references principal-8e2e0553f52a5216. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-871f21de7799, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Repository audit on RESEARCH-ASSET-f2f0b485da92764a recorded that a repository collaborator received elevated permissions. The event references principal-883f23b0e04d7f14. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Identity audit on SALES-ASSET-08c0f29601b74bfa recorded that an account registered a new MFA method. The event references principal-4c8bc42872a0ca65. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Cloud identity audit on ENGINEERING-ASSET-00c2f8de5ff4a52c recorded that a principal assumed a role in another account. The event references principal-4cb5db7ee766c0fa. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Process audit on FINANCE-ASSET-9d45d520b4a54280 recorded that a Python interpreter loaded a script and contacted a service. The event references principal-d052a3f1c4010987. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Ci audit on PROCUREMENT-ASSET-51d14292a906982f recorded that a build pipeline definition gained a new execution step. The event references principal-776e5e2e9ad695a2. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-b39295195d3d match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Service audit on COMMUNICATIONS-ASSET-9cb10b4818b88629 recorded that a remote service-control request created and started a temporary service. The event references principal-9f1825f9f69c7e5f. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Cron audit on RESEARCH-ASSET-25e2f241c7b3849f recorded that a recurring job definition was added to the system schedule. The event references principal-2a055f75f46408a1. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Agent audit on FINANCE-ASSET-9e83a9427493fb22 recorded that a privileged session changed endpoint monitoring settings. The event references principal-456dd0970fc81a4c. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Group audit on FINANCE-ASSET-df066dc7583c9589 recorded that an account was added to a privileged local group. The event references principal-91bee423e82eb7d5. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Winrm audit on PROCUREMENT-ASSET-98512f6cba9a2651 recorded that a remote management session invoked a command on a managed host. The event references principal-e3d261d10a11f3f9. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-7f4e3d83c00a before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Agent audit on RESEARCH-ASSET-01cc4805ed6fe45d recorded that a privileged session changed endpoint monitoring settings. The event references principal-fb3e99ff7e75f725. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Federation audit on FINANCE-ASSET-834ce73eb8e2d5f1 recorded that a tenant federation setting was updated. The event references principal-b4c9940f6c199e33. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Task scheduler audit on OPERATIONS-ASSET-0c0ccf4949e6876b recorded that a scheduled task was registered to execute a program at logon. The event references principal-6b1b6724d1e28e1c. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Resolver logs on FINANCE-ASSET-702feb45e71dd31e recorded that a client requested many long, high-entropy DNS labels. The event references principal-219bc21f1d685857. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Runtime audit on PROCUREMENT-ASSET-ef2802409ab5a514 recorded that a process connected to the container runtime socket. The event references principal-81a676edf02534d4. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-d301e9350f4f specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Cloud identity audit on PROCUREMENT-ASSET-cb3bd3ac326cf3b2 recorded that a principal assumed a role in another account. The event references principal-131a52eaecf4978f. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Systemd audit on OPERATIONS-ASSET-42dd1f251b2cefd5 recorded that a service unit file was changed and the unit reloaded. The event references principal-27edc61f63f1f31a. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-67ffd373fe25 match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Ci audit on PEOPLE-ASSET-ea14ad85e984ee1f recorded that a build pipeline definition gained a new execution step. The event references principal-02ee8abd42195e24. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Process access audit on SALES-ASSET-0e0ff0d46dd9bdcc recorded that a process requested read access to another process memory space. The event references principal-a29d7cafdbef1526. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Mfa audit on LEGAL-ASSET-e69fa0a56ff82707 recorded that multiple MFA challenges were issued during a short interval. The event references principal-f4248a85a02aa075. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Winrm audit on SUPPORT-ASSET-635c3348db734709 recorded that a remote management session invoked a command on a managed host. The event references principal-f79466b09a2bb0fa. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"File audit on RESEARCH-ASSET-08266be3d48a0589 recorded that a process compressed files from several directories into an archive. The event references principal-ba2e548a2cd0e827. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Kubernetes audit on FINANCE-ASSET-e06cf007729f9dbe recorded that a workload mounted a directory from its host filesystem. The event references principal-76bf38f3f96381c7. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Mfa audit on ENGINEERING-ASSET-4741e70baa0f7c7a recorded that multiple MFA challenges were issued during a short interval. The event references principal-7a266bf7aed055c1. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Application audit on SALES-ASSET-5a207e0d30dc6722 recorded that an application requested repeated screen captures. The event references principal-e579eecfc7c0f733. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Configuration audit on PEOPLE-ASSET-5afa9d0b44139e46 recorded that a client proxy setting was changed. The event references principal-c6f3609cd125d978. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Registry audit on OPERATIONS-ASSET-2d36b1b63d0c4ad6 recorded that a workload pulled a container image from a registry. The event references principal-1fdf41d42655dccc. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Function audit on FINANCE-ASSET-715a47edf7141497 recorded that a serverless function package and execution settings were updated. The event references principal-e1d12cf425ed5c27. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Pki audit on RESEARCH-ASSET-5892d31dbb5ae49e recorded that a principal requested a certificate using an authentication template. The event references principal-5044ec496f46d2cd. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-887ddbb4679a specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Backup audit on PEOPLE-ASSET-90b00913ef4755f4 recorded that a backup retention policy was shortened. The event references principal-069c9474003b2644. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Waf logs on OPERATIONS-ASSET-b7ed82085f777d6d recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-82b5142e40756445. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Code integrity audit on LEGAL-ASSET-f6d743064b804557 recorded that an executable without a publisher signature started from a writable directory. The event references principal-4ea2e2cfcda079aa. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"File audit on RESEARCH-ASSET-e40ef73f48b09e4f recorded that a shell startup profile gained an additional command. The event references principal-2434130e3913b6f0. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"File audit on FINANCE-ASSET-a2913f2126217458 recorded that access permissions were broadened on a directory tree. The event references principal-05896b0efe4a938e. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-60ce4a668486 accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Kerberos audit on SUPPORT-ASSET-cee89b8c79f8f807 recorded that an account requested service tickets for multiple services. The event references principal-ba01468b28096ded. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Task scheduler audit on LEGAL-ASSET-9a82bb1a05cff6a6 recorded that a scheduled task was registered to execute a program at logon. The event references principal-5c02a139758a7988. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Service audit on LEGAL-ASSET-c576aa1679d54c28 recorded that a new automatically started service was registered. The event references principal-7b1165f4385ce850. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Change CHG-9acb38da322f lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Browser audit on RESEARCH-ASSET-b0be4ff24f6a9c7d recorded that a browser extension with page-reading permissions was installed. The event references principal-c445644ab42572e7. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Kubernetes audit on RESEARCH-ASSET-d1f7ab9c3de5615d recorded that a cluster admission policy was changed. The event references principal-bc8aec70f878822d. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Configuration audit on RESEARCH-ASSET-c3d25c02edb1b375 recorded that a client proxy setting was changed. The event references principal-c2c0e84c38c559bb. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Change CHG-531564c11015 lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Process audit on SUPPORT-ASSET-0577991db5a15090 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-d0dbfe56694e1edd. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Policy audit on RESEARCH-ASSET-9236351eaaf332af recorded that an audit policy was changed to collect fewer event categories. The event references principal-9505995ed7eba439. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"File audit on PEOPLE-ASSET-cc74b22d2c2ca8f7 recorded that a process compressed files from several directories into an archive. The event references principal-e9c54c5535050840. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Assessment SEC-f58b61eba89c explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Cloud control audit on SUPPORT-ASSET-50842d406b871613 recorded that a session deleted a group of cloud resources. The event references principal-5fa6a0bc38223f91. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Systemd audit on SALES-ASSET-4e41129f633ac17f recorded that a service unit file was changed and the unit reloaded. The event references principal-6e1812150b898dbc. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Flow logs on SUPPORT-ASSET-30ebec702fd5fb40 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-cc4ef6967d7bd3d5. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-73834c1f3e05, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Vpn audit on FINANCE-ASSET-5b805daa08de83aa recorded that a remote-access VPN session was established. The event references principal-cc88ce7b51f0aa37. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Storage audit on SALES-ASSET-54a03152e889d43f recorded that a session deleted several storage snapshots. The event references principal-69a5261a8cfb5a4d. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Cloud control audit on OPERATIONS-ASSET-e8aae5321595ab4e recorded that a cloud logging destination was disabled. The event references principal-a8271fb4edbdf45f. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-42f062fe6734 specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Account audit on PEOPLE-ASSET-aaae6542cf112eee recorded that a local user account was created on a managed system. The event references principal-0953004be50ca69d. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Cron audit on RESEARCH-ASSET-25e2f241c7b3849f recorded that a recurring job definition was added to the system schedule. The event references principal-2a055f75f46408a1. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Database audit on ENGINEERING-ASSET-2c4914b84c80f08c recorded that a session read several tables and exported the query result. The event references principal-b17a9277af7e3124. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-c6483d7d243a specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Directory audit on ENGINEERING-ASSET-74de670cde6f3c91 recorded that a principal requested directory replication data. The event references principal-2491cc3af8b17009. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-2754633027c1 match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Winrm audit on PEOPLE-ASSET-f67c81ba2aebe0a8 recorded that a remote management session invoked a command on a managed host. The event references principal-380dff97d88676ce. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Cloud identity audit on FINANCE-ASSET-e7ffd7ca6e67a506 recorded that a principal assumed a role in another account. The event references principal-9b4f65d2a19e9629. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Account audit on SALES-ASSET-b02113ff8562d223 recorded that a local user account was created on a managed system. The event references principal-3cbed1cc8fc2d897. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"File audit on RESEARCH-ASSET-08266be3d48a0589 recorded that a process compressed files from several directories into an archive. The event references principal-ba2e548a2cd0e827. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Switch telemetry on FINANCE-ASSET-c82eb7bf49c6713c recorded that an address mapping changed repeatedly on a local segment. The event references principal-24aa90be68c12c8b. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Database audit on SUPPORT-ASSET-9310282a796b35af recorded that a session changed a database table definition. The event references principal-c009c7c60f3c400f. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-74bbd29bc698, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Flow logs on ENGINEERING-ASSET-eb2e69d274ba28c2 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-95a534f7e0b0cad5. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Code integrity audit on OPERATIONS-ASSET-06f732c807773233 recorded that an executable without a publisher signature started from a writable directory. The event references principal-28681a2e3d3ce90b. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-c09fbd95d676, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Mail audit on PEOPLE-ASSET-0dab505ef5721fa1 recorded that an account received delegated access to a mailbox. The event references principal-867e051f8d4b0f18. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Federation audit on SALES-ASSET-88538f554d17e7e6 recorded that a tenant federation setting was updated. The event references principal-caaf0b98849ffd32. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Package registry audit on SALES-ASSET-70769ae6745858de recorded that a principal published a new package version. The event references principal-06efaa74600c0f91. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Systemd audit on PROCUREMENT-ASSET-e562e2af350db7c6 recorded that a service unit file was changed and the unit reloaded. The event references principal-a239fb376cfcf526. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Identity audit on LEGAL-ASSET-f678141e2b084a32 recorded that an account registered a new MFA method. The event references principal-500c71ca31b016a9. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Event service audit on PEOPLE-ASSET-3e7af42f465f079f recorded that an event log was cleared by a privileged request. The event references principal-7e44d019c9f83317. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Saas audit on LEGAL-ASSET-febb39399ce8713a recorded that a user requested a bulk export from a business application. The event references principal-56038be98666605f. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Directory audit on COMMUNICATIONS-ASSET-014161d1ab75992f recorded that a principal requested directory replication data. The event references principal-06ff5e4392c8395e. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Group audit on RESEARCH-ASSET-0d0aaf2292482822 recorded that an account was added to a privileged local group. The event references principal-5badc7c76a42d4b2. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Process access audit on ENGINEERING-ASSET-6c512bf3bb9f3c6e recorded that a process requested read access to another process memory space. The event references principal-0c750e6c9b19f34e. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Process audit on COMMUNICATIONS-ASSET-332afb2165aa1448 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-afe5b84c8ef31787. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-aadb3c045a0e match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Systemd audit on PROCUREMENT-ASSET-e562e2af350db7c6 recorded that a service unit file was changed and the unit reloaded. The event references principal-a239fb376cfcf526. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Pki audit on LEGAL-ASSET-06762de597c73d74 recorded that a principal requested a certificate using an authentication template. The event references principal-39b0053611d607fa. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-67f4732dea8e specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Directory audit on LEGAL-ASSET-e41057b50163ec62 recorded that a principal requested directory replication data. The event references principal-27103a43ea428bc2. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Storage audit on PEOPLE-ASSET-1ba8659c3031d7f0 recorded that a session deleted several storage snapshots. The event references principal-cf538081eb476d29. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Code integrity audit on SALES-ASSET-c410ab31c1f04772 recorded that an executable without a publisher signature started from a writable directory. The event references principal-9e4abca76b69be64. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-25cc4ae49bb3 match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Saas audit on RESEARCH-ASSET-b155eac613e67224 recorded that a user requested a bulk export from a business application. The event references principal-5a3ba2a9838be78e. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Service audit on OPERATIONS-ASSET-53e47c7270341ae1 recorded that a remote service-control request created and started a temporary service. The event references principal-ae8a8a74a000dff1. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Wmi audit on PROCUREMENT-ASSET-fda18a4350cff1b3 recorded that a management request started a process through WMI. The event references principal-cba091012017387e. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Identity audit on OPERATIONS-ASSET-775dd42bd2b2e216 recorded that repeated failed sign-ins were recorded for an account. The event references principal-2f8b852f1ede3573. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Wmi audit on ENGINEERING-ASSET-9642a3ef1a26edcb recorded that a management request started a process through WMI. The event references principal-4a2b4bdee8c5d199. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-7450cb200a44 specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Storage access logs on COMMUNICATIONS-ASSET-560f077b5b32381f recorded that a principal downloaded many objects from a storage bucket. The event references principal-2c20310dc28bca65. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Mail and proxy logs on SALES-ASSET-86e0136e86dcbb64 recorded that a user opened a URL delivered in an email message. The event references principal-090cc1db12274cd7. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Ci secret audit on SALES-ASSET-ad09caa9a6596785 recorded that a build job requested a protected pipeline secret. The event references principal-5cac9dd38eee5122. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Application audit on SALES-ASSET-5a207e0d30dc6722 recorded that an application requested repeated screen captures. The event references principal-e579eecfc7c0f733. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-e2dae95873d2 specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Smb audit on SUPPORT-ASSET-e1998cccd3abd998 recorded that a session enumerated a file share and read multiple files. The event references principal-3be2aaf5e58c794d. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Agent audit on ENGINEERING-ASSET-d4aa23315bb70413 recorded that a privileged session changed endpoint monitoring settings. The event references principal-2e08cdbbea0a15c2. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Process access audit on OPERATIONS-ASSET-a4047122fa1f8006 recorded that a process requested read access to another process memory space. The event references principal-b6f3ffe23361d9c9. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-0499e62c1d77 match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Switch telemetry on RESEARCH-ASSET-39ecead5bf809d8c recorded that an address mapping changed repeatedly on a local segment. The event references principal-78520d727e00f06a. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Security retest SEC-094ccd9f6535 covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Identity audit on SALES-ASSET-2f253fe8393025e1 recorded that an account password was reset through a recovery workflow. The event references principal-95366adc4199c0a7. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Change CHG-f084a1d74147 lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Directory audit on PEOPLE-ASSET-37791232d78efc05 recorded that a principal requested directory replication data. The event references principal-55f0d12673ae40b1. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"File audit on COMMUNICATIONS-ASSET-7174b9fee0b011b4 recorded that a process rewrote multiple files into encrypted containers. The event references principal-8e2fefcd77348cfa. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Change CHG-4ed2c68523fd lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Ssh audit on RESEARCH-ASSET-a4cfbeae0c987bb8 recorded that an SSH session opened and requested elevated command execution. The event references principal-f224386eb3a1c8ae. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-fb85cb19ed59 match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Browser audit on COMMUNICATIONS-ASSET-242d23ba4ad50b88 recorded that a browser extension with page-reading permissions was installed. The event references principal-c4eaf539de0f6aa8. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Service audit on FINANCE-ASSET-d962ba7a33513380 recorded that a new automatically started service was registered. The event references principal-238acc934bc77540. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Account audit on PEOPLE-ASSET-aaae6542cf112eee recorded that a local user account was created on a managed system. The event references principal-0953004be50ca69d. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Application audit on PROCUREMENT-ASSET-9ae629f20e56becc recorded that a runtime configuration setting was updated. The event references principal-be5a20df9fa68e8b. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Cloud identity audit on RESEARCH-ASSET-39f1c4acdb98407c recorded that a new programmatic access key was issued to a principal. The event references principal-16f1be9653031bee. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Ssh audit on FINANCE-ASSET-370d0df1776daaea recorded that an SSH session opened and requested elevated command execution. The event references principal-d8496f14d2489876. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Process access audit on OPERATIONS-ASSET-a4047122fa1f8006 recorded that a process requested read access to another process memory space. The event references principal-b6f3ffe23361d9c9. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Cloud control audit on COMMUNICATIONS-ASSET-c7835ea641b313a9 recorded that a session deleted a group of cloud resources. The event references principal-5e2ab493e683591c. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Secret manager audit on ENGINEERING-ASSET-c96b6e8c112e5ab0 recorded that a workload read several secret versions. The event references principal-24b9130cfaf6e9ca. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Registry audit on SUPPORT-ASSET-3b0593850dd40f7b recorded that a registry logon-start entry was created. The event references principal-d3ff9c757ce4b24b. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"File audit on SUPPORT-ASSET-528c23bdb207b71c recorded that access permissions were broadened on a directory tree. The event references principal-f1bdbe7329a336ab. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Identity audit on SUPPORT-ASSET-9a791522c1b9c744 recorded that an account password was reset through a recovery workflow. The event references principal-bd3f8b10beb2211f. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Change CHG-85f47412c6b8 lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Registry audit on SALES-ASSET-797a3ae487efd18f recorded that a workload pulled a container image from a registry. The event references principal-6df652f7e41389ab. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Assessment SEC-0e511c93bc22 explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Database audit on ENGINEERING-ASSET-5b5cb77077baa64c recorded that a session changed a database table definition. The event references principal-6bfe365bf3961695. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Mail audit on SALES-ASSET-1d2f1acd8ca606b9 recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-eaa00c222951727e. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Change CHG-86bb448fc8e9 lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Mail audit on COMMUNICATIONS-ASSET-cf30ec21588a2145 recorded that an account received delegated access to a mailbox. The event references principal-a11312ab2e69f315. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Browser audit on SUPPORT-ASSET-089bd1e438aae68a recorded that a browser extension with page-reading permissions was installed. The event references principal-05dd057e76f4173e. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-816145c4da62 explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Backup audit on RESEARCH-ASSET-d7ec84ee273e258c recorded that a backup retention policy was shortened. The event references principal-46e3d9bc6deb6418. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Compute audit on FINANCE-ASSET-428507c521e75c88 recorded that a principal launched multiple compute instances. The event references principal-a167ad7ce21b7604. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Mail flow logs on LEGAL-ASSET-692e1a748d08a501 recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-527175c687849d2d. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Smb audit on FINANCE-ASSET-c99a2728b7b98f2b recorded that a session enumerated a file share and read multiple files. The event references principal-40d6614472abce2d. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Systemd audit on LEGAL-ASSET-1602066d8a3d5246 recorded that a service unit file was changed and the unit reloaded. The event references principal-cdc1cfc697d46ed4. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Code integrity audit on PROCUREMENT-ASSET-3f90b9195fa39dc7 recorded that an executable without a publisher signature started from a writable directory. The event references principal-f1b547470e053c8b. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Driver audit on PROCUREMENT-ASSET-caa474ba78b6dce6 recorded that a kernel driver was loaded after a package installation. The event references principal-c43c37da7fba502b. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Storage audit on PROCUREMENT-ASSET-f524c33b819a1663 recorded that an object-storage access policy was broadened. The event references principal-daeee49ee65928ba. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-051e1473ade7, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Application audit on OPERATIONS-ASSET-09e59732382536e3 recorded that an application requested repeated screen captures. The event references principal-a45fb9f4a0a7c7be. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Cloud control audit on PEOPLE-ASSET-a565fc161c06dbdd recorded that a cloud logging destination was disabled. The event references principal-b1342e9d7cf466d7. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Resolver logs on ENGINEERING-ASSET-02301b26ed9cf1c5 recorded that a client requested many long, high-entropy DNS labels. The event references principal-8e3fc22d3aadc906. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-0a02fc0ca6f4 before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Systemd audit on PEOPLE-ASSET-e24082f3c52d3f39 recorded that a service unit file was changed and the unit reloaded. The event references principal-b49269ba3a97e459. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Service audit on FINANCE-ASSET-271527485b0e477e recorded that a remote service-control request created and started a temporary service. The event references principal-31971ac078081c89. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Device and file audit on OPERATIONS-ASSET-e188a7d05dfbf7ee recorded that files were copied to a removable storage device. The event references principal-4cd6803b897580b7. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Mail flow logs on RESEARCH-ASSET-a506e0d5600d9442 recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-27bdbe6c899d3b5b. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Pki audit on LEGAL-ASSET-06762de597c73d74 recorded that a principal requested a certificate using an authentication template. The event references principal-39b0053611d607fa. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-67f4732dea8e before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Kerberos audit on COMMUNICATIONS-ASSET-d9b65f7833a03be8 recorded that an account requested service tickets for multiple services. The event references principal-bce81f4ae551beca. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Dns control audit on SUPPORT-ASSET-daac2768071affbb recorded that an authoritative DNS record was updated. The event references principal-004b930761f504d4. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-50edf3932fc2 accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Api gateway logs on FINANCE-ASSET-7a64770a61e92e29 recorded that a client issued a burst of API requests. The event references principal-43cf908ee519b246. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Policy audit on FINANCE-ASSET-e464a7dfab1a5a08 recorded that an audit policy was changed to collect fewer event categories. The event references principal-88be6dc1340765a4. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Application audit on LEGAL-ASSET-2b053903e1a723bb recorded that an application read clipboard contents repeatedly. The event references principal-36dbf50d505a5d2a. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-5371e603b40c accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Flow logs on SUPPORT-ASSET-103a412104563dae recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-a1ca47883deef1d3. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-b39b57fe0a27 explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Ssh audit on PEOPLE-ASSET-97ff8f8fa97fd164 recorded that an SSH session opened and requested elevated command execution. The event references principal-60b1e96c2c9d3478. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Secret manager audit on PEOPLE-ASSET-406b99330a23361c recorded that a workload read several secret versions. The event references principal-c3699eaad53ba8ba. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-3d775aaef186 accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Saas audit on RESEARCH-ASSET-b155eac613e67224 recorded that a user requested a bulk export from a business application. The event references principal-5a3ba2a9838be78e. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Change CHG-4cd3c2a0fbf7 lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"File audit on PROCUREMENT-ASSET-f66c7d2cd9a00208 recorded that a process compressed files from several directories into an archive. The event references principal-1608ac7a92b15a7f. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Cloud identity audit on OPERATIONS-ASSET-04350815f02c233e recorded that a new programmatic access key was issued to a principal. The event references principal-3f0b6fed7f9bbd92. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Waf logs on SALES-ASSET-8a0f506e8e518bc0 recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-eb2ba7446fb1565a. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Mail flow logs on RESEARCH-ASSET-a506e0d5600d9442 recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-27bdbe6c899d3b5b. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Ci secret audit on OPERATIONS-ASSET-e1c6669f5f29a589 recorded that a build job requested a protected pipeline secret. The event references principal-e8010ec93fff4989. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Kerberos audit on PEOPLE-ASSET-4ee9a55c8fd9d93a recorded that an account requested service tickets for multiple services. The event references principal-0978a46d6664fc2a. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Repository audit on SALES-ASSET-60f45c01cacb2ad7 recorded that a repository collaborator received elevated permissions. The event references principal-59983edc6542b65a. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-ff5cd280aa82 accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Identity audit on PEOPLE-ASSET-ab714026bdcab67f recorded that repeated failed sign-ins were recorded for an account. The event references principal-b8f5dfca5dbf6b01. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Assessment SEC-fd425d2fe5a1 explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Windows logon audit on LEGAL-ASSET-30d47fccd7c65f45 recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-5fc9e45b889f41d1. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-d47751c6c07f explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Account audit on PEOPLE-ASSET-aaae6542cf112eee recorded that a local user account was created on a managed system. The event references principal-0953004be50ca69d. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-d8719312ac46 accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Mail flow logs on COMMUNICATIONS-ASSET-60efe7c42d543cb2 recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-6db1155a76f69a6b. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Saas audit on PEOPLE-ASSET-5249110e05a8362d recorded that a user requested a bulk export from a business application. The event references principal-55b28360ed7bad44. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Application audit on SUPPORT-ASSET-bc02457e5d2c9364 recorded that an application read clipboard contents repeatedly. The event references principal-5b5cc7cba3470ef8. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Switch telemetry on SALES-ASSET-67150f5bd544c87a recorded that an address mapping changed repeatedly on a local segment. The event references principal-f4e3b1c2069d2a7e. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-88ef29e55952 explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Share audit on PEOPLE-ASSET-29ff2158775d3e8d recorded that a new network file share was published. The event references principal-d660d14bb1dc5e12. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Dns server audit on OPERATIONS-ASSET-77c8f7df02d0b548 recorded that a client requested a DNS zone transfer. The event references principal-de675342a884898f. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Identity audit on RESEARCH-ASSET-6952971d9edc688b recorded that an account registered a new MFA method. The event references principal-b16ea02f54cbbb97. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"File audit on COMMUNICATIONS-ASSET-20dd539a3853169a recorded that a shell startup profile gained an additional command. The event references principal-c281969fbd0779dd. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Task scheduler audit on COMMUNICATIONS-ASSET-3b8f70e54b109a07 recorded that a scheduled task was registered to execute a program at logon. The event references principal-ea7b65d7a85105ed. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Cloud identity audit on COMMUNICATIONS-ASSET-e9dda7a9ac4613e3 recorded that a new programmatic access key was issued to a principal. The event references principal-b50a9e7363974da3. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Api gateway logs on RESEARCH-ASSET-43a3327a7670f557 recorded that a client issued a burst of API requests. The event references principal-19db88a740f22c57. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-8454e26d656a explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Registry audit on SALES-ASSET-2cd7195afaa340c4 recorded that a registry logon-start entry was created. The event references principal-4dafe2d9d91101fd. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Cloud control audit on SUPPORT-ASSET-f20f7641faecc324 recorded that a cloud logging destination was disabled. The event references principal-4d58eb61705c0ae8. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-4c654c8b0252 covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Registry audit on SUPPORT-ASSET-f57e1958aa803333 recorded that a workload pulled a container image from a registry. The event references principal-10cd1718e32b6b5f. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Process audit on PEOPLE-ASSET-f75719ff0e53a895 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-b17a106beae4504c. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Change CHG-44fa9976e905 lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Storage access logs on ENGINEERING-ASSET-cfa9edf25dbd11b0 recorded that a principal downloaded many objects from a storage bucket. The event references principal-9a3a0f64a8f2a35d. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-2413fe523ec4 accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Directory audit on ENGINEERING-ASSET-74de670cde6f3c91 recorded that a principal requested directory replication data. The event references principal-2491cc3af8b17009. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Winrm audit on FINANCE-ASSET-f7f3ea9e3a52d83c recorded that a remote management session invoked a command on a managed host. The event references principal-13d8273b51b14066. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Certificate audit on RESEARCH-ASSET-a52c58b217e48a75 recorded that a service certificate was replaced. The event references principal-8f17b08464430d9f. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Office audit on SALES-ASSET-bd4695abc7ff04ad recorded that a document macro launched a child interpreter. The event references principal-9bfaf02fa70a4f6b. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Gateway logs on PROCUREMENT-ASSET-b0d37645a10d287b recorded that a client established a long-lived encapsulated network session. The event references principal-1cc47c7a352875b2. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Agent audit on ENGINEERING-ASSET-d4aa23315bb70413 recorded that a privileged session changed endpoint monitoring settings. The event references principal-2e08cdbbea0a15c2. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Vpn audit on SUPPORT-ASSET-e419f3a293f3417a recorded that a remote-access VPN session was established. The event references principal-09df6291fa9e8663. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Kubernetes audit on COMMUNICATIONS-ASSET-a5023ab9f641c1cb recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-8da42e51a76b5b34. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Api gateway logs on LEGAL-ASSET-d8cde4dc3ebdd0ca recorded that a client issued a burst of API requests. The event references principal-9252cd194de4e3ac. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Process audit on SALES-ASSET-c1342eb6176b4ffa recorded that a Python interpreter loaded a script and contacted a service. The event references principal-e11956d74b8d7b52. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-406221714bb0 match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Dns control audit on COMMUNICATIONS-ASSET-9ae5b908b35b63ef recorded that an authoritative DNS record was updated. The event references principal-b17631352023456c. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-c92108ef1ce8 match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Windows logon audit on SALES-ASSET-6ef3ee3501c6fc3e recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-9c0f223e81092f12. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Key service audit on PROCUREMENT-ASSET-97184c5c539ee822 recorded that a principal issued a burst of key-service decrypt requests. The event references principal-d47010910e744f5c. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Dns control audit on ENGINEERING-ASSET-62a2603633015b4a recorded that an authoritative DNS record was updated. The event references principal-38391a49d25a310a. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Certificate audit on ENGINEERING-ASSET-9451d5f5fd9b7794 recorded that a service certificate was replaced. The event references principal-a6fab514c28c1ba9. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Cloud control audit on SUPPORT-ASSET-50842d406b871613 recorded that a session deleted a group of cloud resources. The event references principal-5fa6a0bc38223f91. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-2717e63b0352 before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Mail and proxy logs on RESEARCH-ASSET-0d6948f11ee5b28e recorded that a user opened a URL delivered in an email message. The event references principal-fdb003c9c4c80093. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-9e637a278134 specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Identity audit on RESEARCH-ASSET-88e52266f5af4a21 recorded that a service account established an interactive session. The event references principal-d08379cdebfa5913. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Module audit on ENGINEERING-ASSET-ef21d634c2b3a94b recorded that a process loaded a library from an application-local directory. The event references principal-47653e2725b4086f. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Change CHG-3aae9f772b44 lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Identity audit on RESEARCH-ASSET-77b0ab4459df7f50 recorded that repeated failed sign-ins were recorded for an account. The event references principal-ef9a3ac0fa7044a5. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Key service audit on RESEARCH-ASSET-fa35f918dce61e29 recorded that a principal issued a burst of key-service decrypt requests. The event references principal-139260250781ca0e. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Dhcp telemetry on COMMUNICATIONS-ASSET-a7af3c886d8ee570 recorded that a server issued DHCP offers on a monitored segment. The event references principal-aa2878e706226d96. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Network control audit on ENGINEERING-ASSET-2d4a799851b7227b recorded that a cloud security group gained a broad ingress rule. The event references principal-5b7cb16d420fdcdc. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Key service audit on SUPPORT-ASSET-32d985d5324796c4 recorded that a principal issued a burst of key-service decrypt requests. The event references principal-82b70d458957b545. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Proxy logs on SALES-ASSET-c3dbe91c60733c60 recorded that a client transferred a large payload to an external storage endpoint. The event references principal-fbf3a8a302b7a6c9. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Network control audit on RESEARCH-ASSET-e48fcfb18287d725 recorded that a cloud security group gained a broad ingress rule. The event references principal-0f1496ca8a6383fd. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Assessment SEC-e0eec088db37 explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Storage access logs on PROCUREMENT-ASSET-8beb52fc6c4219bf recorded that a principal downloaded many objects from a storage bucket. The event references principal-de077f5f8d45beed. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"File audit on OPERATIONS-ASSET-53ad24c9deb5d645 recorded that a shell startup profile gained an additional command. The event references principal-6049aaff0c8fe538. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Service audit on LEGAL-ASSET-c576aa1679d54c28 recorded that a new automatically started service was registered. The event references principal-7b1165f4385ce850. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Cloud identity audit on FINANCE-ASSET-44723c4a98b3d8ba recorded that a principal received a policy granting additional permissions. The event references principal-ddbfe461888a8cb6. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Assessment SEC-7c7d3ad551df explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Kubernetes audit on PROCUREMENT-ASSET-2f62998057d28724 recorded that a role binding granted a principal additional cluster permissions. The event references principal-4457a8d289298830. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Account audit on RESEARCH-ASSET-a444b46456cd6186 recorded that a local user account was created on a managed system. The event references principal-dd1721a44a27272f. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Ci secret audit on RESEARCH-ASSET-d46af760b3fcf2d7 recorded that a build job requested a protected pipeline secret. The event references principal-60fe7cbc94a757b5. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Kubernetes audit on PROCUREMENT-ASSET-a846eefa75a51312 recorded that a workload mounted a directory from its host filesystem. The event references principal-0cd6474c03a53052. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Pki audit on ENGINEERING-ASSET-1be9c96304b0e927 recorded that a principal requested a certificate using an authentication template. The event references principal-86425f445bb7386e. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Module audit on RESEARCH-ASSET-49e502fa5df5f407 recorded that a process loaded a library from an application-local directory. The event references principal-52065da876a99294. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Flow logs on ENGINEERING-ASSET-6ee9ce19d8b1f530 recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-5923ac86626d7de4. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Storage audit on FINANCE-ASSET-47f72b6b10bf47c7 recorded that a session deleted several storage snapshots. The event references principal-6ce8e4c42cc80c2d. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-ebc43c967274 match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Cron audit on PEOPLE-ASSET-4b3199ab3c63dd2d recorded that a recurring job definition was added to the system schedule. The event references principal-f1110cbb064f6627. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"File audit on ENGINEERING-ASSET-e53845b276f34712 recorded that a process rewrote multiple files into encrypted containers. The event references principal-f651e132a9d111e2. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"File audit on RESEARCH-ASSET-e7317bc73d028b83 recorded that a process deleted many files within a short interval. The event references principal-2ba5ba91bd6bd5b8. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Cron audit on FINANCE-ASSET-3836d6a68d057960 recorded that a recurring job definition was added to the system schedule. The event references principal-c8b819a1d7d4650c. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Session audit on COMMUNICATIONS-ASSET-9a4f765d7218bb33 recorded that the same session token appeared from different client addresses. The event references principal-961620617e88f850. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Device and file audit on ENGINEERING-ASSET-c9b77c2a506ace86 recorded that files were copied to a removable storage device. The event references principal-7078af09729168a5. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-18a2bc10051e explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Dns server audit on PROCUREMENT-ASSET-e8eb2bcb15a480a1 recorded that a client requested a DNS zone transfer. The event references principal-937daedbc93fd7dd. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Compute audit on COMMUNICATIONS-ASSET-36b3449238b8f470 recorded that a principal launched multiple compute instances. The event references principal-36e251f09c18691b. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Runtime audit on COMMUNICATIONS-ASSET-da48b46f34e4599d recorded that a process connected to the container runtime socket. The event references principal-3deaf11c55ba9307. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-683608b52fd6 covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Dns control audit on FINANCE-ASSET-84a7d1044449f1a8 recorded that an authoritative DNS record was updated. The event references principal-f7395e7a5d189597. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Kubernetes audit on LEGAL-ASSET-82e9dc780e2f0fb0 recorded that a pod was created with privileged execution enabled. The event references principal-7d1067f1bf4b8bd0. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Api gateway logs on PEOPLE-ASSET-010de515bde4832b recorded that a client issued a burst of API requests. The event references principal-828fabb7c52c8ecb. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Cloud control audit on OPERATIONS-ASSET-e8aae5321595ab4e recorded that a cloud logging destination was disabled. The event references principal-a8271fb4edbdf45f. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Change CHG-42f062fe6734 lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Dns control audit on RESEARCH-ASSET-f829e9e9bed9564b recorded that an authoritative DNS record was updated. The event references principal-9fdc73540b6a06a8. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-df17bb222203 match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Cloud control audit on ENGINEERING-ASSET-bbf96ebe3618813b recorded that a cloud logging destination was disabled. The event references principal-7942b0cb0edc33ed. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Kubernetes audit on RESEARCH-ASSET-200dc8ad3542be6e recorded that a role binding granted a principal additional cluster permissions. The event references principal-b8023dd958201bec. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Mail audit on PROCUREMENT-ASSET-57a43dc80cfc93ed recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-40142beb1db7ce4d. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Process audit on OPERATIONS-ASSET-495b246de141f994 recorded that a Python interpreter loaded a script and contacted a service. The event references principal-3264c9e681183a21. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Script audit on COMMUNICATIONS-ASSET-ad52eab51d5bfbe3 recorded that a script interpreter decoded an encoded argument before execution. The event references principal-b20c6bb2ef5361bb. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Application audit on COMMUNICATIONS-ASSET-349e251c3544c259 recorded that a runtime configuration setting was updated. The event references principal-f484d494a6adf949. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Agent audit on OPERATIONS-ASSET-7f3ae95480df95bb recorded that a privileged session changed endpoint monitoring settings. The event references principal-2ff0c372aa7d7315. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-ece303c6c9a5 explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Module audit on PROCUREMENT-ASSET-234ebd90da532d08 recorded that a process loaded a library from an application-local directory. The event references principal-2bfaedc31b23b886. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-0de44bec4994, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Mail flow logs on PROCUREMENT-ASSET-992b1e99dffe114d recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-ffd659ab57383ff2. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"File access audit on LEGAL-ASSET-c0436d9a797b6aac recorded that a process opened a local credential-store file. The event references principal-8f957f68f520d591. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Browser audit on LEGAL-ASSET-df49de2f96b43b40 recorded that a browser extension with page-reading permissions was installed. The event references principal-010a6a482ee1c838. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Winrm audit on PROCUREMENT-ASSET-98512f6cba9a2651 recorded that a remote management session invoked a command on a managed host. The event references principal-e3d261d10a11f3f9. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Session audit on PEOPLE-ASSET-2f7cb210c1411ef5 recorded that the same session token appeared from different client addresses. The event references principal-254fb3d8a50b95f2. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Cloud identity audit on OPERATIONS-ASSET-3155b7b471a38d4e recorded that a principal received a policy granting additional permissions. The event references principal-e51b01012b559bdf. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Agent audit on SALES-ASSET-4f0c6ee9e7bb90ab recorded that a privileged session changed endpoint monitoring settings. The event references principal-b547aa127479e0eb. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Change CHG-2dbd6d4a487e lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Device and file audit on SUPPORT-ASSET-05bbaad00af727ab recorded that files were copied to a removable storage device. The event references principal-dedda897251ae8fc. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-aae8c88a75e5 explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Service audit on ENGINEERING-ASSET-ef233e13b4aa7209 recorded that a new automatically started service was registered. The event references principal-aa6e053019f9dc60. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Application audit on COMMUNICATIONS-ASSET-c8d077447f8b8c1d recorded that an application requested repeated screen captures. The event references principal-062e1b2072504f50. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-0bcd9fb5f5d5 explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Script audit on SUPPORT-ASSET-1db9fff8dffdd6e2 recorded that a script interpreter decoded an encoded argument before execution. The event references principal-cddc3f00bf167947. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"File audit on OPERATIONS-ASSET-a72fe66e9e140fe9 recorded that a process compressed files from several directories into an archive. The event references principal-41403cc0bff319ee. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-3e7e35cdc4df accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Task scheduler audit on OPERATIONS-ASSET-0c0ccf4949e6876b recorded that a scheduled task was registered to execute a program at logon. The event references principal-6b1b6724d1e28e1c. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-9581cd1695eb accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Device and file audit on RESEARCH-ASSET-6da8ae6d7bfc1fd2 recorded that files were copied to a removable storage device. The event references principal-6e75da4e311027c4. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-7ef9b72c356e accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Cron audit on OPERATIONS-ASSET-837b3c551a9b50e7 recorded that a recurring job definition was added to the system schedule. The event references principal-96fb058b67291144. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Account audit on FINANCE-ASSET-00ff9ecf71797cc7 recorded that a local user account was created on a managed system. The event references principal-a4700d3ad9f008de. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Identity audit on PEOPLE-ASSET-ab714026bdcab67f recorded that repeated failed sign-ins were recorded for an account. The event references principal-b8f5dfca5dbf6b01. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Mail and proxy logs on LEGAL-ASSET-bdb95e0606dac9b6 recorded that a user opened a URL delivered in an email message. The event references principal-5ab74a82bf3ac244. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Task scheduler audit on PEOPLE-ASSET-967b5df7e748b2ff recorded that a scheduled task was registered to execute a program at logon. The event references principal-80092436d4633e85. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Cloud identity audit on PROCUREMENT-ASSET-ec7ad16199b37527 recorded that a principal received a policy granting additional permissions. The event references principal-8b968a5cde5474fa. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Federation audit on OPERATIONS-ASSET-d2752a593a5fec4b recorded that a tenant federation setting was updated. The event references principal-5f95a2859726a629. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Process audit on RESEARCH-ASSET-701eef6083bb4949 recorded that a Python interpreter loaded a script and contacted a service. The event references principal-9ed7f8cc72bbc316. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Application audit on PROCUREMENT-ASSET-9ae629f20e56becc recorded that a runtime configuration setting was updated. The event references principal-be5a20df9fa68e8b. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Change CHG-475afd67bbb7 lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Repository audit on FINANCE-ASSET-dc6e3bd56c8a0a87 recorded that a repository collaborator received elevated permissions. The event references principal-28c1f6e75f00c284. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"File audit on ENGINEERING-ASSET-e53845b276f34712 recorded that a process rewrote multiple files into encrypted containers. The event references principal-f651e132a9d111e2. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-428e80a052ce match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Oauth audit on LEGAL-ASSET-00c7e53409190f35 recorded that an application received consent for additional account scopes. The event references principal-aa7e16ffa8e68220. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-17942d82e1c5 match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Identity audit on SALES-ASSET-2f253fe8393025e1 recorded that an account password was reset through a recovery workflow. The event references principal-95366adc4199c0a7. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Proxy logs on RESEARCH-ASSET-2d6466dd3f8c1f6b recorded that a client transferred a large payload to an external storage endpoint. The event references principal-136b3bcae45dcdcd. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Security retest SEC-f0d7cdb75d80 covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Macos launch audit on OPERATIONS-ASSET-26bdf3f25161f2be recorded that a launch agent definition was installed in a user context. The event references principal-707a961a9c8924fd. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Systemd audit on PROCUREMENT-ASSET-e562e2af350db7c6 recorded that a service unit file was changed and the unit reloaded. The event references principal-a239fb376cfcf526. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Gateway logs on COMMUNICATIONS-ASSET-01bdebe9cfb40e2b recorded that a client established a long-lived encapsulated network session. The event references principal-298b7f8258456986. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Change CHG-f610a098f9a2 lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Mail and proxy logs on ENGINEERING-ASSET-d6ab66ae0acf6c7d recorded that a user opened a URL delivered in an email message. The event references principal-0a6867792e03bc3b. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Group audit on RESEARCH-ASSET-0d0aaf2292482822 recorded that an account was added to a privileged local group. The event references principal-5badc7c76a42d4b2. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Assessment SEC-84ca6b796f2f explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Waf logs on ENGINEERING-ASSET-155d31939b4a4ab3 recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-a5bfd2692d01cf27. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Wmi audit on RESEARCH-ASSET-ff750cc74100e1ac recorded that a management request started a process through WMI. The event references principal-2a6d4aeffc691fda. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Change CHG-1d18db7ff87a lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Oauth audit on PEOPLE-ASSET-f620f4cfac01530c recorded that an application received consent for additional account scopes. The event references principal-0999bb32ee8823f5. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Office audit on OPERATIONS-ASSET-a21bbd8f65591dc7 recorded that a document macro launched a child interpreter. The event references principal-640ebd4004779cca. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-02c16ac8ab97 explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Function audit on LEGAL-ASSET-a808b2dbcafaf1de recorded that a serverless function package and execution settings were updated. The event references principal-d18e2930c59bbade. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Change CHG-fafde95d18dc lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Cloud identity audit on SUPPORT-ASSET-d4887989aac3f6e3 recorded that a principal assumed a role in another account. The event references principal-ccdf0cbbc01cef8e. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Database audit on COMMUNICATIONS-ASSET-4fefa2aaca8d930a recorded that a session changed a database table definition. The event references principal-257c7d24c9971d35. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Windows logon audit on OPERATIONS-ASSET-4a019c17c7542e6c recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-dd10cd046f3074f7. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-d77dd0c5b438 before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Smb audit on OPERATIONS-ASSET-903799bcbb7f90a6 recorded that a session enumerated a file share and read multiple files. The event references principal-b3bfcfbe522db4bd. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-a084b14225b3 before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Dns server audit on PEOPLE-ASSET-9dfdc0288f418b98 recorded that a client requested a DNS zone transfer. The event references principal-fb173264d38aac45. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Policy audit on LEGAL-ASSET-fdcb7612a4f13f67 recorded that an audit policy was changed to collect fewer event categories. The event references principal-3d26eee8b88bfb17. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Mail flow logs on SALES-ASSET-40ddb7fd75836262 recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-4279d4843faab477. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Windows logon audit on RESEARCH-ASSET-fcc9667f845ac430 recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-af2356cb5701209c. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Mail audit on PROCUREMENT-ASSET-d1aa07096744ffae recorded that an account received delegated access to a mailbox. The event references principal-77fb31a09163908c. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Mail flow logs on FINANCE-ASSET-05268a477e8094f0 recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-ab4f2f7ab1b6ae29. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Key service audit on SALES-ASSET-4796409e71ec7ec0 recorded that a principal issued a burst of key-service decrypt requests. The event references principal-e868bdfcec891314. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Service audit on SUPPORT-ASSET-2eb791dfb1c8878d recorded that a new automatically started service was registered. The event references principal-7742e70843824b66. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-2607dd9a16cd covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Federation audit on FINANCE-ASSET-834ce73eb8e2d5f1 recorded that a tenant federation setting was updated. The event references principal-b4c9940f6c199e33. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Vpn audit on FINANCE-ASSET-5b805daa08de83aa recorded that a remote-access VPN session was established. The event references principal-cc88ce7b51f0aa37. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Mail audit on ENGINEERING-ASSET-0ca0b75c929f5305 recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-0a0bb31756158aab. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-13d969901ffb explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Ci audit on SALES-ASSET-58f9b0d2c10b53d7 recorded that a build pipeline definition gained a new execution step. The event references principal-db424878959459e6. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Ci secret audit on FINANCE-ASSET-b6445d71bd651026 recorded that a build job requested a protected pipeline secret. The event references principal-634acd477e34564f. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Mail flow logs on PEOPLE-ASSET-9ba2c53dc33b0530 recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-5b015560df1e299f. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Service audit on SALES-ASSET-fffc2b9a7422ce6b recorded that a remote service-control request created and started a temporary service. The event references principal-ab058eda0f6e9097. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Repository audit on SALES-ASSET-60f45c01cacb2ad7 recorded that a repository collaborator received elevated permissions. The event references principal-59983edc6542b65a. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Backup audit on COMMUNICATIONS-ASSET-34bf9b07e39c1f16 recorded that a backup retention policy was shortened. The event references principal-e0e79be492923c4a. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Storage audit on SUPPORT-ASSET-4d8e24bcff05f227 recorded that an object-storage access policy was broadened. The event references principal-5112ec3a6a51c1b1. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-ed17c7cfa2d2 explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Task scheduler audit on SALES-ASSET-14a4b633fa3add9a recorded that a scheduled task was registered to execute a program at logon. The event references principal-bc7f1b7e6f9cd150. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Kubernetes audit on OPERATIONS-ASSET-f1f73c739188a298 recorded that a workload mounted a directory from its host filesystem. The event references principal-5a00d24e558e0ba4. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Change CHG-c2b20252f060 lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Configuration audit on PEOPLE-ASSET-5afa9d0b44139e46 recorded that a client proxy setting was changed. The event references principal-c6f3609cd125d978. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-d88ab608ff72 match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Macos launch audit on FINANCE-ASSET-050b0e8279760750 recorded that a launch agent definition was installed in a user context. The event references principal-7354e7b956585560. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Change CHG-1843d5adc79d lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Device and file audit on PEOPLE-ASSET-6b2be688c0738ea2 recorded that files were copied to a removable storage device. The event references principal-cb796dfd2a52dfa6. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Change CHG-5dd4e63794bd lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Mail audit on SUPPORT-ASSET-d04332aa87461fec recorded that an account received delegated access to a mailbox. The event references principal-4bd49edb0535ebaf. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Ci audit on PROCUREMENT-ASSET-51d14292a906982f recorded that a build pipeline definition gained a new execution step. The event references principal-776e5e2e9ad695a2. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Kubernetes audit on SALES-ASSET-b7d7628f8816a948 recorded that a role binding granted a principal additional cluster permissions. The event references principal-76cb7e33983ecb6a. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Assessment SEC-21d31f74927b explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Share audit on PEOPLE-ASSET-29ff2158775d3e8d recorded that a new network file share was published. The event references principal-d660d14bb1dc5e12. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Package registry audit on RESEARCH-ASSET-b42ad559dc38cada recorded that a principal published a new package version. The event references principal-ae25582585615c9e. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Dns control audit on RESEARCH-ASSET-f829e9e9bed9564b recorded that an authoritative DNS record was updated. The event references principal-9fdc73540b6a06a8. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-df17bb222203 match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Cloud identity audit on OPERATIONS-ASSET-e9ea023dcfe573c8 recorded that a principal assumed a role in another account. The event references principal-33e2cf770673f137. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"File audit on LEGAL-ASSET-4a73488ba2d33df6 recorded that a process rewrote multiple files into encrypted containers. The event references principal-9d7037ae8c34aa83. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Cloud identity audit on PEOPLE-ASSET-db5bfc23857c8681 recorded that a principal assumed a role in another account. The event references principal-3e8604b26d44d800. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Cloud control audit on SALES-ASSET-c5ac5bf2061a85e1 recorded that resources were created in a region with little prior activity. The event references principal-213b93a3248e4777. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-eeab5ca29100 accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Gateway logs on PEOPLE-ASSET-755d4ede711826a7 recorded that a client established a long-lived encapsulated network session. The event references principal-3095e007e6941bdd. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Process access audit on ENGINEERING-ASSET-6c512bf3bb9f3c6e recorded that a process requested read access to another process memory space. The event references principal-0c750e6c9b19f34e. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Kubernetes audit on SUPPORT-ASSET-99bd1381f9f84168 recorded that a pod was created with privileged execution enabled. The event references principal-4de29bd2a93d9674. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Mfa audit on ENGINEERING-ASSET-4741e70baa0f7c7a recorded that multiple MFA challenges were issued during a short interval. The event references principal-7a266bf7aed055c1. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Event service audit on FINANCE-ASSET-9334935a696bff2c recorded that an event log was cleared by a privileged request. The event references principal-f4f6381e73c7f8ed. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Security retest SEC-aa1cb5a12cb4 covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Repository audit on ENGINEERING-ASSET-19fede4e07d7366c recorded that a repository collaborator received elevated permissions. The event references principal-22c3a4b3adce2401. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Application audit on OPERATIONS-ASSET-82d2279115651372 recorded that an application read clipboard contents repeatedly. The event references principal-d93f4c8e19d295a8. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Configuration audit on PROCUREMENT-ASSET-8aac493103d32947 recorded that a client proxy setting was changed. The event references principal-5ba8d1fc71029290. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Security retest SEC-221ec117bac6 covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Backup audit on FINANCE-ASSET-7d6385ebfb9a8a83 recorded that a backup retention policy was shortened. The event references principal-87f1c31296aed897. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Process audit on PEOPLE-ASSET-534c3950a47d5a64 recorded that a JavaScript interpreter executed a local script. The event references principal-8170f0f562dc21d2. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-5bc8db1c86d2 explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Process audit on PROCUREMENT-ASSET-e094a3806b86f26f recorded that a remote-support application started an interactive session. The event references principal-0e21b55912ebea78. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Kubernetes audit on PROCUREMENT-ASSET-a846eefa75a51312 recorded that a workload mounted a directory from its host filesystem. The event references principal-0cd6474c03a53052. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-cea231fffd4e accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Identity audit on FINANCE-ASSET-8c4f9dd18c643b5e recorded that repeated failed sign-ins were recorded for an account. The event references principal-e15b307c4e5bf156. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Process access audit on RESEARCH-ASSET-d44095e784b89a49 recorded that a process requested read access to another process memory space. The event references principal-961efc1f116f534c. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-fdf8eccffc8a explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Compute audit on PROCUREMENT-ASSET-507dec859fa3003b recorded that a principal launched multiple compute instances. The event references principal-611c292a786d76ca. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Registry audit on FINANCE-ASSET-7f731069af53e8e1 recorded that a workload pulled a container image from a registry. The event references principal-b80084fb240685bf. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Ci secret audit on PROCUREMENT-ASSET-7ef0c5a6d6fc8733 recorded that a build job requested a protected pipeline secret. The event references principal-77e6930e6b3513f9. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Change CHG-80e7728b16e8 lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Code integrity audit on OPERATIONS-ASSET-06f732c807773233 recorded that an executable without a publisher signature started from a writable directory. The event references principal-28681a2e3d3ce90b. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Certificate audit on LEGAL-ASSET-028cc6c15478424c recorded that a service certificate was replaced. The event references principal-ab2a10d3b09a07d5. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Runtime audit on FINANCE-ASSET-f76f44e364cb49d4 recorded that a process connected to the container runtime socket. The event references principal-61088a6af6fdfeb5. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Gateway logs on PEOPLE-ASSET-755d4ede711826a7 recorded that a client established a long-lived encapsulated network session. The event references principal-3095e007e6941bdd. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Directory audit on RESEARCH-ASSET-717c1ed36129eee9 recorded that a principal requested directory replication data. The event references principal-71255b0539b4ae1e. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Registry audit on PEOPLE-ASSET-2d7ca72857a14112 recorded that a workload pulled a container image from a registry. The event references principal-f31f9ebfd4a3d389. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Cron audit on SUPPORT-ASSET-0f143a13847207ad recorded that a recurring job definition was added to the system schedule. The event references principal-940a8e24d3cd68aa. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Cloud identity audit on OPERATIONS-ASSET-3155b7b471a38d4e recorded that a principal received a policy granting additional permissions. The event references principal-e51b01012b559bdf. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-d27f6ea5c71e accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Dhcp telemetry on PEOPLE-ASSET-2fdf9f5c1cf8306c recorded that a server issued DHCP offers on a monitored segment. The event references principal-c81573ac45372a70. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-5d13d7e67440, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Cloud control audit on LEGAL-ASSET-152843552545f6c2 recorded that a session deleted a group of cloud resources. The event references principal-441348e944e96c5c. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-30e36caa1c81 match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Device and file audit on LEGAL-ASSET-e36229f519715f46 recorded that files were copied to a removable storage device. The event references principal-ecac25dd7192fc25. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-4d76318bf5c5 accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Storage audit on PROCUREMENT-ASSET-283ac93c3c2be26b recorded that a session deleted several storage snapshots. The event references principal-84f457c32ccdb7a6. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Waf logs on ENGINEERING-ASSET-155d31939b4a4ab3 recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-a5bfd2692d01cf27. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Application audit on ENGINEERING-ASSET-0a500e9acaab2792 recorded that an application requested repeated screen captures. The event references principal-f9139e2001fef8f3. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Api gateway logs on LEGAL-ASSET-d8cde4dc3ebdd0ca recorded that a client issued a burst of API requests. The event references principal-9252cd194de4e3ac. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Process audit on SUPPORT-ASSET-9f8775e0a67ff6e2 recorded that a remote-support application started an interactive session. The event references principal-342d9605d5b86694. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Registry audit on PROCUREMENT-ASSET-76d816b7b04f4b8f recorded that a workload pulled a container image from a registry. The event references principal-12ce95b5667b0630. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Share audit on SALES-ASSET-af32e6af472026fd recorded that a new network file share was published. The event references principal-f1240dad3caae0d8. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-3ea12578c75f accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Service audit on COMMUNICATIONS-ASSET-7e54b0ca38e553fe recorded that a new automatically started service was registered. The event references principal-7d549ca6bce506ce. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Process audit on PROCUREMENT-ASSET-e094a3806b86f26f recorded that a remote-support application started an interactive session. The event references principal-0e21b55912ebea78. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Process audit on OPERATIONS-ASSET-495b246de141f994 recorded that a Python interpreter loaded a script and contacted a service. The event references principal-3264c9e681183a21. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Identity audit on SUPPORT-ASSET-15695a645557b69f recorded that repeated failed sign-ins were recorded for an account. The event references principal-51d00d36a920ed83. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Kubernetes audit on PROCUREMENT-ASSET-8857c7021ba70cdd recorded that a cluster admission policy was changed. The event references principal-0637e683dcd7afbd. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Egress flow logs on SALES-ASSET-a811cdcc9969f943 recorded that a workload opened an encrypted connection to an external service. The event references principal-17514c019150a73d. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Cloud identity audit on PEOPLE-ASSET-db5bfc23857c8681 recorded that a principal assumed a role in another account. The event references principal-3e8604b26d44d800. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Kubernetes audit on RESEARCH-ASSET-e5b9e413bdef9d8d recorded that a pod was created with privileged execution enabled. The event references principal-74b8c2bcccc76ba0. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Kubernetes audit on FINANCE-ASSET-4f8f4d9f800ab9a6 recorded that a cluster admission policy was changed. The event references principal-0f727ece26b623bd. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"File audit on RESEARCH-ASSET-e98c7e7ef8b5bfbe recorded that a process rewrote multiple files into encrypted containers. The event references principal-b60fe0e57ed46b9d. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Mfa audit on SUPPORT-ASSET-72ab1273fb4de7e8 recorded that multiple MFA challenges were issued during a short interval. The event references principal-ed28d619781ff3d6. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-858a32a3b17e explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Api gateway logs on RESEARCH-ASSET-43a3327a7670f557 recorded that a client issued a burst of API requests. The event references principal-19db88a740f22c57. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Security retest SEC-8454e26d656a covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"File audit on FINANCE-ASSET-a2913f2126217458 recorded that access permissions were broadened on a directory tree. The event references principal-05896b0efe4a938e. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Winrm audit on PEOPLE-ASSET-f67c81ba2aebe0a8 recorded that a remote management session invoked a command on a managed host. The event references principal-380dff97d88676ce. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-ccd1f98e04ad, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Registry audit on SALES-ASSET-797a3ae487efd18f recorded that a workload pulled a container image from a registry. The event references principal-6df652f7e41389ab. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Cloud identity audit on RESEARCH-ASSET-809fdc9f1154a3c8 recorded that a principal received a policy granting additional permissions. The event references principal-58f2cdd79c2b5788. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Egress flow logs on FINANCE-ASSET-6fc2f9679740efc1 recorded that a workload opened an encrypted connection to an external service. The event references principal-b6c8a10c3d36b1fc. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Storage audit on RESEARCH-ASSET-4fe3f3661fdb65de recorded that a session deleted several storage snapshots. The event references principal-c8575d45e94d3ebb. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"File audit on PEOPLE-ASSET-df8464b337d342a5 recorded that a process deleted many files within a short interval. The event references principal-f13400db0397fece. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Security retest SEC-6f2add6a40bc covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Process audit on PEOPLE-ASSET-534c3950a47d5a64 recorded that a JavaScript interpreter executed a local script. The event references principal-8170f0f562dc21d2. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-5bc8db1c86d2 specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Cloud control audit on OPERATIONS-ASSET-31b25a4a2bbf0f7e recorded that resources were created in a region with little prior activity. The event references principal-2043ac1bd7256aa6. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Task scheduler audit on LEGAL-ASSET-9a82bb1a05cff6a6 recorded that a scheduled task was registered to execute a program at logon. The event references principal-5c02a139758a7988. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Mail flow logs on PROCUREMENT-ASSET-992b1e99dffe114d recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-ffd659ab57383ff2. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-4952bf9cb85b accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Identity audit on SALES-ASSET-17bd921cea441a1f recorded that repeated failed sign-ins were recorded for an account. The event references principal-d02e40aae87e9ff0. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Group audit on LEGAL-ASSET-c0290e976cae1a6c recorded that an account was added to a privileged local group. The event references principal-0e07ba3cca839e79. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Event service audit on SUPPORT-ASSET-2b5c6ab4e8f6f174 recorded that an event log was cleared by a privileged request. The event references principal-2294144a09bcf573. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-c23c3daa649a, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Egress flow logs on SALES-ASSET-a811cdcc9969f943 recorded that a workload opened an encrypted connection to an external service. The event references principal-17514c019150a73d. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Identity audit on PEOPLE-ASSET-d81992a54d0e0cd4 recorded that a service account established an interactive session. The event references principal-0bc399328dfcae48. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Application audit on ENGINEERING-ASSET-c6a3af2b55d88d84 recorded that a runtime configuration setting was updated. The event references principal-67b63805e0368323. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Compute audit on ENGINEERING-ASSET-67df6013e7bda695 recorded that a principal launched multiple compute instances. The event references principal-d74238a9b43b1893. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"File audit on LEGAL-ASSET-b2789a781837a87b recorded that a shell startup profile gained an additional command. The event references principal-d7a3487fce82090e. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Mfa audit on ENGINEERING-ASSET-4741e70baa0f7c7a recorded that multiple MFA challenges were issued during a short interval. The event references principal-7a266bf7aed055c1. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"File access audit on OPERATIONS-ASSET-1494559c806dea5d recorded that a process opened a local credential-store file. The event references principal-c4b1fa13e42018fb. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Kerberos audit on OPERATIONS-ASSET-15b32c4f5f91cc11 recorded that an account requested service tickets for multiple services. The event references principal-86eb3dff1abf1690. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Storage access logs on PROCUREMENT-ASSET-8beb52fc6c4219bf recorded that a principal downloaded many objects from a storage bucket. The event references principal-de077f5f8d45beed. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Macos launch audit on PEOPLE-ASSET-f2ccd0993eb11ff9 recorded that a launch agent definition was installed in a user context. The event references principal-ff81666bc8b89437. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Cloud control audit on RESEARCH-ASSET-7f111a5abf79c08a recorded that a session deleted a group of cloud resources. The event references principal-e374d397f062ff2d. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Task scheduler audit on OPERATIONS-ASSET-0c0ccf4949e6876b recorded that a scheduled task was registered to execute a program at logon. The event references principal-6b1b6724d1e28e1c. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Repository audit on PEOPLE-ASSET-e8dfe6d75dbb8e1e recorded that a user cloned several source repositories. The event references principal-e971d955c552fbff. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Cloud control audit on PROCUREMENT-ASSET-3d72a13549b9a584 recorded that resources were created in a region with little prior activity. The event references principal-a14765e1d71ea435. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Proxy logs on COMMUNICATIONS-ASSET-5a2ac13c8b310540 recorded that a client transferred a large payload to an external storage endpoint. The event references principal-d735b0162330748a. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Package registry audit on ENGINEERING-ASSET-468e2f1736323150 recorded that a principal published a new package version. The event references principal-cbfd72c0328f2633. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"File audit on FINANCE-ASSET-a4971629c23d55d9 recorded that a process compressed files from several directories into an archive. The event references principal-c74fdddea36d843d. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Gateway logs on COMMUNICATIONS-ASSET-01bdebe9cfb40e2b recorded that a client established a long-lived encapsulated network session. The event references principal-298b7f8258456986. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Process audit on SUPPORT-ASSET-6a54632d13cc3523 recorded that a JavaScript interpreter executed a local script. The event references principal-5989897ff7bc53ab. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-6c9bcf609a88 covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Task scheduler audit on ENGINEERING-ASSET-03b8a656580bfb25 recorded that a scheduled task was registered to execute a program at logon. The event references principal-2a3a3ccb2ea52460. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Pki audit on SUPPORT-ASSET-70be4dd0be19b589 recorded that a principal requested a certificate using an authentication template. The event references principal-3490e3ca6541e91e. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Kubernetes audit on PROCUREMENT-ASSET-fa28de9adbfdddd4 recorded that a pod was created with privileged execution enabled. The event references principal-c0583fecec986fcd. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Network control audit on LEGAL-ASSET-8a1d97d0c15ac118 recorded that a cloud security group gained a broad ingress rule. The event references principal-52d39a8366e69bf4. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Cloud identity audit on PEOPLE-ASSET-db5bfc23857c8681 recorded that a principal assumed a role in another account. The event references principal-3e8604b26d44d800. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-23f818d17081, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Ssh audit on PROCUREMENT-ASSET-76513cf046529603 recorded that an SSH session opened and requested elevated command execution. The event references principal-5b3a8f0f85403c14. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Cloud identity audit on ENGINEERING-ASSET-af1e93943ab29f9c recorded that a new programmatic access key was issued to a principal. The event references principal-44b79fe1a6fcf9a1. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-b5a71bc5db2a before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Cloud identity audit on SUPPORT-ASSET-d4887989aac3f6e3 recorded that a principal assumed a role in another account. The event references principal-ccdf0cbbc01cef8e. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Storage audit on PEOPLE-ASSET-4b18ae09e42fe01b recorded that an object-storage access policy was broadened. The event references principal-7721904d8c389cbb. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-6a5c131edbe9 before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Network control audit on RESEARCH-ASSET-e48fcfb18287d725 recorded that a cloud security group gained a broad ingress rule. The event references principal-0f1496ca8a6383fd. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Identity audit on LEGAL-ASSET-943053d6267ac572 recorded that a service account established an interactive session. The event references principal-158c8b7f105115ea. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Repository audit on PEOPLE-ASSET-ab514f2b7cf1ca44 recorded that a repository collaborator received elevated permissions. The event references principal-49f43d9a0cf7b13c. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Change CHG-fdc9cbf7ebac lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Ssh audit on LEGAL-ASSET-97358e826a1337d7 recorded that an SSH session opened and requested elevated command execution. The event references principal-713d0f7027f2d117. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Dhcp telemetry on COMMUNICATIONS-ASSET-a7af3c886d8ee570 recorded that a server issued DHCP offers on a monitored segment. The event references principal-aa2878e706226d96. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-c1b51b7b5c79 match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Certificate audit on RESEARCH-ASSET-a52c58b217e48a75 recorded that a service certificate was replaced. The event references principal-8f17b08464430d9f. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Dns server audit on OPERATIONS-ASSET-77c8f7df02d0b548 recorded that a client requested a DNS zone transfer. The event references principal-de675342a884898f. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Cloud identity audit on SALES-ASSET-6e863cbb874762df recorded that a principal assumed a role in another account. The event references principal-3f1f6f7b104b9c3f. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-a8c53e28dcb9 match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Driver audit on SUPPORT-ASSET-19c2a39ea2af2cbe recorded that a kernel driver was loaded after a package installation. The event references principal-f5704bc0d4a6300d. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Wmi audit on PEOPLE-ASSET-0793506618492b13 recorded that a management request started a process through WMI. The event references principal-517018be0d1cff5c. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Key service audit on RESEARCH-ASSET-fa35f918dce61e29 recorded that a principal issued a burst of key-service decrypt requests. The event references principal-139260250781ca0e. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Pki audit on FINANCE-ASSET-3748aa367e539143 recorded that a principal requested a certificate using an authentication template. The event references principal-d4df29576d1acbb5. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Directory audit on PEOPLE-ASSET-37791232d78efc05 recorded that a principal requested directory replication data. The event references principal-55f0d12673ae40b1. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Federation audit on OPERATIONS-ASSET-d2752a593a5fec4b recorded that a tenant federation setting was updated. The event references principal-5f95a2859726a629. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Process audit on PEOPLE-ASSET-f75719ff0e53a895 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-b17a106beae4504c. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Repository audit on PROCUREMENT-ASSET-7cc2509e9eb69ebb recorded that a user cloned several source repositories. The event references principal-39fa91ed4065a325. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Process audit on ENGINEERING-ASSET-2b855d0d88712cb8 recorded that a JavaScript interpreter executed a local script. The event references principal-3943e4c085d81398. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Winrm audit on COMMUNICATIONS-ASSET-2bb6a89a28755b1e recorded that a remote management session invoked a command on a managed host. The event references principal-2ae22aaef9849f17. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-e0d2e81a8544 before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Firewall audit on ENGINEERING-ASSET-4346eb459a11971a recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-62f6e1ae625e9e27. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-329131c1f97a accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Mail flow logs on FINANCE-ASSET-05268a477e8094f0 recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-ab4f2f7ab1b6ae29. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Cloud control audit on PROCUREMENT-ASSET-3d72a13549b9a584 recorded that resources were created in a region with little prior activity. The event references principal-a14765e1d71ea435. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Process audit on FINANCE-ASSET-565f2ed301684671 recorded that a remote-support application started an interactive session. The event references principal-a4a07392170d1084. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Assessment SEC-c7ce772c93d9 explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Systemd audit on ENGINEERING-ASSET-0abbd02cc9ffea8d recorded that a service unit file was changed and the unit reloaded. The event references principal-7986cde737b4fe49. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-60355b36d0c9 accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Gateway logs on ENGINEERING-ASSET-8864632089fd4c50 recorded that a client established a long-lived encapsulated network session. The event references principal-90ee640b3b5c5162. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Group audit on LEGAL-ASSET-c0290e976cae1a6c recorded that an account was added to a privileged local group. The event references principal-0e07ba3cca839e79. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Flow logs on PROCUREMENT-ASSET-cd965c50b19b4b1f recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-3abc068e3f191445. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Compute audit on COMMUNICATIONS-ASSET-36b3449238b8f470 recorded that a principal launched multiple compute instances. The event references principal-36e251f09c18691b. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Dns control audit on FINANCE-ASSET-84a7d1044449f1a8 recorded that an authoritative DNS record was updated. The event references principal-f7395e7a5d189597. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Kerberos audit on SALES-ASSET-7d0683e2088779fa recorded that an account requested service tickets for multiple services. The event references principal-b437865450b6fb0e. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Vpn audit on OPERATIONS-ASSET-3b10a040384bc85b recorded that a remote-access VPN session was established. The event references principal-e69c38b8397d46ff. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Storage audit on PROCUREMENT-ASSET-283ac93c3c2be26b recorded that a session deleted several storage snapshots. The event references principal-84f457c32ccdb7a6. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"File audit on FINANCE-ASSET-a2913f2126217458 recorded that access permissions were broadened on a directory tree. The event references principal-05896b0efe4a938e. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Process audit on ENGINEERING-ASSET-2b855d0d88712cb8 recorded that a JavaScript interpreter executed a local script. The event references principal-3943e4c085d81398. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-33ee922d10f1 explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Cloud control audit on COMMUNICATIONS-ASSET-53a6ecae622bccee recorded that a cloud logging destination was disabled. The event references principal-cf25374694280e00. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Policy audit on PEOPLE-ASSET-4626b13b6c89e82c recorded that an audit policy was changed to collect fewer event categories. The event references principal-dc47a10146c766ea. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Kubernetes audit on OPERATIONS-ASSET-914b85ff52bb152e recorded that a role binding granted a principal additional cluster permissions. The event references principal-23475897d2814771. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Secret manager audit on COMMUNICATIONS-ASSET-0901e5043739c868 recorded that a workload read several secret versions. The event references principal-811d7f224d798eaf. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Ci audit on LEGAL-ASSET-307a1ab2be77fe5f recorded that a build pipeline definition gained a new execution step. The event references principal-362aa0b8c3b22688. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Cloud identity audit on ENGINEERING-ASSET-af1e93943ab29f9c recorded that a new programmatic access key was issued to a principal. The event references principal-44b79fe1a6fcf9a1. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Configuration audit on RESEARCH-ASSET-c3d25c02edb1b375 recorded that a client proxy setting was changed. The event references principal-c2c0e84c38c559bb. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Smb audit on PROCUREMENT-ASSET-663a220061cd4095 recorded that a session enumerated a file share and read multiple files. The event references principal-ae5de00ea82776e7. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Assessment SEC-c00c3a42f57d explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Identity audit on OPERATIONS-ASSET-bc3d71283010bd0f recorded that an account password was reset through a recovery workflow. The event references principal-65a355a045f94503. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Process audit on OPERATIONS-ASSET-4be1d9f7adca7d10 recorded that a remote-support application started an interactive session. The event references principal-85052a5f25abdf7a. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Kerberos audit on SALES-ASSET-7d0683e2088779fa recorded that an account requested service tickets for multiple services. The event references principal-b437865450b6fb0e. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Kubernetes audit on COMMUNICATIONS-ASSET-a5023ab9f641c1cb recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-8da42e51a76b5b34. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-a0bd3035280b specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Kubernetes audit on OPERATIONS-ASSET-914b85ff52bb152e recorded that a role binding granted a principal additional cluster permissions. The event references principal-23475897d2814771. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Kubernetes audit on LEGAL-ASSET-d5c1c420f1077ded recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-1d6426e1ff1f69c4. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-28b19d5ecaae before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Identity audit on PEOPLE-ASSET-5f5eb7d500371474 recorded that an account registered a new MFA method. The event references principal-7c9584053a66a813. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Kubernetes audit on ENGINEERING-ASSET-cad5b32322e2d059 recorded that a pod was created with privileged execution enabled. The event references principal-b5a63a5d1fffe886. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Key service audit on SALES-ASSET-4796409e71ec7ec0 recorded that a principal issued a burst of key-service decrypt requests. The event references principal-e868bdfcec891314. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Dns server audit on SUPPORT-ASSET-99242b48e0f1290b recorded that a client requested a DNS zone transfer. The event references principal-c5b7de8a13a46984. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-ff24131b9a24 specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Identity audit on LEGAL-ASSET-3e81b75ec6767272 recorded that repeated failed sign-ins were recorded for an account. The event references principal-4e9f85f638a1922a. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Task scheduler audit on PROCUREMENT-ASSET-bd3697f2e2b8950e recorded that a scheduled task was registered to execute a program at logon. The event references principal-1483881099fae9be. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Ci secret audit on PEOPLE-ASSET-50143023c0d694b1 recorded that a build job requested a protected pipeline secret. The event references principal-236f39206994ec5b. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Agent audit on RESEARCH-ASSET-01cc4805ed6fe45d recorded that a privileged session changed endpoint monitoring settings. The event references principal-fb3e99ff7e75f725. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Assessment SEC-1242f26f3b6a explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Ssh audit on LEGAL-ASSET-97358e826a1337d7 recorded that an SSH session opened and requested elevated command execution. The event references principal-713d0f7027f2d117. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Compute audit on FINANCE-ASSET-428507c521e75c88 recorded that a principal launched multiple compute instances. The event references principal-a167ad7ce21b7604. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Group audit on FINANCE-ASSET-df066dc7583c9589 recorded that an account was added to a privileged local group. The event references principal-91bee423e82eb7d5. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Session audit on SUPPORT-ASSET-39c9a292833723e5 recorded that the same session token appeared from different client addresses. The event references principal-a5ec7d156048f10f. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-cede59290fc3 explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Repository audit on COMMUNICATIONS-ASSET-74eb656a821bda53 recorded that a repository collaborator received elevated permissions. The event references principal-aeb807368ce77066. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-9ecd3f8c22a5 match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Repository audit on FINANCE-ASSET-dc6e3bd56c8a0a87 recorded that a repository collaborator received elevated permissions. The event references principal-28c1f6e75f00c284. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Network control audit on SALES-ASSET-bd4a95d925024567 recorded that a cloud security group gained a broad ingress rule. The event references principal-2e1769cecef25401. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Security retest SEC-29db28979de6 covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Ssh audit on SUPPORT-ASSET-842f8e08ea10f95b recorded that an SSH session opened and requested elevated command execution. The event references principal-3779cc64299d1a95. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Service audit on SUPPORT-ASSET-2eb791dfb1c8878d recorded that a new automatically started service was registered. The event references principal-7742e70843824b66. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Storage audit on SUPPORT-ASSET-519ebc03fcafbccd recorded that a session deleted several storage snapshots. The event references principal-1671f42126c1c5f8. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Smb audit on COMMUNICATIONS-ASSET-88088ffb8b08e158 recorded that a session enumerated a file share and read multiple files. The event references principal-82b755f6442bfd40. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Saas audit on COMMUNICATIONS-ASSET-1937d1daec1efbd9 recorded that a user requested a bulk export from a business application. The event references principal-7aa0534f456ac613. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-b424c7e4107b explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Browser audit on PROCUREMENT-ASSET-50d8010904173019 recorded that a browser extension with page-reading permissions was installed. The event references principal-8e2e0553f52a5216. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Mail audit on ENGINEERING-ASSET-784f3c782f3ac855 recorded that an account received delegated access to a mailbox. The event references principal-2080f4d9197e7c3e. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Vpn audit on FINANCE-ASSET-5b805daa08de83aa recorded that a remote-access VPN session was established. The event references principal-cc88ce7b51f0aa37. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Event service audit on ENGINEERING-ASSET-93dff18c1d7d23e9 recorded that an event log was cleared by a privileged request. The event references principal-32227ffe2b6b23ca. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Federation audit on RESEARCH-ASSET-85e9941ba25e96bb recorded that a tenant federation setting was updated. The event references principal-863b72c786eda302. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"File audit on RESEARCH-ASSET-e7317bc73d028b83 recorded that a process deleted many files within a short interval. The event references principal-2ba5ba91bd6bd5b8. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Proxy logs on FINANCE-ASSET-f9b86d6f6b974e8f recorded that a client transferred a large payload to an external storage endpoint. The event references principal-252b9a9159e9be98. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Share audit on FINANCE-ASSET-689b8f41db9ab4f4 recorded that a new network file share was published. The event references principal-604eb4041d82448c. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Assessment SEC-e4c4b889b049 explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Application audit on OPERATIONS-ASSET-cf2679e9708fa36f recorded that a runtime configuration setting was updated. The event references principal-3db05afeebe1db89. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-53fd9a25d116 before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Process audit on OPERATIONS-ASSET-4be1d9f7adca7d10 recorded that a remote-support application started an interactive session. The event references principal-85052a5f25abdf7a. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-3503c46a3a3a accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Directory audit on FINANCE-ASSET-4f2fe0486abb5c95 recorded that a principal requested directory replication data. The event references principal-b40239cccc5bf96a. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Saas audit on COMMUNICATIONS-ASSET-1937d1daec1efbd9 recorded that a user requested a bulk export from a business application. The event references principal-7aa0534f456ac613. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Flow logs on SUPPORT-ASSET-103a412104563dae recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-a1ca47883deef1d3. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-b39b57fe0a27 specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Storage audit on COMMUNICATIONS-ASSET-4c8d4447eef18c17 recorded that an object-storage access policy was broadened. The event references principal-2ee0983ecf5d6d25. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Process audit on SUPPORT-ASSET-6a54632d13cc3523 recorded that a JavaScript interpreter executed a local script. The event references principal-5989897ff7bc53ab. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Mail flow logs on ENGINEERING-ASSET-b3fe8e13b124582a recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-4618a2ddb02b8454. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-bf3d2eb25bad explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Script audit on SUPPORT-ASSET-1db9fff8dffdd6e2 recorded that a script interpreter decoded an encoded argument before execution. The event references principal-cddc3f00bf167947. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"File audit on RESEARCH-ASSET-e7317bc73d028b83 recorded that a process deleted many files within a short interval. The event references principal-2ba5ba91bd6bd5b8. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Vpn audit on SALES-ASSET-09dd168451b4fb60 recorded that a remote-access VPN session was established. The event references principal-732980774243feef. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Application audit on FINANCE-ASSET-92ef4a42892b1789 recorded that an application read clipboard contents repeatedly. The event references principal-13f5550b59519bb2. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Security retest SEC-5f9748db384d covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Registry audit on PEOPLE-ASSET-2d7ca72857a14112 recorded that a workload pulled a container image from a registry. The event references principal-f31f9ebfd4a3d389. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Cron audit on SALES-ASSET-34715d088f9c8c11 recorded that a recurring job definition was added to the system schedule. The event references principal-69300e7147cdfbd9. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-ce1afd00b60c match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"File audit on FINANCE-ASSET-d2b45ac726791f9b recorded that a process deleted many files within a short interval. The event references principal-e041b8a80436a62f. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Database audit on RESEARCH-ASSET-0df9b1ba7848d017 recorded that a session read several tables and exported the query result. The event references principal-78007df53b70739e. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Waf logs on PROCUREMENT-ASSET-be57d152ab66f42b recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-c19a63b81ac51b37. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Cloud identity audit on PEOPLE-ASSET-f0da82528453fc68 recorded that a principal received a policy granting additional permissions. The event references principal-c5a646fec9c6789b. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-9dd949b65dcf, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Storage audit on PROCUREMENT-ASSET-f524c33b819a1663 recorded that an object-storage access policy was broadened. The event references principal-daeee49ee65928ba. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Assessment SEC-051e1473ade7 explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Package registry audit on FINANCE-ASSET-39c7276454a893cc recorded that a principal published a new package version. The event references principal-9e718ff7956300e6. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Service audit on RESEARCH-ASSET-83637b2bf6e44350 recorded that a new automatically started service was registered. The event references principal-9f4043a1a42fcc90. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Function audit on PROCUREMENT-ASSET-9b0e13d58a2188a8 recorded that a serverless function package and execution settings were updated. The event references principal-12b8d8e2191620d9. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Flow logs on ENGINEERING-ASSET-6ee9ce19d8b1f530 recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-5923ac86626d7de4. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Application audit on LEGAL-ASSET-988ab05a6aaafddb recorded that a runtime configuration setting was updated. The event references principal-2cc56950de78c750. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Module audit on COMMUNICATIONS-ASSET-e298c38c58f7c346 recorded that a process loaded a library from an application-local directory. The event references principal-dd8d62077451bf1c. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Cloud control audit on PEOPLE-ASSET-12878cc06ce2eeff recorded that resources were created in a region with little prior activity. The event references principal-504d0a8a24feb6ee. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Proxy logs on PROCUREMENT-ASSET-a90cefc8840eb875 recorded that a client transferred a large payload to an external storage endpoint. The event references principal-58357f3106f790fd. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Waf logs on RESEARCH-ASSET-f279330020f0e645 recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-a38184b376034ec2. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Script audit on SALES-ASSET-5accd98a99abf46d recorded that a script interpreter decoded an encoded argument before execution. The event references principal-9d518b079e49f304. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Mail audit on PROCUREMENT-ASSET-57a43dc80cfc93ed recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-40142beb1db7ce4d. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-5a4e4b85caef, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Mfa audit on SUPPORT-ASSET-72ab1273fb4de7e8 recorded that multiple MFA challenges were issued during a short interval. The event references principal-ed28d619781ff3d6. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Database audit on RESEARCH-ASSET-0df9b1ba7848d017 recorded that a session read several tables and exported the query result. The event references principal-78007df53b70739e. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Registry audit on ENGINEERING-ASSET-3288f3a3a57d4d49 recorded that a registry logon-start entry was created. The event references principal-ab71b58d6c6b1b8b. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Application audit on PROCUREMENT-ASSET-4c611d31ce0dab93 recorded that an application read clipboard contents repeatedly. The event references principal-8af1d70f167ed8d6. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Cloud identity audit on SUPPORT-ASSET-7e8f88bce8cfa9fc recorded that a principal received a policy granting additional permissions. The event references principal-02df9042c50f2455. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-3018f02f2280, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Cloud identity audit on PEOPLE-ASSET-120c32cb226f1634 recorded that a new programmatic access key was issued to a principal. The event references principal-1aef76f9cfa1105d. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Kerberos audit on COMMUNICATIONS-ASSET-d9b65f7833a03be8 recorded that an account requested service tickets for multiple services. The event references principal-bce81f4ae551beca. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-ec8531e87d0e match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Flow logs on PEOPLE-ASSET-747d1cebe72c1281 recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-d7e614d288290a88. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-ed1a60c54546 before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Function audit on FINANCE-ASSET-715a47edf7141497 recorded that a serverless function package and execution settings were updated. The event references principal-e1d12cf425ed5c27. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-830680725f89 match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Proxy logs on RESEARCH-ASSET-2d6466dd3f8c1f6b recorded that a client transferred a large payload to an external storage endpoint. The event references principal-136b3bcae45dcdcd. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Resolver logs on PROCUREMENT-ASSET-217f3e17146574de recorded that a client requested many long, high-entropy DNS labels. The event references principal-c25feb34aea9c3bd. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Change CHG-3f7cb3c2d4cd lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Event service audit on SUPPORT-ASSET-2b5c6ab4e8f6f174 recorded that an event log was cleared by a privileged request. The event references principal-2294144a09bcf573. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Identity audit on OPERATIONS-ASSET-0bbb0193ab08eb6e recorded that a service account established an interactive session. The event references principal-de6a7bc5c123923c. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-944217b9a885 match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Cloud identity audit on PROCUREMENT-ASSET-e334c75ea7c7bbae recorded that a new programmatic access key was issued to a principal. The event references principal-754b76246081ca60. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Configuration audit on SUPPORT-ASSET-75f85e5b495f1222 recorded that a client proxy setting was changed. The event references principal-02061922c2bafcd3. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Package registry audit on SUPPORT-ASSET-ad8575a16b60726c recorded that a principal published a new package version. The event references principal-b9b60013a399b75b. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-148b2809a01f explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Application audit on LEGAL-ASSET-2b053903e1a723bb recorded that an application read clipboard contents repeatedly. The event references principal-36dbf50d505a5d2a. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Kubernetes audit on SALES-ASSET-bd821e033a435876 recorded that a cluster admission policy was changed. The event references principal-57ab3d2d3751af5f. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Code integrity audit on PROCUREMENT-ASSET-3f90b9195fa39dc7 recorded that an executable without a publisher signature started from a writable directory. The event references principal-f1b547470e053c8b. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-b54e9f76caef before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Cloud control audit on OPERATIONS-ASSET-31b25a4a2bbf0f7e recorded that resources were created in a region with little prior activity. The event references principal-2043ac1bd7256aa6. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"File audit on LEGAL-ASSET-fdae576414dd7376 recorded that a process deleted many files within a short interval. The event references principal-a6b7ec4e30bafd95. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Process audit on SUPPORT-ASSET-9f8775e0a67ff6e2 recorded that a remote-support application started an interactive session. The event references principal-342d9605d5b86694. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Resolver logs on SUPPORT-ASSET-b02540e08d1a5e1b recorded that a client requested many long, high-entropy DNS labels. The event references principal-ac999136f4795cef. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-937a7f4fefbb explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Kubernetes audit on PEOPLE-ASSET-fb423ebd814658c2 recorded that a role binding granted a principal additional cluster permissions. The event references principal-1e6683e3ee80066c. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Service audit on RESEARCH-ASSET-83637b2bf6e44350 recorded that a new automatically started service was registered. The event references principal-9f4043a1a42fcc90. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"File audit on FINANCE-ASSET-2004b1d4a03fd309 recorded that a process rewrote multiple files into encrypted containers. The event references principal-9560a602e126689a. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Cron audit on COMMUNICATIONS-ASSET-d8fc966dee08cb0c recorded that a recurring job definition was added to the system schedule. The event references principal-703666e706c43b5e. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-682a96c4ad02 specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Storage audit on FINANCE-ASSET-768fdc22d9585f23 recorded that an object-storage access policy was broadened. The event references principal-18ac2fe076b447b0. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Secret manager audit on SALES-ASSET-b73f8978ef6e4f27 recorded that a workload read several secret versions. The event references principal-d6b84c181926e6a9. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Service audit on PROCUREMENT-ASSET-28254d89b1701083 recorded that a remote service-control request created and started a temporary service. The event references principal-cfe7f7b5911dcb16. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Application audit on PROCUREMENT-ASSET-0b973fc190e51fb9 recorded that an application requested repeated screen captures. The event references principal-6d7c52f4e39422b1. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Dns control audit on SALES-ASSET-47a87d0c2fc4257b recorded that an authoritative DNS record was updated. The event references principal-3d712bbcbd3470d6. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Resolver logs on ENGINEERING-ASSET-02301b26ed9cf1c5 recorded that a client requested many long, high-entropy DNS labels. The event references principal-8e3fc22d3aadc906. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Kubernetes audit on SUPPORT-ASSET-ea9a39224859df23 recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-c986eaa5cd9383cb. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-8b69d70a8f85 before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Task scheduler audit on SUPPORT-ASSET-fe6538271f60c593 recorded that a scheduled task was registered to execute a program at logon. The event references principal-a844a2602a6529d6. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Kerberos audit on PROCUREMENT-ASSET-f07f0980cf620efa recorded that an account requested service tickets for multiple services. The event references principal-6dd83c14e2a9dd31. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Systemd audit on OPERATIONS-ASSET-42dd1f251b2cefd5 recorded that a service unit file was changed and the unit reloaded. The event references principal-27edc61f63f1f31a. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Compute audit on OPERATIONS-ASSET-ac6d22bf5640da77 recorded that a principal launched multiple compute instances. The event references principal-dec83605ca771167. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Switch telemetry on LEGAL-ASSET-1643dbdebba2d78d recorded that an address mapping changed repeatedly on a local segment. The event references principal-c39fe907de3611c7. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Compute audit on PEOPLE-ASSET-fe0429fc4ead052f recorded that a principal launched multiple compute instances. The event references principal-4fe369a19d9b5bd1. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-29f2557339e9 accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Ssh audit on SALES-ASSET-95483443a44dd70e recorded that an SSH session opened and requested elevated command execution. The event references principal-ee7405179574875a. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-dd6034ca50d0 accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Network control audit on FINANCE-ASSET-93401772cf68a3aa recorded that a cloud security group gained a broad ingress rule. The event references principal-b7b99f534a1030f4. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Kubernetes audit on RESEARCH-ASSET-ca81e4dea7e4d440 recorded that a workload mounted a directory from its host filesystem. The event references principal-142014dd00377291. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-7ea4c276c605, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Process audit on RESEARCH-ASSET-ff9cda8159f26be2 recorded that a remote-support application started an interactive session. The event references principal-c2840b0826e54ab4. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Cloud control audit on PROCUREMENT-ASSET-bf71ebbd91fab3f3 recorded that a cloud logging destination was disabled. The event references principal-24b082eff9f1c2cb. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-3e4d9b00ae95, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Process audit on ENGINEERING-ASSET-db715ea0863774ba recorded that a remote-support application started an interactive session. The event references principal-ca4d1a946cc4272b. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Flow logs on LEGAL-ASSET-fa7ff1fc0a223203 recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-1ef2548f2594a804. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-a168cec8cc2e specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Runtime audit on PROCUREMENT-ASSET-ef2802409ab5a514 recorded that a process connected to the container runtime socket. The event references principal-81a676edf02534d4. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Runtime audit on LEGAL-ASSET-67b364f8c09b4aef recorded that a process connected to the container runtime socket. The event references principal-a26c56705eacce84. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Certificate audit on ENGINEERING-ASSET-9451d5f5fd9b7794 recorded that a service certificate was replaced. The event references principal-a6fab514c28c1ba9. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Process audit on LEGAL-ASSET-1d30eece58fd02aa recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-73ea530a0de82f6d. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-acca8e606736 accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Certificate audit on PEOPLE-ASSET-4d0259660c317b95 recorded that a service certificate was replaced. The event references principal-f191ea3a323e48f8. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-499c7cd8a4bb before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Switch telemetry on PROCUREMENT-ASSET-c13f623edc6be72c recorded that an address mapping changed repeatedly on a local segment. The event references principal-464589d30bf27aee. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Change CHG-c7d5b498273b lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Saas audit on PROCUREMENT-ASSET-94508e8090c4e3fa recorded that a user requested a bulk export from a business application. The event references principal-d0cfd5ec7d96061d. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Systemd audit on SUPPORT-ASSET-38d3359b892c66ba recorded that a service unit file was changed and the unit reloaded. The event references principal-fbace7ec59135a92. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Identity audit on SUPPORT-ASSET-f9b39e12fc139ef0 recorded that an account registered a new MFA method. The event references principal-3c523bf81b3a031f. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-72007c256889 match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"File access audit on ENGINEERING-ASSET-9bb4a75d3491a9be recorded that a process opened a local credential-store file. The event references principal-f9c37bdee298aeea. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Mfa audit on RESEARCH-ASSET-900be36a816445ab recorded that multiple MFA challenges were issued during a short interval. The event references principal-fdb4d3be95b990c6. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Identity audit on PEOPLE-ASSET-5f5eb7d500371474 recorded that an account registered a new MFA method. The event references principal-7c9584053a66a813. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Application audit on PROCUREMENT-ASSET-0b973fc190e51fb9 recorded that an application requested repeated screen captures. The event references principal-6d7c52f4e39422b1. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Winrm audit on FINANCE-ASSET-f7f3ea9e3a52d83c recorded that a remote management session invoked a command on a managed host. The event references principal-13d8273b51b14066. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-a18264203472, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Identity audit on OPERATIONS-ASSET-0bbb0193ab08eb6e recorded that a service account established an interactive session. The event references principal-de6a7bc5c123923c. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Identity audit on LEGAL-ASSET-10052cae7e6f5c6e recorded that an account password was reset through a recovery workflow. The event references principal-69df9c6ec5ef584b. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Identity audit on FINANCE-ASSET-5eeb4551c8b1c0e3 recorded that an account registered a new MFA method. The event references principal-0a574aaa6eaa69b8. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-a79dfaae3330 match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Account audit on PROCUREMENT-ASSET-6b3dfabb9fc718fa recorded that a local user account was created on a managed system. The event references principal-67628d1182b40e07. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Application audit on PEOPLE-ASSET-16eca898293194f8 recorded that an application read clipboard contents repeatedly. The event references principal-9ece0c292d6cf355. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Compute audit on SUPPORT-ASSET-723f94949265b3d7 recorded that a principal launched multiple compute instances. The event references principal-1d5de0b683f369a9. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Api gateway logs on ENGINEERING-ASSET-51721c37d612a2f5 recorded that a client issued a burst of API requests. The event references principal-b27ef27161423988. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Mfa audit on ENGINEERING-ASSET-4741e70baa0f7c7a recorded that multiple MFA challenges were issued during a short interval. The event references principal-7a266bf7aed055c1. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-c0f4f9da777b before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Ci audit on OPERATIONS-ASSET-3c47f8e04ce54395 recorded that a build pipeline definition gained a new execution step. The event references principal-4e3a0bcc0149b2b6. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Service audit on PROCUREMENT-ASSET-7131a22a8a5e3488 recorded that a new automatically started service was registered. The event references principal-7eed072979ca83fe. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Flow logs on OPERATIONS-ASSET-edf434a71b109006 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-16d324cd052a6682. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Waf logs on SALES-ASSET-8a0f506e8e518bc0 recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-eb2ba7446fb1565a. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Federation audit on SALES-ASSET-88538f554d17e7e6 recorded that a tenant federation setting was updated. The event references principal-caaf0b98849ffd32. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Identity audit on ENGINEERING-ASSET-7b28b0fa9a166d69 recorded that repeated failed sign-ins were recorded for an account. The event references principal-1962d3f4c712b2c7. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-28c79a5e4185, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Storage audit on RESEARCH-ASSET-4fe3f3661fdb65de recorded that a session deleted several storage snapshots. The event references principal-c8575d45e94d3ebb. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Identity audit on ENGINEERING-ASSET-ce4355624d538400 recorded that an account password was reset through a recovery workflow. The event references principal-8d13b23a4098f36d. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Dhcp telemetry on PEOPLE-ASSET-2fdf9f5c1cf8306c recorded that a server issued DHCP offers on a monitored segment. The event references principal-c81573ac45372a70. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Cloud identity audit on COMMUNICATIONS-ASSET-e9dda7a9ac4613e3 recorded that a new programmatic access key was issued to a principal. The event references principal-b50a9e7363974da3. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Firewall audit on PEOPLE-ASSET-957a449c8e927512 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-3d550d011d922017. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Repository audit on LEGAL-ASSET-f07ffc46adc231a4 recorded that a repository collaborator received elevated permissions. The event references principal-d071e326612f692d. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-3a502e5c88ef accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Office audit on FINANCE-ASSET-611546d095704224 recorded that a document macro launched a child interpreter. The event references principal-07f2af237b2ad540. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Kubernetes audit on PROCUREMENT-ASSET-a7191d519031e89b recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-a4246f24c83acd17. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-b8898c3cb949 match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Proxy logs on RESEARCH-ASSET-2d6466dd3f8c1f6b recorded that a client transferred a large payload to an external storage endpoint. The event references principal-136b3bcae45dcdcd. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Cloud control audit on PROCUREMENT-ASSET-1ca061884feb0239 recorded that a session deleted a group of cloud resources. The event references principal-bde2c278c233490d. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Registry audit on PEOPLE-ASSET-493d3bd95ab44b29 recorded that a registry logon-start entry was created. The event references principal-b4c380fe3bd5d692. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Mail flow logs on RESEARCH-ASSET-a506e0d5600d9442 recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-27bdbe6c899d3b5b. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Assessment SEC-973acca4a89b explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Policy audit on OPERATIONS-ASSET-bb5aff052239026f recorded that an audit policy was changed to collect fewer event categories. The event references principal-08ce997b82328b8f. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Session audit on SALES-ASSET-e0e65cd3109e663e recorded that the same session token appeared from different client addresses. The event references principal-b32690205f2a72fc. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Service audit on RESEARCH-ASSET-8d77d8342c20fbff recorded that a remote service-control request created and started a temporary service. The event references principal-211275ad14685644. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Group audit on ENGINEERING-ASSET-d30b74960b951b72 recorded that an account was added to a privileged local group. The event references principal-81526d7aed4e1797. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-d2487e1bf585 covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Kubernetes audit on PEOPLE-ASSET-36a1a728506cc2a7 recorded that a workload mounted a directory from its host filesystem. The event references principal-b1c8c5f8e9de87c2. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Change CHG-2d9f2f87fc6f lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Function audit on RESEARCH-ASSET-82ba6903f0ade88c recorded that a serverless function package and execution settings were updated. The event references principal-07c155fce40b0c1d. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Mail and proxy logs on SALES-ASSET-86e0136e86dcbb64 recorded that a user opened a URL delivered in an email message. The event references principal-090cc1db12274cd7. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-714b765147e2 before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Pki audit on LEGAL-ASSET-06762de597c73d74 recorded that a principal requested a certificate using an authentication template. The event references principal-39b0053611d607fa. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Database audit on LEGAL-ASSET-1c120ddc82665e7a recorded that a session read several tables and exported the query result. The event references principal-4636f85408e4dae9. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Change CHG-07dfdeea5788 lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Wmi audit on PEOPLE-ASSET-0793506618492b13 recorded that a management request started a process through WMI. The event references principal-517018be0d1cff5c. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Mail flow logs on SUPPORT-ASSET-4fe85cf52fa083ac recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-b1c48571a99cb1b2. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Application audit on FINANCE-ASSET-5311585386f59d86 recorded that an application requested repeated screen captures. The event references principal-6f04a55a0eba4c05. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Cloud control audit on FINANCE-ASSET-874d671033c104d1 recorded that a cloud logging destination was disabled. The event references principal-b52f94a7d99dc7bf. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-4f49c59dca50 explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Kubernetes audit on RESEARCH-ASSET-7116d85c35ffeedd recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-5cfd10bdd7720813. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Share audit on SUPPORT-ASSET-642a0478e0fea4be recorded that a new network file share was published. The event references principal-d39d2cce091886dd. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-64d18a32228e, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Process audit on PROCUREMENT-ASSET-3482b66b87c99633 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-a0877a981b03e4e2. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Configuration audit on COMMUNICATIONS-ASSET-6d0a4b6d77bc51b5 recorded that a client proxy setting was changed. The event references principal-096d695d5dfbc71f. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Process access audit on RESEARCH-ASSET-d44095e784b89a49 recorded that a process requested read access to another process memory space. The event references principal-961efc1f116f534c. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Dhcp telemetry on ENGINEERING-ASSET-16a2bd6b5dab3cb6 recorded that a server issued DHCP offers on a monitored segment. The event references principal-d5a61a238fb861fb. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-2a94edc0cc55 explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Cloud control audit on SALES-ASSET-bfb02fef7d44a1a0 recorded that a cloud logging destination was disabled. The event references principal-cabdd3811f019647. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Flow logs on PEOPLE-ASSET-747d1cebe72c1281 recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-d7e614d288290a88. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Office audit on COMMUNICATIONS-ASSET-9792dd26544328c7 recorded that a document macro launched a child interpreter. The event references principal-794c3f6a93ed6b1f. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Change CHG-7b2ecf0c9d20 lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Backup audit on RESEARCH-ASSET-d7ec84ee273e258c recorded that a backup retention policy was shortened. The event references principal-46e3d9bc6deb6418. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-34994969d29e match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Database audit on ENGINEERING-ASSET-2c4914b84c80f08c recorded that a session read several tables and exported the query result. The event references principal-b17a9277af7e3124. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Oauth audit on SALES-ASSET-8a294b7f6b4fb5ec recorded that an application received consent for additional account scopes. The event references principal-4be7952cadd1c600. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-71d5d1aa6033 match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Gateway logs on LEGAL-ASSET-4deff653cf2694f9 recorded that a client established a long-lived encapsulated network session. The event references principal-76329b77e1b0e6b1. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Application audit on RESEARCH-ASSET-11f390ae672643c2 recorded that a runtime configuration setting was updated. The event references principal-1a691de3cb24648f. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Change CHG-5ee027dec439 lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"File audit on PEOPLE-ASSET-2821cb52cece6fb9 recorded that a shell startup profile gained an additional command. The event references principal-6665fccc697a255b. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Compute audit on FINANCE-ASSET-428507c521e75c88 recorded that a principal launched multiple compute instances. The event references principal-a167ad7ce21b7604. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Event service audit on SUPPORT-ASSET-2b5c6ab4e8f6f174 recorded that an event log was cleared by a privileged request. The event references principal-2294144a09bcf573. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-c23c3daa649a explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Backup audit on OPERATIONS-ASSET-b26fa319d3d0ce69 recorded that a backup retention policy was shortened. The event references principal-428102206d771c95. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-840fc1b5aa63 explicitly lists this action, source identity and affected resources. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Compute audit on OPERATIONS-ASSET-ac6d22bf5640da77 recorded that a principal launched multiple compute instances. The event references principal-dec83605ca771167. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-616b0bdb3487 match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Database audit on SUPPORT-ASSET-a2d3ef51f6508fc5 recorded that a session read several tables and exported the query result. The event references principal-fc443d6fe94147f2. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Windows logon audit on ENGINEERING-ASSET-9a2b7e9a3eb1704f recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-d502784167672763. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Flow logs on RESEARCH-ASSET-36f3e51101dc72ca recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-4148cfbbdb30636d. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"File audit on SALES-ASSET-6ae931d0f4c709bb recorded that access permissions were broadened on a directory tree. The event references principal-d574e0d5ffd134ab. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-c81ebe290d96 specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Waf logs on COMMUNICATIONS-ASSET-5ce6d959f09ef085 recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-ded293726939201b. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-3f2f3202741b before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Kubernetes audit on LEGAL-ASSET-3c1eaaf59969b766 recorded that a workload mounted a directory from its host filesystem. The event references principal-a5edc19c7aca724f. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-0859776777a5 accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Cloud identity audit on FINANCE-ASSET-e7ffd7ca6e67a506 recorded that a principal assumed a role in another account. The event references principal-9b4f65d2a19e9629. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Change CHG-91f9474661ef lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Resolver logs on SUPPORT-ASSET-b02540e08d1a5e1b recorded that a client requested many long, high-entropy DNS labels. The event references principal-ac999136f4795cef. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Device and file audit on FINANCE-ASSET-95133e3350d50213 recorded that files were copied to a removable storage device. The event references principal-3a08b3fa9560c2b5. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Cloud control audit on RESEARCH-ASSET-2bdeaeb6bfb8b9b8 recorded that a cloud logging destination was disabled. The event references principal-00477aa276d23b17. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Egress flow logs on OPERATIONS-ASSET-2513c8d77423854c recorded that a workload opened an encrypted connection to an external service. The event references principal-ec2152640ea901f5. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Process audit on OPERATIONS-ASSET-a738dad8c83d20bb recorded that a JavaScript interpreter executed a local script. The event references principal-ba7460ce51b6b106. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Windows logon audit on LEGAL-ASSET-30d47fccd7c65f45 recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-5fc9e45b889f41d1. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Security retest SEC-d47751c6c07f covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Storage access logs on ENGINEERING-ASSET-cfa9edf25dbd11b0 recorded that a principal downloaded many objects from a storage bucket. The event references principal-9a3a0f64a8f2a35d. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Process access audit on RESEARCH-ASSET-d44095e784b89a49 recorded that a process requested read access to another process memory space. The event references principal-961efc1f116f534c. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-fdf8eccffc8a specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Device and file audit on ENGINEERING-ASSET-c9b77c2a506ace86 recorded that files were copied to a removable storage device. The event references principal-7078af09729168a5. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Change CHG-18a2bc10051e lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Browser audit on PEOPLE-ASSET-48ee486909d7e37c recorded that a browser extension with page-reading permissions was installed. The event references principal-0d329542446b1b23. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Task scheduler audit on RESEARCH-ASSET-21bf6f06fdc5117a recorded that a scheduled task was registered to execute a program at logon. The event references principal-0cdfb8ebb9ac46b3. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"File audit on OPERATIONS-ASSET-a77dace88afed479 recorded that a process rewrote multiple files into encrypted containers. The event references principal-9bd0bfba4bc5c80f. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Compute audit on COMMUNICATIONS-ASSET-36b3449238b8f470 recorded that a principal launched multiple compute instances. The event references principal-36e251f09c18691b. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Device and file audit on PEOPLE-ASSET-6b2be688c0738ea2 recorded that files were copied to a removable storage device. The event references principal-cb796dfd2a52dfa6. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Identity audit on COMMUNICATIONS-ASSET-ae1258c834d83e6f recorded that an account password was reset through a recovery workflow. The event references principal-98f97f4d1c43e756. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"File audit on LEGAL-ASSET-b2789a781837a87b recorded that a shell startup profile gained an additional command. The event references principal-d7a3487fce82090e. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-ca7ee9399ebf, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Api gateway logs on PEOPLE-ASSET-010de515bde4832b recorded that a client issued a burst of API requests. The event references principal-828fabb7c52c8ecb. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-fd7dac0ee493 match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Backup audit on SUPPORT-ASSET-cc26a0f722f080c9 recorded that a backup retention policy was shortened. The event references principal-d64cfde7265390a0. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Federation audit on OPERATIONS-ASSET-d2752a593a5fec4b recorded that a tenant federation setting was updated. The event references principal-5f95a2859726a629. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-5226f64d676d covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Process audit on SALES-ASSET-c1342eb6176b4ffa recorded that a Python interpreter loaded a script and contacted a service. The event references principal-e11956d74b8d7b52. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Identity audit on RESEARCH-ASSET-6952971d9edc688b recorded that an account registered a new MFA method. The event references principal-b16ea02f54cbbb97. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-d73815e53359 before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Macos launch audit on PEOPLE-ASSET-f2ccd0993eb11ff9 recorded that a launch agent definition was installed in a user context. The event references principal-ff81666bc8b89437. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Application audit on ENGINEERING-ASSET-0a500e9acaab2792 recorded that an application requested repeated screen captures. The event references principal-f9139e2001fef8f3. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Runtime audit on LEGAL-ASSET-67b364f8c09b4aef recorded that a process connected to the container runtime socket. The event references principal-a26c56705eacce84. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Mfa audit on RESEARCH-ASSET-900be36a816445ab recorded that multiple MFA challenges were issued during a short interval. The event references principal-fdb4d3be95b990c6. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Security retest SEC-24e9e24f3a88 covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Oauth audit on ENGINEERING-ASSET-6abd006369fb2ea6 recorded that an application received consent for additional account scopes. The event references principal-7b515ef2be2fa58b. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Vpn audit on PROCUREMENT-ASSET-af5dcb9896a63a8e recorded that a remote-access VPN session was established. The event references principal-29a685b020122aec. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Repository audit on SUPPORT-ASSET-f2c722947f994337 recorded that a repository collaborator received elevated permissions. The event references principal-81983e01bdfb552d. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Backup audit on FINANCE-ASSET-7d6385ebfb9a8a83 recorded that a backup retention policy was shortened. The event references principal-87f1c31296aed897. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Assessment SEC-b7ad19832eb9 explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"File access audit on OPERATIONS-ASSET-1494559c806dea5d recorded that a process opened a local credential-store file. The event references principal-c4b1fa13e42018fb. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Systemd audit on FINANCE-ASSET-2646ce4052597344 recorded that a service unit file was changed and the unit reloaded. The event references principal-38069415a5ef6919. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Saas audit on LEGAL-ASSET-febb39399ce8713a recorded that a user requested a bulk export from a business application. The event references principal-56038be98666605f. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Share audit on RESEARCH-ASSET-f2c54bce84c236d2 recorded that a new network file share was published. The event references principal-0e202f3a7615eefc. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Storage audit on FINANCE-ASSET-768fdc22d9585f23 recorded that an object-storage access policy was broadened. The event references principal-18ac2fe076b447b0. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-d848b68ab9d0 specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Macos launch audit on COMMUNICATIONS-ASSET-a6af7f5427b7cdc8 recorded that a launch agent definition was installed in a user context. The event references principal-1aeb8103bbf51c1f. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Office audit on PEOPLE-ASSET-d75bb0ba4ef1bfaf recorded that a document macro launched a child interpreter. The event references principal-882202a717331e69. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-c0aeb06e72fd before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Identity audit on SALES-ASSET-17bd921cea441a1f recorded that repeated failed sign-ins were recorded for an account. The event references principal-d02e40aae87e9ff0. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Agent audit on COMMUNICATIONS-ASSET-7f32c685e6e40f0f recorded that a privileged session changed endpoint monitoring settings. The event references principal-ce4504f33247e9eb. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Storage audit on SALES-ASSET-54a03152e889d43f recorded that a session deleted several storage snapshots. The event references principal-69a5261a8cfb5a4d. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Driver audit on LEGAL-ASSET-1d7f06f84da720a0 recorded that a kernel driver was loaded after a package installation. The event references principal-419a1d9d514f9429. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Dns server audit on SUPPORT-ASSET-99242b48e0f1290b recorded that a client requested a DNS zone transfer. The event references principal-c5b7de8a13a46984. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Dns server audit on PROCUREMENT-ASSET-e8eb2bcb15a480a1 recorded that a client requested a DNS zone transfer. The event references principal-937daedbc93fd7dd. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Change CHG-f4366df64a20 lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Identity audit on SUPPORT-ASSET-15695a645557b69f recorded that repeated failed sign-ins were recorded for an account. The event references principal-51d00d36a920ed83. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Script audit on SALES-ASSET-5accd98a99abf46d recorded that a script interpreter decoded an encoded argument before execution. The event references principal-9d518b079e49f304. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Service audit on SALES-ASSET-fffc2b9a7422ce6b recorded that a remote service-control request created and started a temporary service. The event references principal-ab058eda0f6e9097. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-c605f1192ab5, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Storage access logs on RESEARCH-ASSET-59340bda9ea1f273 recorded that a principal downloaded many objects from a storage bucket. The event references principal-516ae6385fac5df9. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-826aca68b239 match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Switch telemetry on RESEARCH-ASSET-39ecead5bf809d8c recorded that an address mapping changed repeatedly on a local segment. The event references principal-78520d727e00f06a. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Change CHG-094ccd9f6535 lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Cron audit on PEOPLE-ASSET-4b3199ab3c63dd2d recorded that a recurring job definition was added to the system schedule. The event references principal-f1110cbb064f6627. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"File audit on RESEARCH-ASSET-08266be3d48a0589 recorded that a process compressed files from several directories into an archive. The event references principal-ba2e548a2cd0e827. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Ci secret audit on SALES-ASSET-ad09caa9a6596785 recorded that a build job requested a protected pipeline secret. The event references principal-5cac9dd38eee5122. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-af8275029cde specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Group audit on PROCUREMENT-ASSET-b50d9791f482d6f4 recorded that an account was added to a privileged local group. The event references principal-c07c3b076842f6c0. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Kerberos audit on LEGAL-ASSET-6ee4a0334d8b0730 recorded that an account requested service tickets for multiple services. The event references principal-2772005981d83d01. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Browser audit on RESEARCH-ASSET-b0be4ff24f6a9c7d recorded that a browser extension with page-reading permissions was installed. The event references principal-c445644ab42572e7. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Mfa audit on SALES-ASSET-413206c0391aae90 recorded that multiple MFA challenges were issued during a short interval. The event references principal-13b992911a08e483. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-95a08f3af89a explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Storage audit on SUPPORT-ASSET-519ebc03fcafbccd recorded that a session deleted several storage snapshots. The event references principal-1671f42126c1c5f8. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Api gateway logs on SALES-ASSET-67b00a7811823c9c recorded that a client issued a burst of API requests. The event references principal-0a02b6edf23f48b5. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-7a59a26bccfd before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Device and file audit on LEGAL-ASSET-e36229f519715f46 recorded that files were copied to a removable storage device. The event references principal-ecac25dd7192fc25. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Gateway logs on FINANCE-ASSET-0eba77ccb6dbdba6 recorded that a client established a long-lived encapsulated network session. The event references principal-5f89b733086ddfa5. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-05abb764fadc before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Process audit on SALES-ASSET-96ce257e2204a8a5 recorded that a remote-support application started an interactive session. The event references principal-ae9cce396ea567fe. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-a496e57ef108 accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Device and file audit on OPERATIONS-ASSET-e188a7d05dfbf7ee recorded that files were copied to a removable storage device. The event references principal-4cd6803b897580b7. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Service audit on ENGINEERING-ASSET-ef233e13b4aa7209 recorded that a new automatically started service was registered. The event references principal-aa6e053019f9dc60. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-d54037b9d5d3 explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Application audit on ENGINEERING-ASSET-c6a3af2b55d88d84 recorded that a runtime configuration setting was updated. The event references principal-67b63805e0368323. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"File audit on ENGINEERING-ASSET-e53845b276f34712 recorded that a process rewrote multiple files into encrypted containers. The event references principal-f651e132a9d111e2. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Gateway logs on PEOPLE-ASSET-755d4ede711826a7 recorded that a client established a long-lived encapsulated network session. The event references principal-3095e007e6941bdd. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"File access audit on SALES-ASSET-da211711ae9c0eb7 recorded that a process opened a local credential-store file. The event references principal-d1b0980809a9edd2. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Process audit on OPERATIONS-ASSET-6a681893d2f34701 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-7a707bcde872789a. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-35f74162e903, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Ssh audit on OPERATIONS-ASSET-324bfe1afe152ff0 recorded that an SSH session opened and requested elevated command execution. The event references principal-db6e14b705505251. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Dhcp telemetry on LEGAL-ASSET-5112544cfce28921 recorded that a server issued DHCP offers on a monitored segment. The event references principal-176187e9b5662d2e. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-88bb7a6fa7e3 match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Cloud identity audit on PEOPLE-ASSET-120c32cb226f1634 recorded that a new programmatic access key was issued to a principal. The event references principal-1aef76f9cfa1105d. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-f7c662d51f9c before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Mfa audit on SALES-ASSET-413206c0391aae90 recorded that multiple MFA challenges were issued during a short interval. The event references principal-13b992911a08e483. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Database audit on LEGAL-ASSET-1c120ddc82665e7a recorded that a session read several tables and exported the query result. The event references principal-4636f85408e4dae9. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Egress flow logs on SUPPORT-ASSET-ff3badb46e903585 recorded that a workload opened an encrypted connection to an external service. The event references principal-ef7dbc8f1e7b6a52. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"File audit on ENGINEERING-ASSET-1a60a1286916ad01 recorded that access permissions were broadened on a directory tree. The event references principal-1a1a48bb1e529fb0. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Dns control audit on OPERATIONS-ASSET-d3932800e26302a2 recorded that an authoritative DNS record was updated. The event references principal-acc181df5bf7ded9. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Storage access logs on RESEARCH-ASSET-59340bda9ea1f273 recorded that a principal downloaded many objects from a storage bucket. The event references principal-516ae6385fac5df9. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Windows logon audit on COMMUNICATIONS-ASSET-6f9244839c2eca95 recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-263d3b9d1be1a7e1. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Change CHG-0c0e042bf95b lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Storage audit on SUPPORT-ASSET-519ebc03fcafbccd recorded that a session deleted several storage snapshots. The event references principal-1671f42126c1c5f8. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Mail flow logs on SUPPORT-ASSET-4fe85cf52fa083ac recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-b1c48571a99cb1b2. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Application audit on SUPPORT-ASSET-0d07ed7bee9ce5d7 recorded that an application requested repeated screen captures. The event references principal-1f37918578f8f184. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-fabb542661b9 specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Mail audit on COMMUNICATIONS-ASSET-dece9873e2e03f6f recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-3d08b8fe271ddda1. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-0daab88dffdd explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Application audit on PROCUREMENT-ASSET-4c611d31ce0dab93 recorded that an application read clipboard contents repeatedly. The event references principal-8af1d70f167ed8d6. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-8d36cdb8d54f accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Mail audit on OPERATIONS-ASSET-3bd074cdd8f9b5e6 recorded that an account received delegated access to a mailbox. The event references principal-81775ab116c002d8. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Identity audit on PROCUREMENT-ASSET-b4ae6e9e4fb445a9 recorded that an account password was reset through a recovery workflow. The event references principal-b2c1bc21d87bb7c1. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-c7e2a0d168d1 accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Dhcp telemetry on OPERATIONS-ASSET-495d89e0df4422f6 recorded that a server issued DHCP offers on a monitored segment. The event references principal-ad2763e8b3d1fe71. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-6e9124f82719 accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Kerberos audit on ENGINEERING-ASSET-ca968191bd4b09c5 recorded that an account requested service tickets for multiple services. The event references principal-48c928131e4a9922. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Change CHG-b238dfd87fa8 lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Dns control audit on SUPPORT-ASSET-daac2768071affbb recorded that an authoritative DNS record was updated. The event references principal-004b930761f504d4. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Repository audit on OPERATIONS-ASSET-2cc6b5c22c3989e5 recorded that a user cloned several source repositories. The event references principal-e45f970cca2e32b9. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-1c1d42344a54 match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Proxy logs on LEGAL-ASSET-11a1797ca70316c7 recorded that a client transferred a large payload to an external storage endpoint. The event references principal-0b83b39a8d8a6fb4. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Identity audit on RESEARCH-ASSET-6952971d9edc688b recorded that an account registered a new MFA method. The event references principal-b16ea02f54cbbb97. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Pki audit on LEGAL-ASSET-06762de597c73d74 recorded that a principal requested a certificate using an authentication template. The event references principal-39b0053611d607fa. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"File audit on OPERATIONS-ASSET-a72fe66e9e140fe9 recorded that a process compressed files from several directories into an archive. The event references principal-41403cc0bff319ee. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Database audit on COMMUNICATIONS-ASSET-4fefa2aaca8d930a recorded that a session changed a database table definition. The event references principal-257c7d24c9971d35. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Code integrity audit on LEGAL-ASSET-f6d743064b804557 recorded that an executable without a publisher signature started from a writable directory. The event references principal-4ea2e2cfcda079aa. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Saas audit on SALES-ASSET-3ad767047dba4a21 recorded that a user requested a bulk export from a business application. The event references principal-b81a4cbeea8a89df. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"File audit on PEOPLE-ASSET-cc74b22d2c2ca8f7 recorded that a process compressed files from several directories into an archive. The event references principal-e9c54c5535050840. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Mfa audit on RESEARCH-ASSET-900be36a816445ab recorded that multiple MFA challenges were issued during a short interval. The event references principal-fdb4d3be95b990c6. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Code integrity audit on COMMUNICATIONS-ASSET-ae65063c9a0dd2a0 recorded that an executable without a publisher signature started from a writable directory. The event references principal-32fc5fcb369ae6d2. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Kerberos audit on COMMUNICATIONS-ASSET-d9b65f7833a03be8 recorded that an account requested service tickets for multiple services. The event references principal-bce81f4ae551beca. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Driver audit on RESEARCH-ASSET-5b972011692602fc recorded that a kernel driver was loaded after a package installation. The event references principal-71a994ae28cc3c7a. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Saas audit on PEOPLE-ASSET-5249110e05a8362d recorded that a user requested a bulk export from a business application. The event references principal-55b28360ed7bad44. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Directory audit on RESEARCH-ASSET-717c1ed36129eee9 recorded that a principal requested directory replication data. The event references principal-71255b0539b4ae1e. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Task scheduler audit on FINANCE-ASSET-ee3bbbf183a6aaf2 recorded that a scheduled task was registered to execute a program at logon. The event references principal-6b358d24fc67440c. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Repository audit on OPERATIONS-ASSET-2cc6b5c22c3989e5 recorded that a user cloned several source repositories. The event references principal-e45f970cca2e32b9. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Mail audit on OPERATIONS-ASSET-3a9ba1a13acae41d recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-458bdf5d7e7a4b20. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Proxy logs on SALES-ASSET-c3dbe91c60733c60 recorded that a client transferred a large payload to an external storage endpoint. The event references principal-fbf3a8a302b7a6c9. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Policy audit on SUPPORT-ASSET-6952fff6cd8e7039 recorded that an audit policy was changed to collect fewer event categories. The event references principal-c6ab36fb929298bf. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Kubernetes audit on PROCUREMENT-ASSET-a846eefa75a51312 recorded that a workload mounted a directory from its host filesystem. The event references principal-0cd6474c03a53052. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Repository audit on LEGAL-ASSET-f07ffc46adc231a4 recorded that a repository collaborator received elevated permissions. The event references principal-d071e326612f692d. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Identity audit on PEOPLE-ASSET-5f5eb7d500371474 recorded that an account registered a new MFA method. The event references principal-7c9584053a66a813. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Device and file audit on PROCUREMENT-ASSET-804fb2eb4bbf7ddf recorded that files were copied to a removable storage device. The event references principal-25d93f161d21c79f. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Compute audit on RESEARCH-ASSET-d341eca93691633b recorded that a principal launched multiple compute instances. The event references principal-cf04d4cb340e6373. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Share audit on ENGINEERING-ASSET-15ac20dc277a74c4 recorded that a new network file share was published. The event references principal-33c52b08167e103b. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Script audit on PEOPLE-ASSET-7674cfc3c8c8d12a recorded that a script interpreter decoded an encoded argument before execution. The event references principal-15233cc20a5664b0. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Federation audit on COMMUNICATIONS-ASSET-866384484e84ef96 recorded that a tenant federation setting was updated. The event references principal-e2dd8e40c0e17294. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Process audit on OPERATIONS-ASSET-6a681893d2f34701 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-7a707bcde872789a. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Account audit on LEGAL-ASSET-00d4a961cd35ae5d recorded that a local user account was created on a managed system. The event references principal-ffacf4516ce71040. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-896193a1dcc8 explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Process audit on FINANCE-ASSET-db3968cef4c0b684 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-a71f596247827755. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Vpn audit on PROCUREMENT-ASSET-af5dcb9896a63a8e recorded that a remote-access VPN session was established. The event references principal-29a685b020122aec. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Application audit on SUPPORT-ASSET-1e6a7efeb4ea574b recorded that a runtime configuration setting was updated. The event references principal-8bffad7489ed2f67. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-7ca040cb4a17 before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Winrm audit on RESEARCH-ASSET-35584f0a53bc209b recorded that a remote management session invoked a command on a managed host. The event references principal-7b703d1f8c94aba9. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Kerberos audit on FINANCE-ASSET-0b0adcb58a633d21 recorded that an account requested service tickets for multiple services. The event references principal-bbbe909c0396acf3. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-82ac9c31262c explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"File audit on COMMUNICATIONS-ASSET-23cdf3c51f4342c4 recorded that access permissions were broadened on a directory tree. The event references principal-fb51510da2f10fbb. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Cloud identity audit on FINANCE-ASSET-b948d8305372c015 recorded that a new programmatic access key was issued to a principal. The event references principal-68bd58abfea31389. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Macos launch audit on SALES-ASSET-9700c4adcf12629e recorded that a launch agent definition was installed in a user context. The event references principal-fd31ea054fd63d39. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"File audit on SUPPORT-ASSET-a93f88cca8d4a8b9 recorded that a process rewrote multiple files into encrypted containers. The event references principal-ae3578564d0163ba. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Backup audit on PEOPLE-ASSET-90b00913ef4755f4 recorded that a backup retention policy was shortened. The event references principal-069c9474003b2644. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Script audit on LEGAL-ASSET-38bacff4f7d252bf recorded that a script interpreter decoded an encoded argument before execution. The event references principal-0e6d8e54a19c536c. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Process audit on FINANCE-ASSET-db3968cef4c0b684 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-a71f596247827755. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Mail and proxy logs on PROCUREMENT-ASSET-f73ebff8c2f46ccc recorded that a user opened a URL delivered in an email message. The event references principal-81190b386823c031. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Configuration audit on SALES-ASSET-9818a0f135cc7c5d recorded that a client proxy setting was changed. The event references principal-50e5e76cf1a92613. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Waf logs on SUPPORT-ASSET-e0ebcdef3dfa8416 recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-3a687906c9bbefbc. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-1aa8b676fee8 accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"File audit on LEGAL-ASSET-fdae576414dd7376 recorded that a process deleted many files within a short interval. The event references principal-a6b7ec4e30bafd95. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-a5a57936dce1 accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Repository audit on LEGAL-ASSET-f07ffc46adc231a4 recorded that a repository collaborator received elevated permissions. The event references principal-d071e326612f692d. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Ci secret audit on FINANCE-ASSET-b6445d71bd651026 recorded that a build job requested a protected pipeline secret. The event references principal-634acd477e34564f. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-070a6600c827 match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Dns server audit on COMMUNICATIONS-ASSET-3ba853c8b87dee93 recorded that a client requested a DNS zone transfer. The event references principal-fbb1839d1793e373. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Cloud identity audit on RESEARCH-ASSET-809fdc9f1154a3c8 recorded that a principal received a policy granting additional permissions. The event references principal-58f2cdd79c2b5788. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Firewall audit on FINANCE-ASSET-d80ee8804a4ec6b6 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-b21644c32449b9a0. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-6eb8e5709a02 accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Agent audit on SUPPORT-ASSET-9325bde68edaa545 recorded that a privileged session changed endpoint monitoring settings. The event references principal-1641f4bad60d9f93. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Mail audit on SUPPORT-ASSET-af2380a8ab001950 recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-d2de6ff979b628f2. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Dns control audit on OPERATIONS-ASSET-d3932800e26302a2 recorded that an authoritative DNS record was updated. The event references principal-acc181df5bf7ded9. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Application audit on FINANCE-ASSET-be2eeaec3ad85eb4 recorded that a runtime configuration setting was updated. The event references principal-1d937b1c297b00f3. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-54dc91c257fc match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Account audit on OPERATIONS-ASSET-ad56fc4183b7ca9d recorded that a local user account was created on a managed system. The event references principal-fe2941e164dbf1c4. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Certificate audit on SUPPORT-ASSET-bf2e59d8cf05d409 recorded that a service certificate was replaced. The event references principal-3f10d0f128334232. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-e71c4559849d specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Saas audit on SUPPORT-ASSET-2e07b9359e958267 recorded that a user requested a bulk export from a business application. The event references principal-b7211075b62be127. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Mail audit on SALES-ASSET-1d2f1acd8ca606b9 recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-eaa00c222951727e. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Smb audit on SUPPORT-ASSET-e1998cccd3abd998 recorded that a session enumerated a file share and read multiple files. The event references principal-3be2aaf5e58c794d. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-c55b3433a235 specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Backup audit on LEGAL-ASSET-0b947a06b2f86efb recorded that a backup retention policy was shortened. The event references principal-ec8805dd5dc564d0. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-878f9c1942c8 accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Database audit on PROCUREMENT-ASSET-88d6e016f81704ea recorded that a session changed a database table definition. The event references principal-a7367e91f7bc0a1d. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Oauth audit on PEOPLE-ASSET-f620f4cfac01530c recorded that an application received consent for additional account scopes. The event references principal-0999bb32ee8823f5. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-da3ec5cac05c, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Policy audit on SALES-ASSET-8b2e5805c0958f81 recorded that an audit policy was changed to collect fewer event categories. The event references principal-55b368edee8e470a. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Wmi audit on PEOPLE-ASSET-0793506618492b13 recorded that a management request started a process through WMI. The event references principal-517018be0d1cff5c. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-9e991ae3e908 specifies this action and identifies the initiating test principal. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Cloud identity audit on LEGAL-ASSET-be33ff15ebf5e263 recorded that a principal assumed a role in another account. The event references principal-a89c01a9848a96c2. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-59e7f99b3808 match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Process audit on PEOPLE-ASSET-2c32b67a1236291b recorded that a remote-support application started an interactive session. The event references principal-3d51474c05227a94. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-9cd07794a880, including the operator and target. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Dns control audit on LEGAL-ASSET-b16c2ea371640162 recorded that an authoritative DNS record was updated. The event references principal-162d081f9776c04e. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Process audit on ENGINEERING-ASSET-b8d24c4e39635b0b recorded that a Python interpreter loaded a script and contacted a service. The event references principal-59e5008660f946a5. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Winrm audit on LEGAL-ASSET-6240747fe412756f recorded that a remote management session invoked a command on a managed host. The event references principal-bff5de31e17ff348. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Firewall audit on LEGAL-ASSET-a8345e2e1a01ff48 recorded that a firewall rule was changed to allow an additional traffic path. The event references principal-74a2c9033c8d23b7. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-4b602817cfdb match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"File audit on COMMUNICATIONS-ASSET-aa99d2f314263fcc recorded that a process compressed files from several directories into an archive. The event references principal-f14ddee6e5692d20. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Storage audit on PEOPLE-ASSET-1ba8659c3031d7f0 recorded that a session deleted several storage snapshots. The event references principal-cf538081eb476d29. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Compute audit on PEOPLE-ASSET-fe0429fc4ead052f recorded that a principal launched multiple compute instances. The event references principal-4fe369a19d9b5bd1. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Dhcp telemetry on PEOPLE-ASSET-2fdf9f5c1cf8306c recorded that a server issued DHCP offers on a monitored segment. The event references principal-c81573ac45372a70. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Assessment SEC-5d13d7e67440 explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Windows logon audit on RESEARCH-ASSET-fcc9667f845ac430 recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-af2356cb5701209c. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"File audit on SALES-ASSET-6ae931d0f4c709bb recorded that access permissions were broadened on a directory tree. The event references principal-d574e0d5ffd134ab. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Cloud control audit on LEGAL-ASSET-428365c6643172ec recorded that a cloud logging destination was disabled. The event references principal-5fcf49df98dad6ed. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Change CHG-01b7b218bcc6 lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Device and file audit on OPERATIONS-ASSET-e188a7d05dfbf7ee recorded that files were copied to a removable storage device. The event references principal-4cd6803b897580b7. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Backup audit on RESEARCH-ASSET-d7ec84ee273e258c recorded that a backup retention policy was shortened. The event references principal-46e3d9bc6deb6418. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"File access audit on SUPPORT-ASSET-701fe361a48ad8d6 recorded that a process opened a local credential-store file. The event references principal-0923914a571f26a3. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Secret manager audit on FINANCE-ASSET-848c4b906d36b1f9 recorded that a workload read several secret versions. The event references principal-2d99961e29099c47. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Compute audit on SUPPORT-ASSET-723f94949265b3d7 recorded that a principal launched multiple compute instances. The event references principal-1d5de0b683f369a9. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Office audit on COMMUNICATIONS-ASSET-9792dd26544328c7 recorded that a document macro launched a child interpreter. The event references principal-794c3f6a93ed6b1f. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Registry audit on LEGAL-ASSET-27fcaf5b02ef0a74 recorded that a registry logon-start entry was created. The event references principal-b668661833835ee3. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Service audit on PROCUREMENT-ASSET-7131a22a8a5e3488 recorded that a new automatically started service was registered. The event references principal-7eed072979ca83fe. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Ci secret audit on PROCUREMENT-ASSET-7ef0c5a6d6fc8733 recorded that a build job requested a protected pipeline secret. The event references principal-77e6930e6b3513f9. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Mail and proxy logs on OPERATIONS-ASSET-7ac4ed112230cbe5 recorded that a user opened a URL delivered in an email message. The event references principal-b1bb74d41be20948. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Waf logs on ENGINEERING-ASSET-155d31939b4a4ab3 recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-a5bfd2692d01cf27. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Egress flow logs on COMMUNICATIONS-ASSET-1fa62ed57f8d2679 recorded that a workload opened an encrypted connection to an external service. The event references principal-297491ec275675d7. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-aa4cec8a7aeb match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Group audit on OPERATIONS-ASSET-0c05abbcb3b78111 recorded that an account was added to a privileged local group. The event references principal-67db77b910dcd61e. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Assessment SEC-b56b322396d3 explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Agent audit on OPERATIONS-ASSET-7f3ae95480df95bb recorded that a privileged session changed endpoint monitoring settings. The event references principal-2ff0c372aa7d7315. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Mail flow logs on OPERATIONS-ASSET-b187da0291cabbc9 recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-3df241ac15d172ff. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Service audit on SALES-ASSET-ee4f4ed67afc3eae recorded that a new automatically started service was registered. The event references principal-ae21c97b6a858bb0. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Gateway logs on LEGAL-ASSET-4deff653cf2694f9 recorded that a client established a long-lived encapsulated network session. The event references principal-76329b77e1b0e6b1. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Task scheduler audit on LEGAL-ASSET-9a82bb1a05cff6a6 recorded that a scheduled task was registered to execute a program at logon. The event references principal-5c02a139758a7988. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Registry audit on PEOPLE-ASSET-493d3bd95ab44b29 recorded that a registry logon-start entry was created. The event references principal-b4c380fe3bd5d692. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-0fd356e7c337 specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Ci secret audit on ENGINEERING-ASSET-2fc72026491758e8 recorded that a build job requested a protected pipeline secret. The event references principal-ef329c66a1330a2f. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Cloud control audit on SUPPORT-ASSET-f20f7641faecc324 recorded that a cloud logging destination was disabled. The event references principal-4d58eb61705c0ae8. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Module audit on PEOPLE-ASSET-4e7e86d1ce25eca1 recorded that a process loaded a library from an application-local directory. The event references principal-32a2611884a3eb03. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Office audit on RESEARCH-ASSET-b8dbacd37bf5b2aa recorded that a document macro launched a child interpreter. The event references principal-fd35021fb1b91014. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Change CHG-09baecef883e lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Kubernetes audit on COMMUNICATIONS-ASSET-789b240d08ec701b recorded that a pod was created with privileged execution enabled. The event references principal-bd54f828538e68ca. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Certificate audit on SALES-ASSET-d2e9e0997da46974 recorded that a service certificate was replaced. The event references principal-0e407d6273aa8758. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Code integrity audit on RESEARCH-ASSET-b23d57d440170815 recorded that an executable without a publisher signature started from a writable directory. The event references principal-a70693803f9dbb50. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Api gateway logs on FINANCE-ASSET-7a64770a61e92e29 recorded that a client issued a burst of API requests. The event references principal-43cf908ee519b246. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Macos launch audit on RESEARCH-ASSET-76ee756c91d53577 recorded that a launch agent definition was installed in a user context. The event references principal-cd202933651b57f9. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Registry audit on LEGAL-ASSET-27fcaf5b02ef0a74 recorded that a registry logon-start entry was created. The event references principal-b668661833835ee3. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Security retest SEC-d33deb835df7 covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"File audit on SALES-ASSET-f998f822d677efcd recorded that a process rewrote multiple files into encrypted containers. The event references principal-354f7ba2d1c31de7. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-f6a9a074fa9b specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Ssh audit on ENGINEERING-ASSET-3a8203b9b7564af2 recorded that an SSH session opened and requested elevated command execution. The event references principal-f927bd6e5e00e3e2. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Service audit on FINANCE-ASSET-d962ba7a33513380 recorded that a new automatically started service was registered. The event references principal-238acc934bc77540. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-a474b67a7281 before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Group audit on RESEARCH-ASSET-0d0aaf2292482822 recorded that an account was added to a privileged local group. The event references principal-5badc7c76a42d4b2. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Process audit on SALES-ASSET-d7499e681a58affc recorded that a JavaScript interpreter executed a local script. The event references principal-ce0d21f659b72ac8. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Registry audit on LEGAL-ASSET-27fcaf5b02ef0a74 recorded that a registry logon-start entry was created. The event references principal-b668661833835ee3. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Change CHG-d33deb835df7 lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Flow logs on PROCUREMENT-ASSET-6efd3fd7c57f6ea6 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-2f79b909f0a96c76. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Application audit on LEGAL-ASSET-2b053903e1a723bb recorded that an application read clipboard contents repeatedly. The event references principal-36dbf50d505a5d2a. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-5371e603b40c, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Policy audit on LEGAL-ASSET-fdcb7612a4f13f67 recorded that an audit policy was changed to collect fewer event categories. The event references principal-3d26eee8b88bfb17. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"File access audit on FINANCE-ASSET-334508df57fe9f23 recorded that a process opened a local credential-store file. The event references principal-0966351ff7c24bff. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Change CHG-8320ed3b260f lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Registry audit on OPERATIONS-ASSET-bb2e321557973238 recorded that a registry logon-start entry was created. The event references principal-48a0f7ab86053bfa. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Cloud control audit on COMMUNICATIONS-ASSET-6f90d32e2d49796b recorded that resources were created in a region with little prior activity. The event references principal-f5034ed11bd41e3e. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Script audit on RESEARCH-ASSET-a67da4eb1517ea03 recorded that a script interpreter decoded an encoded argument before execution. The event references principal-e606a4602bed6561. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Script audit on ENGINEERING-ASSET-e2ddc97a2c3f555e recorded that a script interpreter decoded an encoded argument before execution. The event references principal-f5db620bfae68583. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Service audit on LEGAL-ASSET-c27c6fe8739fc291 recorded that a remote service-control request created and started a temporary service. The event references principal-473978dbe47e2846. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Mail audit on ENGINEERING-ASSET-0ca0b75c929f5305 recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-0a0bb31756158aab. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Kerberos audit on OPERATIONS-ASSET-15b32c4f5f91cc11 recorded that an account requested service tickets for multiple services. The event references principal-86eb3dff1abf1690. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Proxy logs on FINANCE-ASSET-f9b86d6f6b974e8f recorded that a client transferred a large payload to an external storage endpoint. The event references principal-252b9a9159e9be98. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Identity audit on SUPPORT-ASSET-9a791522c1b9c744 recorded that an account password was reset through a recovery workflow. The event references principal-bd3f8b10beb2211f. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Account audit on RESEARCH-ASSET-a444b46456cd6186 recorded that a local user account was created on a managed system. The event references principal-dd1721a44a27272f. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Kubernetes audit on RESEARCH-ASSET-200dc8ad3542be6e recorded that a role binding granted a principal additional cluster permissions. The event references principal-b8023dd958201bec. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Process audit on LEGAL-ASSET-8a212c2ca8ae49ba recorded that a Python interpreter loaded a script and contacted a service. The event references principal-a6319754fd6d1b91. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Process audit on PROCUREMENT-ASSET-3482b66b87c99633 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-a0877a981b03e4e2. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Service audit on FINANCE-ASSET-d962ba7a33513380 recorded that a new automatically started service was registered. The event references principal-238acc934bc77540. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Winrm audit on LEGAL-ASSET-6240747fe412756f recorded that a remote management session invoked a command on a managed host. The event references principal-bff5de31e17ff348. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-480576df7510 before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Task scheduler audit on COMMUNICATIONS-ASSET-3b8f70e54b109a07 recorded that a scheduled task was registered to execute a program at logon. The event references principal-ea7b65d7a85105ed. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Macos launch audit on FINANCE-ASSET-050b0e8279760750 recorded that a launch agent definition was installed in a user context. The event references principal-7354e7b956585560. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Identity audit on RESEARCH-ASSET-855e969e96eb06ea recorded that an account password was reset through a recovery workflow. The event references principal-811400d02da15e41. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Federation audit on ENGINEERING-ASSET-ed48b05a54cba0b4 recorded that a tenant federation setting was updated. The event references principal-7dac1305cd5fd7e7. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Waf logs on PROCUREMENT-ASSET-be57d152ab66f42b recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-c19a63b81ac51b37. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Identity audit on PEOPLE-ASSET-f09717db52bad024 recorded that an account password was reset through a recovery workflow. The event references principal-52a4edbb0422bb75. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-76ddc8db8568 explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Code integrity audit on COMMUNICATIONS-ASSET-ae65063c9a0dd2a0 recorded that an executable without a publisher signature started from a writable directory. The event references principal-32fc5fcb369ae6d2. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Process access audit on PEOPLE-ASSET-e69cbb53fe5c9e6a recorded that a process requested read access to another process memory space. The event references principal-b9eeb1db9d8c686f. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Wmi audit on ENGINEERING-ASSET-9642a3ef1a26edcb recorded that a management request started a process through WMI. The event references principal-4a2b4bdee8c5d199. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Event service audit on OPERATIONS-ASSET-6bb0ff67f6f8dbd2 recorded that an event log was cleared by a privileged request. The event references principal-1c69ef2988f5b8db. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Service audit on SALES-ASSET-fffc2b9a7422ce6b recorded that a remote service-control request created and started a temporary service. The event references principal-ab058eda0f6e9097. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Process audit on SUPPORT-ASSET-9f8775e0a67ff6e2 recorded that a remote-support application started an interactive session. The event references principal-342d9605d5b86694. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-82f02a56cbad match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Wmi audit on FINANCE-ASSET-9fd34fa594551e66 recorded that a management request started a process through WMI. The event references principal-1f38151c7990e366. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Office audit on PROCUREMENT-ASSET-9c9a63eb958fdaa6 recorded that a document macro launched a child interpreter. The event references principal-40d050ba88a97331. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Certificate audit on OPERATIONS-ASSET-3ca9753ca5075c61 recorded that a service certificate was replaced. The event references principal-15f1c60782059a24. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Script audit on SUPPORT-ASSET-1db9fff8dffdd6e2 recorded that a script interpreter decoded an encoded argument before execution. The event references principal-cddc3f00bf167947. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-4e87278bbf8a specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Proxy logs on ENGINEERING-ASSET-55fbfe9ce1b9adb6 recorded that a client transferred a large payload to an external storage endpoint. The event references principal-9db93a1b04a04fcd. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Office audit on FINANCE-ASSET-611546d095704224 recorded that a document macro launched a child interpreter. The event references principal-07f2af237b2ad540. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Api gateway logs on PROCUREMENT-ASSET-1c1b6a1c5f9b9bd8 recorded that a client issued a burst of API requests. The event references principal-257e72e6a629f939. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Security retest SEC-99405fd9183d covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Federation audit on PEOPLE-ASSET-307988f8a71d4999 recorded that a tenant federation setting was updated. The event references principal-c9e7767b005f5591. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Mfa audit on OPERATIONS-ASSET-60e8646a52166a20 recorded that multiple MFA challenges were issued during a short interval. The event references principal-db3cac7564325f27. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Api gateway logs on LEGAL-ASSET-d8cde4dc3ebdd0ca recorded that a client issued a burst of API requests. The event references principal-9252cd194de4e3ac. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Event service audit on SUPPORT-ASSET-2b5c6ab4e8f6f174 recorded that an event log was cleared by a privileged request. The event references principal-2294144a09bcf573. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Configuration audit on SALES-ASSET-9818a0f135cc7c5d recorded that a client proxy setting was changed. The event references principal-50e5e76cf1a92613. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Process audit on PROCUREMENT-ASSET-4c9b1e536ca1f43f recorded that a Python interpreter loaded a script and contacted a service. The event references principal-f1d7ec01883c26bc. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Secret manager audit on LEGAL-ASSET-473919a6141fb4d1 recorded that a workload read several secret versions. The event references principal-be429b8818a2a6bf. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Waf logs on COMMUNICATIONS-ASSET-5ce6d959f09ef085 recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-ded293726939201b. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Process audit on OPERATIONS-ASSET-a738dad8c83d20bb recorded that a JavaScript interpreter executed a local script. The event references principal-ba7460ce51b6b106. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Dns server audit on PEOPLE-ASSET-9dfdc0288f418b98 recorded that a client requested a DNS zone transfer. The event references principal-fb173264d38aac45. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Macos launch audit on ENGINEERING-ASSET-20d414dac3bf58ed recorded that a launch agent definition was installed in a user context. The event references principal-9f713f5b46efadf7. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Ssh audit on RESEARCH-ASSET-a4cfbeae0c987bb8 recorded that an SSH session opened and requested elevated command execution. The event references principal-f224386eb3a1c8ae. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-fb85cb19ed59 accounts for the observed action and its target scope. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Device and file audit on SUPPORT-ASSET-05bbaad00af727ab recorded that files were copied to a removable storage device. The event references principal-dedda897251ae8fc. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Ci secret audit on SUPPORT-ASSET-d5ed18de3905520f recorded that a build job requested a protected pipeline secret. The event references principal-7efbed86c5e71c09. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Group audit on LEGAL-ASSET-c0290e976cae1a6c recorded that an account was added to a privileged local group. The event references principal-0e07ba3cca839e79. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Kubernetes audit on RESEARCH-ASSET-7116d85c35ffeedd recorded that a principal opened a pod exec session and read a namespace Secret. The event references principal-5cfd10bdd7720813. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Oauth audit on PROCUREMENT-ASSET-2f4aab546bd1bb38 recorded that an application received consent for additional account scopes. The event references principal-eef62ccd4ff2398c. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Mail audit on OPERATIONS-ASSET-3bd074cdd8f9b5e6 recorded that an account received delegated access to a mailbox. The event references principal-81775ab116c002d8. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-a01c89f46f72 accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Dns control audit on PROCUREMENT-ASSET-a2a68c2dd932f661 recorded that an authoritative DNS record was updated. The event references principal-d6b239df277e509a. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Api gateway logs on LEGAL-ASSET-d8cde4dc3ebdd0ca recorded that a client issued a burst of API requests. The event references principal-9252cd194de4e3ac. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-57584bb8c3e3 specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Oauth audit on OPERATIONS-ASSET-1d059cb4cf3d2fe1 recorded that an application received consent for additional account scopes. The event references principal-68400bad9534528c. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Windows logon audit on PROCUREMENT-ASSET-6de9173566128253 recorded that a remote desktop session opened with clipboard redirection enabled. The event references principal-1e31ae283e3821b5. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Security retest SEC-fa1d27da50ac covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Mfa audit on OPERATIONS-ASSET-60e8646a52166a20 recorded that multiple MFA challenges were issued during a short interval. The event references principal-db3cac7564325f27. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Storage audit on SALES-ASSET-c45545727c82f95d recorded that an object-storage access policy was broadened. The event references principal-c04c49646b6b61bc. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Flow logs on SALES-ASSET-e03d7f92d970afc6 recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-7f74331f29d46d56. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Mail audit on ENGINEERING-ASSET-0ca0b75c929f5305 recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-0a0bb31756158aab. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Gateway logs on ENGINEERING-ASSET-8864632089fd4c50 recorded that a client established a long-lived encapsulated network session. The event references principal-90ee640b3b5c5162. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-fbc3a2487e5e specifies this action and identifies the initiating test principal. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Process audit on PROCUREMENT-ASSET-3482b66b87c99633 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-a0877a981b03e4e2. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Secret manager audit on COMMUNICATIONS-ASSET-0901e5043739c868 recorded that a workload read several secret versions. The event references principal-811d7f224d798eaf. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Cloud identity audit on PEOPLE-ASSET-f0da82528453fc68 recorded that a principal received a policy granting additional permissions. The event references principal-c5a646fec9c6789b. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-9dd949b65dcf accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Identity audit on OPERATIONS-ASSET-bc3d71283010bd0f recorded that an account password was reset through a recovery workflow. The event references principal-65a355a045f94503. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Storage audit on COMMUNICATIONS-ASSET-80a867850d28c413 recorded that a session deleted several storage snapshots. The event references principal-fab18c6abd30f04e. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Certificate audit on ENGINEERING-ASSET-9451d5f5fd9b7794 recorded that a service certificate was replaced. The event references principal-a6fab514c28c1ba9. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-1c0a5e1f7844 before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Ci audit on FINANCE-ASSET-5cdbdad4be0dcfbd recorded that a build pipeline definition gained a new execution step. The event references principal-248c78edaf5546c1. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Egress flow logs on LEGAL-ASSET-1a606b14eab96fee recorded that a workload opened an encrypted connection to an external service. The event references principal-d6bec1039eca165c. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Process audit on ENGINEERING-ASSET-b8d24c4e39635b0b recorded that a Python interpreter loaded a script and contacted a service. The event references principal-59e5008660f946a5. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Ci secret audit on COMMUNICATIONS-ASSET-d9b1648a2cfcda09 recorded that a build job requested a protected pipeline secret. The event references principal-8fc1bbd9d306c19b. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Service audit on PEOPLE-ASSET-7556bd332c3c0972 recorded that a remote service-control request created and started a temporary service. The event references principal-40ab931ed8bd0b59. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Certificate audit on SUPPORT-ASSET-bf2e59d8cf05d409 recorded that a service certificate was replaced. The event references principal-3f10d0f128334232. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Storage access logs on COMMUNICATIONS-ASSET-560f077b5b32381f recorded that a principal downloaded many objects from a storage bucket. The event references principal-2c20310dc28bca65. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-0243bed32c17 before execution. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Cloud identity audit on OPERATIONS-ASSET-e9ea023dcfe573c8 recorded that a principal assumed a role in another account. The event references principal-33e2cf770673f137. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Macos launch audit on FINANCE-ASSET-050b0e8279760750 recorded that a launch agent definition was installed in a user context. The event references principal-7354e7b956585560. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Storage audit on ENGINEERING-ASSET-cd853382d1a0a281 recorded that a session deleted several storage snapshots. The event references principal-39dd7d8e5cbb8cc6. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Resolver logs on OPERATIONS-ASSET-5135623224ddfa0b recorded that a client requested many long, high-entropy DNS labels. The event references principal-4817944b772fb8eb. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Database audit on PROCUREMENT-ASSET-88d6e016f81704ea recorded that a session changed a database table definition. The event references principal-a7367e91f7bc0a1d. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-27a359cd571e match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Agent audit on FINANCE-ASSET-9e83a9427493fb22 recorded that a privileged session changed endpoint monitoring settings. The event references principal-456dd0970fc81a4c. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Vpn audit on ENGINEERING-ASSET-10805fb79cd039f2 recorded that a remote-access VPN session was established. The event references principal-ee63fc11c18dbead. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Smb audit on COMMUNICATIONS-ASSET-88088ffb8b08e158 recorded that a session enumerated a file share and read multiple files. The event references principal-82b755f6442bfd40. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Mail audit on PROCUREMENT-ASSET-d1aa07096744ffae recorded that an account received delegated access to a mailbox. The event references principal-77fb31a09163908c. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-7606c6b51291 before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Identity audit on ENGINEERING-ASSET-7b28b0fa9a166d69 recorded that repeated failed sign-ins were recorded for an account. The event references principal-1962d3f4c712b2c7. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Systemd audit on ENGINEERING-ASSET-0abbd02cc9ffea8d recorded that a service unit file was changed and the unit reloaded. The event references principal-7986cde737b4fe49. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-60355b36d0c9 match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Kubernetes audit on LEGAL-ASSET-a4bb453a13c05590 recorded that a role binding granted a principal additional cluster permissions. The event references principal-f6d0dcce5ee82a68. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-27b44936fb87, including the operator and target. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Identity audit on RESEARCH-ASSET-6952971d9edc688b recorded that an account registered a new MFA method. The event references principal-b16ea02f54cbbb97. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-d73815e53359 match the action to a scheduled security simulation step. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Application audit on SUPPORT-ASSET-1e6a7efeb4ea574b recorded that a runtime configuration setting was updated. The event references principal-8bffad7489ed2f67. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Detection validation plan SEC-7ca040cb4a17 specifies this action and identifies the initiating test principal. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Dhcp telemetry on LEGAL-ASSET-5112544cfce28921 recorded that a server issued DHCP offers on a monitored segment. The event references principal-176187e9b5662d2e. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Mail and proxy logs on FINANCE-ASSET-75c33a0daf443282 recorded that a user opened a URL delivered in an email message. The event references principal-4da288c1eb5d26af. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Runtime audit on FINANCE-ASSET-f76f44e364cb49d4 recorded that a process connected to the container runtime socket. The event references principal-61088a6af6fdfeb5. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Egress flow logs on RESEARCH-ASSET-33b44f93ed777432 recorded that a workload opened an encrypted connection to an external service. The event references principal-33501a4209ab69ba. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Office audit on SUPPORT-ASSET-b861b71047f83874 recorded that a document macro launched a child interpreter. The event references principal-41f626db101e0b15. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Script audit on COMMUNICATIONS-ASSET-ad52eab51d5bfbe3 recorded that a script interpreter decoded an encoded argument before execution. The event references principal-b20c6bb2ef5361bb. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Runtime audit on PROCUREMENT-ASSET-ef2802409ab5a514 recorded that a process connected to the container runtime socket. The event references principal-81a676edf02534d4. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-d301e9350f4f explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Ci secret audit on SUPPORT-ASSET-d5ed18de3905520f recorded that a build job requested a protected pipeline secret. The event references principal-7efbed86c5e71c09. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Kubernetes audit on SALES-ASSET-0cbf08d6604881c3 recorded that a workload mounted a directory from its host filesystem. The event references principal-df9957e225592b1d. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Vpn audit on COMMUNICATIONS-ASSET-cf88b5e111fdd1c4 recorded that a remote-access VPN session was established. The event references principal-323dccf79a1a961c. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-b91bd47acd0f match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Cloud identity audit on SALES-ASSET-97a28d40051be12b recorded that a principal received a policy granting additional permissions. The event references principal-e45a694b7e0b8b49. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-e8095536bbc5 match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Mail and proxy logs on SALES-ASSET-86e0136e86dcbb64 recorded that a user opened a URL delivered in an email message. The event references principal-090cc1db12274cd7. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Process access audit on OPERATIONS-ASSET-a4047122fa1f8006 recorded that a process requested read access to another process memory space. The event references principal-b6f3ffe23361d9c9. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Dhcp telemetry on SALES-ASSET-b9c8816924ddc5c0 recorded that a server issued DHCP offers on a monitored segment. The event references principal-c2f4772a3b098c6c. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Kubernetes audit on LEGAL-ASSET-a4bb453a13c05590 recorded that a role binding granted a principal additional cluster permissions. The event references principal-f6d0dcce5ee82a68. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Storage audit on SALES-ASSET-c45545727c82f95d recorded that an object-storage access policy was broadened. The event references principal-c04c49646b6b61bc. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Change CHG-d708a75a8c70 lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Process audit on PROCUREMENT-ASSET-121cde9378adb9cf recorded that a JavaScript interpreter executed a local script. The event references principal-1a06985b864403e0. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-43499db7bcdc accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"File access audit on RESEARCH-ASSET-41c0744f3eec824f recorded that a process opened a local credential-store file. The event references principal-22db2b4742c4cf72. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-d314e48c0865, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"File access audit on FINANCE-ASSET-334508df57fe9f23 recorded that a process opened a local credential-store file. The event references principal-0966351ff7c24bff. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"File audit on SUPPORT-ASSET-528c23bdb207b71c recorded that access permissions were broadened on a directory tree. The event references principal-f1bdbe7329a336ab. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"File audit on FINANCE-ASSET-a4971629c23d55d9 recorded that a process compressed files from several directories into an archive. The event references principal-c74fdddea36d843d. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Change CHG-007c0ac6573c lists this action and resource scope; the initiating operator is assigned to that change. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Kerberos audit on SALES-ASSET-7d0683e2088779fa recorded that an account requested service tickets for multiple services. The event references principal-b437865450b6fb0e. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Assessment SEC-05b02c1fb1ed explicitly lists this action, source identity and affected resources. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Ci secret audit on FINANCE-ASSET-b6445d71bd651026 recorded that a build job requested a protected pipeline secret. The event references principal-634acd477e34564f. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Process audit on SALES-ASSET-796c322bf9ce4051 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-eb12aa9934f163d5. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Process audit on LEGAL-ASSET-8a212c2ca8ae49ba recorded that a Python interpreter loaded a script and contacted a service. The event references principal-a6319754fd6d1b91. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-a5caa7ca28c5 before execution. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Group audit on FINANCE-ASSET-df066dc7583c9589 recorded that an account was added to a privileged local group. The event references principal-91bee423e82eb7d5. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Change CHG-04f4444a46f3 lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Cron audit on OPERATIONS-ASSET-837b3c551a9b50e7 recorded that a recurring job definition was added to the system schedule. The event references principal-96fb058b67291144. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Task scheduler audit on LEGAL-ASSET-9a82bb1a05cff6a6 recorded that a scheduled task was registered to execute a program at logon. The event references principal-5c02a139758a7988. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Systemd audit on ENGINEERING-ASSET-0abbd02cc9ffea8d recorded that a service unit file was changed and the unit reloaded. The event references principal-7986cde737b4fe49. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Process audit on COMMUNICATIONS-ASSET-32e7de18e8d35e66 recorded that a Python interpreter loaded a script and contacted a service. The event references principal-2424b5e4e4370c09. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-d769bb21c3af explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Storage audit on SALES-ASSET-c45545727c82f95d recorded that an object-storage access policy was broadened. The event references principal-c04c49646b6b61bc. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Browser audit on FINANCE-ASSET-5beff27234a79da1 recorded that a browser extension with page-reading permissions was installed. The event references principal-f62be1e2c47a255f. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Kubernetes audit on FINANCE-ASSET-e06cf007729f9dbe recorded that a workload mounted a directory from its host filesystem. The event references principal-76bf38f3f96381c7. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Cloud control audit on SUPPORT-ASSET-f20f7641faecc324 recorded that a cloud logging destination was disabled. The event references principal-4d58eb61705c0ae8. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Application audit on COMMUNICATIONS-ASSET-c8d077447f8b8c1d recorded that an application requested repeated screen captures. The event references principal-062e1b2072504f50. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Systemd audit on LEGAL-ASSET-1602066d8a3d5246 recorded that a service unit file was changed and the unit reloaded. The event references principal-cdc1cfc697d46ed4. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"Compute audit on SALES-ASSET-4b3abc50600feeb3 recorded that a principal launched multiple compute instances. The event references principal-a87c3d065d8ee0b1. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Storage audit on SALES-ASSET-c45545727c82f95d recorded that an object-storage access policy was broadened. The event references principal-c04c49646b6b61bc. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Runtime audit on PEOPLE-ASSET-616ef8f8f0889aaf recorded that a process connected to the container runtime socket. The event references principal-685ce977f92924b1. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-10cf20c53ae3 match the action, operator identity and affected resources. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Ci audit on PROCUREMENT-ASSET-51d14292a906982f recorded that a build pipeline definition gained a new execution step. The event references principal-776e5e2e9ad695a2. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-b39295195d3d match the action to a scheduled security simulation step. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Task scheduler audit on SUPPORT-ASSET-fe6538271f60c593 recorded that a scheduled task was registered to execute a program at logon. The event references principal-a844a2602a6529d6. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The workflow owner could not be established and the remaining records do not verify the purpose of the action. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Mail flow logs on LEGAL-ASSET-692e1a748d08a501 recorded that a mailbox sent messages to many recipients in a short interval. The event references principal-527175c687849d2d. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action belongs to a session established during an independently confirmed account takeover. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Kubernetes audit on PROCUREMENT-ASSET-fa28de9adbfdddd4 recorded that a pod was created with privileged execution enabled. The event references principal-c0583fecec986fcd. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Egress flow logs on RESEARCH-ASSET-33b44f93ed777432 recorded that a workload opened an encrypted connection to an external service. The event references principal-33501a4209ab69ba. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Flow logs on OPERATIONS-ASSET-498d986f9a323163 recorded that a source attempted connections to multiple service ports across several hosts. The event references principal-921d661770eeeb14. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Module audit on ENGINEERING-ASSET-ef21d634c2b3a94b recorded that a process loaded a library from an application-local directory. The event references principal-47653e2725b4086f. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-3aae9f772b44 covers the action and the resource owner approved the listed targets. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Database audit on ENGINEERING-ASSET-5b5cb77077baa64c recorded that a session changed a database table definition. The event references principal-6bfe365bf3961695. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Application audit on PROCUREMENT-ASSET-4c611d31ce0dab93 recorded that an application read clipboard contents repeatedly. The event references principal-8af1d70f167ed8d6. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-8d36cdb8d54f match the action, operator identity and affected resources. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Cron audit on PROCUREMENT-ASSET-ccd7b77f6fbe55e6 recorded that a recurring job definition was added to the system schedule. The event references principal-ff6d598ce8d74f2d. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-2d91130bd682 explicitly covers the action and initiating administrator. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Dhcp telemetry on SALES-ASSET-b9c8816924ddc5c0 recorded that a server issued DHCP offers on a monitored segment. The event references principal-c2f4772a3b098c6c. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action matches a recurring business transaction in prior reviewed sessions, including its scope and result. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Mail and proxy logs on COMMUNICATIONS-ASSET-48a9f26bd10054b4 recorded that a user opened a URL delivered in an email message. The event references principal-0e84a6c758769248. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Kubernetes audit on LEGAL-ASSET-3c1eaaf59969b766 recorded that a workload mounted a directory from its host filesystem. The event references principal-a5edc19c7aca724f. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Gateway logs on SALES-ASSET-712c30d2818c912a recorded that a client established a long-lived encapsulated network session. The event references principal-0cbf398f28282f6a. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Certificate audit on RESEARCH-ASSET-a52c58b217e48a75 recorded that a service certificate was replaced. The event references principal-8f17b08464430d9f. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Process audit on FINANCE-ASSET-7c0fff41e30d4380 recorded that a JavaScript interpreter executed a local script. The event references principal-5ba5da6cfca5af4e. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Flow logs on SALES-ASSET-60c136594edf1098 recorded that a source sent ICMP echo requests to a sequence of addresses. The event references principal-a5e562da0b238c72. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Network control audit on OPERATIONS-ASSET-bd217021cb34aa91 recorded that a cloud security group gained a broad ingress rule. The event references principal-2dc6c3bb2730ad8e. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-a3d7f1e5f5ab explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Smb audit on SALES-ASSET-f9e0160f65640ecb recorded that a session enumerated a file share and read multiple files. The event references principal-5b93bfe2ff3ce2df. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Vpn audit on PEOPLE-ASSET-8b15c5e5fc77cfb3 recorded that a remote-access VPN session was established. The event references principal-61e8cff53a9f17ad. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Two context sources disagree about workflow attribution and neither can be independently verified. The retained observable alone cannot separate an ordinary workflow, operational error, test or unauthorised use.","target":"unknown"}
{"text":"File audit on SUPPORT-ASSET-528c23bdb207b71c recorded that access permissions were broadened on a directory tree. The event references principal-f1bdbe7329a336ab. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Process audit on ENGINEERING-ASSET-2b855d0d88712cb8 recorded that a JavaScript interpreter executed a local script. The event references principal-3943e4c085d81398. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"File audit on FINANCE-ASSET-a4971629c23d55d9 recorded that a process compressed files from several directories into an archive. The event references principal-c74fdddea36d843d. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Assessment SEC-007c0ac6573c explicitly lists this action, source identity and affected resources. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Ssh audit on SALES-ASSET-95483443a44dd70e recorded that an SSH session opened and requested elevated command execution. The event references principal-ee7405179574875a. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-dd6034ca50d0, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Process audit on OPERATIONS-ASSET-6a681893d2f34701 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-7a707bcde872789a. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The resource scope differs from the actor’s baseline and the owner cannot identify a matching work request. No independent source confirms compromise, and no verified change or assessment explains the deviation.","target":"suspicious"}
{"text":"Cloud identity audit on SALES-ASSET-6e863cbb874762df recorded that a principal assumed a role in another account. The event references principal-3f1f6f7b104b9c3f. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Process correlation links the action to code that incident responders independently verified was under attacker control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Switch telemetry on OPERATIONS-ASSET-30a277f008dd59f9 recorded that an address mapping changed repeatedly on a local segment. The event references principal-f95a18784ccda07e. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Application traces map the action to a documented product feature used in this team’s daily work. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"Key service audit on COMMUNICATIONS-ASSET-5437588d51522a99 recorded that a principal issued a burst of key-service decrypt requests. The event references principal-f88907eb1e848f20. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-0523046703ba, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Cloud identity audit on SALES-ASSET-6e863cbb874762df recorded that a principal assumed a role in another account. The event references principal-3f1f6f7b104b9c3f. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-a8c53e28dcb9 accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Mail audit on SALES-ASSET-bd6fcb0d83d6d9d8 recorded that an account received delegated access to a mailbox. The event references principal-44c7b65ec7f1b04b. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Exercise records for SEC-c9ed48a00076 match the action to a scheduled security simulation step. The assessment coordinator verified the test identity, prior approval and matching execution window.","target":"authorised_testing"}
{"text":"Process audit on SUPPORT-ASSET-6a54632d13cc3523 recorded that a JavaScript interpreter executed a local script. The event references principal-5989897ff7bc53ab. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. The primary event was retained, but the correlation records needed to connect it to a business or security workflow are missing. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Configuration audit on SALES-ASSET-9818a0f135cc7c5d recorded that a client proxy setting was changed. The event references principal-50e5e76cf1a92613. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The actor describes the action as routine, but the cited workflow does not cover the observed resource scope. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Kerberos audit on COMMUNICATIONS-ASSET-d9b65f7833a03be8 recorded that an account requested service tickets for multiple services. The event references principal-bce81f4ae551beca. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-ec8531e87d0e accounts for the observed action and its target scope. The engagement record and target owner independently verify prior permission, timing and completion within scope.","target":"authorised_testing"}
{"text":"Kubernetes audit on ENGINEERING-ASSET-74d13411d760b9a6 recorded that a role binding granted a principal additional cluster permissions. The event references principal-dbf4764de8118d40. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Change CHG-7dea0ed053b4 lists this action and resource scope; the initiating operator is assigned to that change. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Dns control audit on COMMUNICATIONS-ASSET-9ae5b908b35b63ef recorded that an authoritative DNS record was updated. The event references principal-b17631352023456c. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Identity review has not established account takeover, and downstream evidence remains inconclusive.","target":"suspicious"}
{"text":"Ci secret audit on ENGINEERING-ASSET-2fc72026491758e8 recorded that a build job requested a protected pipeline secret. The event references principal-ef329c66a1330a2f. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The sequence differs from prior sessions and there is no matching explanation in the available workflow records. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Repository audit on FINANCE-ASSET-107bba51318f26e9 recorded that a user cloned several source repositories. The event references principal-f147d2a9dbf7d7a7. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Task scheduler audit on FINANCE-ASSET-ee3bbbf183a6aaf2 recorded that a scheduled task was registered to execute a program at logon. The event references principal-6b358d24fc67440c. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-cdc3be664550, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Storage audit on OPERATIONS-ASSET-29e0421fa3b9bb88 recorded that an object-storage access policy was broadened. The event references principal-e4fd29cc648a5ac6. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Ci secret audit on PROCUREMENT-ASSET-7ef0c5a6d6fc8733 recorded that a build job requested a protected pipeline secret. The event references principal-77e6930e6b3513f9. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Job records account for the action as a recurring business task using its established identity and resources. The application owner confirmed the ordinary workflow and its expected result; no maintenance or security exercise was involved.","target":"benign"}
{"text":"Database audit on LEGAL-ASSET-3632866debb967ca recorded that a session changed a database table definition. The event references principal-862aa2954135f309. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. Peer workflow records corroborate the result and scope, with no unexplained follow-on events or operational error.","target":"benign"}
{"text":"File audit on SALES-ASSET-8fef53d84dc3e73f recorded that a process deleted many files within a short interval. The event references principal-1dec5bfe36cba361. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Access records tie the action to a principal that used recovered credentials without the resource owner’s permission. The affected team confirmed that this specific action had no business, maintenance or assessment approval.","target":"malicious"}
{"text":"Service audit on FINANCE-ASSET-271527485b0e477e recorded that a remote service-control request created and started a temporary service. The event references principal-31971ac078081c89. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Ssh audit on SALES-ASSET-95483443a44dd70e recorded that an SSH session opened and requested elevated command execution. The event references principal-ee7405179574875a. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The initiating client is new for this actor and has not been reconciled with the asset inventory. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Ci secret audit on RESEARCH-ASSET-d46af760b3fcf2d7 recorded that a build job requested a protected pipeline secret. The event references principal-60fe7cbc94a757b5. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Neither the intended workflow nor any unauthorised outcome can be verified from the retained evidence.","target":"unknown"}
{"text":"Wmi audit on RESEARCH-ASSET-ff750cc74100e1ac recorded that a management request started a process through WMI. The event references principal-2a6d4aeffc691fda. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The workflow and authorisation records for this time window expired before review. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Application audit on COMMUNICATIONS-ASSET-349e251c3544c259 recorded that a runtime configuration setting was updated. The event references principal-f484d494a6adf949. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A scheduling setting invoked the wrong workflow; the team reproduced the event with the same setting. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"File audit on PROCUREMENT-ASSET-a3fde179ef5ff962 recorded that access permissions were broadened on a directory tree. The event references principal-bb1784cca8241c87. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Application records match the action to the user’s established business workflow and assigned resource scope. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"File audit on ENGINEERING-ASSET-b0203944931a2946 recorded that a process compressed files from several directories into an archive. The event references principal-c59c85332aba5a32. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Oauth audit on PROCUREMENT-ASSET-2f4aab546bd1bb38 recorded that an application received consent for additional account scopes. The event references principal-eef62ccd4ff2398c. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Storage audit on RESEARCH-ASSET-4fe3f3661fdb65de recorded that a session deleted several storage snapshots. The event references principal-c8575d45e94d3ebb. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The resource owner’s approved operations request CHG-58e3441d3a28 explicitly covers the action and initiating administrator. The change owner independently verified the operator and execution window; the resulting state matches the request.","target":"expected_admin"}
{"text":"Database audit on RESEARCH-ASSET-d8c71a5a44c49e60 recorded that a session changed a database table definition. The event references principal-355812fdc0609439. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Kubernetes audit on SALES-ASSET-0cbf08d6604881c3 recorded that a workload mounted a directory from its host filesystem. The event references principal-df9957e225592b1d. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. Session records link the action to a token that the identity team independently established was stolen. Independent resource audit confirms the action crossed the assigned access scope; the owner rejected it as unauthorised.","target":"malicious"}
{"text":"Dns server audit on FINANCE-ASSET-b5978ac018c6f58c recorded that a client requested a DNS zone transfer. The event references principal-eef8de7d2245f076. Business context: financial reporting and reconciliation. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-73e7d312daff match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Group audit on COMMUNICATIONS-ASSET-c7bad2289a06229c recorded that an account was added to a privileged local group. The event references principal-45633364c2ed091b. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The executed action matches the reviewed maintenance runbook in CHG-11e022798a72, including the operator and target. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Cron audit on SUPPORT-ASSET-0f143a13847207ad recorded that a recurring job definition was added to the system schedule. The event references principal-940a8e24d3cd68aa. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. Deployment records for CHG-3c6fee2a51cc match the action, operator identity and affected resources. Operations audit verified the prior approval, allowed window and successful completion within the requested scope.","target":"expected_admin"}
{"text":"Service audit on OPERATIONS-ASSET-53e47c7270341ae1 recorded that a remote service-control request created and started a temporary service. The event references principal-ae8a8a74a000dff1. Business context: service delivery and infrastructure. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A user request and application receipt account for the action within the user’s ordinary permissions. The resource owner verified the business purpose; correlated records show the expected result without a configuration fault.","target":"benign"}
{"text":"Function audit on SUPPORT-ASSET-639b47faa57b7d52 recorded that a serverless function package and execution settings were updated. The event references principal-142321e2377f77dd. Business context: customer case management. The event occurred during a service recovery period. Environment: Centrally managed services supporting multiple teams. A workflow used an incorrect identity mapping; replay with that mapping reproduced the event. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Account audit on PROCUREMENT-ASSET-6b3dfabb9fc718fa recorded that a local user account was created on a managed system. The event references principal-67628d1182b40e07. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. Change CHG-7771a9778540 lists this action and resource scope; the initiating operator is assigned to that change. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Process audit on ENGINEERING-ASSET-254e39c6de0e65b8 recorded that PowerShell executed a script and opened an HTTPS session. The event references principal-b4a1f0cd4cef32ed. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. A controlled rerun with the corrected configuration produced the intended result and did not reproduce the alert.","target":"misconfiguration"}
{"text":"Mail audit on LEGAL-ASSET-2836d47d3aa0d5af recorded that an account received delegated access to a mailbox. The event references principal-e1699b7a3eeb56fc. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. Operations linked the action to the recovery procedure authorised under CHG-4a9a13f802d8 before execution. The approval predates execution, the timing is inside its window, and the post-change check matches the intended result.","target":"expected_admin"}
{"text":"Storage audit on SALES-ASSET-c45545727c82f95d recorded that an object-storage access policy was broadened. The event references principal-c04c49646b6b61bc. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A collection gap removed the surrounding events needed to determine the action’s purpose and outcome. Review remains unresolved because the available evidence supports more than one explanation.","target":"unknown"}
{"text":"Identity audit on PEOPLE-ASSET-ab714026bdcab67f recorded that repeated failed sign-ins were recorded for an account. The event references principal-b8f5dfca5dbf6b01. Business context: employee services and workforce records. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Module audit on SALES-ASSET-0a5edb66b7d6ecd7 recorded that a process loaded a library from an application-local directory. The event references principal-adbbffe7727b888c. Business context: customer relationship management. The observation window had higher than usual service demand. Environment: Centrally managed services supporting multiple teams. A job configuration selected the wrong resource scope; replaying that configuration reproduced the action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}
{"text":"Waf logs on LEGAL-ASSET-558884e90876ee10 recorded that HTTP requests contained input patterns matching an injection detection rule. The event references principal-3ea85690224829da. Business context: contract and records management. The observation window coincided with quarter-end processing. Environment: Centrally managed services supporting multiple teams. The action traces to a workload for which forensic review established an unauthorised change of control. The resource owner verified that this action was outside the actor’s permission and no test or operations approval covered it.","target":"malicious"}
{"text":"Kubernetes audit on ENGINEERING-ASSET-cad5b32322e2d059 recorded that a pod was created with privileged execution enabled. The event references principal-b5a63a5d1fffe886. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. An incorrect retry setting caused the action to recur; service traces reproduced the same sequence. The owner verified the error and its correction; subsequent executions remained within the intended workflow.","target":"misconfiguration"}
{"text":"Mail audit on ENGINEERING-ASSET-0ca0b75c929f5305 recorded that a mailbox rule was created to forward a subset of incoming messages. The event references principal-0a0bb31756158aab. Business context: product development and integration. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. Security retest SEC-13d969901ffb covers the action and the resource owner approved the listed targets. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"File access audit on COMMUNICATIONS-ASSET-5eb665c77394105b recorded that a process opened a local credential-store file. The event references principal-a9229a1030eb8134. Business context: internal and external communications. The event occurred during the local weekday work period. Environment: Centrally managed services supporting multiple teams. The security team’s validation job SEC-27b06aed4bdc accounts for the observed action and its target scope. The approval predates the event, the action is inside the exercise window, and collection records show no scope overrun.","target":"authorised_testing"}
{"text":"Agent audit on RESEARCH-ASSET-01cc4805ed6fe45d recorded that a privileged session changed endpoint monitoring settings. The event references principal-fb3e99ff7e75f725. Business context: internal research and analysis. The observation window coincided with an application release day. Environment: Centrally managed services supporting multiple teams. The volume and timing differ from the established baseline and the responsible team has not explained the deviation. Available follow-on records do not establish a harmful result or a reproduced configuration fault.","target":"suspicious"}
{"text":"Vpn audit on PROCUREMENT-ASSET-af5dcb9896a63a8e recorded that a remote-access VPN session was established. The event references principal-29a685b020122aec. Business context: supplier and purchasing workflows. The event occurred during a staff shift handover. Environment: Centrally managed services supporting multiple teams. A deployment template supplied an unintended setting; a controlled replay reproduced the observed action. Correcting the setting stopped the condition; follow-up review found no evidence of an unauthorised actor.","target":"misconfiguration"}