Daily Edition · Page 5

THE DAILY INDEX

Technology, AI, software, security, crypto and business

ATTACKS & VULNERABILITIES

TLDR InfoSec

THE SECURITY PRINCIPLES GUIDING 1PASSWORD'S APPROACH TO AI

Seven core security principles for AI integration: encrypting secrets, using deterministic authorization over probabilistic LLM decisions, preventing raw credentials in LLM contexts, maintaining auditability, ensuring transparency, implementing least privilege, and balancing security with usability. AI agents must follow strict access controls, similar to humans, with credentials delivered securely (e.g., OAuth) rather than through LLM prompts, maintaining a zero-knowledge architecture. These principles show that traditional siloed privileged access management is inadequate for the AI era, which will require unified frameworks for both human and AI interactions.

THREE DOTS TO ROOT: HOW I FOUND A PATH TRAVERSAL IN MICROSOFT'S AGENTIC WEB

Microsoft's NLWeb is a new framework designed to allow AI agents to interact with websites and APIs via natural language. This author describes how they discovered a path traversal vulnerability that could lead to the disclosure of arbitrary files such as `/etc/passwd` or `.env`. The vulnerability was caused by the use of the `os.path.normpath()` function, which does not prevent “climbing out” of the directory using `../`.

CONSTRUCTING A TRUSTWORTHY EVALUATION METHODOLOGY FOR CONTEXTUAL SECURITY ANALYSIS

DryRun Security uses an AI engine called Contextual Security Analysis (CSA) to analyze code changes probabilistically. Each PR goes through three steps: whole-PR synthesis to understand the goal, hunk-scoped reasoning to isolate individual code hunks and filter out unrelated changes, and on-demand context acquisition to retrieve supporting files and dependencies. DryRun also has a secondary audit model that randomly samples production findings every 24 hours to check instruction compliance, hallucination detection, and vulnerability accuracy.

APPSEC/PRODSEC'S REALITY GAP

Application and Product Security face a disparity in connecting theoretical security concepts to practical environments. A lack of context defines the problem space, teams trying to avoid slowing down development, security tools not addressing where teams are struggling or organizational scale, and tooling being designed for gates instead of guardrails. AI-based tools may help in providing more context and tailored experiences, but they will not alleviate the resource constraints that many teams face.

TLDR IndexPage 5