Model weights: who approves what reaches the agent?
Model approval needs to follow the artifact that reaches execution and the authority available to the agent. The Lazarus study helps frame acceptance criteria for both decisions.
Blog
Практические руководства по пентесту, исследованию уязвимостей и инструментам безопасности на базе ИИ.
Статьи публикуются на английском и португальском языках.
Исследования
135 публикаций
Railway: reconcile secret rotation, deployment and AI charges
Recovering from an exposed secret involves access, application behavior and billed usage. Use the Railway case to define acceptance evidence for each decision.
NEAR AI: scoping data and software in inference
An AI integration review needs to follow the software processing each request and the credentials around it. Organize evidence by service before deciding which data and operations can return to the workflow.
Microsoft in November: verify Office fixes by update channel
An exploited Outlook vulnerability deserves attention even with a Moderate rating. Accepting the update requires evidence that the relevant Office installation received its applicable fix.
SAP: accept the patch with route and runtime evidence
SAP’s November fixes require checking the component, the access path and the effective configuration. Organize that evidence so change acceptance does not depend on the version inventory alone.
Fireworks and Notion: scoping data at a provider
The Fireworks and Notion notices show why supplier reviews must trace data and credentials by function. Establish the affected dataset before deciding what recovery requires.
Xen Orchestra: acceptance must cover tokens, pools and backups
A Xen Orchestra update must be matched to the correct component and channel. A suspected intrusion also calls for reviewing authority that remains valid over pools and backups.
Beget: evidence linking a backup to its account and service
A surviving copy needs to be linked to the correct customer and service before returning to operation. Recovery also depends on the catalog, permissions and configuration that make that association verifiable.
Vanderbilt: isolate devices while preserving the response channel
During an incident, the device used to request help may itself be under suspicion. A separate channel and a response authority help record decisions without turning initial reports into confirmed conclusions.