GRC is broken. FedRAMP 20x might fix it

Source: GRC is broken. FedRAMP 20x might fix it | CSO Online

Author: unknown

URL: https://www.csoonline.com/article/4188995/grc-is-broken-fedramp-20x-might-fix-it.html

ONE SENTENCE SUMMARY:

Traditional compliance often audits curated snapshots; FedRAMP 20x and GRC engineering push continuous, machine-readable telemetry to restore trust through transparency.

MAIN POINTS:

  1. Compliance can become theatre when scope and narratives are managed for passing.
  2. SOC 2 and ISO 27001 are point-in-time snapshots, not maturity guarantees.
  3. Sampling-based audits miss drift, bypasses, and operational shortcuts outside the evidence window.
  4. “Passing audits does not equal security” because real behavior can diverge from documented controls.
  5. FedRAMP 20x targets automation-first assurance with machine-readable evidence and continuous validation.
  6. APIs and telemetry enable auditors to query complete datasets instead of curated screenshots.
  7. Exposing every VM, drift event, and posture history shifts focus to continuous posture maintenance.
  8. Full SDLC visibility reveals bypassed approvals and hotfix patterns hidden by selected pull requests.
  9. Identity lifecycle assurance improves by showing complete JML histories, not sampled access reviews.
  10. Auditor focus moves from control artifacts to validating evidence pipeline completeness and data integrity.

TAKEAWAYS:

  1. Optimize assurance around meaningful risk reduction, not “pass the audit” metrics.
  2. Build continuous evidence pipelines using APIs, telemetry, and structured, machine-readable outputs.
  3. Accept messy operational truth as a driver for improvement rather than a reputational threat.
  4. Adopt iteration loops for controls like engineering: measure, refine, and continuously validate.
  5. Prepare for trust models where customers and assessors query live assurance layers, not PDFs.

5 Claude Agent Skills Risks Every CISO Should Know

Source: Cloud Security Alliance

Author: unknown

URL: https://www.akto.io/blog/claude-agent-risks-for-cisos

ONE SENTENCE SUMMARY:

Claude SKILL.md agent skills mirror npm supply-chain risks, with widespread vulnerabilities, weak governance, over-privilege, stealthy markdown payloads, and cross-platform propagation.

MAIN POINTS:

  1. Claude Skills extend agents quickly but significantly expand the enterprise attack surface.
  2. Multiple audits show 26.1%–36.82% of skills contain at least one security flaw.
  3. OWASP introduced Agentic Skills Top 10 (AST10) in March 2026 to classify risks.
  4. Ungoverned installations create skill sprawl without inventory, SOC visibility, or centralized control.
  5. Silent skill loading from local directories enables unmanaged execution on developer workstations.
  6. Open registries allow poisoning via impersonation, malware uploads, and absent provenance mechanisms.
  7. Upstream compromise can trigger credential theft or execution merely by cloning untrusted projects.
  8. Skills inherit full agent context, causing over-privileged access to tokens, secrets, and PII.
  9. Markdown instructions can covertly direct exfiltration, evading traditional code-signature scanners.
  10. Cross-platform SKILL.md portability enables rapid reindexing, unsafe updates, and inconsistent permission behaviors.

TAKEAWAYS:

  1. Building a complete skill inventory is prerequisite to least privilege, scanning, and incident response.
  2. Treat skill registries like hostile supply chains without signing, verification, and publisher trust controls.
  3. Enforce per-skill isolation and sandboxing to prevent “one approval, infinite permissions” failures.
  4. Detect instruction-based threats by analyzing natural-language behaviors, not just executable code patterns.
  5. Containment requires immutable version pinning and update governance across every platform indexing SKILL.md.

Dangling CNAMEs: The Critical DNS Misconfiguration Most Organizations Still Miss

Source: Cloud Security Alliance

Author: unknown

URL: https://cloudsecurityalliance.org/articles/dangling-cnames-the-critical-dns-misconfiguration-most-organizations-still-miss

ONE SENTENCE SUMMARY:

Researchers found attackers hijacking trusted university subdomains via dangling CNAMEs, highlighting the need for continuous DNS posture management.

MAIN POINTS:

  1. Campaign abused abandoned CNAME records across major universities’ trusted .edu subdomains.
  2. Takeovers enabled hosting pornography, scams, fake apps, and malware delivery infrastructure.
  3. Dangling CNAMEs persist when DNS points to decommissioned cloud resources.
  4. Attackers reclaim missing cloud resource names to inherit control of organization subdomains.
  5. Trust in educational domains boosted SEO rankings, increasing exposure to malicious content.
  6. Cloud-era asset churn outpaces manual, fragmented DNS management, creating DNS sprawl.
  7. Separate teams manage cloud resources and DNS, leaving orphaned records unnoticed.
  8. Threat actors reportedly automate discovery and monetization of takeover-prone DNS entries.
  9. Traditional security tools miss inactive DNS dependencies and orphaned external relationships.
  10. Business damage is reputational, impacting search trust, deliverability, compliance, and brand credibility.

TAKEAWAYS:

  1. Prioritize monitoring external DNS dependencies as part of the organization’s attack surface.
  2. Automate detection and remediation of dangling CNAMEs across clouds and third-party platforms.
  3. Integrate DNS validation into infrastructure provisioning and deprovisioning lifecycle workflows.
  4. Adopt DNS Posture Management to continuously find orphaned records and takeover opportunities.
  5. Treat subdomain reputation as a security asset attackers can weaponize at low cost.

Anthropic’s Claude Tag gives AI agents independent identities

Source: Help Net Security

Author: Anamarija Pogorelec

URL: https://www.helpnetsecurity.com/2026/06/24/anthropic-claude-tag-agent-identity-model/

ONE SENTENCE SUMMARY:

Anthropic’s Claude Tag introduces agent identities per workspace/channel, enabling scoped tool access, isolation, auditing, RBAC, and safer collaboration.

MAIN POINTS:

  1. Claude Tag uses a dedicated agent identity with permissions independent from individual employees.
  2. Administrators configure default tools, connections, plugins, and instructions at the workspace level.
  3. Channel-specific overrides allow different permissions for engineering, sales, legal, and other compartments.
  4. Broad, low-risk tools run in shared channels; personal/team-specific tools stay in DMs.
  5. Revoking access becomes simpler by disabling the agent identity rather than many user accounts.
  6. Private channels receive separate identities; public channels share a workspace-wide identity.
  7. Isolation prevents private-channel information from being accessible across other channels without explicit permission.
  8. Enterprise RBAC can restrict which users are allowed to interact with Claude in a channel.
  9. Tool credentials are bound to the channel identity and blocked from unauthorized destinations.
  10. Comprehensive logging records tasks, memory updates, and network requests for auditable activity trails.

TAKEAWAYS:

  1. Agent identity shifts authorization from per-user ACLs to compartment-scoped agent capabilities.
  2. Separation from personal accounts reduces inadvertent disclosure of private documents in shared collaboration spaces.
  3. Least-privilege becomes practical by scoping repositories, API keys, and tools per channel.
  4. Auditing improves because Claude’s actions appear both in Claude logs and connected service logs.
  5. Planned identity-aware controls may require both user rights and channel permissions for sensitive actions.

Best practices for deploying Secure Boot certificate updates

Source: Windows IT Pro Blog articles

Author: Nuno_Costa

URL: https://techcommunity.microsoft.com/blog/windows-itpro-blog/best-practices-for-deploying-secure-boot-certificate-updates/4529884

ONE SENTENCE SUMMARY:

Coordinated Secure Boot certificate updates across Windows, OEMs, and firmware strengthen global root of trust through phased rollouts and tools.

MAIN POINTS:

  1. Coordinated rollout spans operating systems, device manufacturers, and firmware vendors to update Secure Boot certificates.
  2. Many clients, servers, and VMs already updated; remaining deployments should still be completed.
  3. Pilot testing first increases confidence before broader rollouts across IT and Windows teams.
  4. Layered deployments combine OEM firmware updates with Windows security updates via staged automation.
  5. Tool choice varies; Intune, Group Policy, Azure automation, and PowerShell can all work.
  6. Keeping Windows updated typically installs new certificates automatically on supported devices.
  7. Secure Boot default enablement simplifies receiving certificates; re-enable it if disabled.
  8. Windows Security app shows certificate readiness and Secure Boot status, but is often disabled in enterprises.
  9. Some devices require OEM firmware updates; older models may lack vendor-supported firmware releases.
  10. Microsoft created status messages, playbooks, AMAs, logs, scripts, remediations, and reporting from internal learnings.

TAKEAWAYS:

  1. Finish the Secure Boot certificate transition to maintain current, evolving platform protections.
  2. Use phased rollouts with validation for certificates, boot managers, and firmware updates.
  3. Maintain regular Windows updates and confirm Secure Boot remains enabled across endpoints.
  4. Verify firmware currency through OEM support channels when devices lag certificate readiness.
  5. Leverage Microsoft playbooks, Windows Security insights, and enterprise tooling to monitor progress.

Guarding AI memory

Source: Microsoft Security Blog

Author: Natalie Isak and Sarah Cooley

URL: https://www.microsoft.com/en-us/security/blog/2026/06/22/guarding-ai-memory/

ONE SENTENCE SUMMARY:

AI memory enables persistent personalization but expands attack surface, requiring rigorous governance, logging, boundaries, and defense-in-depth protections across systems.

MAIN POINTS:

  1. Persistent memory turns AI from stateless tool into continuous learning collaborator.
  2. Stored context increases attack surface beyond single-prompt compromise opportunities.
  3. Agent memory holds sensitive user data requiring customer-data-grade protections.
  4. Memory influences behavior and tool calls, demanding strong governance controls.
  5. Asynchronous memory updates disrupt traditional human-in-the-loop safety patterns.
  6. Adversaries can poison memory and trigger delayed tool execution later.
  7. M365 sanitizes memory writes using prompt-injection classifiers and stripping.
  8. Task Adherence checks detect tool-call misalignment with user intent.
  9. Storage inherits M365 compliance: DSR, tenant isolation, Lockbox, encryption-at-rest.
  10. Auditability via MemoryUpdated logs enables SOC hunting, alerts, eDiscovery, and traceability.

TAKEAWAYS:

  1. Persistent memory converts transient prompt attacks into long-lived compromises.
  2. Multi-turn attacker strategies require defenses beyond single-interaction guardrails.
  3. Provenance and intent validation should precede any durable memory persistence.
  4. Deterministic access boundaries must isolate memory across users, agents, and tenants.
  5. End-to-end visibility and user controls build trustworthy, governable AI at scale.

Timelines

Source: Windows Incident Response

Author: Unknown

URL: http://windowsir.blogspot.com/2026/06/timelines.html

ONE SENTENCE SUMMARY:

Timelines are foundational DFIR tools, enabling early, contextual investigation by correlating multi-source events and guiding evidence collection decisions.

MAIN POINTS:

  1. Timeline analysis has been central to the author’s investigations since around 2008.
  2. A custom five-field “TLN” format was developed and remains in use.
  3. Prior blog series detailed tools and methods for building consistent forensic timelines.
  4. Published threat reports often contain timeline information, sometimes reformatted for readability.
  5. Earlier SecureWorks work showcased the same timeline format used for years.
  6. Eventmap was created to tag relevant events and reduce timeline noise.
  7. Events Ripper was developed to establish pivot points for deeper investigative branching.
  8. Recent ransomware predeployment investigation used long-standing tools and techniques.
  9. Micro-timelines and overlays combined MFT, USN journal, browser history, and more.
  10. Timelines should start investigations after collection, not be a final spreadsheet task.

TAKEAWAYS:

  1. Start building timelines early to steer analysis and accelerate incident understanding.
  2. Standardized formats improve repeatability and communication across investigations and reports.
  3. Tagging and pivoting techniques help analysts focus amid high-volume event data.
  4. Overlaying diverse artifacts reveals relationships and sequences invisible in isolation.
  5. Missing data sources should be documented because absence informs control effectiveness assessments.

Everyone’s Selling AI That Kills Pentesting. We Built One That Doesn’t.

Source: Black Hills Information Security, Inc.

Author: BHIS

URL: https://www.blackhillsinfosec.com/introducing-fusion-ai/

ONE SENTENCE SUMMARY:

Fusion AI augments external penetration testing with transparent, methodology-driven agents and human verification, lowering costs while improving coverage against AI-enabled attackers.

MAIN POINTS:

  1. Market hype claims agentic red teams will replace pentesters; Fusion AI rejects that premise.
  2. Offering costs about one-third of traditional external pentests, keeping humans in final control.
  3. Originated from an internal challenge to build an AI-powered external testing capability.
  4. Initial prototypes used Claude Code before evolving into a custom agentic investigation platform.
  5. Core differentiator is embedding BHIS testing methodology, not merely automating scanner output.
  6. Agents prioritize chaining medium/low/informational findings into impactful exploit paths.
  7. Platform provides full transparency: commands, steps, validation evidence, and reproducibility details.
  8. Motivation included adversaries adopting AI, highlighted by Anthropic’s report on Chinese actor misuse.
  9. Pilot testing focused on reducing hallucinations and improving actionable output quality.
  10. Real-world coverage win: detected compromised site via injected gambling links and likely exploit chain.

TAKEAWAYS:

  1. Human-in-the-loop review remains essential for severity accuracy and false-positive control.
  2. Methodology and institutional knowledge matter more than “AI-powered” branding.
  3. Transparent audit trails help solve AI interpretability and enable reliable verification.
  4. Automation can uncover tedious indicators humans often miss under tight engagement timelines.
  5. Lower-cost external testing expands access for smaller organizations previously priced out.

Microsoft AntiSSRF open-source library helps block server-side request forgery

Source: Help Net Security

Author: Anamarija Pogorelec

URL: https://www.helpnetsecurity.com/2026/06/17/microsoft-antissrf-open-source-library/

ONE SENTENCE SUMMARY:

Microsoft’s open-source AntiSSRF library validates untrusted URLs and outbound connections in .NET/Node.js to prevent SSRF attacks.

MAIN POINTS:

  1. AntiSSRF is an open-source Microsoft library designed to reduce SSRF risk.
  2. It validates URLs and network connections before outbound requests are made.
  3. Supports both .NET and Node.js applications as a drop-in component.
  4. Distributed under the permissive MIT license and hosted on GitHub.
  5. SSRF lets attackers coerce servers into requesting arbitrary internal or external endpoints.
  6. Impacts include internal service exposure, sensitive data leakage, disruption, and remote code execution.
  7. Vulnerabilities often start from unvalidated customer-supplied strings used to build URLs.
  8. Treats all incoming HTTP request data as untrusted, including backend-originated inputs.
  9. Uses an agent to block requests to internal or sensitive IP address ranges.
  10. Policy configuration controls allow/deny lists, HTTP plaintext rules, and required/denied headers.

TAKEAWAYS:

  1. Validate every URL-like input, even when formed from seemingly harmless identifiers.
  2. Enforce centralized outbound-request policy via AntiSSRFPolicy rather than ad-hoc checks.
  3. Blocking internal IP ranges is a practical default defense against SSRF pivoting.
  4. Built-in domain validators help safely target Azure Key Vault and Azure Storage endpoints.
  5. Adoption is straightforward for HttpClient and Node HTTP/HTTPS agents with common client examples.

Microsoft confirms Office apps launch issues after June updates

Source: BleepingComputer

Author: Sergiu Gatlan

URL: https://www.bleepingcomputer.com/news/microsoft/microsoft-confirms-office-apps-launch-issues-after-june-updates/

ONE SENTENCE SUMMARY:

Microsoft is investigating a Windows-update-triggered OLE automation issue blocking third-party apps from launching Office or opening documents reliably.

MAIN POINTS:

  1. A new known issue blocks third-party apps from launching Microsoft Office applications.
  2. Systems affected are fully updated with Windows patches released on/after June 9, 2026.
  3. Impacted Office products include Word, Excel, PowerPoint, Access, and others.
  4. Root cause involves third-party software using OLE automation to control Office.
  5. Failures may occur silently, with Office or documents not opening and no error.
  6. Reported affected apps include CCH Engagement, Zotero, and Workpaper Manager.
  7. Some vertical software is impacted, including dental tools like Dentrix and Softdent.
  8. Microsoft recommends opening Office apps/documents directly as a temporary workaround.
  9. Enterprises can request an organization-wide workaround via Microsoft Support for Business.
  10. A fix is being developed and will ship in a future Windows update.

TAKEAWAYS:

  1. Validate business-critical integrations that rely on Office OLE automation after June 2026 updates.
  2. Implement interim user guidance to launch Office directly rather than via third-party tools.
  3. Engage Microsoft Support for Business if widespread workflows are disrupted.
  4. Monitor Windows update releases for the promised remediation and related advisories.
  5. Expect silent failures, so add testing/monitoring to catch broken document-opening workflows.

Cisco Umbrella Virtual Appliance Privilege Escalation Vulnerability

Source: Cisco Security Advisory

Author: unknown

URL: https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-umbrella-priv-esc-F4wJB7AU?vs_f=Cisco%20Security%20Advisory%26vs_cat=Security%20Intelligence%26vs_type=RSS%26vs_p=Cisco%20Umbrella%20Virtual%20Appliance%20Privilege%20Escalation%20Vulnerability%26vs_k=1

ONE SENTENCE SUMMARY:

Cisco Umbrella Virtual Appliance vmadmin CLI flaw enables authenticated local vmadmin users to gain root via command validation weakness, fixed by updates.

MAIN POINTS:

  1. Vulnerability affects Cisco Umbrella Virtual Appliance vmadmin CLI.
  2. Attack requires authenticated, local access to the device.
  3. Threat actor must already possess vmadmin privileges.
  4. Root cause is insufficient validation of user-supplied commands.
  5. Exploitation involves running specific commands through the CLI.
  6. Successful attack results in privilege escalation to root.
  7. Cisco issued software updates to remediate the issue.
  8. No workaround options are available for mitigation.
  9. Advisory rates the Security Impact Rating as Medium.
  10. Assigned identifier is CVE-2026-20246.

TAKEAWAYS:

  1. Prioritize patching affected appliances because compensating controls are unavailable.
  2. Restrict local access and vmadmin account usage to reduce exploit likelihood.
  3. Monitor and audit vmadmin CLI activity for suspicious command execution.
  4. Treat medium-severity local escalation as high operational risk on shared systems.
  5. Use the Cisco advisory link as the authoritative source for fixed versions.

Palo Alto Warns of Active Exploitation of PAN-OS GlobalProtect VPN Flaw

Source: The Hacker News

Author: info@thehackernews.com (The Hacker News)

URL: https://thehackernews.com/2026/06/palo-alto-warns-of-active-exploitation.html

ONE SENTENCE SUMMARY:

Palo Alto Networks reports limited active exploitation of PAN-OS CVE-2026-0257, urging log hunting, IoC blocking, and prompt mitigation.

MAIN POINTS:

  1. Palo Alto Networks observed active exploitation targeting GlobalProtect portals for unauthorized access.
  2. CVE-2026-0257 is an authentication bypass in PAN-OS portal and gateway components.
  3. The flaw enables attackers to bypass controls and initiate VPN connections.
  4. In-the-wild exploitation has been limited, first seen on May 17, 2026.
  5. Attribution remains unknown for the observed exploitation attempts.
  6. No post-access activity or lateral movement has been identified so far.
  7. Only a small subset of probed devices established VPN sessions and gateway-connected events.
  8. Published IoCs include multiple suspicious IP addresses tied to the activity.
  9. Additional IoCs list hostnames and MAC addresses associated with potential exploitation.
  10. CISA added the CVE to KEV, mandating FCEB mitigation by June 1, 2026.

TAKEAWAYS:

  1. Prioritize patching or mitigation for CVE-2026-0257 due to confirmed exploitation.
  2. Search GlobalProtect logs for successful gateway-connected events indicating compromise.
  3. Hunt for PoC-linked client values like Windows 10 Pro 64-bit and empty domain fields.
  4. Block and monitor provided IPs, hostnames, and MAC addresses in security controls.
  5. Use KEV deadlines to drive rapid remediation timelines and compliance reporting.

SearchLeak: How We Turned M365 Copilot Into a One-Click Data Exfiltration Weapon

Source: Varonis Blog

Author: Dolev Taler

URL: https://www.varonis.com/blog/searchleak

ONE SENTENCE SUMMARY:

SearchLeak chained P2P prompt injection, streaming HTML race, and Bing SSRF to silently exfiltrate Microsoft 365 Copilot Enterprise data via one click.

MAIN POINTS:

  1. Varonis found a three-stage chain weaponizing Copilot Enterprise Search for covert data theft.
  2. Parameter-to-Prompt Injection lets the URL q parameter become executable Copilot instructions.
  3. Enterprise Search’s focus on organizational content makes it ideal for harvesting sensitive business data.
  4. Attack requires only one click on a trusted microsoft.com link—no plugins or permissions.
  5. A streaming-phase HTML rendering race allows <img> requests before output sanitization.
  6. Post-processing <code> wrapping occurs too late; the browser already emitted the outbound request.
  7. CSP blocks direct attacker domains, but *.bing.com is allowlisted for images.
  8. Bing’s “search by image” endpoint server-fetches attacker URLs, acting as an SSRF proxy.
  9. Exfiltration is achieved by embedding stolen mailbox content into the image URL path.
  10. Microsoft patched as CVE-2026-42824, rated critical, highlighting AI-enabled chaining of classic bugs.

TAKEAWAYS:

  1. Treat AI query parameters as potential instruction channels, not merely search input.
  2. Apply sanitization during streaming/render time, not after model output completion.
  3. Audit CSP allowlists for endpoints that perform server-side URL fetches.
  4. Detect suspicious Copilot Search URLs containing encoded HTML tags or exfiltration prompts.
  5. User awareness matters: long encoded Microsoft links and unsolicited Copilot searches warrant reporting.

CQURE Hacks #81: The Ultimate KQL Query Toolkit for Threat Hunters and Security Analysts

Source: CQURE Academy

Author: Daniel

URL: https://cqureacademy.com/blog/cqure-hacks-81-the-ultimate-kql-query-toolkit-for-threat-hunters-and-security-analysts/

ONE SENTENCE SUMMARY:

Eight reusable KQL queries enable baselining, incident response, and threat hunting through traffic, auth, scanning, C2, anomalies, fingerprints, and egress monitoring.

MAIN POINTS:

  1. Daily baseline query tracks volume, success rate, failures, intrusion attempts, and unique IPs.
  2. Trend binning with 1-day intervals helps detect deviations like sudden intrusion spikes.
  3. Incident-response query identifies top malicious IPs, timing, attack types, ports, and protocols.
  4. make_set() highlights multi-technique attackers and supports rapid blocklisting and triage.
  5. Failed authentication analysis uses hourly grouping and thresholds to spot brute force patterns.
  6. Distinct source/target counts differentiate password spraying from targeted account attacks.
  7. Port-scan detection monitors 15-minute windows, flagging hosts probing multiple ports quickly.
  8. Botnet C2 hunting profiles payload percentiles and user agents to find beaconing behavior.
  9. Protocol anomaly detection flags rare protocol-port combinations and scores suspicious patterns via joins.
  10. User-agent and egress queries distinguish scanners from attackers and expose risky outbound communications.

TAKEAWAYS:

  1. Establish normal behavior first, then investigate meaningful deviations.
  2. Pivot quickly from baseline anomalies to attacker attribution and response actions.
  3. Use time windows, thresholds, and uniqueness metrics to reduce noise and reveal patterns.
  4. Combine behavioral profiling (payloads, user agents, protocol-port mismatches) with scoring for stealthy threats.
  5. Treat these queries as a coordinated, customizable toolkit run on reliable schedules.

Zero Trust for AI Agents: How to Enforce Anthropic’s Framework

Source: Varonis Blog

Author: Nolan Necoechea

URL: https://www.varonis.com/blog/zero-trust-for-ai-agents

ONE SENTENCE SUMMARY:

Anthropic proposes Zero Trust for AI agents, while Varonis argues enforcement demands data-context discovery, guardrails, monitoring, governance, and testing.

MAIN POINTS:

  1. Perimeter defenses fail as social engineering and stolen credentials bypass traditional controls.
  2. AI accelerates attacks by scaling manipulation and increasing compromised-identity blast radius.
  3. Agents bypass application controls, directly hitting databases, APIs, and data stores at machine speed.
  4. Zero Trust must adapt to agents with cryptographic identity, task-scoped permissions, and protected memory.
  5. Six pillars include identity, access scoping, observability, behavioral response, I/O controls, integrity recovery.
  6. Agent-specific threats span prompt injection, tool poisoning, privilege abuse, memory poisoning, supply chain attacks.
  7. Frontier models can chain weaknesses to create exploits in hours, compressing attacker timelines.
  8. Framework defines maturity tiers and an implementation workflow, plus Agentic SOAR for rapid response.
  9. Bolt-on AI controls miss the data layer, where excessive access and sensitive exposure cause damage.
  10. Varonis Atlas maps to and extends the framework across discover, assess, enforce, govern, monitor, test.

TAKEAWAYS:

  1. Treat agent identities as first-class principals with verifiable provenance and authorization boundaries.
  2. Implement least privilege per task rather than persistent role-based permissions for autonomous systems.
  3. Combine runtime guardrails with deep logging to detect tool-chaining and indirect leakage patterns.
  4. Prioritize data context—classification, lineage, and exposure—so “authorized” access doesn’t equal safe access.
  5. Close the loop using continuous adversarial testing feeding policies and automated response workflows.

NIST AI RMF: Where to Start with AI Governance

Source: Rivial Security Blog

Author: Randy Lindberg

URL: https://www.rivialsecurity.com/blog/nist-ai-rmf-where-to-start-with-ai-governance

ONE SENTENCE SUMMARY:

Start AI governance with NIST AI RMF Govern, integrate into cyber risk, add inventories/controls, use FS AI RMF, report quantified ROI.

MAIN POINTS:

  1. AI adoption is accelerating faster than prior technology waves, embedding into core operations.
  2. Governance must begin immediately because AI appears via tools, vendors, and silent updates.
  3. NIST AI RMF provides four functions: Govern, Map, Measure, Manage.
  4. Prioritize Govern by establishing AI policy, ownership, procurement, and AI-aware change management.
  5. Build and maintain an AI system inventory tied to approvals, evidence, monitoring, and reporting.
  6. Fold AI risk into existing cybersecurity risk program, avoiding parallel AI risk silos.
  7. Extend eight cyber-risk elements with AI-aware updates, including AI-specific KRIs and TEVV.
  8. Quantitative risk measurement (e.g., Monte Carlo) beats qualitative heat maps for decision-making.
  9. FS AI RMF adds concrete, auditable controls useful beyond financial services for implementation.
  10. Board reporting should use dollars, expected loss reduction, and ROI, not red-yellow-green visuals.

TAKEAWAYS:

  1. Publish a workable AI policy now, then iterate as AI capabilities rapidly change.
  2. Treat AI as a risk dimension on existing systems, keeping one risk register and methodology.
  3. Counter shadow AI by offering approved tools and a fast intake/approval path.
  4. Add “accuracy” to CIA impacts to capture drift, bias, and hallucinations (CIA+A).
  5. Use breach-per-record and downtime estimates as ranges to quantify AI risk financially.

ServiceNow Data Breach: Gated Advisory Left Customers Unaware of Exploited Zero-Auth API

Source: Tech Times

Author: unknown

URL: https://www.techtimes.com/articles/318166/20260610/servicenow-data-breach-gated-advisory-left-customers-unaware-exploited-zero-auth-api.htm

ONE SENTENCE SUMMARY:

ServiceNow fixed an unauthenticated API data-query flaw after confirmed exploitation, drawing criticism for delayed, gated disclosure and urgent customer response actions.

MAIN POINTS:

  1. Attackers queried sensitive ServiceNow customer tables via an unauthenticated API endpoint.
  2. Misconfiguration set requires_authentication=false, bypassing identity and privilege checks entirely.
  3. Reported exploited path was /api/now/related_list_edit/create against instance tables.
  4. Suspicious requests often came from IP 51.159.98.241, about five per tenant.
  5. Confirmed activity occurred June 2–3, 2026; hosted instances patched June 5.
  6. ServiceNow published advisory June 9, but hid it behind support-portal authentication.
  7. Limited notification meant many customers lacked a trigger to start incident response.
  8. Potentially exposed data includes tickets, HR records, assets, incident reports, tokens, and secrets.
  9. Credential leakage can enable lateral movement into integrated enterprise systems without further exploits.
  10. This is ServiceNow’s third major auth-related issue in eight months; first with pre-patch data access.

TAKEAWAYS:

  1. Search transaction logs for /api/now/related_list_edit/create and IP 51.159.98.241 during June 2–5.
  2. Review all Scripted REST Resources for requires_authentication disabled, including custom endpoints.
  3. Rotate credentials embedded in tickets and integrations immediately, assuming potential exposure.
  4. Enable verbose REST/API logging to support future scoping and exfiltration assessment.
  5. Engage legal counsel early since “queried vs exfiltrated” affects GDPR, HIPAA, and SEC obligations.

June Patch Tuesday marks a ‘new normal’ with over 200 CVEs, 32 rated ‘critical’

Source: June Patch Tuesday marks a ‘new normal’ with over 200 CVEs, 32 rated ‘critical’ | CSO Online

Author: unknown

URL: https://www.csoonline.com/article/4183632/june-patch-tuesday-marks-a-new-normal-with-over-200-cves-32-rated-critical.html

ONE SENTENCE SUMMARY:

June Patch Tuesday delivered record vulnerability volumes, including Microsoft’s 200+ CVEs, critical SAP flaws, and Adobe enterprise patches amid AI-accelerated discovery.

MAIN POINTS:

  1. Microsoft released fixes for over 200 CVEs, including three publicly disclosed zero days.
  2. Thirty-two Microsoft patches are rated critical, with additional high-risk flaws needing urgent assessment.
  3. Microsoft warns monthly CVE counts will keep rising and expects more out-of-band updates.
  4. AI-assisted discovery is shrinking time between bug existence and detection, pressuring patch cycles.
  5. Previously hard-to-audit areas like hypervisor code and Kerberos are yielding more vulnerabilities.
  6. Exchange Server CVE-2026-42897 moved from workaround guidance to an active-exploit patch.
  7. Microsoft flagged 15 flaws as “more likely” to be exploited, including http.sys kernel RCE CVE-2026-47291.
  8. High-rated Hyper-V VM escape vulnerabilities demand attention in virtualized enterprise environments.
  9. SAP issued 15 patches, including four critical vulnerabilities across core enterprise products.
  10. Adobe patched 123 vulnerabilities, highlighted by CVSS 10 issues in Campaign Classic and critical ColdFusion bugs.

TAKEAWAYS:

  1. Shift from slow patch testing to risk-based prioritization aligned with exploitation likelihood.
  2. Automate patching pipelines to handle sustained, “new baseline” vulnerability volumes.
  3. Treat internet-facing Windows services using http.sys as urgent remediation targets.
  4. Prioritize SAP ABAP/NetWeaver criticals due to high impact and low/no-auth attack paths.
  5. Include Adobe enterprise platforms (Campaign Classic, ColdFusion, Reader) in rapid patch SLAs.

Microsoft changes how Defender for Endpoint EDR updates are delivered on Windows

Source: Help Net Security

Author: Sinisa Markovic

URL: https://www.helpnetsecurity.com/2026/06/08/microsoft-defender-for-endpoint-edr-updates/

ONE SENTENCE SUMMARY:

Microsoft will deliver Defender for Endpoint EDR updates via Microsoft Update, accelerating independent improvements across supported Windows versions by fall 2026.

MAIN POINTS:

  1. EDR security improvements will ship independently from monthly Windows OS updates.
  2. Rollout began late May 2026 for Windows 10 devices.
  3. Expansion to Windows 11 and other supported Windows versions occurs later in 2026.
  4. Microsoft expects deployment completion by fall 2026.
  5. Microsoft Update-managed organizations require no changes to receive EDR updates.
  6. Manual package deployment environments must add the new Defender update package.
  7. Existing documentation and procedures should be revised to reflect the new delivery method.
  8. Helpdesk and SecOps teams should be informed about updated EDR update behavior.
  9. Delivery uses Microsoft Update via KB5005292 after prerequisites are installed.
  10. New Defender Update Service creates %ProgramData%\Microsoft\Microsoft Defender\Defender Update on first EDR update.

TAKEAWAYS:

  1. Plan prerequisites and Sense version compliance before expecting EDR updates through Microsoft Update.
  2. Treat KB5005292 as the enabling mechanism once required cumulative updates exist.
  3. Update orchestration processes for manual deployment to avoid missing EDR improvements.
  4. Prepare operational teams for generally restart-free updates and rare failure-driven reboots.
  5. Verify supported OS builds have the specified 2025-07/2025-08 cumulative updates or newer.

Microsoft Defender now monitors RPC activity

Source: Microsoft Defender for Endpoint Blog articles

Author: EdanZwick

URL: https://techcommunity.microsoft.com/blog/microsoftdefenderatpblog/microsoft-defender-now-monitors-rpc-activity/4523368

ONE SENTENCE SUMMARY:

Microsoft Defender now audits inbound remote RPC calls at OpNum granularity to detect, disrupt, and hunt common Windows attacks.

MAIN POINTS:

  1. Remote procedure call enables invoking remote functions as if executed locally.
  2. Windows and Active Directory rely heavily on RPC, making it a frequent attacker target.
  3. RPC interfaces group server functionality and are identified by UUIDs.
  4. OpNum uniquely identifies the specific function invoked within an RPC interface.
  5. Lateral movement commonly abuses RPC for remote tasks, services, and WMI execution.
  6. Credential theft includes DCSync replication abuse and remote registry-based secrets dumping.
  7. Privilege escalation can involve authentication coercion through legitimate RPC interfaces.
  8. Discovery tooling like SharpHound enumerates users, sessions, and shares via RPC calls.
  9. Defender uses Windows Filtering Platform integration to audit remote RPC even with encrypted transports.
  10. Telemetry targets inbound server-side remote RPC only; local and outbound RPC are excluded.

TAKEAWAYS:

  1. OpNum-level visibility improves detection precision beyond interface-only monitoring.
  2. Audit-only WFP filters provide scalable RPC telemetry without disrupting normal traffic.
  3. Hunting data enables investigations of remote registry saves, service creation, and session discovery.
  4. Built-in detections cover Impacket activity, secrets theft indicators, and coercion attempts.
  5. Workstation RPC monitoring is GA, while server coverage is gradually rolling out.

VS Code Adds 2-Hour Extension Auto-Update Delay to Limit Supply Chain Attacks

Source: The Hacker News

Author: info@thehackernews.com (The Hacker News)

URL: https://thehackernews.com/2026/06/vs-code-adds-2-hour-extension-auto.html

ONE SENTENCE SUMMARY:

VS Code now delays most extension auto-updates by two hours to reduce exposure to newly published supply-chain attacks.

MAIN POINTS:

  1. Microsoft introduced a two-hour delay for automatic VS Code extension updates.
  2. The change aims to mitigate software supply chain threats from compromised releases.
  3. This protection activates when automatic extension updates are enabled.
  4. The feature is available beginning with Visual Studio Code version 1.123.
  5. Users can still manually install updates immediately via the “Update” button.
  6. Extension details show why an update is pending and when it will occur.
  7. Trusted publishers’ extensions bypass the delay and update immediately.
  8. RubyGems added an opt-in cooldown to Bundler 4.0.13 for delayed gem installs.
  9. Bun, npm, pnpm, and Yarn added minimum-release-age controls with specific settings.
  10. Minimum-age thresholds reduce the spread window before malicious packages are detected and removed.

TAKEAWAYS:

  1. Delayed updates are emerging as a standard defense across developer ecosystems.
  2. A short cooldown can meaningfully limit exposure to fast-moving malicious releases.
  3. Manual update options preserve developer flexibility despite automated delays.
  4. Trust-based exceptions prioritize speed for major publishers, but increase reliance on publisher integrity.
  5. Supply-chain risk is rising, making proactive installation and update gating increasingly important.

New ChatGPT Lockdown Mode Limits Tools That Could Enable Data Exfiltration

Source: The Hacker News

Author: info@thehackernews.com (The Hacker News)

URL: https://thehackernews.com/2026/06/new-chatgpt-lockdown-mode-limits-tools.html

ONE SENTENCE SUMMARY:

OpenAI’s ChatGPT Lockdown Mode reduces prompt-injection data exfiltration risk by restricting networked tools, while adding session management controls.

MAIN POINTS:

  1. Introduces optional Lockdown Mode for eligible personal accounts to mitigate prompt-injection exfiltration.
  2. Targets users handling sensitive data needing stronger protection guarantees.
  3. Available across Free, Go, Plus, Pro, and self-serve Business plans.
  4. Limits tools connecting to web or external services to reduce outbound data leakage.
  5. Builds on sandboxing and controls against URL-based exfiltration techniques.
  6. Focuses on removing exfiltration pathways, not preventing prompt injections outright.
  7. Leaves memory, file uploads, and conversation sharing behavior unchanged.
  8. Disables or restricts browsing, images, deep research, agent mode, canvas networking, and downloads.
  9. Mutually exclusive with Developer Mode; enabling one automatically disables the other.
  10. Adds session review/logout feature with device, app, location, timing, and trust indicators.

TAKEAWAYS:

  1. Activate Lockdown Mode when sensitive data exposure would be high impact.
  2. Expect reduced functionality as a tradeoff for fewer outbound exfiltration routes.
  3. Recognize residual risk from apps, capability combinations, or novel techniques.
  4. Understand prompt injections can still manipulate outputs even without data theft.
  5. Use new session-management tooling to detect and respond to account compromise quickly.

HexStrike AI RED-TEAM With 127 Security Tools and BOAZ Red Team Integration

Source: Cyber Security News

Author: Guru Baran

URL: https://cybersecuritynews.com/hexstrike-ai-red-team-tool/

ONE SENTENCE SUMMARY:

HexStrike AI v6.0 is an MCP-based framework enabling autonomous pentesting and BOAZ evasion payloads via 127 tools.

MAIN POINTS:

  1. Forked HexStrike AI v6.0 introduces MCP-driven cybersecurity automation for red team operations.
  2. FastMCP server bridges LLMs with a curated offensive security toolchain.
  3. Intelligent Decision Engine selects tools and executes multi-phase assessments with minimal guidance.
  4. Supports Claude Desktop, Cursor, VS Code Copilot, Roo Code, partial 5ire, others.
  5. Integrates BOAZ multilayer AV/EDR evasion via five dedicated MCP tools.
  6. BOAZ includes 77+ process-injection loaders across syscall, stealth, memory guard, threadless, VEH/VCH, userland.
  7. Provides 12 encoding schemes including AES, ChaCha20, RC4, XOR, UUID, Base45/64/58.
  8. Implements bypass techniques: API unhooking, ETW patching, LLVM obfuscation with Akira/Pluto.
  9. Ships 127 tools; 53 auto-installed, 74 manual due to licensing/dependencies/platform constraints.
  10. Full setup needs ~24GB and 60–90 minutes, dominated by LLVM obfuscator builds.

TAKEAWAYS:

  1. AI agents can compress days of manual pentest orchestration into minutes of automated workflows.
  2. BOAZ integration turns scanning into an end-to-end stealth payload pipeline.
  3. Operational readiness depends on significant installation effort and selective manual tool provisioning.
  4. Documentation restricts use to authorized engagements, bug bounties, CTFs, and approved red teams.
  5. LLM orchestration frameworks create dual-use risk by scaling offensive actions with reduced oversight.

Cybersecurity Hygiene Reinforced by the 2026 Verizon DBIR

Source: Blog Feed – Center for Internet Security

Author: unknown

URL: https://www.cisecurity.org/insights/blog/cybersecurity-hygiene-reinforced-by-the-2026-verizon-dbir

ONE SENTENCE SUMMARY:

Verizon’s 2026 DBIR shows CIS Controls and Benchmarks improve cyber hygiene, reducing exposure and countering prevalent modern attack techniques effectively.

MAIN POINTS:

  1. DBIR links common breach patterns to foundational security hygiene gaps across organizations.
  2. CIS Controls provide prioritized, actionable safeguards aligned to real-world attack paths.
  3. CIS Benchmarks harden system configurations, shrinking misconfiguration-driven compromise opportunities.
  4. Mapping DBIR top threats to CIS safeguards helps focus limited resources on highest risks.
  5. Strong identity, access management, and MFA reduce credential theft and account takeover impact.
  6. Vulnerability and patch management limit exploitation windows used by ransomware and initial access brokers.
  7. Secure configuration baselines improve consistency across cloud, endpoints, servers, and network devices.
  8. Continuous monitoring and logging support faster detection and response to prevalent intrusion techniques.
  9. Backup, recovery, and resilience controls blunt ransomware business impact and downtime.
  10. Governance and measurement using CIS frameworks enable repeatable hygiene improvements over time.

TAKEAWAYS:

  1. Prioritizing CIS Controls is a practical way to address the most frequent DBIR attack patterns.
  2. Implementing CIS Benchmarks reduces preventable breaches caused by insecure default configurations.
  3. Aligning security programs to evidence-based reports improves decision-making and investment justification.
  4. Standardized baselines and continuous verification are essential for sustaining cybersecurity hygiene.
  5. Combining prevention, detection, and recovery controls provides better defense against modern, multi-stage attacks.

Tenable joins Anthropic’s Project Glasswing to advance AI-era cyber defense

Source: Tenable Blog

Author: Vlad Korsunsky

URL: https://www.tenable.com/blog/anthropic-claude-mythos-tenable-joins-project-glasswing

ONE SENTENCE SUMMARY:

Tenable joins Anthropic’s Project Glasswing to benchmark Claude Mythos Preview, enhancing exposure management while studying frontier AI risks, controls, and governance.

MAIN POINTS:

  1. Project Glasswing collaboration evaluates Claude Mythos Preview for cybersecurity defender advantage.
  2. Advanced reasoning is benchmarked for attack path analysis, exposure prioritization, and remediation.
  3. Tenable aims to reduce overload from escalating findings and expanding attack surfaces.
  4. Frontier AI could accelerate offensive capabilities, pressuring defensive operations soon.
  5. Research will explore Mythos Preview for reinforcing analysis and strengthening Tenable’s internal security.
  6. Mythos will be compared with other models to challenge assumptions and uncover risk patterns.
  7. Defender differentiation depends on contextualized insights, not exclusive access to one AI model.
  8. Exposure management platforms may ingest frontier-model telemetry as a new security signal source.
  9. Organizations inherit risk from third-party AI they didn’t build, expanding the AI attack surface.
  10. Tenable One already integrates Claude Compliance API and Claude-powered workflows via Tenable Hexa AI.

TAKEAWAYS:

  1. Benchmarking frontier reasoning can materially improve prioritization and remediation decisions.
  2. Preparing for widely available attacker-grade AI requires faster, coordinated enterprise remediation.
  3. Combining AI signals with asset intelligence and attack paths drives better risk reduction.
  4. Understanding model behaviors informs practical controls, governance, and internal security practices.
  5. Partnerships like Glasswing accelerate responsible translation of AI advances into customer value.