Issues for enterprises
Enclave, as per the weblog submit, famous that organizations that ran Azure SRE Agent through the preview window should deal with the interval as probably uncovered and assessment any credentials, configuration knowledge, or delicate info which will have handed by way of agent conversations or CLI outputs.
Hagenah stated agentic operations providers should be ruled extra like privileged automation platforms than strange SaaS instruments.
“Earlier than granting that degree of entry, I might need very clear solutions on tenant isolation and resource-level authorization. It shouldn’t be sufficient {that a} token is legitimate. The service has to confirm that the caller belongs to the fitting tenant, is allowed for that particular agent, and is allowed to entry that particular stream, thread, software output, or motion,” he stated.
The agent ought to run below a devoted managed id with minimal permissions, and integrations with command execution, log question, supply repositories, and incident platforms must be reviewed like some other privileged system, Hagenah stated. Enterprises additionally have to know who linked, what threads they accessed, what instructions ran, and what output was returned, with logs exportable to the SIEM. Microsoft didn’t instantly reply to a request for remark.
The article initially appeared in CSO.
