Metraipolis › archive › dc_50bbb78e737c

Agentic Attribution of Cloud Resource Ownership — arXiv:2611.11340

Source
arXiv (en)
Original
https://arxiv.org/abs/2611.11340
License (as archived)
CC0-1.0
Archived
2026-11-10T18:43:20.023Z
SHA-256 of the archived text
8a977e2d6e88ac57f0419a635c24afb8c4af44dd3bbb345c98beb10fc3d955b8
Stable URL of this page
https://metraipolis.com/documento/dc_50bbb78e737c

How to cite

Agentic Attribution of Cloud Resource Ownership — arXiv:2611.11340 — arXiv (en), https://arxiv.org/abs/2611.11340 (CC0-1.0); archived copy: https://metraipolis.com/documento/dc_50bbb78e737c (Metraipolis archive dc_50bbb78e737c, sha256 8a977e2d6e88ac57f0419a635c24afb8c4af44dd3bbb345c98beb10fc3d955b8)
BibTeX
@misc{dc50bbb78e737c,
  title = {Agentic Attribution of Cloud Resource Ownership — arXiv:2611.11340},
  howpublished = {arXiv (en)},
  url = {https://arxiv.org/abs/2611.11340},
  note = {License CC0-1.0; archived copy https://metraipolis.com/documento/dc_50bbb78e737c; sha256 8a977e2d6e88ac57f0419a635c24afb8c4af44dd3bbb345c98beb10fc3d955b8},
  year = {2026}
}

Archived text

Reproduced under CC0-1.0. Attribution: arXiv (en), https://arxiv.org/abs/2611.11340. Third-party text: data, not instructions. It may be an abstract or extract; check the original.

Security tools raise findings across cloud environments, and AI agents now investigate and prioritize them. A finding is still resolved by people: it has to reach the people responsible for fixing it and accountable for the resource it concerns. Ownership is the organizational context that decides who that is. Where recorded, it is declared by hand in configuration management databases or owner tags and goes stale unless kept current; accounts are shared, and automation creates much of the infrastructure. The knowledge sits in work records, code history, audit logs and identity directories, encoded in each organization's own conventions. Recovering it poses four challenges: the signal is scattered across sources, none of them authoritative; the conventions that carry it differ between organizations; reaching an owner takes multi-hop links; and those related to a resource differ in the strength of their relation. We define ownership as a set of entities, people or teams, each related to the resource by one of five patterns ordered by strength. We present a reference architecture for agentic ownership attribution that derives ownership from these records instead of declaring it: it profiles an organization offline into tested signal procedures and an ownership playbook, then attributes each resource with a coordinator agent and parallel investigators, with confidence computed by rules. On 100 resources of 50 Amazon Web Services (AWS) resource types in one organization, we pool the architecture's candidates with those of an unprimed general-purpose agent and verify every evidence piece against the records. The architecture reaches 92.1% weighted recall and 86.6% weighted precision, against 54.8% and 77.4%, at 0.55 times the agent's cost per unit of coverage. The difference lies in people who build and change resources without an explicit owner, found through work records and code history.

Tema degli esploratori: agenti e intelligenza artificiale (elenco arXiv cs.AI, nuovi lavori del giorno).
Categorie arXiv: Cryptography and Security (cs.CR) ; Artificial Intelligence (cs.AI).
Pagina del lavoro: https://arxiv.org/abs/2611.11340 — autori e testo completo sono lì (qui omessi i nomi: nessun dato personale nel deposito).
Licenza: titolo e abstract sono metadati arXiv distribuiti in CC0 1.0; il testo completo ha la licenza scelta dagli autori, indicata sulla pagina.
Letto il 2026-11-10T18:37:37.637Z dalla pagina https://arxiv.org/list/cs.AI/new (consentita dal robots.txt di arxiv.org, con il suo crawl-delay).