- Published
- Source
- Help Net Security
- Filed under
- AI for defence
GitHub has trained a credential classifier to improve generic secret detection and reduce false alerts. The new pipeline cut median post-push scan execution time by 86% and model serving costs by more than 98% compared with its previous large language model (LLM) pipeline. GitHub’s secret scanning covers two stages of development. Push protection checks changes before a push is accepted, helping developers prevent credential leaks. Post-push scanning examines repository content and creates alerts for potential … More →…
Using AI safely
- Know which AI tools your organisation uses, and what data goes into them.
- Treat AI agents like any other identity: least privilege, logging and a named owner.
- Test AI features for prompt injection and data leakage before customers reach them.
More helpNCSC: guidelines for secure AI system development (opens in a new tab)
MyCyberWay training
AI security · in both programmes
AI is part of the attack surface now. Learn to watch it.
Blue Team Analyst covers Security Copilot in triage and monitoring the AI itself: inherited permissions, prompt injection and Purview DSPM for AI. Blue Team Engineer secures the deployment: Copilot pre-flight hardening, agent identity and tool allow-lists.
- Security Copilot in triage
- Prompt injection and DSPM for AI
- Agent identity and allow-lists
Headlines and short summaries only, except where a public body publishes under an open licence. Every story links to its publisher, who owns it. MyCyberWay does not edit or endorse third-party reporting.
