Evidence search
Search
Search titles, summaries, topics, providers, authors, and the full open-access corpus.
Results for “Training data”
6 publicationsTreat a cloud model retirement as a security change
Bedrock and Agent Platform fail closed on a model's retirement date, while Foundry can swap a different model in behind the same deployment name. Read the three calendars, compare the replacement's controls and decide per deployment.
AI systems · Amazon Web Services / Microsoft Azure / Google Cloud · By Cloud Security DeskGive persistent agent memory an admission boundary
Separate conversational candidates from admitted memory, preserve their permitted audience, and make derived summaries repairable.
AI systems · LangChain · By Cloud Security DeskSecurity evidence for AI release decisions
A release approval should identify the changed application, the claims its tests support and the evidence that expires when a model, prompt, data path or runtime changes.
AI systems · By Cloud Security DeskWhat coding benchmarks can prove about a model
A coding benchmark result depends on its tasks, harness and tests. A reproducible count of SWE-bench Verified shows why the denominator belongs beside every comparison.
AI systems · By Cloud Security DeskWhere fine tuning data needs a trust boundary
A training dataset can preserve its checksum and still teach the wrong behavior. Admission controls need to separate origin, transformation, approved use and the model change they produce.
AI systems · By Cloud Security DeskQwen3.8-Flash-Next and GLM-5.3-Flash share a 3:1 long-context pattern
Both models replace most conventional attention layers with recurrent state and reserve sparse attention for periodic retrieval. Their differences lie in where they place capacity, how much neural computation they activate, and what their serving stacks must keep trustworthy.
AI systems · Resilience · By Umair Akbar and Ahmed Elshekh