Datasets:
| {"text":"File audit telemetry on ASSET-cf3be86beac0dee3 recorded that a shell startup profile gained an additional command. The event references principal-269542d8ca3527cd. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: Retained sources disagree on attribution and the missing source cannot be reconstructed. Available evidence cannot distinguish routine, approved, erroneous and unauthorised causes. The evidence does not support choosing a stronger conclusion.","target":"unknown"} | |
| {"text":"Registry telemetry on ASSET-4938f25ac72b185c recorded that a logon start registry entry was created. The event references principal-fba84b98a4c57ccd. Business context: production platform operations. The event occurred during a routine service period. Evidence: Responder confirmed compromise predates the event and session correlation ties this action to that compromised control path. Access policy and the owner agree that the initiating identity lacked permission for this operation. No approved operations work, normal business process or sanctioned assessment covers it.","target":"malicious"} | |
| {"text":"Session telemetry on ASSET-9c2327f65647fb97 recorded that the same session token appeared from different client addresses. The event references principal-37639d5d3739c11a. Business context: production platform operations. The event occurred during a routine service period. Evidence: This action is justified by assessment scope, not maintenance or a configuration correction. Execution matches the authorised assessment window, test identity and listed targets. The engagement plan identifies the observed action as an in scope assessment step.","target":"authorised_testing"} | |
| {"text":"Identity telemetry on ASSET-c32286d46cf22a77 recorded that a refresh token was used from a new network location. The event references principal-7482392e6af16b70. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: Access policy and the owner agree that the initiating identity lacked permission for this operation. No approved operations work, normal business process or sanctioned assessment covers it. Responder confirmed compromise predates the event and session correlation ties this action to that compromised control path.","target":"malicious"} | |
| {"text":"Registry telemetry on ASSET-0c39025cdd728b7c recorded that a logon start registry entry was created. The event references principal-b445cfc37449d009. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: The action is a clear departure from prior activity for this identity and remains unaccounted for. Investigators verify the anomaly without establishing credential theft or hostile control. No operations change, assessment engagement or reproducible configuration issue explains it.","target":"suspicious"} | |
| {"text":"Authentication telemetry on ASSET-548e4c710d1107ac recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-6fe9774ae0c36a6b. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: Independent telemetry confirms unusual scope and sequence that the responsible team cannot explain. Maintenance, test and settings records provide no verified explanation. The deviation is real, but compromise is not established.","target":"suspicious"} | |
| {"text":"macOS security telemetry on ASSET-bdac430ee3d8f240 recorded that a system extension was loaded. The event references principal-a71c59b5c3e1bdd9. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Review finds no evidence of account compromise or unauthorised control. Correcting the value prevents recurrence while preserving intended workload behaviour. A controlled reproduction generates the same event only when an incorrect configuration value is present.","target":"misconfiguration"} | |
| {"text":"Software management telemetry on ASSET-f2f2d49fc14cce3a recorded that a package was installed on a managed endpoint. The event references principal-81eb77e2008fdfd9. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: Review finds no evidence of account compromise or unauthorised control. A controlled reproduction generates the same event only when an incorrect configuration value is present. Correcting the value prevents recurrence while preserving intended workload behaviour.","target":"misconfiguration"} | |
| {"text":"Session telemetry on ASSET-926cbea91206be7b recorded that the same session token appeared from different client addresses. The event references principal-f1087c5e5eb18984. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: The resource owner and assessment coordinator confirm permission existed beforehand and activity stayed within scope. The controlling record is a security engagement rather than an operations change or ordinary workflow. A preapproved security validation record lists the technique, test identity and affected resource.","target":"authorised_testing"} | |
| {"text":"Endpoint security telemetry on ASSET-7e53d3e4e297766b recorded that an endpoint protection exclusion was created. The event references principal-86e0d09fd796b1f9. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: The deviation is real, but compromise is not established. Independent telemetry confirms unusual scope and sequence that the responsible team cannot explain. Maintenance, test and settings records provide no verified explanation.","target":"suspicious"} | |
| {"text":"Device control telemetry on ASSET-259ab04dcd3e71c8 recorded that a removable storage device was mounted. The event references principal-736440c29d2c2ffc. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: Authorisation comes from operational change control, not an assessment engagement. The maintenance record explicitly covers the action and affected resource. Operations audit independently confirms operator, scope, timing and successful requested state.","target":"expected_admin"} | |
| {"text":"Identity telemetry on ASSET-791a839682be1692 recorded that a refresh token was used from a new network location. The event references principal-d9496fe520292c09. Business context: production platform operations. The event occurred during a routine service period. Evidence: A change control record approved before execution names this operator, target and requested operation. Execution occurs inside the authorised window and verification checks match the planned outcome. This is documented maintenance rather than a security exercise or recurring business workflow.","target":"expected_admin"} | |
| {"text":"Authentication telemetry on ASSET-c2a6c281824dee93 recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-151aed5aab3c16bb. Business context: production platform operations. The event occurred during a routine service period. Evidence: Maintenance, test and settings records provide no verified explanation. The deviation is real, but compromise is not established. Independent telemetry confirms unusual scope and sequence that the responsible team cannot explain.","target":"suspicious"} | |
| {"text":"Authentication telemetry on ASSET-07ae88df5010a363 recorded that a principal requested an unusual number of service tickets. The event references principal-b13a83bf104bbe9d. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: It is not tied to maintenance, a security exercise or a configuration correction. Business system records identify the action as part of a recurring workflow already used by this team. The business owner confirms the purpose and downstream records show the normal result.","target":"benign"} | |
| {"text":"Session telemetry on ASSET-926cbea91206be7b recorded that the same session token appeared from different client addresses. The event references principal-f1087c5e5eb18984. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: A change control record approved before execution names this operator, target and requested operation. Execution occurs inside the authorised window and verification checks match the planned outcome. This is documented maintenance rather than a security exercise or recurring business workflow.","target":"expected_admin"} | |
| {"text":"Authentication telemetry on ASSET-2f156a171e44e4a2 recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-4fcc4eb2ba23ea73. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Engineers isolate an unintended setting and reproduce the action under controlled replay. Attribution records do not support an unauthorised actor as the cause. The corrected configuration produces the intended outcome and the alert does not recur.","target":"misconfiguration"} | |
| {"text":"Endpoint security telemetry on ASSET-e83f6274411aaa6d recorded that an endpoint protection exclusion was created. The event references principal-e6554316398adcdc. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: Key identity and timing evidence is unavailable while remaining records conflict. A reliable disposition cannot be established without missing corroboration. Both authorised and unauthorised explanations remain plausible from the surviving material.","target":"unknown"} | |
| {"text":"Authentication telemetry on ASSET-07ae88df5010a363 recorded that a principal requested an unusual number of service tickets. The event references principal-b13a83bf104bbe9d. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: Available evidence cannot distinguish routine, approved, erroneous and unauthorised causes. Retained sources disagree on attribution and the missing source cannot be reconstructed. The evidence does not support choosing a stronger conclusion.","target":"unknown"} | |
| {"text":"Device control telemetry on ASSET-259ab04dcd3e71c8 recorded that a removable storage device was mounted. The event references principal-736440c29d2c2ffc. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: Responder confirmed compromise predates the event and session correlation ties this action to that compromised control path. Access policy and the owner agree that the initiating identity lacked permission for this operation. No approved operations work, normal business process or sanctioned assessment covers it.","target":"malicious"} | |
| {"text":"Endpoint security telemetry on ASSET-0b357e20610a5fb7 recorded that an endpoint protection exclusion was created. The event references principal-e1bbd626857b07af. Business context: production platform operations. The event occurred during a routine service period. Evidence: Both authorised and unauthorised explanations remain plausible from the surviving material. Key identity and timing evidence is unavailable while remaining records conflict. A reliable disposition cannot be established without missing corroboration.","target":"unknown"} | |
| {"text":"Software management telemetry on ASSET-946283b501ad60f2 recorded that a package was installed on a managed endpoint. The event references principal-3a055ab31c161145. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: The engagement plan identifies the observed action as an in scope assessment step. Execution matches the authorised assessment window, test identity and listed targets. This action is justified by assessment scope, not maintenance or a configuration correction.","target":"authorised_testing"} | |
| {"text":"Identity telemetry on ASSET-c9e5007dceb66f51 recorded that a refresh token was used from a new network location. The event references principal-23fb944802ed7c95. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: Engineers isolate an unintended setting and reproduce the action under controlled replay. Attribution records do not support an unauthorised actor as the cause. The corrected configuration produces the intended outcome and the alert does not recur.","target":"misconfiguration"} | |
| {"text":"Device control telemetry on ASSET-10321812fb8412ae recorded that a removable storage device was mounted. The event references principal-5642e2e1a1479b48. Business context: production platform operations. The event occurred during a routine service period. Evidence: No approved operations work, normal business process or sanctioned assessment covers it. Access policy and the owner agree that the initiating identity lacked permission for this operation. Responder confirmed compromise predates the event and session correlation ties this action to that compromised control path.","target":"malicious"} | |
| {"text":"Device control telemetry on ASSET-af254892f4cef978 recorded that a removable storage device was mounted. The event references principal-c8f4d8895c66119b. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: Independent telemetry confirms unusual scope and sequence that the responsible team cannot explain. Maintenance, test and settings records provide no verified explanation. The deviation is real, but compromise is not established.","target":"suspicious"} | |
| {"text":"Device control telemetry on ASSET-af254892f4cef978 recorded that a removable storage device was mounted. The event references principal-c8f4d8895c66119b. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: A forensic timeline traces this action to a token conclusively recovered from an intruder controlled session. Neither change control nor security assessment records provide authorisation. The owner confirms the operation exceeded authorised resource scope.","target":"malicious"} | |
| {"text":"Device control telemetry on ASSET-7df9d0278b9bd4a7 recorded that a removable storage device was mounted. The event references principal-9a4767494da5d5a5. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: Key identity and timing evidence is unavailable while remaining records conflict. Both authorised and unauthorised explanations remain plausible from the surviving material. A reliable disposition cannot be established without missing corroboration.","target":"unknown"} | |
| {"text":"Registry telemetry on ASSET-87f634c5db0bf0a4 recorded that a logon start registry entry was created. The event references principal-b4878bc054d3d019. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: It is not tied to maintenance, a security exercise or a configuration correction. The business owner confirms the purpose and downstream records show the normal result. Business system records identify the action as part of a recurring workflow already used by this team.","target":"benign"} | |
| {"text":"Registry telemetry on ASSET-4938f25ac72b185c recorded that a logon start registry entry was created. The event references principal-fba84b98a4c57ccd. Business context: production platform operations. The event occurred during a routine service period. Evidence: Maintenance, test and settings records provide no verified explanation. Independent telemetry confirms unusual scope and sequence that the responsible team cannot explain. The deviation is real, but compromise is not established.","target":"suspicious"} | |
| {"text":"Endpoint security telemetry on ASSET-0b357e20610a5fb7 recorded that an endpoint protection exclusion was created. The event references principal-e1bbd626857b07af. Business context: production platform operations. The event occurred during a routine service period. Evidence: It is not tied to maintenance, a security exercise or a configuration correction. The business owner confirms the purpose and downstream records show the normal result. Business system records identify the action as part of a recurring workflow already used by this team.","target":"benign"} | |
| {"text":"File audit telemetry on ASSET-244b3eddb26e9638 recorded that a shell startup profile gained an additional command. The event references principal-0f3323543c67b8a9. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: It is not tied to maintenance, a security exercise or a configuration correction. The business owner confirms the purpose and downstream records show the normal result. Business system records identify the action as part of a recurring workflow already used by this team.","target":"benign"} | |
| {"text":"File audit telemetry on ASSET-92d7a4b0f0832bdb recorded that a shell startup profile gained an additional command. The event references principal-416cb22cec72515c. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: The engagement plan identifies the observed action as an in scope assessment step. Execution matches the authorised assessment window, test identity and listed targets. This action is justified by assessment scope, not maintenance or a configuration correction.","target":"authorised_testing"} | |
| {"text":"Endpoint security telemetry on ASSET-e83f6274411aaa6d recorded that an endpoint protection exclusion was created. The event references principal-e6554316398adcdc. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: The maintenance record explicitly covers the action and affected resource. Authorisation comes from operational change control, not an assessment engagement. Operations audit independently confirms operator, scope, timing and successful requested state.","target":"expected_admin"} | |
| {"text":"Device control telemetry on ASSET-ebb2be94ec626240 recorded that a removable storage device was mounted. The event references principal-f26b6fc008fdefc3. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Business system records identify the action as part of a recurring workflow already used by this team. It is not tied to maintenance, a security exercise or a configuration correction. The business owner confirms the purpose and downstream records show the normal result.","target":"benign"} | |
| {"text":"Authentication telemetry on ASSET-2f156a171e44e4a2 recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-4fcc4eb2ba23ea73. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Neither change control nor security assessment records provide authorisation. A forensic timeline traces this action to a token conclusively recovered from an intruder controlled session. The owner confirms the operation exceeded authorised resource scope.","target":"malicious"} | |
| {"text":"Software management telemetry on ASSET-f2f2d49fc14cce3a recorded that a package was installed on a managed endpoint. The event references principal-81eb77e2008fdfd9. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: This action is justified by assessment scope, not maintenance or a configuration correction. Execution matches the authorised assessment window, test identity and listed targets. The engagement plan identifies the observed action as an in scope assessment step.","target":"authorised_testing"} | |
| {"text":"Authentication telemetry on ASSET-6db2c84b2223d2a6 recorded that a principal requested an unusual number of service tickets. The event references principal-2d3de75c1517cbb8. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: No administrator change, test engagement or settings fault is required to explain it. The event aligns with the established application process, normal identity and expected resource scope. Independent workflow records corroborate ordinary use and expected completion.","target":"benign"} | |
| {"text":"File audit telemetry on ASSET-92d7a4b0f0832bdb recorded that a shell startup profile gained an additional command. The event references principal-416cb22cec72515c. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: Business system records identify the action as part of a recurring workflow already used by this team. It is not tied to maintenance, a security exercise or a configuration correction. The business owner confirms the purpose and downstream records show the normal result.","target":"benign"} | |
| {"text":"Registry telemetry on ASSET-1e7cb34006b816e1 recorded that a logon start registry entry was created. The event references principal-030b4d8a5377e36c. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: No administrator change, test engagement or settings fault is required to explain it. Independent workflow records corroborate ordinary use and expected completion. The event aligns with the established application process, normal identity and expected resource scope.","target":"benign"} | |
| {"text":"Device control telemetry on ASSET-6c043b46458f7c8a recorded that a removable storage device was mounted. The event references principal-c5abfb1e9d8d9902. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: The engagement plan identifies the observed action as an in scope assessment step. This action is justified by assessment scope, not maintenance or a configuration correction. Execution matches the authorised assessment window, test identity and listed targets.","target":"authorised_testing"} | |
| {"text":"Authentication telemetry on ASSET-c872ba5f50ae32d6 recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-633558f364d854e1. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: Review finds no evidence of account compromise or unauthorised control. Correcting the value prevents recurrence while preserving intended workload behaviour. A controlled reproduction generates the same event only when an incorrect configuration value is present.","target":"misconfiguration"} | |
| {"text":"Authentication telemetry on ASSET-8cf90cff1a6cb992 recorded that a principal requested an unusual number of service tickets. The event references principal-771b0d2efb9a5186. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: Correcting the value prevents recurrence while preserving intended workload behaviour. Review finds no evidence of account compromise or unauthorised control. A controlled reproduction generates the same event only when an incorrect configuration value is present.","target":"misconfiguration"} | |
| {"text":"Endpoint security telemetry on ASSET-75ff6bb05605e6fb recorded that an endpoint protection exclusion was created. The event references principal-76e700dc719d3b69. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: The action is a clear departure from prior activity for this identity and remains unaccounted for. Investigators verify the anomaly without establishing credential theft or hostile control. No operations change, assessment engagement or reproducible configuration issue explains it.","target":"suspicious"} | |
| {"text":"Authentication telemetry on ASSET-a15a854111323f76 recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-cb2a201458ef6079. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: No approved operations work, normal business process or sanctioned assessment covers it. Access policy and the owner agree that the initiating identity lacked permission for this operation. Responder confirmed compromise predates the event and session correlation ties this action to that compromised control path.","target":"malicious"} | |
| {"text":"Authentication telemetry on ASSET-5e68633aa4272d07 recorded that a principal requested an unusual number of service tickets. The event references principal-a3a1c3419e57c2b9. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Maintenance, test and settings records provide no verified explanation. The deviation is real, but compromise is not established. Independent telemetry confirms unusual scope and sequence that the responsible team cannot explain.","target":"suspicious"} | |
| {"text":"Authentication telemetry on ASSET-c872ba5f50ae32d6 recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-633558f364d854e1. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: Execution occurs inside the authorised window and verification checks match the planned outcome. This is documented maintenance rather than a security exercise or recurring business workflow. A change control record approved before execution names this operator, target and requested operation.","target":"expected_admin"} | |
| {"text":"File audit telemetry on ASSET-244b3eddb26e9638 recorded that a shell startup profile gained an additional command. The event references principal-0f3323543c67b8a9. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: Execution occurs inside the authorised window and verification checks match the planned outcome. This is documented maintenance rather than a security exercise or recurring business workflow. A change control record approved before execution names this operator, target and requested operation.","target":"expected_admin"} | |
| {"text":"Authentication telemetry on ASSET-548e4c710d1107ac recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-6fe9774ae0c36a6b. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: Engineers isolate an unintended setting and reproduce the action under controlled replay. The corrected configuration produces the intended outcome and the alert does not recur. Attribution records do not support an unauthorised actor as the cause.","target":"misconfiguration"} | |
| {"text":"Endpoint security telemetry on ASSET-7e53d3e4e297766b recorded that an endpoint protection exclusion was created. The event references principal-86e0d09fd796b1f9. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: The resource owner and assessment coordinator confirm permission existed beforehand and activity stayed within scope. The controlling record is a security engagement rather than an operations change or ordinary workflow. A preapproved security validation record lists the technique, test identity and affected resource.","target":"authorised_testing"} | |
| {"text":"File audit telemetry on ASSET-cf3be86beac0dee3 recorded that a shell startup profile gained an additional command. The event references principal-269542d8ca3527cd. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: This action is justified by assessment scope, not maintenance or a configuration correction. Execution matches the authorised assessment window, test identity and listed targets. The engagement plan identifies the observed action as an in scope assessment step.","target":"authorised_testing"} | |
| {"text":"Software management telemetry on ASSET-06e87c8ba3d49d7f recorded that a package was installed on a managed endpoint. The event references principal-0e15aa0fe26d14ba. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: Key identity and timing evidence is unavailable while remaining records conflict. Both authorised and unauthorised explanations remain plausible from the surviving material. A reliable disposition cannot be established without missing corroboration.","target":"unknown"} | |
| {"text":"Authentication telemetry on ASSET-384932eeebedeb57 recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-e0b285e79e60c451. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: Retained sources disagree on attribution and the missing source cannot be reconstructed. The evidence does not support choosing a stronger conclusion. Available evidence cannot distinguish routine, approved, erroneous and unauthorised causes.","target":"unknown"} | |
| {"text":"Registry telemetry on ASSET-1e7cb34006b816e1 recorded that a logon start registry entry was created. The event references principal-030b4d8a5377e36c. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: This action is justified by assessment scope, not maintenance or a configuration correction. The engagement plan identifies the observed action as an in scope assessment step. Execution matches the authorised assessment window, test identity and listed targets.","target":"authorised_testing"} | |
| {"text":"Session telemetry on ASSET-b1230d6c50948f68 recorded that the same session token appeared from different client addresses. The event references principal-4a757c51da729678. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: The owner confirms the operation exceeded authorised resource scope. A forensic timeline traces this action to a token conclusively recovered from an intruder controlled session. Neither change control nor security assessment records provide authorisation.","target":"malicious"} | |
| {"text":"Authentication telemetry on ASSET-f1b4768b1ee1bd7b recorded that a principal requested an unusual number of service tickets. The event references principal-2d35dcb74491ee63. Business context: production platform operations. The event occurred during a routine service period. Evidence: Authorisation comes from operational change control, not an assessment engagement. Operations audit independently confirms operator, scope, timing and successful requested state. The maintenance record explicitly covers the action and affected resource.","target":"expected_admin"} | |
| {"text":"Software management telemetry on ASSET-946283b501ad60f2 recorded that a package was installed on a managed endpoint. The event references principal-3a055ab31c161145. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: Available evidence cannot distinguish routine, approved, erroneous and unauthorised causes. Retained sources disagree on attribution and the missing source cannot be reconstructed. The evidence does not support choosing a stronger conclusion.","target":"unknown"} | |
| {"text":"Authentication telemetry on ASSET-548e4c710d1107ac recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-6fe9774ae0c36a6b. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: This is documented maintenance rather than a security exercise or recurring business workflow. A change control record approved before execution names this operator, target and requested operation. Execution occurs inside the authorised window and verification checks match the planned outcome.","target":"expected_admin"} | |
| {"text":"Registry telemetry on ASSET-0c39025cdd728b7c recorded that a logon start registry entry was created. The event references principal-b445cfc37449d009. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: The controlling record is a security engagement rather than an operations change or ordinary workflow. The resource owner and assessment coordinator confirm permission existed beforehand and activity stayed within scope. A preapproved security validation record lists the technique, test identity and affected resource.","target":"authorised_testing"} | |
| {"text":"macOS security telemetry on ASSET-49e92eb9ee86195a recorded that a system extension was loaded. The event references principal-2cead65e8d2af689. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: The owner confirms the operation exceeded authorised resource scope. Neither change control nor security assessment records provide authorisation. A forensic timeline traces this action to a token conclusively recovered from an intruder controlled session.","target":"malicious"} | |
| {"text":"Software management telemetry on ASSET-06e87c8ba3d49d7f recorded that a package was installed on a managed endpoint. The event references principal-0e15aa0fe26d14ba. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: The resource owner and assessment coordinator confirm permission existed beforehand and activity stayed within scope. A preapproved security validation record lists the technique, test identity and affected resource. The controlling record is a security engagement rather than an operations change or ordinary workflow.","target":"authorised_testing"} | |
| {"text":"Identity telemetry on ASSET-1a0546d031ade59d recorded that a refresh token was used from a new network location. The event references principal-9b0ea911c4279184. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: The action is a clear departure from prior activity for this identity and remains unaccounted for. No operations change, assessment engagement or reproducible configuration issue explains it. Investigators verify the anomaly without establishing credential theft or hostile control.","target":"suspicious"} | |
| {"text":"Software management telemetry on ASSET-ea03e3935a4440a1 recorded that a package was installed on a managed endpoint. The event references principal-4576ae7a9839e853. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Retained sources disagree on attribution and the missing source cannot be reconstructed. Available evidence cannot distinguish routine, approved, erroneous and unauthorised causes. The evidence does not support choosing a stronger conclusion.","target":"unknown"} | |
| {"text":"Endpoint security telemetry on ASSET-160e6026e1614ce4 recorded that an endpoint protection exclusion was created. The event references principal-a5a9164c0612b141. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: Independent telemetry confirms unusual scope and sequence that the responsible team cannot explain. The deviation is real, but compromise is not established. Maintenance, test and settings records provide no verified explanation.","target":"suspicious"} | |
| {"text":"Registry telemetry on ASSET-12375d2acdd5c83c recorded that a logon start registry entry was created. The event references principal-82275ea6f7900f1a. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: Investigators verify the anomaly without establishing credential theft or hostile control. No operations change, assessment engagement or reproducible configuration issue explains it. The action is a clear departure from prior activity for this identity and remains unaccounted for.","target":"suspicious"} | |
| {"text":"Registry telemetry on ASSET-181916903bb96a17 recorded that a logon start registry entry was created. The event references principal-53c6c1059b4ce6f8. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: The action is a clear departure from prior activity for this identity and remains unaccounted for. No operations change, assessment engagement or reproducible configuration issue explains it. Investigators verify the anomaly without establishing credential theft or hostile control.","target":"suspicious"} | |
| {"text":"Device control telemetry on ASSET-ebb2be94ec626240 recorded that a removable storage device was mounted. The event references principal-f26b6fc008fdefc3. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Operations audit independently confirms operator, scope, timing and successful requested state. The maintenance record explicitly covers the action and affected resource. Authorisation comes from operational change control, not an assessment engagement.","target":"expected_admin"} | |
| {"text":"Software management telemetry on ASSET-ea03e3935a4440a1 recorded that a package was installed on a managed endpoint. The event references principal-4576ae7a9839e853. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: This action is justified by assessment scope, not maintenance or a configuration correction. The engagement plan identifies the observed action as an in scope assessment step. Execution matches the authorised assessment window, test identity and listed targets.","target":"authorised_testing"} | |
| {"text":"Session telemetry on ASSET-84339bd64baee543 recorded that the same session token appeared from different client addresses. The event references principal-fbe0cdae58b1cae5. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: This action is justified by assessment scope, not maintenance or a configuration correction. The engagement plan identifies the observed action as an in scope assessment step. Execution matches the authorised assessment window, test identity and listed targets.","target":"authorised_testing"} | |
| {"text":"Software management telemetry on ASSET-ea03e3935a4440a1 recorded that a package was installed on a managed endpoint. The event references principal-4576ae7a9839e853. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Maintenance, test and settings records provide no verified explanation. Independent telemetry confirms unusual scope and sequence that the responsible team cannot explain. The deviation is real, but compromise is not established.","target":"suspicious"} | |
| {"text":"Authentication telemetry on ASSET-5e68633aa4272d07 recorded that a principal requested an unusual number of service tickets. The event references principal-a3a1c3419e57c2b9. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Neither change control nor security assessment records provide authorisation. A forensic timeline traces this action to a token conclusively recovered from an intruder controlled session. The owner confirms the operation exceeded authorised resource scope.","target":"malicious"} | |
| {"text":"File audit telemetry on ASSET-7f9c55b3dbd9e2db recorded that a shell startup profile gained an additional command. The event references principal-59b6261d348cafc2. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: Authorisation comes from operational change control, not an assessment engagement. The maintenance record explicitly covers the action and affected resource. Operations audit independently confirms operator, scope, timing and successful requested state.","target":"expected_admin"} | |
| {"text":"Authentication telemetry on ASSET-6db2c84b2223d2a6 recorded that a principal requested an unusual number of service tickets. The event references principal-2d3de75c1517cbb8. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: A change control record approved before execution names this operator, target and requested operation. Execution occurs inside the authorised window and verification checks match the planned outcome. This is documented maintenance rather than a security exercise or recurring business workflow.","target":"expected_admin"} | |
| {"text":"macOS security telemetry on ASSET-daf3ffb9d8aa9b1d recorded that a system extension was loaded. The event references principal-2663849fde66787e. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: No administrator change, test engagement or settings fault is required to explain it. The event aligns with the established application process, normal identity and expected resource scope. Independent workflow records corroborate ordinary use and expected completion.","target":"benign"} | |
| {"text":"Authentication telemetry on ASSET-07ae88df5010a363 recorded that a principal requested an unusual number of service tickets. The event references principal-b13a83bf104bbe9d. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: Neither change control nor security assessment records provide authorisation. A forensic timeline traces this action to a token conclusively recovered from an intruder controlled session. The owner confirms the operation exceeded authorised resource scope.","target":"malicious"} | |
| {"text":"Endpoint security telemetry on ASSET-75ff6bb05605e6fb recorded that an endpoint protection exclusion was created. The event references principal-76e700dc719d3b69. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: Execution matches the authorised assessment window, test identity and listed targets. This action is justified by assessment scope, not maintenance or a configuration correction. The engagement plan identifies the observed action as an in scope assessment step.","target":"authorised_testing"} | |
| {"text":"Software management telemetry on ASSET-32df6ce14eab6663 recorded that a package was installed on a managed endpoint. The event references principal-23ffd379ff47e0ee. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: The deviation is real, but compromise is not established. Maintenance, test and settings records provide no verified explanation. Independent telemetry confirms unusual scope and sequence that the responsible team cannot explain.","target":"suspicious"} | |
| {"text":"Authentication telemetry on ASSET-c872ba5f50ae32d6 recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-633558f364d854e1. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: Key identity and timing evidence is unavailable while remaining records conflict. Both authorised and unauthorised explanations remain plausible from the surviving material. A reliable disposition cannot be established without missing corroboration.","target":"unknown"} | |
| {"text":"Endpoint security telemetry on ASSET-7e53d3e4e297766b recorded that an endpoint protection exclusion was created. The event references principal-86e0d09fd796b1f9. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Operations audit independently confirms operator, scope, timing and successful requested state. The maintenance record explicitly covers the action and affected resource. Authorisation comes from operational change control, not an assessment engagement.","target":"expected_admin"} | |
| {"text":"macOS security telemetry on ASSET-bdac430ee3d8f240 recorded that a system extension was loaded. The event references principal-a71c59b5c3e1bdd9. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Access policy and the owner agree that the initiating identity lacked permission for this operation. Responder confirmed compromise predates the event and session correlation ties this action to that compromised control path. No approved operations work, normal business process or sanctioned assessment covers it.","target":"malicious"} | |
| {"text":"Authentication telemetry on ASSET-548e4c710d1107ac recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-6fe9774ae0c36a6b. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: Business system records identify the action as part of a recurring workflow already used by this team. The business owner confirms the purpose and downstream records show the normal result. It is not tied to maintenance, a security exercise or a configuration correction.","target":"benign"} | |
| {"text":"Authentication telemetry on ASSET-c2a6c281824dee93 recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-151aed5aab3c16bb. Business context: production platform operations. The event occurred during a routine service period. Evidence: Execution occurs inside the authorised window and verification checks match the planned outcome. A change control record approved before execution names this operator, target and requested operation. This is documented maintenance rather than a security exercise or recurring business workflow.","target":"expected_admin"} | |
| {"text":"Authentication telemetry on ASSET-2f156a171e44e4a2 recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-4fcc4eb2ba23ea73. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: The event aligns with the established application process, normal identity and expected resource scope. No administrator change, test engagement or settings fault is required to explain it. Independent workflow records corroborate ordinary use and expected completion.","target":"benign"} | |
| {"text":"Registry telemetry on ASSET-0c39025cdd728b7c recorded that a logon start registry entry was created. The event references principal-b445cfc37449d009. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: Responder confirmed compromise predates the event and session correlation ties this action to that compromised control path. Access policy and the owner agree that the initiating identity lacked permission for this operation. No approved operations work, normal business process or sanctioned assessment covers it.","target":"malicious"} | |
| {"text":"Session telemetry on ASSET-6cd03581f6091ff2 recorded that the same session token appeared from different client addresses. The event references principal-b11813f0e5d8f95b. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: A preapproved security validation record lists the technique, test identity and affected resource. The resource owner and assessment coordinator confirm permission existed beforehand and activity stayed within scope. The controlling record is a security engagement rather than an operations change or ordinary workflow.","target":"authorised_testing"} | |
| {"text":"Device control telemetry on ASSET-259ab04dcd3e71c8 recorded that a removable storage device was mounted. The event references principal-736440c29d2c2ffc. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: A controlled reproduction generates the same event only when an incorrect configuration value is present. Correcting the value prevents recurrence while preserving intended workload behaviour. Review finds no evidence of account compromise or unauthorised control.","target":"misconfiguration"} | |
| {"text":"Device control telemetry on ASSET-259ab04dcd3e71c8 recorded that a removable storage device was mounted. The event references principal-736440c29d2c2ffc. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: The deviation is real, but compromise is not established. Independent telemetry confirms unusual scope and sequence that the responsible team cannot explain. Maintenance, test and settings records provide no verified explanation.","target":"suspicious"} | |
| {"text":"Registry telemetry on ASSET-87f634c5db0bf0a4 recorded that a logon start registry entry was created. The event references principal-b4878bc054d3d019. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: A controlled reproduction generates the same event only when an incorrect configuration value is present. Correcting the value prevents recurrence while preserving intended workload behaviour. Review finds no evidence of account compromise or unauthorised control.","target":"misconfiguration"} | |
| {"text":"macOS security telemetry on ASSET-49e92eb9ee86195a recorded that a system extension was loaded. The event references principal-2cead65e8d2af689. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: Review finds no evidence of account compromise or unauthorised control. Correcting the value prevents recurrence while preserving intended workload behaviour. A controlled reproduction generates the same event only when an incorrect configuration value is present.","target":"misconfiguration"} | |
| {"text":"macOS security telemetry on ASSET-daf3ffb9d8aa9b1d recorded that a system extension was loaded. The event references principal-2663849fde66787e. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: Retained sources disagree on attribution and the missing source cannot be reconstructed. Available evidence cannot distinguish routine, approved, erroneous and unauthorised causes. The evidence does not support choosing a stronger conclusion.","target":"unknown"} | |
| {"text":"Session telemetry on ASSET-84339bd64baee543 recorded that the same session token appeared from different client addresses. The event references principal-fbe0cdae58b1cae5. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: The corrected configuration produces the intended outcome and the alert does not recur. Engineers isolate an unintended setting and reproduce the action under controlled replay. Attribution records do not support an unauthorised actor as the cause.","target":"misconfiguration"} | |
| {"text":"Device control telemetry on ASSET-7df9d0278b9bd4a7 recorded that a removable storage device was mounted. The event references principal-9a4767494da5d5a5. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: The owner confirms the operation exceeded authorised resource scope. Neither change control nor security assessment records provide authorisation. A forensic timeline traces this action to a token conclusively recovered from an intruder controlled session.","target":"malicious"} | |
| {"text":"macOS security telemetry on ASSET-cf2bf4132c332f02 recorded that a system extension was loaded. The event references principal-b7f804e447bbee6d. Business context: production platform operations. The event occurred during a routine service period. Evidence: Attribution records do not support an unauthorised actor as the cause. Engineers isolate an unintended setting and reproduce the action under controlled replay. The corrected configuration produces the intended outcome and the alert does not recur.","target":"misconfiguration"} | |
| {"text":"File audit telemetry on ASSET-7f9c55b3dbd9e2db recorded that a shell startup profile gained an additional command. The event references principal-59b6261d348cafc2. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: Attribution records do not support an unauthorised actor as the cause. Engineers isolate an unintended setting and reproduce the action under controlled replay. The corrected configuration produces the intended outcome and the alert does not recur.","target":"misconfiguration"} | |
| {"text":"Authentication telemetry on ASSET-c2a6c281824dee93 recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-151aed5aab3c16bb. Business context: production platform operations. The event occurred during a routine service period. Evidence: Both authorised and unauthorised explanations remain plausible from the surviving material. A reliable disposition cannot be established without missing corroboration. Key identity and timing evidence is unavailable while remaining records conflict.","target":"unknown"} | |
| {"text":"Session telemetry on ASSET-6cd03581f6091ff2 recorded that the same session token appeared from different client addresses. The event references principal-b11813f0e5d8f95b. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: Attribution records do not support an unauthorised actor as the cause. The corrected configuration produces the intended outcome and the alert does not recur. Engineers isolate an unintended setting and reproduce the action under controlled replay.","target":"misconfiguration"} | |
| {"text":"Authentication telemetry on ASSET-acf343492ca3e416 recorded that a principal requested an unusual number of service tickets. The event references principal-4cddd26b2e55cccf. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: This action is justified by assessment scope, not maintenance or a configuration correction. Execution matches the authorised assessment window, test identity and listed targets. The engagement plan identifies the observed action as an in scope assessment step.","target":"authorised_testing"} | |
| {"text":"Software management telemetry on ASSET-32df6ce14eab6663 recorded that a package was installed on a managed endpoint. The event references principal-23ffd379ff47e0ee. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: It is not tied to maintenance, a security exercise or a configuration correction. Business system records identify the action as part of a recurring workflow already used by this team. The business owner confirms the purpose and downstream records show the normal result.","target":"benign"} | |
| {"text":"Identity telemetry on ASSET-c32286d46cf22a77 recorded that a refresh token was used from a new network location. The event references principal-7482392e6af16b70. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: Attribution records do not support an unauthorised actor as the cause. The corrected configuration produces the intended outcome and the alert does not recur. Engineers isolate an unintended setting and reproduce the action under controlled replay.","target":"misconfiguration"} | |
| {"text":"Device control telemetry on ASSET-ebb2be94ec626240 recorded that a removable storage device was mounted. The event references principal-f26b6fc008fdefc3. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Maintenance, test and settings records provide no verified explanation. The deviation is real, but compromise is not established. Independent telemetry confirms unusual scope and sequence that the responsible team cannot explain.","target":"suspicious"} | |
| {"text":"Registry telemetry on ASSET-87f634c5db0bf0a4 recorded that a logon start registry entry was created. The event references principal-b4878bc054d3d019. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Responder confirmed compromise predates the event and session correlation ties this action to that compromised control path. No approved operations work, normal business process or sanctioned assessment covers it. Access policy and the owner agree that the initiating identity lacked permission for this operation.","target":"malicious"} | |
| {"text":"Endpoint security telemetry on ASSET-75ff6bb05605e6fb recorded that an endpoint protection exclusion was created. The event references principal-76e700dc719d3b69. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: The event aligns with the established application process, normal identity and expected resource scope. No administrator change, test engagement or settings fault is required to explain it. Independent workflow records corroborate ordinary use and expected completion.","target":"benign"} | |
| {"text":"Registry telemetry on ASSET-0c39025cdd728b7c recorded that a logon start registry entry was created. The event references principal-b445cfc37449d009. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: A change control record approved before execution names this operator, target and requested operation. This is documented maintenance rather than a security exercise or recurring business workflow. Execution occurs inside the authorised window and verification checks match the planned outcome.","target":"expected_admin"} | |
| {"text":"Authentication telemetry on ASSET-2f156a171e44e4a2 recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-4fcc4eb2ba23ea73. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: A change control record approved before execution names this operator, target and requested operation. Execution occurs inside the authorised window and verification checks match the planned outcome. This is documented maintenance rather than a security exercise or recurring business workflow.","target":"expected_admin"} | |
| {"text":"macOS security telemetry on ASSET-a16d729bf97e1d4d recorded that a system extension was loaded. The event references principal-9ead5e0a2f20aaad. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: A change control record approved before execution names this operator, target and requested operation. Execution occurs inside the authorised window and verification checks match the planned outcome. This is documented maintenance rather than a security exercise or recurring business workflow.","target":"expected_admin"} | |
| {"text":"File audit telemetry on ASSET-244b3eddb26e9638 recorded that a shell startup profile gained an additional command. The event references principal-0f3323543c67b8a9. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: The owner confirms the operation exceeded authorised resource scope. Neither change control nor security assessment records provide authorisation. A forensic timeline traces this action to a token conclusively recovered from an intruder controlled session.","target":"malicious"} | |
| {"text":"Authentication telemetry on ASSET-a15a854111323f76 recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-cb2a201458ef6079. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: This action is justified by assessment scope, not maintenance or a configuration correction. The engagement plan identifies the observed action as an in scope assessment step. Execution matches the authorised assessment window, test identity and listed targets.","target":"authorised_testing"} | |
| {"text":"macOS security telemetry on ASSET-bdac430ee3d8f240 recorded that a system extension was loaded. The event references principal-a71c59b5c3e1bdd9. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: It is not tied to maintenance, a security exercise or a configuration correction. The business owner confirms the purpose and downstream records show the normal result. Business system records identify the action as part of a recurring workflow already used by this team.","target":"benign"} | |
| {"text":"File audit telemetry on ASSET-92d7a4b0f0832bdb recorded that a shell startup profile gained an additional command. The event references principal-416cb22cec72515c. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: The owner confirms the operation exceeded authorised resource scope. Neither change control nor security assessment records provide authorisation. A forensic timeline traces this action to a token conclusively recovered from an intruder controlled session.","target":"malicious"} | |
| {"text":"Authentication telemetry on ASSET-8cf90cff1a6cb992 recorded that a principal requested an unusual number of service tickets. The event references principal-771b0d2efb9a5186. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: The action is a clear departure from prior activity for this identity and remains unaccounted for. No operations change, assessment engagement or reproducible configuration issue explains it. Investigators verify the anomaly without establishing credential theft or hostile control.","target":"suspicious"} | |
| {"text":"Authentication telemetry on ASSET-c872ba5f50ae32d6 recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-633558f364d854e1. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: No administrator change, test engagement or settings fault is required to explain it. The event aligns with the established application process, normal identity and expected resource scope. Independent workflow records corroborate ordinary use and expected completion.","target":"benign"} | |
| {"text":"Session telemetry on ASSET-84339bd64baee543 recorded that the same session token appeared from different client addresses. The event references principal-fbe0cdae58b1cae5. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: The deviation is real, but compromise is not established. Independent telemetry confirms unusual scope and sequence that the responsible team cannot explain. Maintenance, test and settings records provide no verified explanation.","target":"suspicious"} | |
| {"text":"Authentication telemetry on ASSET-c2a6c281824dee93 recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-151aed5aab3c16bb. Business context: production platform operations. The event occurred during a routine service period. Evidence: Business system records identify the action as part of a recurring workflow already used by this team. It is not tied to maintenance, a security exercise or a configuration correction. The business owner confirms the purpose and downstream records show the normal result.","target":"benign"} | |
| {"text":"Authentication telemetry on ASSET-07ae88df5010a363 recorded that a principal requested an unusual number of service tickets. The event references principal-b13a83bf104bbe9d. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: A preapproved security validation record lists the technique, test identity and affected resource. The resource owner and assessment coordinator confirm permission existed beforehand and activity stayed within scope. The controlling record is a security engagement rather than an operations change or ordinary workflow.","target":"authorised_testing"} | |
| {"text":"macOS security telemetry on ASSET-587baa850a4db605 recorded that a system extension was loaded. The event references principal-fb6516f42fcbcfe2. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: Operations audit independently confirms operator, scope, timing and successful requested state. Authorisation comes from operational change control, not an assessment engagement. The maintenance record explicitly covers the action and affected resource.","target":"expected_admin"} | |
| {"text":"Software management telemetry on ASSET-32df6ce14eab6663 recorded that a package was installed on a managed endpoint. The event references principal-23ffd379ff47e0ee. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: A controlled reproduction generates the same event only when an incorrect configuration value is present. Review finds no evidence of account compromise or unauthorised control. Correcting the value prevents recurrence while preserving intended workload behaviour.","target":"misconfiguration"} | |
| {"text":"Identity telemetry on ASSET-b2bd654cd5ab023a recorded that a refresh token was used from a new network location. The event references principal-73aee0a8494cc453. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Investigators verify the anomaly without establishing credential theft or hostile control. No operations change, assessment engagement or reproducible configuration issue explains it. The action is a clear departure from prior activity for this identity and remains unaccounted for.","target":"suspicious"} | |
| {"text":"Registry telemetry on ASSET-12375d2acdd5c83c recorded that a logon start registry entry was created. The event references principal-82275ea6f7900f1a. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: Key identity and timing evidence is unavailable while remaining records conflict. Both authorised and unauthorised explanations remain plausible from the surviving material. A reliable disposition cannot be established without missing corroboration.","target":"unknown"} | |
| {"text":"File audit telemetry on ASSET-2d0f26265383a3e9 recorded that a shell startup profile gained an additional command. The event references principal-c496e6a38f3f9b56. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Operations audit independently confirms operator, scope, timing and successful requested state. The maintenance record explicitly covers the action and affected resource. Authorisation comes from operational change control, not an assessment engagement.","target":"expected_admin"} | |
| {"text":"Registry telemetry on ASSET-0c39025cdd728b7c recorded that a logon start registry entry was created. The event references principal-b445cfc37449d009. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: The corrected configuration produces the intended outcome and the alert does not recur. Attribution records do not support an unauthorised actor as the cause. Engineers isolate an unintended setting and reproduce the action under controlled replay.","target":"misconfiguration"} | |
| {"text":"Endpoint security telemetry on ASSET-e83f6274411aaa6d recorded that an endpoint protection exclusion was created. The event references principal-e6554316398adcdc. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: Correcting the value prevents recurrence while preserving intended workload behaviour. Review finds no evidence of account compromise or unauthorised control. A controlled reproduction generates the same event only when an incorrect configuration value is present.","target":"misconfiguration"} | |
| {"text":"File audit telemetry on ASSET-70dbeadf16553ad5 recorded that a shell startup profile gained an additional command. The event references principal-a133c5d9cfe383ed. Business context: production platform operations. The event occurred during a routine service period. Evidence: Correcting the value prevents recurrence while preserving intended workload behaviour. Review finds no evidence of account compromise or unauthorised control. A controlled reproduction generates the same event only when an incorrect configuration value is present.","target":"misconfiguration"} | |
| {"text":"Session telemetry on ASSET-27aed1797a5563b5 recorded that the same session token appeared from different client addresses. The event references principal-e56850509a38c06d. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: A preapproved security validation record lists the technique, test identity and affected resource. The controlling record is a security engagement rather than an operations change or ordinary workflow. The resource owner and assessment coordinator confirm permission existed beforehand and activity stayed within scope.","target":"authorised_testing"} | |
| {"text":"Device control telemetry on ASSET-ebb2be94ec626240 recorded that a removable storage device was mounted. The event references principal-f26b6fc008fdefc3. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: A reliable disposition cannot be established without missing corroboration. Key identity and timing evidence is unavailable while remaining records conflict. Both authorised and unauthorised explanations remain plausible from the surviving material.","target":"unknown"} | |
| {"text":"Device control telemetry on ASSET-10321812fb8412ae recorded that a removable storage device was mounted. The event references principal-5642e2e1a1479b48. Business context: production platform operations. The event occurred during a routine service period. Evidence: A preapproved security validation record lists the technique, test identity and affected resource. The resource owner and assessment coordinator confirm permission existed beforehand and activity stayed within scope. The controlling record is a security engagement rather than an operations change or ordinary workflow.","target":"authorised_testing"} | |
| {"text":"Device control telemetry on ASSET-259ab04dcd3e71c8 recorded that a removable storage device was mounted. The event references principal-736440c29d2c2ffc. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: It is not tied to maintenance, a security exercise or a configuration correction. Business system records identify the action as part of a recurring workflow already used by this team. The business owner confirms the purpose and downstream records show the normal result.","target":"benign"} | |
| {"text":"Software management telemetry on ASSET-7843b4a839c3e633 recorded that a package was installed on a managed endpoint. The event references principal-8dd235eee07bf8d4. Business context: production platform operations. The event occurred during a routine service period. Evidence: No approved operations work, normal business process or sanctioned assessment covers it. Responder confirmed compromise predates the event and session correlation ties this action to that compromised control path. Access policy and the owner agree that the initiating identity lacked permission for this operation.","target":"malicious"} | |
| {"text":"Session telemetry on ASSET-b1230d6c50948f68 recorded that the same session token appeared from different client addresses. The event references principal-4a757c51da729678. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: Attribution records do not support an unauthorised actor as the cause. Engineers isolate an unintended setting and reproduce the action under controlled replay. The corrected configuration produces the intended outcome and the alert does not recur.","target":"misconfiguration"} | |
| {"text":"Device control telemetry on ASSET-10321812fb8412ae recorded that a removable storage device was mounted. The event references principal-5642e2e1a1479b48. Business context: production platform operations. The event occurred during a routine service period. Evidence: The corrected configuration produces the intended outcome and the alert does not recur. Attribution records do not support an unauthorised actor as the cause. Engineers isolate an unintended setting and reproduce the action under controlled replay.","target":"misconfiguration"} | |
| {"text":"Endpoint security telemetry on ASSET-e83f6274411aaa6d recorded that an endpoint protection exclusion was created. The event references principal-e6554316398adcdc. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: The action is a clear departure from prior activity for this identity and remains unaccounted for. No operations change, assessment engagement or reproducible configuration issue explains it. Investigators verify the anomaly without establishing credential theft or hostile control.","target":"suspicious"} | |
| {"text":"Endpoint security telemetry on ASSET-7e53d3e4e297766b recorded that an endpoint protection exclusion was created. The event references principal-86e0d09fd796b1f9. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Responder confirmed compromise predates the event and session correlation ties this action to that compromised control path. Access policy and the owner agree that the initiating identity lacked permission for this operation. No approved operations work, normal business process or sanctioned assessment covers it.","target":"malicious"} | |
| {"text":"Endpoint security telemetry on ASSET-160e6026e1614ce4 recorded that an endpoint protection exclusion was created. The event references principal-a5a9164c0612b141. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: This action is justified by assessment scope, not maintenance or a configuration correction. The engagement plan identifies the observed action as an in scope assessment step. Execution matches the authorised assessment window, test identity and listed targets.","target":"authorised_testing"} | |
| {"text":"Authentication telemetry on ASSET-8cf90cff1a6cb992 recorded that a principal requested an unusual number of service tickets. The event references principal-771b0d2efb9a5186. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: This action is justified by assessment scope, not maintenance or a configuration correction. Execution matches the authorised assessment window, test identity and listed targets. The engagement plan identifies the observed action as an in scope assessment step.","target":"authorised_testing"} | |
| {"text":"Device control telemetry on ASSET-ebb2be94ec626240 recorded that a removable storage device was mounted. The event references principal-f26b6fc008fdefc3. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: This action is justified by assessment scope, not maintenance or a configuration correction. The engagement plan identifies the observed action as an in scope assessment step. Execution matches the authorised assessment window, test identity and listed targets.","target":"authorised_testing"} | |
| {"text":"macOS security telemetry on ASSET-49e92eb9ee86195a recorded that a system extension was loaded. The event references principal-2cead65e8d2af689. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: The evidence does not support choosing a stronger conclusion. Available evidence cannot distinguish routine, approved, erroneous and unauthorised causes. Retained sources disagree on attribution and the missing source cannot be reconstructed.","target":"unknown"} | |
| {"text":"Endpoint security telemetry on ASSET-0b357e20610a5fb7 recorded that an endpoint protection exclusion was created. The event references principal-e1bbd626857b07af. Business context: production platform operations. The event occurred during a routine service period. Evidence: A forensic timeline traces this action to a token conclusively recovered from an intruder controlled session. Neither change control nor security assessment records provide authorisation. The owner confirms the operation exceeded authorised resource scope.","target":"malicious"} | |
| {"text":"Software management telemetry on ASSET-06e87c8ba3d49d7f recorded that a package was installed on a managed endpoint. The event references principal-0e15aa0fe26d14ba. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: Investigators verify the anomaly without establishing credential theft or hostile control. The action is a clear departure from prior activity for this identity and remains unaccounted for. No operations change, assessment engagement or reproducible configuration issue explains it.","target":"suspicious"} | |
| {"text":"Registry telemetry on ASSET-87f634c5db0bf0a4 recorded that a logon start registry entry was created. The event references principal-b4878bc054d3d019. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Both authorised and unauthorised explanations remain plausible from the surviving material. Key identity and timing evidence is unavailable while remaining records conflict. A reliable disposition cannot be established without missing corroboration.","target":"unknown"} | |
| {"text":"Identity telemetry on ASSET-3425b69fbdfab7e6 recorded that a refresh token was used from a new network location. The event references principal-9fa4e0696ae4fe07. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: Investigators verify the anomaly without establishing credential theft or hostile control. No operations change, assessment engagement or reproducible configuration issue explains it. The action is a clear departure from prior activity for this identity and remains unaccounted for.","target":"suspicious"} | |
| {"text":"Device control telemetry on ASSET-7df9d0278b9bd4a7 recorded that a removable storage device was mounted. The event references principal-9a4767494da5d5a5. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: The event aligns with the established application process, normal identity and expected resource scope. No administrator change, test engagement or settings fault is required to explain it. Independent workflow records corroborate ordinary use and expected completion.","target":"benign"} | |
| {"text":"Software management telemetry on ASSET-32df6ce14eab6663 recorded that a package was installed on a managed endpoint. The event references principal-23ffd379ff47e0ee. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: A reliable disposition cannot be established without missing corroboration. Key identity and timing evidence is unavailable while remaining records conflict. Both authorised and unauthorised explanations remain plausible from the surviving material.","target":"unknown"} | |
| {"text":"Identity telemetry on ASSET-791a839682be1692 recorded that a refresh token was used from a new network location. The event references principal-d9496fe520292c09. Business context: production platform operations. The event occurred during a routine service period. Evidence: The owner confirms the operation exceeded authorised resource scope. Neither change control nor security assessment records provide authorisation. A forensic timeline traces this action to a token conclusively recovered from an intruder controlled session.","target":"malicious"} | |
| {"text":"Authentication telemetry on ASSET-c2a6c281824dee93 recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-151aed5aab3c16bb. Business context: production platform operations. The event occurred during a routine service period. Evidence: Execution matches the authorised assessment window, test identity and listed targets. This action is justified by assessment scope, not maintenance or a configuration correction. The engagement plan identifies the observed action as an in scope assessment step.","target":"authorised_testing"} | |
| {"text":"Registry telemetry on ASSET-12375d2acdd5c83c recorded that a logon start registry entry was created. The event references principal-82275ea6f7900f1a. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: Access policy and the owner agree that the initiating identity lacked permission for this operation. No approved operations work, normal business process or sanctioned assessment covers it. Responder confirmed compromise predates the event and session correlation ties this action to that compromised control path.","target":"malicious"} | |
| {"text":"Endpoint security telemetry on ASSET-e83f6274411aaa6d recorded that an endpoint protection exclusion was created. The event references principal-e6554316398adcdc. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: No administrator change, test engagement or settings fault is required to explain it. The event aligns with the established application process, normal identity and expected resource scope. Independent workflow records corroborate ordinary use and expected completion.","target":"benign"} | |
| {"text":"Authentication telemetry on ASSET-a15a854111323f76 recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-cb2a201458ef6079. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: A change control record approved before execution names this operator, target and requested operation. Execution occurs inside the authorised window and verification checks match the planned outcome. This is documented maintenance rather than a security exercise or recurring business workflow.","target":"expected_admin"} | |
| {"text":"Identity telemetry on ASSET-3425b69fbdfab7e6 recorded that a refresh token was used from a new network location. The event references principal-9fa4e0696ae4fe07. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: The corrected configuration produces the intended outcome and the alert does not recur. Attribution records do not support an unauthorised actor as the cause. Engineers isolate an unintended setting and reproduce the action under controlled replay.","target":"misconfiguration"} | |
| {"text":"Session telemetry on ASSET-926cbea91206be7b recorded that the same session token appeared from different client addresses. The event references principal-f1087c5e5eb18984. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: The deviation is real, but compromise is not established. Independent telemetry confirms unusual scope and sequence that the responsible team cannot explain. Maintenance, test and settings records provide no verified explanation.","target":"suspicious"} | |
| {"text":"Session telemetry on ASSET-27aed1797a5563b5 recorded that the same session token appeared from different client addresses. The event references principal-e56850509a38c06d. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: Execution occurs inside the authorised window and verification checks match the planned outcome. This is documented maintenance rather than a security exercise or recurring business workflow. A change control record approved before execution names this operator, target and requested operation.","target":"expected_admin"} | |
| {"text":"Identity telemetry on ASSET-3425b69fbdfab7e6 recorded that a refresh token was used from a new network location. The event references principal-9fa4e0696ae4fe07. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: Operations audit independently confirms operator, scope, timing and successful requested state. Authorisation comes from operational change control, not an assessment engagement. The maintenance record explicitly covers the action and affected resource.","target":"expected_admin"} | |
| {"text":"Software management telemetry on ASSET-f2f2d49fc14cce3a recorded that a package was installed on a managed endpoint. The event references principal-81eb77e2008fdfd9. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: No operations change, assessment engagement or reproducible configuration issue explains it. The action is a clear departure from prior activity for this identity and remains unaccounted for. Investigators verify the anomaly without establishing credential theft or hostile control.","target":"suspicious"} | |
| {"text":"macOS security telemetry on ASSET-cf2bf4132c332f02 recorded that a system extension was loaded. The event references principal-b7f804e447bbee6d. Business context: production platform operations. The event occurred during a routine service period. Evidence: The owner confirms the operation exceeded authorised resource scope. A forensic timeline traces this action to a token conclusively recovered from an intruder controlled session. Neither change control nor security assessment records provide authorisation.","target":"malicious"} | |
| {"text":"Endpoint security telemetry on ASSET-0b357e20610a5fb7 recorded that an endpoint protection exclusion was created. The event references principal-e1bbd626857b07af. Business context: production platform operations. The event occurred during a routine service period. Evidence: A controlled reproduction generates the same event only when an incorrect configuration value is present. Correcting the value prevents recurrence while preserving intended workload behaviour. Review finds no evidence of account compromise or unauthorised control.","target":"misconfiguration"} | |
| {"text":"Endpoint security telemetry on ASSET-db6194ae20a3b5bb recorded that an endpoint protection exclusion was created. The event references principal-d91aeef0e18e03dd. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: Responder confirmed compromise predates the event and session correlation ties this action to that compromised control path. Access policy and the owner agree that the initiating identity lacked permission for this operation. No approved operations work, normal business process or sanctioned assessment covers it.","target":"malicious"} | |
| {"text":"Session telemetry on ASSET-6cd03581f6091ff2 recorded that the same session token appeared from different client addresses. The event references principal-b11813f0e5d8f95b. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: Responder confirmed compromise predates the event and session correlation ties this action to that compromised control path. No approved operations work, normal business process or sanctioned assessment covers it. Access policy and the owner agree that the initiating identity lacked permission for this operation.","target":"malicious"} | |
| {"text":"Authentication telemetry on ASSET-acf343492ca3e416 recorded that a principal requested an unusual number of service tickets. The event references principal-4cddd26b2e55cccf. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: Attribution records do not support an unauthorised actor as the cause. Engineers isolate an unintended setting and reproduce the action under controlled replay. The corrected configuration produces the intended outcome and the alert does not recur.","target":"misconfiguration"} | |
| {"text":"Software management telemetry on ASSET-ea03e3935a4440a1 recorded that a package was installed on a managed endpoint. The event references principal-4576ae7a9839e853. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Operations audit independently confirms operator, scope, timing and successful requested state. Authorisation comes from operational change control, not an assessment engagement. The maintenance record explicitly covers the action and affected resource.","target":"expected_admin"} | |
| {"text":"Identity telemetry on ASSET-3425b69fbdfab7e6 recorded that a refresh token was used from a new network location. The event references principal-9fa4e0696ae4fe07. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: Business system records identify the action as part of a recurring workflow already used by this team. It is not tied to maintenance, a security exercise or a configuration correction. The business owner confirms the purpose and downstream records show the normal result.","target":"benign"} | |
| {"text":"File audit telemetry on ASSET-92d7a4b0f0832bdb recorded that a shell startup profile gained an additional command. The event references principal-416cb22cec72515c. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: A change control record approved before execution names this operator, target and requested operation. This is documented maintenance rather than a security exercise or recurring business workflow. Execution occurs inside the authorised window and verification checks match the planned outcome.","target":"expected_admin"} | |
| {"text":"Authentication telemetry on ASSET-a15a854111323f76 recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-cb2a201458ef6079. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: The deviation is real, but compromise is not established. Independent telemetry confirms unusual scope and sequence that the responsible team cannot explain. Maintenance, test and settings records provide no verified explanation.","target":"suspicious"} | |
| {"text":"Authentication telemetry on ASSET-5e68633aa4272d07 recorded that a principal requested an unusual number of service tickets. The event references principal-a3a1c3419e57c2b9. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Operations audit independently confirms operator, scope, timing and successful requested state. The maintenance record explicitly covers the action and affected resource. Authorisation comes from operational change control, not an assessment engagement.","target":"expected_admin"} | |
| {"text":"macOS security telemetry on ASSET-587baa850a4db605 recorded that a system extension was loaded. The event references principal-fb6516f42fcbcfe2. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: No administrator change, test engagement or settings fault is required to explain it. The event aligns with the established application process, normal identity and expected resource scope. Independent workflow records corroborate ordinary use and expected completion.","target":"benign"} | |
| {"text":"Session telemetry on ASSET-6cd03581f6091ff2 recorded that the same session token appeared from different client addresses. The event references principal-b11813f0e5d8f95b. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: The maintenance record explicitly covers the action and affected resource. Authorisation comes from operational change control, not an assessment engagement. Operations audit independently confirms operator, scope, timing and successful requested state.","target":"expected_admin"} | |
| {"text":"File audit telemetry on ASSET-244b3eddb26e9638 recorded that a shell startup profile gained an additional command. The event references principal-0f3323543c67b8a9. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: The resource owner and assessment coordinator confirm permission existed beforehand and activity stayed within scope. A preapproved security validation record lists the technique, test identity and affected resource. The controlling record is a security engagement rather than an operations change or ordinary workflow.","target":"authorised_testing"} | |
| {"text":"Authentication telemetry on ASSET-6db2c84b2223d2a6 recorded that a principal requested an unusual number of service tickets. The event references principal-2d3de75c1517cbb8. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: Neither change control nor security assessment records provide authorisation. The owner confirms the operation exceeded authorised resource scope. A forensic timeline traces this action to a token conclusively recovered from an intruder controlled session.","target":"malicious"} | |
| {"text":"macOS security telemetry on ASSET-daf3ffb9d8aa9b1d recorded that a system extension was loaded. The event references principal-2663849fde66787e. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: The engagement plan identifies the observed action as an in scope assessment step. Execution matches the authorised assessment window, test identity and listed targets. This action is justified by assessment scope, not maintenance or a configuration correction.","target":"authorised_testing"} | |
| {"text":"Session telemetry on ASSET-b1230d6c50948f68 recorded that the same session token appeared from different client addresses. The event references principal-4a757c51da729678. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: Available evidence cannot distinguish routine, approved, erroneous and unauthorised causes. Retained sources disagree on attribution and the missing source cannot be reconstructed. The evidence does not support choosing a stronger conclusion.","target":"unknown"} | |
| {"text":"Software management telemetry on ASSET-7843b4a839c3e633 recorded that a package was installed on a managed endpoint. The event references principal-8dd235eee07bf8d4. Business context: production platform operations. The event occurred during a routine service period. Evidence: A preapproved security validation record lists the technique, test identity and affected resource. The controlling record is a security engagement rather than an operations change or ordinary workflow. The resource owner and assessment coordinator confirm permission existed beforehand and activity stayed within scope.","target":"authorised_testing"} | |
| {"text":"Session telemetry on ASSET-27aed1797a5563b5 recorded that the same session token appeared from different client addresses. The event references principal-e56850509a38c06d. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: The business owner confirms the purpose and downstream records show the normal result. It is not tied to maintenance, a security exercise or a configuration correction. Business system records identify the action as part of a recurring workflow already used by this team.","target":"benign"} | |
| {"text":"Authentication telemetry on ASSET-2f156a171e44e4a2 recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-4fcc4eb2ba23ea73. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Key identity and timing evidence is unavailable while remaining records conflict. Both authorised and unauthorised explanations remain plausible from the surviving material. A reliable disposition cannot be established without missing corroboration.","target":"unknown"} | |
| {"text":"Authentication telemetry on ASSET-c2a6c281824dee93 recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-151aed5aab3c16bb. Business context: production platform operations. The event occurred during a routine service period. Evidence: Neither change control nor security assessment records provide authorisation. A forensic timeline traces this action to a token conclusively recovered from an intruder controlled session. The owner confirms the operation exceeded authorised resource scope.","target":"malicious"} | |
| {"text":"Authentication telemetry on ASSET-6db2c84b2223d2a6 recorded that a principal requested an unusual number of service tickets. The event references principal-2d3de75c1517cbb8. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: The controlling record is a security engagement rather than an operations change or ordinary workflow. The resource owner and assessment coordinator confirm permission existed beforehand and activity stayed within scope. A preapproved security validation record lists the technique, test identity and affected resource.","target":"authorised_testing"} | |
| {"text":"Authentication telemetry on ASSET-2f156a171e44e4a2 recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-4fcc4eb2ba23ea73. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Investigators verify the anomaly without establishing credential theft or hostile control. No operations change, assessment engagement or reproducible configuration issue explains it. The action is a clear departure from prior activity for this identity and remains unaccounted for.","target":"suspicious"} | |
| {"text":"Identity telemetry on ASSET-b2bd654cd5ab023a recorded that a refresh token was used from a new network location. The event references principal-73aee0a8494cc453. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: A reliable disposition cannot be established without missing corroboration. Both authorised and unauthorised explanations remain plausible from the surviving material. Key identity and timing evidence is unavailable while remaining records conflict.","target":"unknown"} | |
| {"text":"Endpoint security telemetry on ASSET-e83f6274411aaa6d recorded that an endpoint protection exclusion was created. The event references principal-e6554316398adcdc. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: No approved operations work, normal business process or sanctioned assessment covers it. Responder confirmed compromise predates the event and session correlation ties this action to that compromised control path. Access policy and the owner agree that the initiating identity lacked permission for this operation.","target":"malicious"} | |
| {"text":"Endpoint security telemetry on ASSET-db6194ae20a3b5bb recorded that an endpoint protection exclusion was created. The event references principal-d91aeef0e18e03dd. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: Correcting the value prevents recurrence while preserving intended workload behaviour. A controlled reproduction generates the same event only when an incorrect configuration value is present. Review finds no evidence of account compromise or unauthorised control.","target":"misconfiguration"} | |
| {"text":"Software management telemetry on ASSET-7843b4a839c3e633 recorded that a package was installed on a managed endpoint. The event references principal-8dd235eee07bf8d4. Business context: production platform operations. The event occurred during a routine service period. Evidence: Operations audit independently confirms operator, scope, timing and successful requested state. The maintenance record explicitly covers the action and affected resource. Authorisation comes from operational change control, not an assessment engagement.","target":"expected_admin"} | |
| {"text":"Session telemetry on ASSET-6cd03581f6091ff2 recorded that the same session token appeared from different client addresses. The event references principal-b11813f0e5d8f95b. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: Maintenance, test and settings records provide no verified explanation. Independent telemetry confirms unusual scope and sequence that the responsible team cannot explain. The deviation is real, but compromise is not established.","target":"suspicious"} | |
| {"text":"Authentication telemetry on ASSET-6db2c84b2223d2a6 recorded that a principal requested an unusual number of service tickets. The event references principal-2d3de75c1517cbb8. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: No operations change, assessment engagement or reproducible configuration issue explains it. The action is a clear departure from prior activity for this identity and remains unaccounted for. Investigators verify the anomaly without establishing credential theft or hostile control.","target":"suspicious"} | |
| {"text":"Session telemetry on ASSET-9c2327f65647fb97 recorded that the same session token appeared from different client addresses. The event references principal-37639d5d3739c11a. Business context: production platform operations. The event occurred during a routine service period. Evidence: Engineers isolate an unintended setting and reproduce the action under controlled replay. Attribution records do not support an unauthorised actor as the cause. The corrected configuration produces the intended outcome and the alert does not recur.","target":"misconfiguration"} | |
| {"text":"macOS security telemetry on ASSET-cf2bf4132c332f02 recorded that a system extension was loaded. The event references principal-b7f804e447bbee6d. Business context: production platform operations. The event occurred during a routine service period. Evidence: Key identity and timing evidence is unavailable while remaining records conflict. Both authorised and unauthorised explanations remain plausible from the surviving material. A reliable disposition cannot be established without missing corroboration.","target":"unknown"} | |
| {"text":"File audit telemetry on ASSET-cf3be86beac0dee3 recorded that a shell startup profile gained an additional command. The event references principal-269542d8ca3527cd. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: No approved operations work, normal business process or sanctioned assessment covers it. Responder confirmed compromise predates the event and session correlation ties this action to that compromised control path. Access policy and the owner agree that the initiating identity lacked permission for this operation.","target":"malicious"} | |
| {"text":"Registry telemetry on ASSET-87f634c5db0bf0a4 recorded that a logon start registry entry was created. The event references principal-b4878bc054d3d019. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: The engagement plan identifies the observed action as an in scope assessment step. This action is justified by assessment scope, not maintenance or a configuration correction. Execution matches the authorised assessment window, test identity and listed targets.","target":"authorised_testing"} | |
| {"text":"Session telemetry on ASSET-84339bd64baee543 recorded that the same session token appeared from different client addresses. The event references principal-fbe0cdae58b1cae5. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: No approved operations work, normal business process or sanctioned assessment covers it. Responder confirmed compromise predates the event and session correlation ties this action to that compromised control path. Access policy and the owner agree that the initiating identity lacked permission for this operation.","target":"malicious"} | |
| {"text":"macOS security telemetry on ASSET-49e92eb9ee86195a recorded that a system extension was loaded. The event references principal-2cead65e8d2af689. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: No operations change, assessment engagement or reproducible configuration issue explains it. Investigators verify the anomaly without establishing credential theft or hostile control. The action is a clear departure from prior activity for this identity and remains unaccounted for.","target":"suspicious"} | |
| {"text":"Session telemetry on ASSET-b1230d6c50948f68 recorded that the same session token appeared from different client addresses. The event references principal-4a757c51da729678. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: The resource owner and assessment coordinator confirm permission existed beforehand and activity stayed within scope. The controlling record is a security engagement rather than an operations change or ordinary workflow. A preapproved security validation record lists the technique, test identity and affected resource.","target":"authorised_testing"} | |
| {"text":"Session telemetry on ASSET-b1230d6c50948f68 recorded that the same session token appeared from different client addresses. The event references principal-4a757c51da729678. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: Operations audit independently confirms operator, scope, timing and successful requested state. Authorisation comes from operational change control, not an assessment engagement. The maintenance record explicitly covers the action and affected resource.","target":"expected_admin"} | |
| {"text":"Session telemetry on ASSET-926cbea91206be7b recorded that the same session token appeared from different client addresses. The event references principal-f1087c5e5eb18984. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Correcting the value prevents recurrence while preserving intended workload behaviour. A controlled reproduction generates the same event only when an incorrect configuration value is present. Review finds no evidence of account compromise or unauthorised control.","target":"misconfiguration"} | |
| {"text":"File audit telemetry on ASSET-70dbeadf16553ad5 recorded that a shell startup profile gained an additional command. The event references principal-a133c5d9cfe383ed. Business context: production platform operations. The event occurred during a routine service period. Evidence: No operations change, assessment engagement or reproducible configuration issue explains it. Investigators verify the anomaly without establishing credential theft or hostile control. The action is a clear departure from prior activity for this identity and remains unaccounted for.","target":"suspicious"} | |
| {"text":"File audit telemetry on ASSET-244b3eddb26e9638 recorded that a shell startup profile gained an additional command. The event references principal-0f3323543c67b8a9. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: Independent telemetry confirms unusual scope and sequence that the responsible team cannot explain. Maintenance, test and settings records provide no verified explanation. The deviation is real, but compromise is not established.","target":"suspicious"} | |
| {"text":"macOS security telemetry on ASSET-587baa850a4db605 recorded that a system extension was loaded. The event references principal-fb6516f42fcbcfe2. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: Correcting the value prevents recurrence while preserving intended workload behaviour. Review finds no evidence of account compromise or unauthorised control. A controlled reproduction generates the same event only when an incorrect configuration value is present.","target":"misconfiguration"} | |
| {"text":"Registry telemetry on ASSET-4938f25ac72b185c recorded that a logon start registry entry was created. The event references principal-fba84b98a4c57ccd. Business context: production platform operations. The event occurred during a routine service period. Evidence: Key identity and timing evidence is unavailable while remaining records conflict. A reliable disposition cannot be established without missing corroboration. Both authorised and unauthorised explanations remain plausible from the surviving material.","target":"unknown"} | |
| {"text":"File audit telemetry on ASSET-92d7a4b0f0832bdb recorded that a shell startup profile gained an additional command. The event references principal-416cb22cec72515c. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: Engineers isolate an unintended setting and reproduce the action under controlled replay. The corrected configuration produces the intended outcome and the alert does not recur. Attribution records do not support an unauthorised actor as the cause.","target":"misconfiguration"} | |
| {"text":"Registry telemetry on ASSET-12375d2acdd5c83c recorded that a logon start registry entry was created. The event references principal-82275ea6f7900f1a. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: Authorisation comes from operational change control, not an assessment engagement. Operations audit independently confirms operator, scope, timing and successful requested state. The maintenance record explicitly covers the action and affected resource.","target":"expected_admin"} | |
| {"text":"Authentication telemetry on ASSET-f1b4768b1ee1bd7b recorded that a principal requested an unusual number of service tickets. The event references principal-2d35dcb74491ee63. Business context: production platform operations. The event occurred during a routine service period. Evidence: Access policy and the owner agree that the initiating identity lacked permission for this operation. No approved operations work, normal business process or sanctioned assessment covers it. Responder confirmed compromise predates the event and session correlation ties this action to that compromised control path.","target":"malicious"} | |
| {"text":"Endpoint security telemetry on ASSET-75ff6bb05605e6fb recorded that an endpoint protection exclusion was created. The event references principal-76e700dc719d3b69. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: A controlled reproduction generates the same event only when an incorrect configuration value is present. Correcting the value prevents recurrence while preserving intended workload behaviour. Review finds no evidence of account compromise or unauthorised control.","target":"misconfiguration"} | |
| {"text":"Authentication telemetry on ASSET-8cf90cff1a6cb992 recorded that a principal requested an unusual number of service tickets. The event references principal-771b0d2efb9a5186. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: No approved operations work, normal business process or sanctioned assessment covers it. Responder confirmed compromise predates the event and session correlation ties this action to that compromised control path. Access policy and the owner agree that the initiating identity lacked permission for this operation.","target":"malicious"} | |
| {"text":"Software management telemetry on ASSET-7843b4a839c3e633 recorded that a package was installed on a managed endpoint. The event references principal-8dd235eee07bf8d4. Business context: production platform operations. The event occurred during a routine service period. Evidence: The business owner confirms the purpose and downstream records show the normal result. Business system records identify the action as part of a recurring workflow already used by this team. It is not tied to maintenance, a security exercise or a configuration correction.","target":"benign"} | |
| {"text":"Registry telemetry on ASSET-1e7cb34006b816e1 recorded that a logon start registry entry was created. The event references principal-030b4d8a5377e36c. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: Investigators verify the anomaly without establishing credential theft or hostile control. No operations change, assessment engagement or reproducible configuration issue explains it. The action is a clear departure from prior activity for this identity and remains unaccounted for.","target":"suspicious"} | |
| {"text":"Authentication telemetry on ASSET-f1b4768b1ee1bd7b recorded that a principal requested an unusual number of service tickets. The event references principal-2d35dcb74491ee63. Business context: production platform operations. The event occurred during a routine service period. Evidence: The business owner confirms the purpose and downstream records show the normal result. It is not tied to maintenance, a security exercise or a configuration correction. Business system records identify the action as part of a recurring workflow already used by this team.","target":"benign"} | |
| {"text":"Device control telemetry on ASSET-af254892f4cef978 recorded that a removable storage device was mounted. The event references principal-c8f4d8895c66119b. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: Correcting the value prevents recurrence while preserving intended workload behaviour. A controlled reproduction generates the same event only when an incorrect configuration value is present. Review finds no evidence of account compromise or unauthorised control.","target":"misconfiguration"} | |
| {"text":"Session telemetry on ASSET-27aed1797a5563b5 recorded that the same session token appeared from different client addresses. The event references principal-e56850509a38c06d. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: Available evidence cannot distinguish routine, approved, erroneous and unauthorised causes. The evidence does not support choosing a stronger conclusion. Retained sources disagree on attribution and the missing source cannot be reconstructed.","target":"unknown"} | |
| {"text":"macOS security telemetry on ASSET-587baa850a4db605 recorded that a system extension was loaded. The event references principal-fb6516f42fcbcfe2. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: The controlling record is a security engagement rather than an operations change or ordinary workflow. The resource owner and assessment coordinator confirm permission existed beforehand and activity stayed within scope. A preapproved security validation record lists the technique, test identity and affected resource.","target":"authorised_testing"} | |
| {"text":"Software management telemetry on ASSET-946283b501ad60f2 recorded that a package was installed on a managed endpoint. The event references principal-3a055ab31c161145. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: No approved operations work, normal business process or sanctioned assessment covers it. Responder confirmed compromise predates the event and session correlation ties this action to that compromised control path. Access policy and the owner agree that the initiating identity lacked permission for this operation.","target":"malicious"} | |
| {"text":"Software management telemetry on ASSET-f2f2d49fc14cce3a recorded that a package was installed on a managed endpoint. The event references principal-81eb77e2008fdfd9. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: Business system records identify the action as part of a recurring workflow already used by this team. The business owner confirms the purpose and downstream records show the normal result. It is not tied to maintenance, a security exercise or a configuration correction.","target":"benign"} | |
| {"text":"Device control telemetry on ASSET-7df9d0278b9bd4a7 recorded that a removable storage device was mounted. The event references principal-9a4767494da5d5a5. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: The maintenance record explicitly covers the action and affected resource. Operations audit independently confirms operator, scope, timing and successful requested state. Authorisation comes from operational change control, not an assessment engagement.","target":"expected_admin"} | |
| {"text":"Identity telemetry on ASSET-1a0546d031ade59d recorded that a refresh token was used from a new network location. The event references principal-9b0ea911c4279184. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: The owner confirms the operation exceeded authorised resource scope. A forensic timeline traces this action to a token conclusively recovered from an intruder controlled session. Neither change control nor security assessment records provide authorisation.","target":"malicious"} | |
| {"text":"Authentication telemetry on ASSET-acf343492ca3e416 recorded that a principal requested an unusual number of service tickets. The event references principal-4cddd26b2e55cccf. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: The action is a clear departure from prior activity for this identity and remains unaccounted for. Investigators verify the anomaly without establishing credential theft or hostile control. No operations change, assessment engagement or reproducible configuration issue explains it.","target":"suspicious"} | |
| {"text":"Authentication telemetry on ASSET-384932eeebedeb57 recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-e0b285e79e60c451. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: The maintenance record explicitly covers the action and affected resource. Operations audit independently confirms operator, scope, timing and successful requested state. Authorisation comes from operational change control, not an assessment engagement.","target":"expected_admin"} | |
| {"text":"Session telemetry on ASSET-9c2327f65647fb97 recorded that the same session token appeared from different client addresses. The event references principal-37639d5d3739c11a. Business context: production platform operations. The event occurred during a routine service period. Evidence: Maintenance, test and settings records provide no verified explanation. The deviation is real, but compromise is not established. Independent telemetry confirms unusual scope and sequence that the responsible team cannot explain.","target":"suspicious"} | |
| {"text":"Authentication telemetry on ASSET-a15a854111323f76 recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-cb2a201458ef6079. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: Independent workflow records corroborate ordinary use and expected completion. No administrator change, test engagement or settings fault is required to explain it. The event aligns with the established application process, normal identity and expected resource scope.","target":"benign"} | |
| {"text":"Authentication telemetry on ASSET-384932eeebedeb57 recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-e0b285e79e60c451. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: Responder confirmed compromise predates the event and session correlation ties this action to that compromised control path. Access policy and the owner agree that the initiating identity lacked permission for this operation. No approved operations work, normal business process or sanctioned assessment covers it.","target":"malicious"} | |
| {"text":"macOS security telemetry on ASSET-a16d729bf97e1d4d recorded that a system extension was loaded. The event references principal-9ead5e0a2f20aaad. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: Review finds no evidence of account compromise or unauthorised control. A controlled reproduction generates the same event only when an incorrect configuration value is present. Correcting the value prevents recurrence while preserving intended workload behaviour.","target":"misconfiguration"} | |
| {"text":"Authentication telemetry on ASSET-c872ba5f50ae32d6 recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-633558f364d854e1. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: A forensic timeline traces this action to a token conclusively recovered from an intruder controlled session. Neither change control nor security assessment records provide authorisation. The owner confirms the operation exceeded authorised resource scope.","target":"malicious"} | |
| {"text":"Software management telemetry on ASSET-946283b501ad60f2 recorded that a package was installed on a managed endpoint. The event references principal-3a055ab31c161145. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: Engineers isolate an unintended setting and reproduce the action under controlled replay. The corrected configuration produces the intended outcome and the alert does not recur. Attribution records do not support an unauthorised actor as the cause.","target":"misconfiguration"} | |
| {"text":"Authentication telemetry on ASSET-384932eeebedeb57 recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-e0b285e79e60c451. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: The controlling record is a security engagement rather than an operations change or ordinary workflow. The resource owner and assessment coordinator confirm permission existed beforehand and activity stayed within scope. A preapproved security validation record lists the technique, test identity and affected resource.","target":"authorised_testing"} | |
| {"text":"Identity telemetry on ASSET-1a0546d031ade59d recorded that a refresh token was used from a new network location. The event references principal-9b0ea911c4279184. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: Business system records identify the action as part of a recurring workflow already used by this team. The business owner confirms the purpose and downstream records show the normal result. It is not tied to maintenance, a security exercise or a configuration correction.","target":"benign"} | |
| {"text":"Endpoint security telemetry on ASSET-0b357e20610a5fb7 recorded that an endpoint protection exclusion was created. The event references principal-e1bbd626857b07af. Business context: production platform operations. The event occurred during a routine service period. Evidence: Operations audit independently confirms operator, scope, timing and successful requested state. Authorisation comes from operational change control, not an assessment engagement. The maintenance record explicitly covers the action and affected resource.","target":"expected_admin"} | |
| {"text":"Registry telemetry on ASSET-181916903bb96a17 recorded that a logon start registry entry was created. The event references principal-53c6c1059b4ce6f8. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: The evidence does not support choosing a stronger conclusion. Available evidence cannot distinguish routine, approved, erroneous and unauthorised causes. Retained sources disagree on attribution and the missing source cannot be reconstructed.","target":"unknown"} | |
| {"text":"Endpoint security telemetry on ASSET-160e6026e1614ce4 recorded that an endpoint protection exclusion was created. The event references principal-a5a9164c0612b141. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: A controlled reproduction generates the same event only when an incorrect configuration value is present. Correcting the value prevents recurrence while preserving intended workload behaviour. Review finds no evidence of account compromise or unauthorised control.","target":"misconfiguration"} | |
| {"text":"Session telemetry on ASSET-9c2327f65647fb97 recorded that the same session token appeared from different client addresses. The event references principal-37639d5d3739c11a. Business context: production platform operations. The event occurred during a routine service period. Evidence: Available evidence cannot distinguish routine, approved, erroneous and unauthorised causes. The evidence does not support choosing a stronger conclusion. Retained sources disagree on attribution and the missing source cannot be reconstructed.","target":"unknown"} | |
| {"text":"macOS security telemetry on ASSET-a16d729bf97e1d4d recorded that a system extension was loaded. The event references principal-9ead5e0a2f20aaad. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: Neither change control nor security assessment records provide authorisation. A forensic timeline traces this action to a token conclusively recovered from an intruder controlled session. The owner confirms the operation exceeded authorised resource scope.","target":"malicious"} | |
| {"text":"Authentication telemetry on ASSET-5e68633aa4272d07 recorded that a principal requested an unusual number of service tickets. The event references principal-a3a1c3419e57c2b9. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: A controlled reproduction generates the same event only when an incorrect configuration value is present. Correcting the value prevents recurrence while preserving intended workload behaviour. Review finds no evidence of account compromise or unauthorised control.","target":"misconfiguration"} | |
| {"text":"macOS security telemetry on ASSET-49e92eb9ee86195a recorded that a system extension was loaded. The event references principal-2cead65e8d2af689. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: The event aligns with the established application process, normal identity and expected resource scope. No administrator change, test engagement or settings fault is required to explain it. Independent workflow records corroborate ordinary use and expected completion.","target":"benign"} | |
| {"text":"Identity telemetry on ASSET-1a0546d031ade59d recorded that a refresh token was used from a new network location. The event references principal-9b0ea911c4279184. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: The evidence does not support choosing a stronger conclusion. Available evidence cannot distinguish routine, approved, erroneous and unauthorised causes. Retained sources disagree on attribution and the missing source cannot be reconstructed.","target":"unknown"} | |
| {"text":"File audit telemetry on ASSET-cf3be86beac0dee3 recorded that a shell startup profile gained an additional command. The event references principal-269542d8ca3527cd. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: The deviation is real, but compromise is not established. Independent telemetry confirms unusual scope and sequence that the responsible team cannot explain. Maintenance, test and settings records provide no verified explanation.","target":"suspicious"} | |
| {"text":"Device control telemetry on ASSET-6c043b46458f7c8a recorded that a removable storage device was mounted. The event references principal-c5abfb1e9d8d9902. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: The action is a clear departure from prior activity for this identity and remains unaccounted for. Investigators verify the anomaly without establishing credential theft or hostile control. No operations change, assessment engagement or reproducible configuration issue explains it.","target":"suspicious"} | |
| {"text":"File audit telemetry on ASSET-244b3eddb26e9638 recorded that a shell startup profile gained an additional command. The event references principal-0f3323543c67b8a9. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: Review finds no evidence of account compromise or unauthorised control. Correcting the value prevents recurrence while preserving intended workload behaviour. A controlled reproduction generates the same event only when an incorrect configuration value is present.","target":"misconfiguration"} | |
| {"text":"Identity telemetry on ASSET-b2bd654cd5ab023a recorded that a refresh token was used from a new network location. The event references principal-73aee0a8494cc453. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: A change control record approved before execution names this operator, target and requested operation. This is documented maintenance rather than a security exercise or recurring business workflow. Execution occurs inside the authorised window and verification checks match the planned outcome.","target":"expected_admin"} | |
| {"text":"macOS security telemetry on ASSET-a16d729bf97e1d4d recorded that a system extension was loaded. The event references principal-9ead5e0a2f20aaad. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: The business owner confirms the purpose and downstream records show the normal result. It is not tied to maintenance, a security exercise or a configuration correction. Business system records identify the action as part of a recurring workflow already used by this team.","target":"benign"} | |
| {"text":"Authentication telemetry on ASSET-384932eeebedeb57 recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-e0b285e79e60c451. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: Correcting the value prevents recurrence while preserving intended workload behaviour. Review finds no evidence of account compromise or unauthorised control. A controlled reproduction generates the same event only when an incorrect configuration value is present.","target":"misconfiguration"} | |
| {"text":"Software management telemetry on ASSET-06e87c8ba3d49d7f recorded that a package was installed on a managed endpoint. The event references principal-0e15aa0fe26d14ba. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: A change control record approved before execution names this operator, target and requested operation. This is documented maintenance rather than a security exercise or recurring business workflow. Execution occurs inside the authorised window and verification checks match the planned outcome.","target":"expected_admin"} | |
| {"text":"Authentication telemetry on ASSET-548e4c710d1107ac recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-6fe9774ae0c36a6b. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: The resource owner and assessment coordinator confirm permission existed beforehand and activity stayed within scope. A preapproved security validation record lists the technique, test identity and affected resource. The controlling record is a security engagement rather than an operations change or ordinary workflow.","target":"authorised_testing"} | |
| {"text":"Authentication telemetry on ASSET-384932eeebedeb57 recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-e0b285e79e60c451. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: No operations change, assessment engagement or reproducible configuration issue explains it. The action is a clear departure from prior activity for this identity and remains unaccounted for. Investigators verify the anomaly without establishing credential theft or hostile control.","target":"suspicious"} | |
| {"text":"Registry telemetry on ASSET-181916903bb96a17 recorded that a logon start registry entry was created. The event references principal-53c6c1059b4ce6f8. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: This is documented maintenance rather than a security exercise or recurring business workflow. Execution occurs inside the authorised window and verification checks match the planned outcome. A change control record approved before execution names this operator, target and requested operation.","target":"expected_admin"} | |
| {"text":"Authentication telemetry on ASSET-a15a854111323f76 recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-cb2a201458ef6079. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: The corrected configuration produces the intended outcome and the alert does not recur. Engineers isolate an unintended setting and reproduce the action under controlled replay. Attribution records do not support an unauthorised actor as the cause.","target":"misconfiguration"} | |
| {"text":"Authentication telemetry on ASSET-8cf90cff1a6cb992 recorded that a principal requested an unusual number of service tickets. The event references principal-771b0d2efb9a5186. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: Retained sources disagree on attribution and the missing source cannot be reconstructed. The evidence does not support choosing a stronger conclusion. Available evidence cannot distinguish routine, approved, erroneous and unauthorised causes.","target":"unknown"} | |
| {"text":"Registry telemetry on ASSET-1e7cb34006b816e1 recorded that a logon start registry entry was created. The event references principal-030b4d8a5377e36c. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: The evidence does not support choosing a stronger conclusion. Retained sources disagree on attribution and the missing source cannot be reconstructed. Available evidence cannot distinguish routine, approved, erroneous and unauthorised causes.","target":"unknown"} | |
| {"text":"Identity telemetry on ASSET-c32286d46cf22a77 recorded that a refresh token was used from a new network location. The event references principal-7482392e6af16b70. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: The resource owner and assessment coordinator confirm permission existed beforehand and activity stayed within scope. A preapproved security validation record lists the technique, test identity and affected resource. The controlling record is a security engagement rather than an operations change or ordinary workflow.","target":"authorised_testing"} | |
| {"text":"macOS security telemetry on ASSET-bdac430ee3d8f240 recorded that a system extension was loaded. The event references principal-a71c59b5c3e1bdd9. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: This is documented maintenance rather than a security exercise or recurring business workflow. A change control record approved before execution names this operator, target and requested operation. Execution occurs inside the authorised window and verification checks match the planned outcome.","target":"expected_admin"} | |
| {"text":"Endpoint security telemetry on ASSET-0b357e20610a5fb7 recorded that an endpoint protection exclusion was created. The event references principal-e1bbd626857b07af. Business context: production platform operations. The event occurred during a routine service period. Evidence: Investigators verify the anomaly without establishing credential theft or hostile control. The action is a clear departure from prior activity for this identity and remains unaccounted for. No operations change, assessment engagement or reproducible configuration issue explains it.","target":"suspicious"} | |
| {"text":"macOS security telemetry on ASSET-bdac430ee3d8f240 recorded that a system extension was loaded. The event references principal-a71c59b5c3e1bdd9. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Execution matches the authorised assessment window, test identity and listed targets. The engagement plan identifies the observed action as an in scope assessment step. This action is justified by assessment scope, not maintenance or a configuration correction.","target":"authorised_testing"} | |
| {"text":"Registry telemetry on ASSET-12375d2acdd5c83c recorded that a logon start registry entry was created. The event references principal-82275ea6f7900f1a. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: Business system records identify the action as part of a recurring workflow already used by this team. The business owner confirms the purpose and downstream records show the normal result. It is not tied to maintenance, a security exercise or a configuration correction.","target":"benign"} | |
| {"text":"macOS security telemetry on ASSET-587baa850a4db605 recorded that a system extension was loaded. The event references principal-fb6516f42fcbcfe2. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: A reliable disposition cannot be established without missing corroboration. Both authorised and unauthorised explanations remain plausible from the surviving material. Key identity and timing evidence is unavailable while remaining records conflict.","target":"unknown"} | |
| {"text":"Identity telemetry on ASSET-791a839682be1692 recorded that a refresh token was used from a new network location. The event references principal-d9496fe520292c09. Business context: production platform operations. The event occurred during a routine service period. Evidence: A reliable disposition cannot be established without missing corroboration. Both authorised and unauthorised explanations remain plausible from the surviving material. Key identity and timing evidence is unavailable while remaining records conflict.","target":"unknown"} | |
| {"text":"Identity telemetry on ASSET-3425b69fbdfab7e6 recorded that a refresh token was used from a new network location. The event references principal-9fa4e0696ae4fe07. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: This action is justified by assessment scope, not maintenance or a configuration correction. Execution matches the authorised assessment window, test identity and listed targets. The engagement plan identifies the observed action as an in scope assessment step.","target":"authorised_testing"} | |
| {"text":"Device control telemetry on ASSET-6c043b46458f7c8a recorded that a removable storage device was mounted. The event references principal-c5abfb1e9d8d9902. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: Neither change control nor security assessment records provide authorisation. A forensic timeline traces this action to a token conclusively recovered from an intruder controlled session. The owner confirms the operation exceeded authorised resource scope.","target":"malicious"} | |
| {"text":"Registry telemetry on ASSET-1e7cb34006b816e1 recorded that a logon start registry entry was created. The event references principal-030b4d8a5377e36c. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: The maintenance record explicitly covers the action and affected resource. Authorisation comes from operational change control, not an assessment engagement. Operations audit independently confirms operator, scope, timing and successful requested state.","target":"expected_admin"} | |
| {"text":"Software management telemetry on ASSET-f2f2d49fc14cce3a recorded that a package was installed on a managed endpoint. The event references principal-81eb77e2008fdfd9. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: A reliable disposition cannot be established without missing corroboration. Both authorised and unauthorised explanations remain plausible from the surviving material. Key identity and timing evidence is unavailable while remaining records conflict.","target":"unknown"} | |
| {"text":"Session telemetry on ASSET-926cbea91206be7b recorded that the same session token appeared from different client addresses. The event references principal-f1087c5e5eb18984. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: It is not tied to maintenance, a security exercise or a configuration correction. The business owner confirms the purpose and downstream records show the normal result. Business system records identify the action as part of a recurring workflow already used by this team.","target":"benign"} | |
| {"text":"Session telemetry on ASSET-926cbea91206be7b recorded that the same session token appeared from different client addresses. The event references principal-f1087c5e5eb18984. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Key identity and timing evidence is unavailable while remaining records conflict. A reliable disposition cannot be established without missing corroboration. Both authorised and unauthorised explanations remain plausible from the surviving material.","target":"unknown"} | |
| {"text":"Endpoint security telemetry on ASSET-e83f6274411aaa6d recorded that an endpoint protection exclusion was created. The event references principal-e6554316398adcdc. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: The engagement plan identifies the observed action as an in scope assessment step. This action is justified by assessment scope, not maintenance or a configuration correction. Execution matches the authorised assessment window, test identity and listed targets.","target":"authorised_testing"} | |
| {"text":"Authentication telemetry on ASSET-8cf90cff1a6cb992 recorded that a principal requested an unusual number of service tickets. The event references principal-771b0d2efb9a5186. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: Operations audit independently confirms operator, scope, timing and successful requested state. The maintenance record explicitly covers the action and affected resource. Authorisation comes from operational change control, not an assessment engagement.","target":"expected_admin"} | |
| {"text":"Authentication telemetry on ASSET-384932eeebedeb57 recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-e0b285e79e60c451. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: The business owner confirms the purpose and downstream records show the normal result. It is not tied to maintenance, a security exercise or a configuration correction. Business system records identify the action as part of a recurring workflow already used by this team.","target":"benign"} | |
| {"text":"Endpoint security telemetry on ASSET-7e53d3e4e297766b recorded that an endpoint protection exclusion was created. The event references principal-86e0d09fd796b1f9. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Correcting the value prevents recurrence while preserving intended workload behaviour. Review finds no evidence of account compromise or unauthorised control. A controlled reproduction generates the same event only when an incorrect configuration value is present.","target":"misconfiguration"} | |
| {"text":"Identity telemetry on ASSET-c9e5007dceb66f51 recorded that a refresh token was used from a new network location. The event references principal-23fb944802ed7c95. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: The event aligns with the established application process, normal identity and expected resource scope. No administrator change, test engagement or settings fault is required to explain it. Independent workflow records corroborate ordinary use and expected completion.","target":"benign"} | |
| {"text":"macOS security telemetry on ASSET-daf3ffb9d8aa9b1d recorded that a system extension was loaded. The event references principal-2663849fde66787e. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: No approved operations work, normal business process or sanctioned assessment covers it. Access policy and the owner agree that the initiating identity lacked permission for this operation. Responder confirmed compromise predates the event and session correlation ties this action to that compromised control path.","target":"malicious"} | |
| {"text":"Device control telemetry on ASSET-10321812fb8412ae recorded that a removable storage device was mounted. The event references principal-5642e2e1a1479b48. Business context: production platform operations. The event occurred during a routine service period. Evidence: The deviation is real, but compromise is not established. Independent telemetry confirms unusual scope and sequence that the responsible team cannot explain. Maintenance, test and settings records provide no verified explanation.","target":"suspicious"} | |
| {"text":"Device control telemetry on ASSET-af254892f4cef978 recorded that a removable storage device was mounted. The event references principal-c8f4d8895c66119b. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: The controlling record is a security engagement rather than an operations change or ordinary workflow. A preapproved security validation record lists the technique, test identity and affected resource. The resource owner and assessment coordinator confirm permission existed beforehand and activity stayed within scope.","target":"authorised_testing"} | |
| {"text":"Authentication telemetry on ASSET-5e68633aa4272d07 recorded that a principal requested an unusual number of service tickets. The event references principal-a3a1c3419e57c2b9. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Retained sources disagree on attribution and the missing source cannot be reconstructed. The evidence does not support choosing a stronger conclusion. Available evidence cannot distinguish routine, approved, erroneous and unauthorised causes.","target":"unknown"} | |
| {"text":"Software management telemetry on ASSET-7843b4a839c3e633 recorded that a package was installed on a managed endpoint. The event references principal-8dd235eee07bf8d4. Business context: production platform operations. The event occurred during a routine service period. Evidence: Engineers isolate an unintended setting and reproduce the action under controlled replay. Attribution records do not support an unauthorised actor as the cause. The corrected configuration produces the intended outcome and the alert does not recur.","target":"misconfiguration"} | |
| {"text":"macOS security telemetry on ASSET-cf2bf4132c332f02 recorded that a system extension was loaded. The event references principal-b7f804e447bbee6d. Business context: production platform operations. The event occurred during a routine service period. Evidence: A change control record approved before execution names this operator, target and requested operation. This is documented maintenance rather than a security exercise or recurring business workflow. Execution occurs inside the authorised window and verification checks match the planned outcome.","target":"expected_admin"} | |
| {"text":"macOS security telemetry on ASSET-daf3ffb9d8aa9b1d recorded that a system extension was loaded. The event references principal-2663849fde66787e. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: Engineers isolate an unintended setting and reproduce the action under controlled replay. Attribution records do not support an unauthorised actor as the cause. The corrected configuration produces the intended outcome and the alert does not recur.","target":"misconfiguration"} | |
| {"text":"Device control telemetry on ASSET-10321812fb8412ae recorded that a removable storage device was mounted. The event references principal-5642e2e1a1479b48. Business context: production platform operations. The event occurred during a routine service period. Evidence: A reliable disposition cannot be established without missing corroboration. Key identity and timing evidence is unavailable while remaining records conflict. Both authorised and unauthorised explanations remain plausible from the surviving material.","target":"unknown"} | |
| {"text":"Endpoint security telemetry on ASSET-160e6026e1614ce4 recorded that an endpoint protection exclusion was created. The event references principal-a5a9164c0612b141. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: The maintenance record explicitly covers the action and affected resource. Operations audit independently confirms operator, scope, timing and successful requested state. Authorisation comes from operational change control, not an assessment engagement.","target":"expected_admin"} | |
| {"text":"File audit telemetry on ASSET-7f9c55b3dbd9e2db recorded that a shell startup profile gained an additional command. The event references principal-59b6261d348cafc2. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: Business system records identify the action as part of a recurring workflow already used by this team. The business owner confirms the purpose and downstream records show the normal result. It is not tied to maintenance, a security exercise or a configuration correction.","target":"benign"} | |
| {"text":"Device control telemetry on ASSET-259ab04dcd3e71c8 recorded that a removable storage device was mounted. The event references principal-736440c29d2c2ffc. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: Key identity and timing evidence is unavailable while remaining records conflict. Both authorised and unauthorised explanations remain plausible from the surviving material. A reliable disposition cannot be established without missing corroboration.","target":"unknown"} | |
| {"text":"Endpoint security telemetry on ASSET-75ff6bb05605e6fb recorded that an endpoint protection exclusion was created. The event references principal-76e700dc719d3b69. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: Both authorised and unauthorised explanations remain plausible from the surviving material. Key identity and timing evidence is unavailable while remaining records conflict. A reliable disposition cannot be established without missing corroboration.","target":"unknown"} | |
| {"text":"Software management telemetry on ASSET-06e87c8ba3d49d7f recorded that a package was installed on a managed endpoint. The event references principal-0e15aa0fe26d14ba. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: Access policy and the owner agree that the initiating identity lacked permission for this operation. No approved operations work, normal business process or sanctioned assessment covers it. Responder confirmed compromise predates the event and session correlation ties this action to that compromised control path.","target":"malicious"} | |
| {"text":"Software management telemetry on ASSET-32df6ce14eab6663 recorded that a package was installed on a managed endpoint. The event references principal-23ffd379ff47e0ee. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: This action is justified by assessment scope, not maintenance or a configuration correction. Execution matches the authorised assessment window, test identity and listed targets. The engagement plan identifies the observed action as an in scope assessment step.","target":"authorised_testing"} | |
| {"text":"Device control telemetry on ASSET-7df9d0278b9bd4a7 recorded that a removable storage device was mounted. The event references principal-9a4767494da5d5a5. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: Attribution records do not support an unauthorised actor as the cause. Engineers isolate an unintended setting and reproduce the action under controlled replay. The corrected configuration produces the intended outcome and the alert does not recur.","target":"misconfiguration"} | |
| {"text":"Authentication telemetry on ASSET-2f156a171e44e4a2 recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-4fcc4eb2ba23ea73. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: The controlling record is a security engagement rather than an operations change or ordinary workflow. A preapproved security validation record lists the technique, test identity and affected resource. The resource owner and assessment coordinator confirm permission existed beforehand and activity stayed within scope.","target":"authorised_testing"} | |
| {"text":"Registry telemetry on ASSET-1e7cb34006b816e1 recorded that a logon start registry entry was created. The event references principal-030b4d8a5377e36c. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: Correcting the value prevents recurrence while preserving intended workload behaviour. Review finds no evidence of account compromise or unauthorised control. A controlled reproduction generates the same event only when an incorrect configuration value is present.","target":"misconfiguration"} | |
| {"text":"Authentication telemetry on ASSET-548e4c710d1107ac recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-6fe9774ae0c36a6b. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: No approved operations work, normal business process or sanctioned assessment covers it. Responder confirmed compromise predates the event and session correlation ties this action to that compromised control path. Access policy and the owner agree that the initiating identity lacked permission for this operation.","target":"malicious"} | |
| {"text":"Authentication telemetry on ASSET-8cf90cff1a6cb992 recorded that a principal requested an unusual number of service tickets. The event references principal-771b0d2efb9a5186. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: The business owner confirms the purpose and downstream records show the normal result. Business system records identify the action as part of a recurring workflow already used by this team. It is not tied to maintenance, a security exercise or a configuration correction.","target":"benign"} | |
| {"text":"Authentication telemetry on ASSET-5e68633aa4272d07 recorded that a principal requested an unusual number of service tickets. The event references principal-a3a1c3419e57c2b9. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: The event aligns with the established application process, normal identity and expected resource scope. No administrator change, test engagement or settings fault is required to explain it. Independent workflow records corroborate ordinary use and expected completion.","target":"benign"} | |
| {"text":"Identity telemetry on ASSET-791a839682be1692 recorded that a refresh token was used from a new network location. The event references principal-d9496fe520292c09. Business context: production platform operations. The event occurred during a routine service period. Evidence: Business system records identify the action as part of a recurring workflow already used by this team. It is not tied to maintenance, a security exercise or a configuration correction. The business owner confirms the purpose and downstream records show the normal result.","target":"benign"} | |
| {"text":"Device control telemetry on ASSET-7df9d0278b9bd4a7 recorded that a removable storage device was mounted. The event references principal-9a4767494da5d5a5. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: Investigators verify the anomaly without establishing credential theft or hostile control. No operations change, assessment engagement or reproducible configuration issue explains it. The action is a clear departure from prior activity for this identity and remains unaccounted for.","target":"suspicious"} | |
| {"text":"Authentication telemetry on ASSET-f1b4768b1ee1bd7b recorded that a principal requested an unusual number of service tickets. The event references principal-2d35dcb74491ee63. Business context: production platform operations. The event occurred during a routine service period. Evidence: This action is justified by assessment scope, not maintenance or a configuration correction. The engagement plan identifies the observed action as an in scope assessment step. Execution matches the authorised assessment window, test identity and listed targets.","target":"authorised_testing"} | |
| {"text":"Identity telemetry on ASSET-c32286d46cf22a77 recorded that a refresh token was used from a new network location. The event references principal-7482392e6af16b70. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: This is documented maintenance rather than a security exercise or recurring business workflow. Execution occurs inside the authorised window and verification checks match the planned outcome. A change control record approved before execution names this operator, target and requested operation.","target":"expected_admin"} | |
| {"text":"Endpoint security telemetry on ASSET-160e6026e1614ce4 recorded that an endpoint protection exclusion was created. The event references principal-a5a9164c0612b141. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: Both authorised and unauthorised explanations remain plausible from the surviving material. A reliable disposition cannot be established without missing corroboration. Key identity and timing evidence is unavailable while remaining records conflict.","target":"unknown"} | |
| {"text":"Software management telemetry on ASSET-ea03e3935a4440a1 recorded that a package was installed on a managed endpoint. The event references principal-4576ae7a9839e853. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Attribution records do not support an unauthorised actor as the cause. The corrected configuration produces the intended outcome and the alert does not recur. Engineers isolate an unintended setting and reproduce the action under controlled replay.","target":"misconfiguration"} | |
| {"text":"macOS security telemetry on ASSET-587baa850a4db605 recorded that a system extension was loaded. The event references principal-fb6516f42fcbcfe2. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: The deviation is real, but compromise is not established. Independent telemetry confirms unusual scope and sequence that the responsible team cannot explain. Maintenance, test and settings records provide no verified explanation.","target":"suspicious"} | |
| {"text":"Identity telemetry on ASSET-c9e5007dceb66f51 recorded that a refresh token was used from a new network location. The event references principal-23fb944802ed7c95. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: Independent telemetry confirms unusual scope and sequence that the responsible team cannot explain. Maintenance, test and settings records provide no verified explanation. The deviation is real, but compromise is not established.","target":"suspicious"} | |
| {"text":"Software management telemetry on ASSET-946283b501ad60f2 recorded that a package was installed on a managed endpoint. The event references principal-3a055ab31c161145. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: Operations audit independently confirms operator, scope, timing and successful requested state. The maintenance record explicitly covers the action and affected resource. Authorisation comes from operational change control, not an assessment engagement.","target":"expected_admin"} | |
| {"text":"macOS security telemetry on ASSET-a16d729bf97e1d4d recorded that a system extension was loaded. The event references principal-9ead5e0a2f20aaad. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: The evidence does not support choosing a stronger conclusion. Available evidence cannot distinguish routine, approved, erroneous and unauthorised causes. Retained sources disagree on attribution and the missing source cannot be reconstructed.","target":"unknown"} | |
| {"text":"Endpoint security telemetry on ASSET-db6194ae20a3b5bb recorded that an endpoint protection exclusion was created. The event references principal-d91aeef0e18e03dd. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: Investigators verify the anomaly without establishing credential theft or hostile control. The action is a clear departure from prior activity for this identity and remains unaccounted for. No operations change, assessment engagement or reproducible configuration issue explains it.","target":"suspicious"} | |
| {"text":"Endpoint security telemetry on ASSET-7e53d3e4e297766b recorded that an endpoint protection exclusion was created. The event references principal-86e0d09fd796b1f9. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: It is not tied to maintenance, a security exercise or a configuration correction. Business system records identify the action as part of a recurring workflow already used by this team. The business owner confirms the purpose and downstream records show the normal result.","target":"benign"} | |
| {"text":"Session telemetry on ASSET-6cd03581f6091ff2 recorded that the same session token appeared from different client addresses. The event references principal-b11813f0e5d8f95b. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: The event aligns with the established application process, normal identity and expected resource scope. No administrator change, test engagement or settings fault is required to explain it. Independent workflow records corroborate ordinary use and expected completion.","target":"benign"} | |
| {"text":"File audit telemetry on ASSET-2d0f26265383a3e9 recorded that a shell startup profile gained an additional command. The event references principal-c496e6a38f3f9b56. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: A preapproved security validation record lists the technique, test identity and affected resource. The resource owner and assessment coordinator confirm permission existed beforehand and activity stayed within scope. The controlling record is a security engagement rather than an operations change or ordinary workflow.","target":"authorised_testing"} | |
| {"text":"Registry telemetry on ASSET-4938f25ac72b185c recorded that a logon start registry entry was created. The event references principal-fba84b98a4c57ccd. Business context: production platform operations. The event occurred during a routine service period. Evidence: The controlling record is a security engagement rather than an operations change or ordinary workflow. A preapproved security validation record lists the technique, test identity and affected resource. The resource owner and assessment coordinator confirm permission existed beforehand and activity stayed within scope.","target":"authorised_testing"} | |
| {"text":"Software management telemetry on ASSET-ea03e3935a4440a1 recorded that a package was installed on a managed endpoint. The event references principal-4576ae7a9839e853. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Access policy and the owner agree that the initiating identity lacked permission for this operation. Responder confirmed compromise predates the event and session correlation ties this action to that compromised control path. No approved operations work, normal business process or sanctioned assessment covers it.","target":"malicious"} | |
| {"text":"Device control telemetry on ASSET-6c043b46458f7c8a recorded that a removable storage device was mounted. The event references principal-c5abfb1e9d8d9902. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: Both authorised and unauthorised explanations remain plausible from the surviving material. A reliable disposition cannot be established without missing corroboration. Key identity and timing evidence is unavailable while remaining records conflict.","target":"unknown"} | |
| {"text":"Identity telemetry on ASSET-b2bd654cd5ab023a recorded that a refresh token was used from a new network location. The event references principal-73aee0a8494cc453. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: The controlling record is a security engagement rather than an operations change or ordinary workflow. The resource owner and assessment coordinator confirm permission existed beforehand and activity stayed within scope. A preapproved security validation record lists the technique, test identity and affected resource.","target":"authorised_testing"} | |
| {"text":"Software management telemetry on ASSET-06e87c8ba3d49d7f recorded that a package was installed on a managed endpoint. The event references principal-0e15aa0fe26d14ba. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: The event aligns with the established application process, normal identity and expected resource scope. No administrator change, test engagement or settings fault is required to explain it. Independent workflow records corroborate ordinary use and expected completion.","target":"benign"} | |
| {"text":"macOS security telemetry on ASSET-49e92eb9ee86195a recorded that a system extension was loaded. The event references principal-2cead65e8d2af689. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: The controlling record is a security engagement rather than an operations change or ordinary workflow. The resource owner and assessment coordinator confirm permission existed beforehand and activity stayed within scope. A preapproved security validation record lists the technique, test identity and affected resource.","target":"authorised_testing"} | |
| {"text":"Endpoint security telemetry on ASSET-7e53d3e4e297766b recorded that an endpoint protection exclusion was created. The event references principal-86e0d09fd796b1f9. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: A reliable disposition cannot be established without missing corroboration. Key identity and timing evidence is unavailable while remaining records conflict. Both authorised and unauthorised explanations remain plausible from the surviving material.","target":"unknown"} | |
| {"text":"Session telemetry on ASSET-6cd03581f6091ff2 recorded that the same session token appeared from different client addresses. The event references principal-b11813f0e5d8f95b. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: Key identity and timing evidence is unavailable while remaining records conflict. Both authorised and unauthorised explanations remain plausible from the surviving material. A reliable disposition cannot be established without missing corroboration.","target":"unknown"} | |
| {"text":"Identity telemetry on ASSET-c9e5007dceb66f51 recorded that a refresh token was used from a new network location. The event references principal-23fb944802ed7c95. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: The engagement plan identifies the observed action as an in scope assessment step. This action is justified by assessment scope, not maintenance or a configuration correction. Execution matches the authorised assessment window, test identity and listed targets.","target":"authorised_testing"} | |
| {"text":"Authentication telemetry on ASSET-f1b4768b1ee1bd7b recorded that a principal requested an unusual number of service tickets. The event references principal-2d35dcb74491ee63. Business context: production platform operations. The event occurred during a routine service period. Evidence: Available evidence cannot distinguish routine, approved, erroneous and unauthorised causes. The evidence does not support choosing a stronger conclusion. Retained sources disagree on attribution and the missing source cannot be reconstructed.","target":"unknown"} | |
| {"text":"Authentication telemetry on ASSET-acf343492ca3e416 recorded that a principal requested an unusual number of service tickets. The event references principal-4cddd26b2e55cccf. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: A change control record approved before execution names this operator, target and requested operation. This is documented maintenance rather than a security exercise or recurring business workflow. Execution occurs inside the authorised window and verification checks match the planned outcome.","target":"expected_admin"} | |
| {"text":"Identity telemetry on ASSET-c32286d46cf22a77 recorded that a refresh token was used from a new network location. The event references principal-7482392e6af16b70. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: Investigators verify the anomaly without establishing credential theft or hostile control. No operations change, assessment engagement or reproducible configuration issue explains it. The action is a clear departure from prior activity for this identity and remains unaccounted for.","target":"suspicious"} | |
| {"text":"Registry telemetry on ASSET-181916903bb96a17 recorded that a logon start registry entry was created. The event references principal-53c6c1059b4ce6f8. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: The owner confirms the operation exceeded authorised resource scope. A forensic timeline traces this action to a token conclusively recovered from an intruder controlled session. Neither change control nor security assessment records provide authorisation.","target":"malicious"} | |
| {"text":"Software management telemetry on ASSET-f2f2d49fc14cce3a recorded that a package was installed on a managed endpoint. The event references principal-81eb77e2008fdfd9. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: The maintenance record explicitly covers the action and affected resource. Operations audit independently confirms operator, scope, timing and successful requested state. Authorisation comes from operational change control, not an assessment engagement.","target":"expected_admin"} | |
| {"text":"Registry telemetry on ASSET-181916903bb96a17 recorded that a logon start registry entry was created. The event references principal-53c6c1059b4ce6f8. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: The corrected configuration produces the intended outcome and the alert does not recur. Engineers isolate an unintended setting and reproduce the action under controlled replay. Attribution records do not support an unauthorised actor as the cause.","target":"misconfiguration"} | |
| {"text":"Software management telemetry on ASSET-06e87c8ba3d49d7f recorded that a package was installed on a managed endpoint. The event references principal-0e15aa0fe26d14ba. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: A controlled reproduction generates the same event only when an incorrect configuration value is present. Review finds no evidence of account compromise or unauthorised control. Correcting the value prevents recurrence while preserving intended workload behaviour.","target":"misconfiguration"} | |
| {"text":"Device control telemetry on ASSET-af254892f4cef978 recorded that a removable storage device was mounted. The event references principal-c8f4d8895c66119b. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: Authorisation comes from operational change control, not an assessment engagement. Operations audit independently confirms operator, scope, timing and successful requested state. The maintenance record explicitly covers the action and affected resource.","target":"expected_admin"} | |
| {"text":"Authentication telemetry on ASSET-6db2c84b2223d2a6 recorded that a principal requested an unusual number of service tickets. The event references principal-2d3de75c1517cbb8. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: Review finds no evidence of account compromise or unauthorised control. Correcting the value prevents recurrence while preserving intended workload behaviour. A controlled reproduction generates the same event only when an incorrect configuration value is present.","target":"misconfiguration"} | |
| {"text":"Endpoint security telemetry on ASSET-db6194ae20a3b5bb recorded that an endpoint protection exclusion was created. The event references principal-d91aeef0e18e03dd. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: Available evidence cannot distinguish routine, approved, erroneous and unauthorised causes. Retained sources disagree on attribution and the missing source cannot be reconstructed. The evidence does not support choosing a stronger conclusion.","target":"unknown"} | |
| {"text":"File audit telemetry on ASSET-70dbeadf16553ad5 recorded that a shell startup profile gained an additional command. The event references principal-a133c5d9cfe383ed. Business context: production platform operations. The event occurred during a routine service period. Evidence: A preapproved security validation record lists the technique, test identity and affected resource. The controlling record is a security engagement rather than an operations change or ordinary workflow. The resource owner and assessment coordinator confirm permission existed beforehand and activity stayed within scope.","target":"authorised_testing"} | |
| {"text":"Identity telemetry on ASSET-c9e5007dceb66f51 recorded that a refresh token was used from a new network location. The event references principal-23fb944802ed7c95. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: This is documented maintenance rather than a security exercise or recurring business workflow. Execution occurs inside the authorised window and verification checks match the planned outcome. A change control record approved before execution names this operator, target and requested operation.","target":"expected_admin"} | |
| {"text":"Session telemetry on ASSET-27aed1797a5563b5 recorded that the same session token appeared from different client addresses. The event references principal-e56850509a38c06d. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: A controlled reproduction generates the same event only when an incorrect configuration value is present. Review finds no evidence of account compromise or unauthorised control. Correcting the value prevents recurrence while preserving intended workload behaviour.","target":"misconfiguration"} | |
| {"text":"Identity telemetry on ASSET-c9e5007dceb66f51 recorded that a refresh token was used from a new network location. The event references principal-23fb944802ed7c95. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: A reliable disposition cannot be established without missing corroboration. Both authorised and unauthorised explanations remain plausible from the surviving material. Key identity and timing evidence is unavailable while remaining records conflict.","target":"unknown"} | |
| {"text":"Identity telemetry on ASSET-3425b69fbdfab7e6 recorded that a refresh token was used from a new network location. The event references principal-9fa4e0696ae4fe07. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: The owner confirms the operation exceeded authorised resource scope. A forensic timeline traces this action to a token conclusively recovered from an intruder controlled session. Neither change control nor security assessment records provide authorisation.","target":"malicious"} | |
| {"text":"macOS security telemetry on ASSET-bdac430ee3d8f240 recorded that a system extension was loaded. The event references principal-a71c59b5c3e1bdd9. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Independent telemetry confirms unusual scope and sequence that the responsible team cannot explain. The deviation is real, but compromise is not established. Maintenance, test and settings records provide no verified explanation.","target":"suspicious"} | |
| {"text":"Session telemetry on ASSET-84339bd64baee543 recorded that the same session token appeared from different client addresses. The event references principal-fbe0cdae58b1cae5. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: Independent workflow records corroborate ordinary use and expected completion. No administrator change, test engagement or settings fault is required to explain it. The event aligns with the established application process, normal identity and expected resource scope.","target":"benign"} | |
| {"text":"macOS security telemetry on ASSET-daf3ffb9d8aa9b1d recorded that a system extension was loaded. The event references principal-2663849fde66787e. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: The action is a clear departure from prior activity for this identity and remains unaccounted for. No operations change, assessment engagement or reproducible configuration issue explains it. Investigators verify the anomaly without establishing credential theft or hostile control.","target":"suspicious"} | |
| {"text":"Registry telemetry on ASSET-12375d2acdd5c83c recorded that a logon start registry entry was created. The event references principal-82275ea6f7900f1a. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: Attribution records do not support an unauthorised actor as the cause. The corrected configuration produces the intended outcome and the alert does not recur. Engineers isolate an unintended setting and reproduce the action under controlled replay.","target":"misconfiguration"} | |
| {"text":"Registry telemetry on ASSET-4938f25ac72b185c recorded that a logon start registry entry was created. The event references principal-fba84b98a4c57ccd. Business context: production platform operations. The event occurred during a routine service period. Evidence: Authorisation comes from operational change control, not an assessment engagement. Operations audit independently confirms operator, scope, timing and successful requested state. The maintenance record explicitly covers the action and affected resource.","target":"expected_admin"} | |
| {"text":"Device control telemetry on ASSET-10321812fb8412ae recorded that a removable storage device was mounted. The event references principal-5642e2e1a1479b48. Business context: production platform operations. The event occurred during a routine service period. Evidence: Authorisation comes from operational change control, not an assessment engagement. Operations audit independently confirms operator, scope, timing and successful requested state. The maintenance record explicitly covers the action and affected resource.","target":"expected_admin"} | |
| {"text":"macOS security telemetry on ASSET-587baa850a4db605 recorded that a system extension was loaded. The event references principal-fb6516f42fcbcfe2. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: Access policy and the owner agree that the initiating identity lacked permission for this operation. Responder confirmed compromise predates the event and session correlation ties this action to that compromised control path. No approved operations work, normal business process or sanctioned assessment covers it.","target":"malicious"} | |
| {"text":"Session telemetry on ASSET-b1230d6c50948f68 recorded that the same session token appeared from different client addresses. The event references principal-4a757c51da729678. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: Independent workflow records corroborate ordinary use and expected completion. No administrator change, test engagement or settings fault is required to explain it. The event aligns with the established application process, normal identity and expected resource scope.","target":"benign"} | |
| {"text":"Endpoint security telemetry on ASSET-0b357e20610a5fb7 recorded that an endpoint protection exclusion was created. The event references principal-e1bbd626857b07af. Business context: production platform operations. The event occurred during a routine service period. Evidence: Execution matches the authorised assessment window, test identity and listed targets. The engagement plan identifies the observed action as an in scope assessment step. This action is justified by assessment scope, not maintenance or a configuration correction.","target":"authorised_testing"} | |
| {"text":"Session telemetry on ASSET-9c2327f65647fb97 recorded that the same session token appeared from different client addresses. The event references principal-37639d5d3739c11a. Business context: production platform operations. The event occurred during a routine service period. Evidence: The event aligns with the established application process, normal identity and expected resource scope. No administrator change, test engagement or settings fault is required to explain it. Independent workflow records corroborate ordinary use and expected completion.","target":"benign"} | |
| {"text":"File audit telemetry on ASSET-2d0f26265383a3e9 recorded that a shell startup profile gained an additional command. The event references principal-c496e6a38f3f9b56. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Maintenance, test and settings records provide no verified explanation. Independent telemetry confirms unusual scope and sequence that the responsible team cannot explain. The deviation is real, but compromise is not established.","target":"suspicious"} | |
| {"text":"Session telemetry on ASSET-b1230d6c50948f68 recorded that the same session token appeared from different client addresses. The event references principal-4a757c51da729678. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: The action is a clear departure from prior activity for this identity and remains unaccounted for. Investigators verify the anomaly without establishing credential theft or hostile control. No operations change, assessment engagement or reproducible configuration issue explains it.","target":"suspicious"} | |
| {"text":"Software management telemetry on ASSET-946283b501ad60f2 recorded that a package was installed on a managed endpoint. The event references principal-3a055ab31c161145. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: Maintenance, test and settings records provide no verified explanation. Independent telemetry confirms unusual scope and sequence that the responsible team cannot explain. The deviation is real, but compromise is not established.","target":"suspicious"} | |
| {"text":"macOS security telemetry on ASSET-daf3ffb9d8aa9b1d recorded that a system extension was loaded. The event references principal-2663849fde66787e. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: Operations audit independently confirms operator, scope, timing and successful requested state. Authorisation comes from operational change control, not an assessment engagement. The maintenance record explicitly covers the action and affected resource.","target":"expected_admin"} | |
| {"text":"Device control telemetry on ASSET-7df9d0278b9bd4a7 recorded that a removable storage device was mounted. The event references principal-9a4767494da5d5a5. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: A preapproved security validation record lists the technique, test identity and affected resource. The resource owner and assessment coordinator confirm permission existed beforehand and activity stayed within scope. The controlling record is a security engagement rather than an operations change or ordinary workflow.","target":"authorised_testing"} | |
| {"text":"Authentication telemetry on ASSET-c872ba5f50ae32d6 recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-633558f364d854e1. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: This action is justified by assessment scope, not maintenance or a configuration correction. The engagement plan identifies the observed action as an in scope assessment step. Execution matches the authorised assessment window, test identity and listed targets.","target":"authorised_testing"} | |
| {"text":"Identity telemetry on ASSET-791a839682be1692 recorded that a refresh token was used from a new network location. The event references principal-d9496fe520292c09. Business context: production platform operations. The event occurred during a routine service period. Evidence: Execution matches the authorised assessment window, test identity and listed targets. This action is justified by assessment scope, not maintenance or a configuration correction. The engagement plan identifies the observed action as an in scope assessment step.","target":"authorised_testing"} | |
| {"text":"Session telemetry on ASSET-84339bd64baee543 recorded that the same session token appeared from different client addresses. The event references principal-fbe0cdae58b1cae5. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: Operations audit independently confirms operator, scope, timing and successful requested state. Authorisation comes from operational change control, not an assessment engagement. The maintenance record explicitly covers the action and affected resource.","target":"expected_admin"} | |
| {"text":"Identity telemetry on ASSET-b2bd654cd5ab023a recorded that a refresh token was used from a new network location. The event references principal-73aee0a8494cc453. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Engineers isolate an unintended setting and reproduce the action under controlled replay. The corrected configuration produces the intended outcome and the alert does not recur. Attribution records do not support an unauthorised actor as the cause.","target":"misconfiguration"} | |
| {"text":"Identity telemetry on ASSET-c32286d46cf22a77 recorded that a refresh token was used from a new network location. The event references principal-7482392e6af16b70. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: Retained sources disagree on attribution and the missing source cannot be reconstructed. The evidence does not support choosing a stronger conclusion. Available evidence cannot distinguish routine, approved, erroneous and unauthorised causes.","target":"unknown"} | |
| {"text":"Authentication telemetry on ASSET-6db2c84b2223d2a6 recorded that a principal requested an unusual number of service tickets. The event references principal-2d3de75c1517cbb8. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: A reliable disposition cannot be established without missing corroboration. Both authorised and unauthorised explanations remain plausible from the surviving material. Key identity and timing evidence is unavailable while remaining records conflict.","target":"unknown"} | |
| {"text":"Device control telemetry on ASSET-6c043b46458f7c8a recorded that a removable storage device was mounted. The event references principal-c5abfb1e9d8d9902. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: Independent workflow records corroborate ordinary use and expected completion. No administrator change, test engagement or settings fault is required to explain it. The event aligns with the established application process, normal identity and expected resource scope.","target":"benign"} | |
| {"text":"Authentication telemetry on ASSET-acf343492ca3e416 recorded that a principal requested an unusual number of service tickets. The event references principal-4cddd26b2e55cccf. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: A reliable disposition cannot be established without missing corroboration. Key identity and timing evidence is unavailable while remaining records conflict. Both authorised and unauthorised explanations remain plausible from the surviving material.","target":"unknown"} | |
| {"text":"macOS security telemetry on ASSET-bdac430ee3d8f240 recorded that a system extension was loaded. The event references principal-a71c59b5c3e1bdd9. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Available evidence cannot distinguish routine, approved, erroneous and unauthorised causes. The evidence does not support choosing a stronger conclusion. Retained sources disagree on attribution and the missing source cannot be reconstructed.","target":"unknown"} | |
| {"text":"Device control telemetry on ASSET-af254892f4cef978 recorded that a removable storage device was mounted. The event references principal-c8f4d8895c66119b. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: Both authorised and unauthorised explanations remain plausible from the surviving material. A reliable disposition cannot be established without missing corroboration. Key identity and timing evidence is unavailable while remaining records conflict.","target":"unknown"} | |
| {"text":"Identity telemetry on ASSET-b2bd654cd5ab023a recorded that a refresh token was used from a new network location. The event references principal-73aee0a8494cc453. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: A forensic timeline traces this action to a token conclusively recovered from an intruder controlled session. The owner confirms the operation exceeded authorised resource scope. Neither change control nor security assessment records provide authorisation.","target":"malicious"} | |
| {"text":"File audit telemetry on ASSET-cf3be86beac0dee3 recorded that a shell startup profile gained an additional command. The event references principal-269542d8ca3527cd. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: No administrator change, test engagement or settings fault is required to explain it. Independent workflow records corroborate ordinary use and expected completion. The event aligns with the established application process, normal identity and expected resource scope.","target":"benign"} | |
| {"text":"File audit telemetry on ASSET-2d0f26265383a3e9 recorded that a shell startup profile gained an additional command. The event references principal-c496e6a38f3f9b56. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Neither change control nor security assessment records provide authorisation. A forensic timeline traces this action to a token conclusively recovered from an intruder controlled session. The owner confirms the operation exceeded authorised resource scope.","target":"malicious"} | |
| {"text":"Identity telemetry on ASSET-1a0546d031ade59d recorded that a refresh token was used from a new network location. The event references principal-9b0ea911c4279184. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: Execution occurs inside the authorised window and verification checks match the planned outcome. This is documented maintenance rather than a security exercise or recurring business workflow. A change control record approved before execution names this operator, target and requested operation.","target":"expected_admin"} | |
| {"text":"File audit telemetry on ASSET-70dbeadf16553ad5 recorded that a shell startup profile gained an additional command. The event references principal-a133c5d9cfe383ed. Business context: production platform operations. The event occurred during a routine service period. Evidence: The maintenance record explicitly covers the action and affected resource. Operations audit independently confirms operator, scope, timing and successful requested state. Authorisation comes from operational change control, not an assessment engagement.","target":"expected_admin"} | |
| {"text":"Device control telemetry on ASSET-6c043b46458f7c8a recorded that a removable storage device was mounted. The event references principal-c5abfb1e9d8d9902. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: Attribution records do not support an unauthorised actor as the cause. The corrected configuration produces the intended outcome and the alert does not recur. Engineers isolate an unintended setting and reproduce the action under controlled replay.","target":"misconfiguration"} | |
| {"text":"Session telemetry on ASSET-27aed1797a5563b5 recorded that the same session token appeared from different client addresses. The event references principal-e56850509a38c06d. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: The owner confirms the operation exceeded authorised resource scope. A forensic timeline traces this action to a token conclusively recovered from an intruder controlled session. Neither change control nor security assessment records provide authorisation.","target":"malicious"} | |
| {"text":"Device control telemetry on ASSET-259ab04dcd3e71c8 recorded that a removable storage device was mounted. The event references principal-736440c29d2c2ffc. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: Execution matches the authorised assessment window, test identity and listed targets. This action is justified by assessment scope, not maintenance or a configuration correction. The engagement plan identifies the observed action as an in scope assessment step.","target":"authorised_testing"} | |
| {"text":"Session telemetry on ASSET-9c2327f65647fb97 recorded that the same session token appeared from different client addresses. The event references principal-37639d5d3739c11a. Business context: production platform operations. The event occurred during a routine service period. Evidence: Execution occurs inside the authorised window and verification checks match the planned outcome. This is documented maintenance rather than a security exercise or recurring business workflow. A change control record approved before execution names this operator, target and requested operation.","target":"expected_admin"} | |
| {"text":"Authentication telemetry on ASSET-a15a854111323f76 recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-cb2a201458ef6079. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: Key identity and timing evidence is unavailable while remaining records conflict. A reliable disposition cannot be established without missing corroboration. Both authorised and unauthorised explanations remain plausible from the surviving material.","target":"unknown"} | |
| {"text":"Endpoint security telemetry on ASSET-160e6026e1614ce4 recorded that an endpoint protection exclusion was created. The event references principal-a5a9164c0612b141. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: Independent workflow records corroborate ordinary use and expected completion. The event aligns with the established application process, normal identity and expected resource scope. No administrator change, test engagement or settings fault is required to explain it.","target":"benign"} | |
| {"text":"Authentication telemetry on ASSET-f1b4768b1ee1bd7b recorded that a principal requested an unusual number of service tickets. The event references principal-2d35dcb74491ee63. Business context: production platform operations. The event occurred during a routine service period. Evidence: A controlled reproduction generates the same event only when an incorrect configuration value is present. Correcting the value prevents recurrence while preserving intended workload behaviour. Review finds no evidence of account compromise or unauthorised control.","target":"misconfiguration"} | |
| {"text":"Session telemetry on ASSET-27aed1797a5563b5 recorded that the same session token appeared from different client addresses. The event references principal-e56850509a38c06d. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: The deviation is real, but compromise is not established. Independent telemetry confirms unusual scope and sequence that the responsible team cannot explain. Maintenance, test and settings records provide no verified explanation.","target":"suspicious"} | |
| {"text":"File audit telemetry on ASSET-70dbeadf16553ad5 recorded that a shell startup profile gained an additional command. The event references principal-a133c5d9cfe383ed. Business context: production platform operations. The event occurred during a routine service period. Evidence: The business owner confirms the purpose and downstream records show the normal result. It is not tied to maintenance, a security exercise or a configuration correction. Business system records identify the action as part of a recurring workflow already used by this team.","target":"benign"} | |
| {"text":"Endpoint security telemetry on ASSET-75ff6bb05605e6fb recorded that an endpoint protection exclusion was created. The event references principal-76e700dc719d3b69. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: Execution occurs inside the authorised window and verification checks match the planned outcome. A change control record approved before execution names this operator, target and requested operation. This is documented maintenance rather than a security exercise or recurring business workflow.","target":"expected_admin"} | |
| {"text":"Registry telemetry on ASSET-181916903bb96a17 recorded that a logon start registry entry was created. The event references principal-53c6c1059b4ce6f8. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: The event aligns with the established application process, normal identity and expected resource scope. Independent workflow records corroborate ordinary use and expected completion. No administrator change, test engagement or settings fault is required to explain it.","target":"benign"} | |
| {"text":"macOS security telemetry on ASSET-49e92eb9ee86195a recorded that a system extension was loaded. The event references principal-2cead65e8d2af689. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: The maintenance record explicitly covers the action and affected resource. Operations audit independently confirms operator, scope, timing and successful requested state. Authorisation comes from operational change control, not an assessment engagement.","target":"expected_admin"} | |
| {"text":"File audit telemetry on ASSET-cf3be86beac0dee3 recorded that a shell startup profile gained an additional command. The event references principal-269542d8ca3527cd. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: This is documented maintenance rather than a security exercise or recurring business workflow. Execution occurs inside the authorised window and verification checks match the planned outcome. A change control record approved before execution names this operator, target and requested operation.","target":"expected_admin"} | |
| {"text":"File audit telemetry on ASSET-70dbeadf16553ad5 recorded that a shell startup profile gained an additional command. The event references principal-a133c5d9cfe383ed. Business context: production platform operations. The event occurred during a routine service period. Evidence: The evidence does not support choosing a stronger conclusion. Available evidence cannot distinguish routine, approved, erroneous and unauthorised causes. Retained sources disagree on attribution and the missing source cannot be reconstructed.","target":"unknown"} | |
| {"text":"Device control telemetry on ASSET-ebb2be94ec626240 recorded that a removable storage device was mounted. The event references principal-f26b6fc008fdefc3. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Engineers isolate an unintended setting and reproduce the action under controlled replay. Attribution records do not support an unauthorised actor as the cause. The corrected configuration produces the intended outcome and the alert does not recur.","target":"misconfiguration"} | |
| {"text":"Software management telemetry on ASSET-32df6ce14eab6663 recorded that a package was installed on a managed endpoint. The event references principal-23ffd379ff47e0ee. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: This is documented maintenance rather than a security exercise or recurring business workflow. A change control record approved before execution names this operator, target and requested operation. Execution occurs inside the authorised window and verification checks match the planned outcome.","target":"expected_admin"} | |
| {"text":"Registry telemetry on ASSET-0c39025cdd728b7c recorded that a logon start registry entry was created. The event references principal-b445cfc37449d009. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: It is not tied to maintenance, a security exercise or a configuration correction. Business system records identify the action as part of a recurring workflow already used by this team. The business owner confirms the purpose and downstream records show the normal result.","target":"benign"} | |
| {"text":"Session telemetry on ASSET-84339bd64baee543 recorded that the same session token appeared from different client addresses. The event references principal-fbe0cdae58b1cae5. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: Retained sources disagree on attribution and the missing source cannot be reconstructed. The evidence does not support choosing a stronger conclusion. Available evidence cannot distinguish routine, approved, erroneous and unauthorised causes.","target":"unknown"} | |
| {"text":"macOS security telemetry on ASSET-cf2bf4132c332f02 recorded that a system extension was loaded. The event references principal-b7f804e447bbee6d. Business context: production platform operations. The event occurred during a routine service period. Evidence: The resource owner and assessment coordinator confirm permission existed beforehand and activity stayed within scope. A preapproved security validation record lists the technique, test identity and affected resource. The controlling record is a security engagement rather than an operations change or ordinary workflow.","target":"authorised_testing"} | |
| {"text":"Registry telemetry on ASSET-181916903bb96a17 recorded that a logon start registry entry was created. The event references principal-53c6c1059b4ce6f8. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: This action is justified by assessment scope, not maintenance or a configuration correction. Execution matches the authorised assessment window, test identity and listed targets. The engagement plan identifies the observed action as an in scope assessment step.","target":"authorised_testing"} | |
| {"text":"Authentication telemetry on ASSET-acf343492ca3e416 recorded that a principal requested an unusual number of service tickets. The event references principal-4cddd26b2e55cccf. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: Independent workflow records corroborate ordinary use and expected completion. No administrator change, test engagement or settings fault is required to explain it. The event aligns with the established application process, normal identity and expected resource scope.","target":"benign"} | |
| {"text":"Registry telemetry on ASSET-12375d2acdd5c83c recorded that a logon start registry entry was created. The event references principal-82275ea6f7900f1a. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: The controlling record is a security engagement rather than an operations change or ordinary workflow. The resource owner and assessment coordinator confirm permission existed beforehand and activity stayed within scope. A preapproved security validation record lists the technique, test identity and affected resource.","target":"authorised_testing"} | |
| {"text":"Device control telemetry on ASSET-af254892f4cef978 recorded that a removable storage device was mounted. The event references principal-c8f4d8895c66119b. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: The business owner confirms the purpose and downstream records show the normal result. Business system records identify the action as part of a recurring workflow already used by this team. It is not tied to maintenance, a security exercise or a configuration correction.","target":"benign"} | |
| {"text":"Session telemetry on ASSET-926cbea91206be7b recorded that the same session token appeared from different client addresses. The event references principal-f1087c5e5eb18984. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Access policy and the owner agree that the initiating identity lacked permission for this operation. Responder confirmed compromise predates the event and session correlation ties this action to that compromised control path. No approved operations work, normal business process or sanctioned assessment covers it.","target":"malicious"} | |
| {"text":"Software management telemetry on ASSET-ea03e3935a4440a1 recorded that a package was installed on a managed endpoint. The event references principal-4576ae7a9839e853. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Independent workflow records corroborate ordinary use and expected completion. The event aligns with the established application process, normal identity and expected resource scope. No administrator change, test engagement or settings fault is required to explain it.","target":"benign"} | |
| {"text":"Identity telemetry on ASSET-791a839682be1692 recorded that a refresh token was used from a new network location. The event references principal-d9496fe520292c09. Business context: production platform operations. The event occurred during a routine service period. Evidence: Attribution records do not support an unauthorised actor as the cause. The corrected configuration produces the intended outcome and the alert does not recur. Engineers isolate an unintended setting and reproduce the action under controlled replay.","target":"misconfiguration"} | |
| {"text":"File audit telemetry on ASSET-70dbeadf16553ad5 recorded that a shell startup profile gained an additional command. The event references principal-a133c5d9cfe383ed. Business context: production platform operations. The event occurred during a routine service period. Evidence: Responder confirmed compromise predates the event and session correlation ties this action to that compromised control path. No approved operations work, normal business process or sanctioned assessment covers it. Access policy and the owner agree that the initiating identity lacked permission for this operation.","target":"malicious"} | |
| {"text":"Authentication telemetry on ASSET-f1b4768b1ee1bd7b recorded that a principal requested an unusual number of service tickets. The event references principal-2d35dcb74491ee63. Business context: production platform operations. The event occurred during a routine service period. Evidence: The action is a clear departure from prior activity for this identity and remains unaccounted for. No operations change, assessment engagement or reproducible configuration issue explains it. Investigators verify the anomaly without establishing credential theft or hostile control.","target":"suspicious"} | |
| {"text":"Authentication telemetry on ASSET-07ae88df5010a363 recorded that a principal requested an unusual number of service tickets. The event references principal-b13a83bf104bbe9d. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: Correcting the value prevents recurrence while preserving intended workload behaviour. Review finds no evidence of account compromise or unauthorised control. A controlled reproduction generates the same event only when an incorrect configuration value is present.","target":"misconfiguration"} | |
| {"text":"Identity telemetry on ASSET-3425b69fbdfab7e6 recorded that a refresh token was used from a new network location. The event references principal-9fa4e0696ae4fe07. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: The evidence does not support choosing a stronger conclusion. Available evidence cannot distinguish routine, approved, erroneous and unauthorised causes. Retained sources disagree on attribution and the missing source cannot be reconstructed.","target":"unknown"} | |
| {"text":"macOS security telemetry on ASSET-cf2bf4132c332f02 recorded that a system extension was loaded. The event references principal-b7f804e447bbee6d. Business context: production platform operations. The event occurred during a routine service period. Evidence: It is not tied to maintenance, a security exercise or a configuration correction. Business system records identify the action as part of a recurring workflow already used by this team. The business owner confirms the purpose and downstream records show the normal result.","target":"benign"} | |
| {"text":"Software management telemetry on ASSET-946283b501ad60f2 recorded that a package was installed on a managed endpoint. The event references principal-3a055ab31c161145. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: The event aligns with the established application process, normal identity and expected resource scope. No administrator change, test engagement or settings fault is required to explain it. Independent workflow records corroborate ordinary use and expected completion.","target":"benign"} | |
| {"text":"Identity telemetry on ASSET-1a0546d031ade59d recorded that a refresh token was used from a new network location. The event references principal-9b0ea911c4279184. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: A controlled reproduction generates the same event only when an incorrect configuration value is present. Review finds no evidence of account compromise or unauthorised control. Correcting the value prevents recurrence while preserving intended workload behaviour.","target":"misconfiguration"} | |
| {"text":"Identity telemetry on ASSET-791a839682be1692 recorded that a refresh token was used from a new network location. The event references principal-d9496fe520292c09. Business context: production platform operations. The event occurred during a routine service period. Evidence: Investigators verify the anomaly without establishing credential theft or hostile control. The action is a clear departure from prior activity for this identity and remains unaccounted for. No operations change, assessment engagement or reproducible configuration issue explains it.","target":"suspicious"} | |
| {"text":"File audit telemetry on ASSET-92d7a4b0f0832bdb recorded that a shell startup profile gained an additional command. The event references principal-416cb22cec72515c. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: Independent telemetry confirms unusual scope and sequence that the responsible team cannot explain. Maintenance, test and settings records provide no verified explanation. The deviation is real, but compromise is not established.","target":"suspicious"} | |
| {"text":"Registry telemetry on ASSET-0c39025cdd728b7c recorded that a logon start registry entry was created. The event references principal-b445cfc37449d009. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: Both authorised and unauthorised explanations remain plausible from the surviving material. A reliable disposition cannot be established without missing corroboration. Key identity and timing evidence is unavailable while remaining records conflict.","target":"unknown"} | |
| {"text":"Authentication telemetry on ASSET-c872ba5f50ae32d6 recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-633558f364d854e1. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: Investigators verify the anomaly without establishing credential theft or hostile control. No operations change, assessment engagement or reproducible configuration issue explains it. The action is a clear departure from prior activity for this identity and remains unaccounted for.","target":"suspicious"} | |
| {"text":"Device control telemetry on ASSET-10321812fb8412ae recorded that a removable storage device was mounted. The event references principal-5642e2e1a1479b48. Business context: production platform operations. The event occurred during a routine service period. Evidence: Business system records identify the action as part of a recurring workflow already used by this team. The business owner confirms the purpose and downstream records show the normal result. It is not tied to maintenance, a security exercise or a configuration correction.","target":"benign"} | |
| {"text":"File audit telemetry on ASSET-92d7a4b0f0832bdb recorded that a shell startup profile gained an additional command. The event references principal-416cb22cec72515c. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: Available evidence cannot distinguish routine, approved, erroneous and unauthorised causes. Retained sources disagree on attribution and the missing source cannot be reconstructed. The evidence does not support choosing a stronger conclusion.","target":"unknown"} | |
| {"text":"Identity telemetry on ASSET-1a0546d031ade59d recorded that a refresh token was used from a new network location. The event references principal-9b0ea911c4279184. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: This action is justified by assessment scope, not maintenance or a configuration correction. Execution matches the authorised assessment window, test identity and listed targets. The engagement plan identifies the observed action as an in scope assessment step.","target":"authorised_testing"} | |
| {"text":"File audit telemetry on ASSET-7f9c55b3dbd9e2db recorded that a shell startup profile gained an additional command. The event references principal-59b6261d348cafc2. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: Independent telemetry confirms unusual scope and sequence that the responsible team cannot explain. The deviation is real, but compromise is not established. Maintenance, test and settings records provide no verified explanation.","target":"suspicious"} | |
| {"text":"File audit telemetry on ASSET-2d0f26265383a3e9 recorded that a shell startup profile gained an additional command. The event references principal-c496e6a38f3f9b56. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Independent workflow records corroborate ordinary use and expected completion. The event aligns with the established application process, normal identity and expected resource scope. No administrator change, test engagement or settings fault is required to explain it.","target":"benign"} | |
| {"text":"Authentication telemetry on ASSET-07ae88df5010a363 recorded that a principal requested an unusual number of service tickets. The event references principal-b13a83bf104bbe9d. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: A change control record approved before execution names this operator, target and requested operation. This is documented maintenance rather than a security exercise or recurring business workflow. Execution occurs inside the authorised window and verification checks match the planned outcome.","target":"expected_admin"} | |
| {"text":"Endpoint security telemetry on ASSET-db6194ae20a3b5bb recorded that an endpoint protection exclusion was created. The event references principal-d91aeef0e18e03dd. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: No administrator change, test engagement or settings fault is required to explain it. Independent workflow records corroborate ordinary use and expected completion. The event aligns with the established application process, normal identity and expected resource scope.","target":"benign"} | |
| {"text":"Session telemetry on ASSET-9c2327f65647fb97 recorded that the same session token appeared from different client addresses. The event references principal-37639d5d3739c11a. Business context: production platform operations. The event occurred during a routine service period. Evidence: The owner confirms the operation exceeded authorised resource scope. A forensic timeline traces this action to a token conclusively recovered from an intruder controlled session. Neither change control nor security assessment records provide authorisation.","target":"malicious"} | |
| {"text":"Endpoint security telemetry on ASSET-160e6026e1614ce4 recorded that an endpoint protection exclusion was created. The event references principal-a5a9164c0612b141. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: Neither change control nor security assessment records provide authorisation. The owner confirms the operation exceeded authorised resource scope. A forensic timeline traces this action to a token conclusively recovered from an intruder controlled session.","target":"malicious"} | |
| {"text":"Device control telemetry on ASSET-ebb2be94ec626240 recorded that a removable storage device was mounted. The event references principal-f26b6fc008fdefc3. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Responder confirmed compromise predates the event and session correlation ties this action to that compromised control path. Access policy and the owner agree that the initiating identity lacked permission for this operation. No approved operations work, normal business process or sanctioned assessment covers it.","target":"malicious"} | |
| {"text":"File audit telemetry on ASSET-2d0f26265383a3e9 recorded that a shell startup profile gained an additional command. The event references principal-c496e6a38f3f9b56. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: A reliable disposition cannot be established without missing corroboration. Both authorised and unauthorised explanations remain plausible from the surviving material. Key identity and timing evidence is unavailable while remaining records conflict.","target":"unknown"} | |
| {"text":"Registry telemetry on ASSET-4938f25ac72b185c recorded that a logon start registry entry was created. The event references principal-fba84b98a4c57ccd. Business context: production platform operations. The event occurred during a routine service period. Evidence: It is not tied to maintenance, a security exercise or a configuration correction. Business system records identify the action as part of a recurring workflow already used by this team. The business owner confirms the purpose and downstream records show the normal result.","target":"benign"} | |
| {"text":"macOS security telemetry on ASSET-cf2bf4132c332f02 recorded that a system extension was loaded. The event references principal-b7f804e447bbee6d. Business context: production platform operations. The event occurred during a routine service period. Evidence: The deviation is real, but compromise is not established. Maintenance, test and settings records provide no verified explanation. Independent telemetry confirms unusual scope and sequence that the responsible team cannot explain.","target":"suspicious"} | |
| {"text":"Endpoint security telemetry on ASSET-db6194ae20a3b5bb recorded that an endpoint protection exclusion was created. The event references principal-d91aeef0e18e03dd. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: The resource owner and assessment coordinator confirm permission existed beforehand and activity stayed within scope. A preapproved security validation record lists the technique, test identity and affected resource. The controlling record is a security engagement rather than an operations change or ordinary workflow.","target":"authorised_testing"} | |
| {"text":"Registry telemetry on ASSET-4938f25ac72b185c recorded that a logon start registry entry was created. The event references principal-fba84b98a4c57ccd. Business context: production platform operations. The event occurred during a routine service period. Evidence: Review finds no evidence of account compromise or unauthorised control. A controlled reproduction generates the same event only when an incorrect configuration value is present. Correcting the value prevents recurrence while preserving intended workload behaviour.","target":"misconfiguration"} | |
| {"text":"Identity telemetry on ASSET-c9e5007dceb66f51 recorded that a refresh token was used from a new network location. The event references principal-23fb944802ed7c95. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: No approved operations work, normal business process or sanctioned assessment covers it. Responder confirmed compromise predates the event and session correlation ties this action to that compromised control path. Access policy and the owner agree that the initiating identity lacked permission for this operation.","target":"malicious"} | |
| {"text":"File audit telemetry on ASSET-7f9c55b3dbd9e2db recorded that a shell startup profile gained an additional command. The event references principal-59b6261d348cafc2. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: The controlling record is a security engagement rather than an operations change or ordinary workflow. The resource owner and assessment coordinator confirm permission existed beforehand and activity stayed within scope. A preapproved security validation record lists the technique, test identity and affected resource.","target":"authorised_testing"} | |
| {"text":"File audit telemetry on ASSET-2d0f26265383a3e9 recorded that a shell startup profile gained an additional command. The event references principal-c496e6a38f3f9b56. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Correcting the value prevents recurrence while preserving intended workload behaviour. A controlled reproduction generates the same event only when an incorrect configuration value is present. Review finds no evidence of account compromise or unauthorised control.","target":"misconfiguration"} | |
| {"text":"Software management telemetry on ASSET-32df6ce14eab6663 recorded that a package was installed on a managed endpoint. The event references principal-23ffd379ff47e0ee. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: Neither change control nor security assessment records provide authorisation. A forensic timeline traces this action to a token conclusively recovered from an intruder controlled session. The owner confirms the operation exceeded authorised resource scope.","target":"malicious"} | |
| {"text":"Authentication telemetry on ASSET-acf343492ca3e416 recorded that a principal requested an unusual number of service tickets. The event references principal-4cddd26b2e55cccf. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: Access policy and the owner agree that the initiating identity lacked permission for this operation. Responder confirmed compromise predates the event and session correlation ties this action to that compromised control path. No approved operations work, normal business process or sanctioned assessment covers it.","target":"malicious"} | |
| {"text":"Registry telemetry on ASSET-87f634c5db0bf0a4 recorded that a logon start registry entry was created. The event references principal-b4878bc054d3d019. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: This is documented maintenance rather than a security exercise or recurring business workflow. A change control record approved before execution names this operator, target and requested operation. Execution occurs inside the authorised window and verification checks match the planned outcome.","target":"expected_admin"} | |
| {"text":"macOS security telemetry on ASSET-a16d729bf97e1d4d recorded that a system extension was loaded. The event references principal-9ead5e0a2f20aaad. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: Execution matches the authorised assessment window, test identity and listed targets. The engagement plan identifies the observed action as an in scope assessment step. This action is justified by assessment scope, not maintenance or a configuration correction.","target":"authorised_testing"} | |
| {"text":"File audit telemetry on ASSET-7f9c55b3dbd9e2db recorded that a shell startup profile gained an additional command. The event references principal-59b6261d348cafc2. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: Both authorised and unauthorised explanations remain plausible from the surviving material. Key identity and timing evidence is unavailable while remaining records conflict. A reliable disposition cannot be established without missing corroboration.","target":"unknown"} | |
| {"text":"Software management telemetry on ASSET-7843b4a839c3e633 recorded that a package was installed on a managed endpoint. The event references principal-8dd235eee07bf8d4. Business context: production platform operations. The event occurred during a routine service period. Evidence: Available evidence cannot distinguish routine, approved, erroneous and unauthorised causes. The evidence does not support choosing a stronger conclusion. Retained sources disagree on attribution and the missing source cannot be reconstructed.","target":"unknown"} | |
| {"text":"Software management telemetry on ASSET-7843b4a839c3e633 recorded that a package was installed on a managed endpoint. The event references principal-8dd235eee07bf8d4. Business context: production platform operations. The event occurred during a routine service period. Evidence: Investigators verify the anomaly without establishing credential theft or hostile control. The action is a clear departure from prior activity for this identity and remains unaccounted for. No operations change, assessment engagement or reproducible configuration issue explains it.","target":"suspicious"} | |
| {"text":"File audit telemetry on ASSET-cf3be86beac0dee3 recorded that a shell startup profile gained an additional command. The event references principal-269542d8ca3527cd. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: Attribution records do not support an unauthorised actor as the cause. Engineers isolate an unintended setting and reproduce the action under controlled replay. The corrected configuration produces the intended outcome and the alert does not recur.","target":"misconfiguration"} | |
| {"text":"Identity telemetry on ASSET-b2bd654cd5ab023a recorded that a refresh token was used from a new network location. The event references principal-73aee0a8494cc453. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: The event aligns with the established application process, normal identity and expected resource scope. No administrator change, test engagement or settings fault is required to explain it. Independent workflow records corroborate ordinary use and expected completion.","target":"benign"} | |
| {"text":"Software management telemetry on ASSET-f2f2d49fc14cce3a recorded that a package was installed on a managed endpoint. The event references principal-81eb77e2008fdfd9. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: The owner confirms the operation exceeded authorised resource scope. A forensic timeline traces this action to a token conclusively recovered from an intruder controlled session. Neither change control nor security assessment records provide authorisation.","target":"malicious"} | |
| {"text":"Registry telemetry on ASSET-1e7cb34006b816e1 recorded that a logon start registry entry was created. The event references principal-030b4d8a5377e36c. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: Neither change control nor security assessment records provide authorisation. The owner confirms the operation exceeded authorised resource scope. A forensic timeline traces this action to a token conclusively recovered from an intruder controlled session.","target":"malicious"} | |
| {"text":"Authentication telemetry on ASSET-548e4c710d1107ac recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-6fe9774ae0c36a6b. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: A reliable disposition cannot be established without missing corroboration. Both authorised and unauthorised explanations remain plausible from the surviving material. Key identity and timing evidence is unavailable while remaining records conflict.","target":"unknown"} | |
| {"text":"macOS security telemetry on ASSET-a16d729bf97e1d4d recorded that a system extension was loaded. The event references principal-9ead5e0a2f20aaad. Business context: centrally managed corporate endpoints. The event occurred during normal staff activity. Evidence: No operations change, assessment engagement or reproducible configuration issue explains it. The action is a clear departure from prior activity for this identity and remains unaccounted for. Investigators verify the anomaly without establishing credential theft or hostile control.","target":"suspicious"} | |
| {"text":"Endpoint security telemetry on ASSET-db6194ae20a3b5bb recorded that an endpoint protection exclusion was created. The event references principal-d91aeef0e18e03dd. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: The maintenance record explicitly covers the action and affected resource. Authorisation comes from operational change control, not an assessment engagement. Operations audit independently confirms operator, scope, timing and successful requested state.","target":"expected_admin"} | |
| {"text":"Identity telemetry on ASSET-c32286d46cf22a77 recorded that a refresh token was used from a new network location. The event references principal-7482392e6af16b70. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: Independent workflow records corroborate ordinary use and expected completion. No administrator change, test engagement or settings fault is required to explain it. The event aligns with the established application process, normal identity and expected resource scope.","target":"benign"} | |
| {"text":"Authentication telemetry on ASSET-5e68633aa4272d07 recorded that a principal requested an unusual number of service tickets. The event references principal-a3a1c3419e57c2b9. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Execution matches the authorised assessment window, test identity and listed targets. The engagement plan identifies the observed action as an in scope assessment step. This action is justified by assessment scope, not maintenance or a configuration correction.","target":"authorised_testing"} | |
| {"text":"Authentication telemetry on ASSET-c2a6c281824dee93 recorded that multiple failed sign ins were followed by a successful sign in. The event references principal-151aed5aab3c16bb. Business context: production platform operations. The event occurred during a routine service period. Evidence: A controlled reproduction generates the same event only when an incorrect configuration value is present. Correcting the value prevents recurrence while preserving intended workload behaviour. Review finds no evidence of account compromise or unauthorised control.","target":"misconfiguration"} | |
| {"text":"Endpoint security telemetry on ASSET-75ff6bb05605e6fb recorded that an endpoint protection exclusion was created. The event references principal-76e700dc719d3b69. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: Neither change control nor security assessment records provide authorisation. The owner confirms the operation exceeded authorised resource scope. A forensic timeline traces this action to a token conclusively recovered from an intruder controlled session.","target":"malicious"} | |
| {"text":"File audit telemetry on ASSET-244b3eddb26e9638 recorded that a shell startup profile gained an additional command. The event references principal-0f3323543c67b8a9. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: Key identity and timing evidence is unavailable while remaining records conflict. Both authorised and unauthorised explanations remain plausible from the surviving material. A reliable disposition cannot be established without missing corroboration.","target":"unknown"} | |
| {"text":"Device control telemetry on ASSET-6c043b46458f7c8a recorded that a removable storage device was mounted. The event references principal-c5abfb1e9d8d9902. Business context: internal product engineering. The event occurred during an ordinary development period. Evidence: The maintenance record explicitly covers the action and affected resource. Operations audit independently confirms operator, scope, timing and successful requested state. Authorisation comes from operational change control, not an assessment engagement.","target":"expected_admin"} | |
| {"text":"Registry telemetry on ASSET-87f634c5db0bf0a4 recorded that a logon start registry entry was created. The event references principal-b4878bc054d3d019. Business context: finance and reconciliation systems. The event occurred during scheduled business processing. Evidence: Maintenance, test and settings records provide no verified explanation. Independent telemetry confirms unusual scope and sequence that the responsible team cannot explain. The deviation is real, but compromise is not established.","target":"suspicious"} | |
| {"text":"Authentication telemetry on ASSET-07ae88df5010a363 recorded that a principal requested an unusual number of service tickets. The event references principal-b13a83bf104bbe9d. Business context: workforce administration systems. The event occurred during standard employee service operations. Evidence: The deviation is real, but compromise is not established. Maintenance, test and settings records provide no verified explanation. Independent telemetry confirms unusual scope and sequence that the responsible team cannot explain.","target":"suspicious"} | |
| {"text":"File audit telemetry on ASSET-7f9c55b3dbd9e2db recorded that a shell startup profile gained an additional command. The event references principal-59b6261d348cafc2. Business context: customer operations systems. The event occurred during normal service delivery. Evidence: Responder confirmed compromise predates the event and session correlation ties this action to that compromised control path. Access policy and the owner agree that the initiating identity lacked permission for this operation. No approved operations work, normal business process or sanctioned assessment covers it.","target":"malicious"} | |