# Logging

Logging is the creation and management of records of events occurring in computing assets, including platforms, networks, services, and cloud environments.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Performance impact of excessive logging in Amazon Aurora PostgreSQL

DevFeed: [Performance impact of excessive logging in Amazon Aurora PostgreSQL](<https://devfeed.tech/articles/performance-impact-of-excessive-logging-in-amazon-aurora-postgresql-144312.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/performance-impact-of-excessive-logging-in-amazon-aurora-postgresql/>)

Author: Baji Shaik

Published: 2026-11-19T19:10:08Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.md>), [Logging](<https://devfeed.tech/topics/logging.md>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>), [database-optimization](<https://devfeed.tech/topics/database-optimization.md>), [performance-engineering](<https://devfeed.tech/topics/performance-engineering.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>)

Tags: [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [audit-logging](<https://devfeed.tech/tags/audit-logging.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [bottleneck](<https://devfeed.tech/tags/bottleneck.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [logging](<https://devfeed.tech/tags/logging.md>), [performance](<https://devfeed.tech/tags/performance.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [rds-for-postgresql](<https://devfeed.tech/tags/rds-for-postgresql.md>), [throughput](<https://devfeed.tech/tags/throughput.md>)

### AI overview

In a pgbench test on Aurora PostgreSQL 17, verbose logging had little effect at 8 clients, but at 800 clients, logging every statement reduced throughput by about 10%; adding `pgaudit.log = ALL` cut whole-run throughput from 16,202 to 5,039 TPS. Sampling showed sessions mostly active on CPU rather than waiting on instrumented resources, and a 537 MB log file written in under a minute supported a bottleneck in log generation and writing. The article recommends checking `pg_settings`, correlating slow periods with `pg_stat_activity` wait events and RDS log-file sizes, and testing at production-like concurrency. For audit needs, it suggests narrowing logged statement classes or using `pgaudit.log_statement = off` to retain structured audit details while dropping embedded SQL text; it advises confirming the reduction on the workload.

### Source excerpt

Excessive database and audit logging can quietly become a performance bottleneck in Amazon Aurora and Amazon RDS for PostgreSQL. Using a reproducible pgbench example, this post shows when logging overhead is negligible and when it cuts throughput by about three times, how to spot it with wait events and log file evidence, and how to reduce it.

## How to use Amazon Aurora DSQL audit logs

DevFeed: [How to use Amazon Aurora DSQL audit logs](<https://devfeed.tech/articles/how-to-use-amazon-aurora-dsql-audit-logs-141385.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/how-to-use-amazon-aurora-dsql-audit-logs/>)

Author: Koji Shinkubo

Published: 2026-11-18T21:33:01Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [DSQL](<https://devfeed.tech/topics/dsql.md>), [audit](<https://devfeed.tech/topics/audit.md>), [Logging](<https://devfeed.tech/topics/logging.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [Query (disambiguation)](<https://devfeed.tech/topics/query.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-athena](<https://devfeed.tech/tags/amazon-athena.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [athena](<https://devfeed.tech/tags/athena.md>), [audit](<https://devfeed.tech/tags/audit.md>), [audit-logging](<https://devfeed.tech/tags/audit-logging.md>), [audit-logs](<https://devfeed.tech/tags/audit-logs.md>), [configure](<https://devfeed.tech/tags/configure.md>), [database](<https://devfeed.tech/tags/database.md>), [dsql](<https://devfeed.tech/tags/dsql.md>), [field](<https://devfeed.tech/tags/field.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [logging](<https://devfeed.tech/tags/logging.md>), [logs](<https://devfeed.tech/tags/logs.md>), [post](<https://devfeed.tech/tags/post.md>), [query](<https://devfeed.tech/tags/query.md>), [records](<https://devfeed.tech/tags/records.md>), [requirements](<https://devfeed.tech/tags/requirements.md>), [s3](<https://devfeed.tech/tags/s3.md>), [sql](<https://devfeed.tech/tags/sql.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

Aurora DSQL audit logging records configured SQL statement classes and delivers records to S3; it is off until both a destination and recording settings are configured. The article describes role-based scope, including READ/SELECT, and a setup that separates audit administration from DBA permissions. Records can identify the IAM role and database role, transaction, statement, and optionally bound values and row counts. Athena can query the S3 logs, while CloudTrail connection events can be joined by session ID to add client IP information; transaction IDs can also link audit records to CDC changes. Limits and tradeoffs include potentially high log volume and charges, no table- or column-level scope, no client IP or success/failure field in audit records, and recording statements from rolled-back transactions. The article recommends testing scope and volume before production and protecting sensitive log content through access controls, encryption, and retention settings.

### Source excerpt

Amazon Aurora DSQL audit logging records the SQL statements that run in your database and delivers them to Amazon S3. This post shows how to configure audit logging to meet regulatory requirements, explains what each recorded field proves in an audit, and shows how to query the logs in Amazon S3 with Amazon Athena.

## Finding and closing gaps in security logging with AI

DevFeed: [Finding and closing gaps in security logging with AI](<https://devfeed.tech/articles/finding-and-closing-gaps-in-security-logging-with-ai-141081.md>)

Original publisher: [Read original article](<https://1password.com/blog/ai-security-logging-gaps>)

Author: info@1password.com (Sanya Kohli)

Published: 2026-11-18T00:00:00Z

Content type: article

Language: en

Sources: [1Password](<https://devfeed.tech/sources/blog-on-1password-blog.md>)

Topics: [Security Information and Event Management (SIEM)](<https://devfeed.tech/topics/siem-security.md>), [Logging](<https://devfeed.tech/topics/logging.md>), [Threat monitoring](<https://devfeed.tech/topics/threat-monitoring.md>), [human review](<https://devfeed.tech/topics/human-review.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>)

Tags: [1password](<https://devfeed.tech/tags/1password.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-skills](<https://devfeed.tech/tags/ai-skills.md>), [ai-tool](<https://devfeed.tech/tags/ai-tool.md>), [audit](<https://devfeed.tech/tags/audit.md>), [detection-rules](<https://devfeed.tech/tags/detection-rules.md>), [developers](<https://devfeed.tech/tags/developers.md>), [inventory](<https://devfeed.tech/tags/inventory.md>), [investigation](<https://devfeed.tech/tags/investigation.md>), [logging](<https://devfeed.tech/tags/logging.md>), [logs](<https://devfeed.tech/tags/logs.md>), [onboarding](<https://devfeed.tech/tags/onboarding.md>), [parsing](<https://devfeed.tech/tags/parsing.md>), [report](<https://devfeed.tech/tags/report.md>), [security](<https://devfeed.tech/tags/security.md>), [security-incident](<https://devfeed.tech/tags/security-incident.md>), [security-information-and-event-management](<https://devfeed.tech/tags/security-information-and-event-management.md>), [siem](<https://devfeed.tech/tags/siem.md>), [skills](<https://devfeed.tech/tags/skills.md>), [visibility](<https://devfeed.tech/tags/visibility.md>)

### AI overview

1Password built a scheduled audit that compares procurement and internal tool inventories with SIEM log sources, flags missing sources and collection or parsing problems, and produces a prioritized report for engineers. Code handles API data collection, matching, and publication; an AI model assesses likely security relevance and explains potential gaps. Reports are reviewed through pull requests and retain history, while checks guard against empty inputs and omitted assessments. For approved gaps, reusable AI skills guide log collection, parsing, access controls, documentation, and detection-rule preparation. Engineers verify findings, approve consequential changes, configure production credentials, and confirm logs are searchable before the workflow advances. The approach can miss tools when names are ambiguous; a SIEM name match does not prove complete activity coverage, and infrequently generated logs may need extra checks. Human review remains necessary.

### Source excerpt

A security incident is the worst time to discover that the logs you need were never collected. Even with a security information and event management (SIEM) in place, critical logging gaps can go unnoticed. Some tools may not send logs at all, while others may appear to be integrated but have collection or parsing issues that make their logs difficult to use during an investigation. With multiple tools, it can be a challenge to know what's missing or whether the logs you have are actually usable. At 1Password, finding these gaps meant manually comparing our tool inventory against SIEM log sources, one tool at a time. The process was time-consuming, difficult to keep up to date, and hard to scale as our environment evolved. We needed a more reliable way to identify gaps before they affected an investigation. We saw an opportunity to use AI to change how we identify security logging gaps and onboard new log sources. Instead of relying on time-consuming manual reviews, we built an approach that uses AI to uncover potential gaps and guide engineers through onboarding, while keeping critical decisions in human hands. Here's how we built it, what we learned, and where AI makes a difference. Collecting logs is only the beginning As 1Password adopts new tools, maintaining security visibility requires more than simply sending logs to the SIEM. We need to determine which logs matter for security, collect them, and ensure they contain the searchable information engineers need during an investigation. Even when logs are successfully ingested, important details can remain buried in unparsed text. Without proper parsing, engineers may struggle to search those details or build reliable detection rules. To address these challenges, we built an automated audit that compares our tool inventories against SIEM log sources and produces a prioritized report of potential logging gaps. For gaps we decide to close, we use AI skills: reusable instruction files that guide an AI tool through sp

## Logging AI Prompts and Responses in Java Without Leaking Sensitive Data

DevFeed: [Logging AI Prompts and Responses in Java Without Leaking Sensitive Data](<https://devfeed.tech/articles/logging-ai-prompts-and-responses-in-java-without-leaking-sensitive-data-133710.md>)

Original publisher: [Read original article](<https://www.sitepoint.com/logging-ai-prompts-and-responses-in-java-without-leaking-sensitive-data/>)

Author: TechPanda

Published: 2026-11-14T06:15:17Z

Content type: article

Language: en

Sources: [SitePoint](<https://devfeed.tech/sources/sitepoint.md>)

Topics: [API Logging](<https://devfeed.tech/topics/api-logging.md>), [data loss prevention](<https://devfeed.tech/topics/data-loss-prevention.md>), [Logging](<https://devfeed.tech/topics/logging.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [Java](<https://devfeed.tech/topics/java.md>), [sensitive data](<https://devfeed.tech/topics/sensitive-data.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-prompts](<https://devfeed.tech/tags/ai-prompts.md>), [data](<https://devfeed.tech/tags/data.md>), [java](<https://devfeed.tech/tags/java.md>), [logging](<https://devfeed.tech/tags/logging.md>), [responses](<https://devfeed.tech/tags/responses.md>), [sensitive-data](<https://devfeed.tech/tags/sensitive-data.md>)

### AI overview

The article recommends logging metadata for every Java AI call while limiting prompt and response content to masked samples and failed calls. Route all content through one PiiMasker before it reaches any logger; use compiled, ordered regex rules for structured data such as emails, card numbers, phone numbers, and bearer tokens. Regex may miss names and sensitive details in free text, so combine it with entity recognition, known-value replacement, and field-level masking during prompt construction. For tracing repeated values, use keyed HMAC pseudonyms rather than unkeyed hashes. Write structured JSON records, keep content briefly, and restrict access. Assemble streamed responses before masking because sensitive values can span chunks; treat tool arguments and results as content too. The excerpt also advises testing masking against messy examples and guarding against raw payloads in debug logs, SDK exceptions, and wire-level HTTP logging.

### Source excerpt

null Continue reading Logging AI Prompts and Responses in Java Without Leaking Sensitive Data on SitePoint.

## Investigate the person behind the risk with Cloud SIEM

DevFeed: [Investigate the person behind the risk with Cloud SIEM](<https://devfeed.tech/articles/investigate-the-person-behind-the-risk-with-cloud-siem-132656.md>)

Original publisher: [Read original article](<https://www.datadoghq.com/blog/cloud-siem-investigate-user-entity-risks/>)

Author: Jason Hunsberger; Jenny Park

Published: 2026-11-13T00:00:00Z

Content type: tutorial

Language: en

Sources: [Datadog](<https://devfeed.tech/sources/datadog-the-monitor-blog.md>)

Topics: [Security Information and Event Management (SIEM)](<https://devfeed.tech/topics/siem-security.md>), [datadog](<https://devfeed.tech/topics/datadog.md>), [Logging](<https://devfeed.tech/topics/logging.md>)

Tags: [about](<https://devfeed.tech/tags/about.md>), [account](<https://devfeed.tech/tags/account.md>), [administration](<https://devfeed.tech/tags/administration.md>), [after](<https://devfeed.tech/tags/after.md>), [all](<https://devfeed.tech/tags/all.md>), [also](<https://devfeed.tech/tags/also.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-siem](<https://devfeed.tech/tags/cloud-siem.md>), [connect](<https://devfeed.tech/tags/connect.md>), [datadog](<https://devfeed.tech/tags/datadog.md>), [google](<https://devfeed.tech/tags/google.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [identity-and-access-management](<https://devfeed.tech/tags/identity-and-access-management.md>), [learn](<https://devfeed.tech/tags/learn.md>), [learn-how-to](<https://devfeed.tech/tags/learn-how-to.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [okta](<https://devfeed.tech/tags/okta.md>), [risk](<https://devfeed.tech/tags/risk.md>), [risks](<https://devfeed.tech/tags/risks.md>), [security](<https://devfeed.tech/tags/security.md>), [siem](<https://devfeed.tech/tags/siem.md>), [threat-detection](<https://devfeed.tech/tags/threat-detection.md>), [threats](<https://devfeed.tech/tags/threats.md>), [users](<https://devfeed.tech/tags/users.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Datadog Cloud SIEM links security signals to directory identities and associated accounts so analysts can investigate risk at the person level. Entity Packs bring identity context from Google Workspace, Microsoft Entra ID, and Okta into signals and User Inventory; entity resolution traces federated identities and assumed roles back to a human user. Analysts can follow a signal into User Inventory to review activity and linked-account risk, then use Entity Risks to inspect the detections contributing to an account's score or rank users by combined risk. The article's example traces a critical-risk account to detections involving disabled audit logging, an Exchange inbox rule, and application consent. Entity Risks notifications can target individual entities or user identity and apply configured conditions; the example rule covers IT Security users at HIGH severity or above. Setup requires a supported Entity Pack and the `SIEM Entities Read` permission.

### Source excerpt

Learn how to connect security signals to users, investigate linked account risks, and prioritize threats with Entity Risks in Datadog Cloud SIEM.

## N-able Disables Cloud Services Following Disclosure of "Able2Shell" Exploit Chains

DevFeed: [N-able Disables Cloud Services Following Disclosure of "Able2Shell" Exploit Chains](<https://devfeed.tech/articles/n-able-disables-cloud-services-following-disclosure-of-able2shell-exploit-chains-124129.md>)

Original publisher: [Read original article](<https://www.huntress.com/blog/n-able-disables-cloud-services-following-disclosure-of-able2shell-exploit-chains>)

Author: Lindsey O'Donnell-Welch; Susannah Matt

Published: 2026-11-09T21:00:00Z

Content type: news

Language: en

Sources: [Cyber Newsroom](<https://devfeed.tech/sources/cyber-newsroom.md>), [Huntress Blog](<https://devfeed.tech/sources/huntress-blog.md>)

Topics: [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>), [cloud service outage management](<https://devfeed.tech/topics/cloud-service-outage-management.md>), [Logging](<https://devfeed.tech/topics/logging.md>), [Managed Services](<https://devfeed.tech/topics/managed-services.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [access-controls](<https://devfeed.tech/tags/access-controls.md>), [active-exploitation](<https://devfeed.tech/tags/active-exploitation.md>), [actively-exploited](<https://devfeed.tech/tags/actively-exploited.md>), [administrator](<https://devfeed.tech/tags/administrator.md>), [all](<https://devfeed.tech/tags/all.md>), [allowed](<https://devfeed.tech/tags/allowed.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [code](<https://devfeed.tech/tags/code.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [critical](<https://devfeed.tech/tags/critical.md>), [disclosure](<https://devfeed.tech/tags/disclosure.md>), [execution](<https://devfeed.tech/tags/execution.md>), [exploit](<https://devfeed.tech/tags/exploit.md>), [n-able](<https://devfeed.tech/tags/n-able.md>), [n-central](<https://devfeed.tech/tags/n-central.md>), [offline](<https://devfeed.tech/tags/offline.md>), [privilege-escalation](<https://devfeed.tech/tags/privilege-escalation.md>), [remote](<https://devfeed.tech/tags/remote.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>)

### AI overview

N-able took its hosted N-central environment offline on November 9 while addressing 33 disclosed critical vulnerabilities affecting Appliance 2026.4.0.31 and likely earlier versions. Chaining them reportedly enables three remote-code-execution exploits and one privilege-escalation exploit to root. As of November 9 at 15:15 UTC, N-able said it had seen no active exploitation; a hotfix was in development with no exact ETA. The excerpt advises on-premises customers to take servers offline and all customers to wait for N-able's confirmation before restoring service. It also recommends reviewing login and authentication activity from November 8 onward and audit logs for suspicious access, scripts, remote sessions, or administrator accounts, and involving incident response if activity is found. Hosted customers should expect an outage and check N-able's status page. The patched version number was not yet known.

### Source excerpt

N-able took N-central offline after 33 critical flaws were disclosed, including chains enabling remote code execution and privilege escalation.

## EventHOI: Event-Driven Resource-Efficient Hand-Object Interaction Logging on Smartglasses

DevFeed: [EventHOI: Event-Driven Resource-Efficient Hand-Object Interaction Logging on Smartglasses](<https://devfeed.tech/articles/eventhoi-event-driven-resource-efficient-hand-object-interaction-logging-on-smartglasses-123684.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.09089>)

Author: Le Zhang, Kailai Cui, Hao Chen, Vlad Roznyatovskiy, Jianzhong Zhang, Anhong Guo, Kang G. Shin, Ke Sun

Published: 2026-11-09T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Distributed Computing](<https://devfeed.tech/sources/arxiv-distributed-computing.md>)

Topics: [Logging](<https://devfeed.tech/topics/logging.md>), [Bluetooth LE](<https://devfeed.tech/topics/bluetooth-le.md>), [smartdevices](<https://devfeed.tech/topics/smartdevices.md>)

Tags: [bandwidth](<https://devfeed.tech/tags/bandwidth.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [ble](<https://devfeed.tech/tags/ble.md>), [bluetooth](<https://devfeed.tech/tags/bluetooth.md>), [bluetooth-low-energy](<https://devfeed.tech/tags/bluetooth-low-energy.md>), [compression](<https://devfeed.tech/tags/compression.md>), [cs-cv](<https://devfeed.tech/tags/cs-cv.md>), [cs-dc](<https://devfeed.tech/tags/cs-dc.md>), [cs-hc](<https://devfeed.tech/tags/cs-hc.md>), [energy](<https://devfeed.tech/tags/energy.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [event-driven](<https://devfeed.tech/tags/event-driven.md>), [imu](<https://devfeed.tech/tags/imu.md>), [logging](<https://devfeed.tech/tags/logging.md>), [prototype](<https://devfeed.tech/tags/prototype.md>), [recognition](<https://devfeed.tech/tags/recognition.md>), [rgb](<https://devfeed.tech/tags/rgb.md>), [streaming](<https://devfeed.tech/tags/streaming.md>)

### AI overview

EventHOI uses low-power event sensing to decide when smartglasses should capture RGB images and where to preserve visual detail. An IMU-based pipeline suppresses motion caused by the wearer, letting residual hand-object motion guide capture timing and spatial compression. On a 50-hour benchmark involving 97 subjects and a 20-hour dataset collected from 10 participants, the prototype reduced always-on backend power consumption 5.8-10.4x and uplink bandwidth 2.9x versus RGB-only baselines, with minimal loss in hand-object interaction recognition accuracy. Its RGB uplink stayed below 130 kbps, within commodity Bluetooth Low Energy bandwidth budgets.

### Source excerpt

arXiv:2611.09089v1 Announce Type: new Abstract: Hand-object interactions (HOIs) can be captured by smartglasses to learn how people manipulate objects in daily life. Automatic logging of these interactions from an egocentric perspective provides time-stamped evidence of daily actions for applications like memory assistance. However, continuous RGB capture and wireless transmission exceed the energy and bandwidth budgets of smartglasses. We present EventHOI, an event-driven sensing and compression system that couples selective RGB capture with HOI-aware encoding to enable egocentric logging over Bluetooth Low Energy (BLE) while preserving downstream HOI logging performance. Our key insight is to use low-power event sensing both to determine when RGB capture is needed and to identify where visual detail must be preserved. A lightweight IMU-based egomotion cancellation pipeline suppresses egomotion-induced events so that residual HOI motion can guide RGB triggering and spatial compression. We build a smartglasses prototype and conduct an end-to-end evaluation of EventHOI on a 50-hour egocentric benchmark with 97 subjects and a 20-hour real-world dataset we collect from 10 participants, together covering a broad range of daily-life scenarios and environments. Compared to RGB-only baselines, EventHOI reduces always-on backend power consumption by 5.8-10.4x and uplink bandwidth by 2.9x, with minimal HOI recognition accuracy loss. The resulting RGB uplink of less than 130 kbps fits within commodity BLE bandwidth budgets, making stable BLE video streaming feasible for egocentric HOI logging. Demo video and project website: https://eventhoi.github.io

## SSO is broken? The answer is already in your session log

DevFeed: [SSO is broken? The answer is already in your session log](<https://devfeed.tech/articles/sso-is-broken-the-answer-is-already-in-your-session-log-124330.md>)

Original publisher: [Read original article](<https://workos.com/blog/sso-broken-session-log>)

Author: WorkOS

Published: 2026-11-09T00:00:00Z

Content type: tutorial

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [sessions](<https://devfeed.tech/topics/sessions.md>), [Logging](<https://devfeed.tech/topics/logging.md>), [log management](<https://devfeed.tech/topics/log-management.md>)

Tags: [configuration](<https://devfeed.tech/tags/configuration.md>), [customer](<https://devfeed.tech/tags/customer.md>), [datadog](<https://devfeed.tech/tags/datadog.md>), [events](<https://devfeed.tech/tags/events.md>), [failed](<https://devfeed.tech/tags/failed.md>), [identity-provider](<https://devfeed.tech/tags/identity-provider.md>), [it](<https://devfeed.tech/tags/it.md>), [sso](<https://devfeed.tech/tags/sso.md>), [status](<https://devfeed.tech/tags/status.md>), [workos](<https://devfeed.tech/tags/workos.md>)

### AI overview

WorkOS session logs can pinpoint where an SSO failure occurs and who can fix it. In the dashboard, filter a connection's Sessions tab by email, status, origin or time, then inspect the IdP request, response and any error. Success shifts investigation to app handling or authorization; failed sessions may point to the IdP or to your attribute mapping. Required attributes that are missing can fail sign-in, while unmapped optional attributes return null and may leave a successful session with empty fields. Origin helps distinguish app-started, IdP-started and Admin Portal test flows; OIDC is SP-initiated only. For patterns, use SSO events with connection IDs and error details: stream them to Datadog or count failures by connection through the cursor-paginated Events API. When the IdP is responsible, share the session ID, timestamp, status and response with its administrator.

### Source excerpt

Every WorkOS SSO attempt records its status, origin and the IdP's response. Read it in five minutes and know whether the fix is yours or the customer's.

## On the hunt for ARTEX: understanding agentic attacks in AWS environments

DevFeed: [On the hunt for ARTEX: understanding agentic attacks in AWS environments](<https://devfeed.tech/articles/on-the-hunt-for-artex-understanding-agentic-attacks-in-aws-environments-126361.md>)

Original publisher: [Read original article](<https://securitylabs.datadoghq.com/articles/artex-agentic-attacks-aws-environments/>)

Author: Julie Agnes Sparks

Published: 2026-11-09T00:00:00Z

Content type: news

Language: en

Sources: [Datadog Security Labs](<https://devfeed.tech/sources/datadog-security-labs.md>)

Topics: [Cybersecurity](<https://devfeed.tech/topics/cybersecurity.md>), [Amazon Cognito](<https://devfeed.tech/topics/amazon-cognito.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [Amazon CloudWatch Logs](<https://devfeed.tech/topics/amazon-cloudwatch-logs.md>), [AWS CloudTrail](<https://devfeed.tech/topics/aws-cloudtrail.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Logging](<https://devfeed.tech/topics/logging.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-native](<https://devfeed.tech/tags/ai-native.md>), [artex](<https://devfeed.tech/tags/artex.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [aws](<https://devfeed.tech/tags/aws.md>), [cloudwatch](<https://devfeed.tech/tags/cloudwatch.md>), [cognito](<https://devfeed.tech/tags/cognito.md>), [framework](<https://devfeed.tech/tags/framework.md>), [keys](<https://devfeed.tech/tags/keys.md>), [penetration](<https://devfeed.tech/tags/penetration.md>), [public](<https://devfeed.tech/tags/public.md>), [wild](<https://devfeed.tech/tags/wild.md>)

### AI overview

Datadog observed ARTEX-attributed activity in AWS environments using compromised long-term IAM keys and public Cognito user pools. With keys, it repeatedly searched CloudWatch logs for financial terms, file paths, secrets, and internal details using `FilterLogEvents`; in Cognito cases, it attempted account recovery and sign-up, collected tokens, then tried AWS resource discovery. The Cognito session described lacked permissions, so its discovery calls failed. ARTEX coordinates LLM agents through a hosted platform that can switch among configured inference providers and keys, meaning behavior can vary with the model. For hunting, the excerpt recommends checking ARTEX user agents and associated IPs, then reviewing noisy probing, S3 enumeration, permission errors, unusual credential use, and relevant CloudTrail events. It also notes that long-lived access keys should be rotated or removed when inactive or unused.

### Source excerpt

We share in-the-wild activity from ARTEX, an AI-native penetration framework, against AWS environments, including CloudWatch log hunting with compromised access keys and abuse of public Cognito user pools.

## Log Management vs SIEM: Understanding the Key Differences and Use Cases

DevFeed: [Log Management vs SIEM: Understanding the Key Differences and Use Cases](<https://devfeed.tech/articles/log-management-vs-siem-understanding-the-key-differences-and-use-cases-117734.md>)

Original publisher: [Read original article](<https://newrelic.com/blog/log/log-management-vs-siem>)

Author: John Blust

Published: 2026-11-04T12:00:00Z

Content type: article

Language: en

Sources: [New Relic](<https://devfeed.tech/sources/new-relic.md>)

Topics: [log management](<https://devfeed.tech/topics/log-management.md>), [Security Information and Event Management (SIEM)](<https://devfeed.tech/topics/siem-security.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Logging](<https://devfeed.tech/topics/logging.md>), [Threat monitoring](<https://devfeed.tech/topics/threat-monitoring.md>)

Tags: [ai-powered](<https://devfeed.tech/tags/ai-powered.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [devops](<https://devfeed.tech/tags/devops.md>), [log-management](<https://devfeed.tech/tags/log-management.md>), [security](<https://devfeed.tech/tags/security.md>), [siem](<https://devfeed.tech/tags/siem.md>), [use-cases](<https://devfeed.tech/tags/use-cases.md>), [visibility](<https://devfeed.tech/tags/visibility.md>)

### AI overview

Log management and SIEM both collect and analyze telemetry, but serve different workflows: log management supports operational visibility and troubleshooting, while SIEM correlates security telemetry for threat detection, incident response, and compliance. Log management is often sufficient for teams focused on system reliability; SIEM is needed for active security monitoring and compliance reporting. Many organizations use both, with shared telemetry helping teams investigate incidents across operational and security contexts. Tool choice depends on use case, retention and scale needs, integrations, and compliance obligations.

### Source excerpt

Discover the differences between log management vs SIEM and learn when each tool is right for your team to improve visibility and security.

## DevOps Log Management: A Comprehensive Evaluation Guide

DevFeed: [DevOps Log Management: A Comprehensive Evaluation Guide](<https://devfeed.tech/articles/devops-log-management-a-comprehensive-evaluation-guide-117733.md>)

Original publisher: [Read original article](<https://newrelic.com/blog/log/devops-log-management>)

Author: John Blust

Published: 2026-11-04T12:00:00Z

Content type: article

Language: en

Sources: [New Relic](<https://devfeed.tech/sources/new-relic.md>)

Topics: [log management](<https://devfeed.tech/topics/log-management.md>), [Logging](<https://devfeed.tech/topics/logging.md>), [DevOps](<https://devfeed.tech/topics/devops.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Application Performance Management (APM)](<https://devfeed.tech/topics/apm.md>), [Azure DevOps](<https://devfeed.tech/topics/azure-devops.md>), [Security Information and Event Management (SIEM)](<https://devfeed.tech/topics/siem-security.md>)

Tags: [accelerate](<https://devfeed.tech/tags/accelerate.md>), [access-controls](<https://devfeed.tech/tags/access-controls.md>), [agents](<https://devfeed.tech/tags/agents.md>), [aggregation](<https://devfeed.tech/tags/aggregation.md>), [ai](<https://devfeed.tech/tags/ai.md>), [alert](<https://devfeed.tech/tags/alert.md>), [alerting](<https://devfeed.tech/tags/alerting.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [anomaly-detection](<https://devfeed.tech/tags/anomaly-detection.md>), [api](<https://devfeed.tech/tags/api.md>), [apm](<https://devfeed.tech/tags/apm.md>), [application](<https://devfeed.tech/tags/application.md>), [applications](<https://devfeed.tech/tags/applications.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [data](<https://devfeed.tech/tags/data.md>), [devops](<https://devfeed.tech/tags/devops.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [guide](<https://devfeed.tech/tags/guide.md>), [log-management](<https://devfeed.tech/tags/log-management.md>), [noise](<https://devfeed.tech/tags/noise.md>)

### AI overview

Effective DevOps log management centers on searchable, structured logs correlated with metrics, traces and deployment data, so teams can trace incidents across distributed services. The guide distinguishes Azure DevOps audit logs, which record administrative activity in the platform, from operational logs that capture runtime behavior. It outlines a pipeline of collection, enrichment and indexing, analysis and alerting, and retention and governance. Suggested practices include consistent structured logging, sampling or deduplication of noisy events, trace IDs and deployment markers. Its evaluation criteria include query performance, ingestion flexibility, noise controls, alert quality, pricing and ease of parsing. The guide presents New Relic as a unified option with cross-telemetry querying, no-code parsing and federated logs; these are source claims. It also states that pricing is 100 GB/month free and $0.40/GB thereafter.

### Source excerpt

Discover how effective devops log management helps you quickly troubleshoot incidents, reduce noise, and improve operational visibility with the right data.

## Find your logging gaps before they become compliance gaps with CloudTrail Data Event Coverage

DevFeed: [Find your logging gaps before they become compliance gaps with CloudTrail Data Event Coverage](<https://devfeed.tech/articles/find-your-logging-gaps-before-they-become-compliance-gaps-with-cloudtrail-data-event-coverage-117168.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/mt/find-your-logging-gaps-before-they-become-compliance-gaps-with-cloudtrail-data-event-coverage/>)

Author: Damini Kumar

Published: 2026-11-03T23:32:28Z

Content type: article

Language: en

Sources: [AWS Cloud Operations Blog](<https://devfeed.tech/sources/aws-cloud-operations-blog.md>)

Topics: [AWS CloudTrail](<https://devfeed.tech/topics/aws-cloudtrail.md>), [Logging](<https://devfeed.tech/topics/logging.md>), [API Logging](<https://devfeed.tech/topics/api-logging.md>), [audit](<https://devfeed.tech/topics/audit.md>), [Threat monitoring](<https://devfeed.tech/topics/threat-monitoring.md>)

Tags: [account](<https://devfeed.tech/tags/account.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [api](<https://devfeed.tech/tags/api.md>), [auditing](<https://devfeed.tech/tags/auditing.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cloudtrail](<https://devfeed.tech/tags/aws-cloudtrail.md>), [cloud-operations](<https://devfeed.tech/tags/cloud-operations.md>), [cloudtrail](<https://devfeed.tech/tags/cloudtrail.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [console](<https://devfeed.tech/tags/console.md>), [control](<https://devfeed.tech/tags/control.md>), [control-plane](<https://devfeed.tech/tags/control-plane.md>), [coverage](<https://devfeed.tech/tags/coverage.md>), [data](<https://devfeed.tech/tags/data.md>), [event](<https://devfeed.tech/tags/event.md>), [event-coverage](<https://devfeed.tech/tags/event-coverage.md>), [events](<https://devfeed.tech/tags/events.md>), [logging](<https://devfeed.tech/tags/logging.md>), [management](<https://devfeed.tech/tags/management.md>), [operational](<https://devfeed.tech/tags/operational.md>), [records](<https://devfeed.tech/tags/records.md>), [resources](<https://devfeed.tech/tags/resources.md>)

### AI overview

CloudTrail's Data event coverage page shows which supported resources have data event logging enabled, with overall and service category coverage scores and resource level gaps. It can display a single account or, after setup, an organization's member accounts and Regions. Organization view requires AWS Organizations membership, Resource Explorer organization level aggregation, and an organization scoped view; single account discovery also requires Resource Explorer indexing. From a category card, users can select resources or resource types and choose a trail or, for eligible existing customers, an event data store as the destination. Data events incur separate charges based on activity volume. The page's one click setup is less granular than advanced event selectors, which can filter by resource type, ARN, operation type, and excluded patterns; those selectors can be configured directly in CloudTrail or IaC. The page can also help check that IaC configurations provide expected coverage.

### Source excerpt

AWS CloudTrail now includes a Data event coverage page in the AWS CloudTrail console, giving you a single view of how well your resources are covered by data event logging. CloudTrail records API activity across your AWS account for security auditing, compliance, and operational troubleshooting. Management events, the control-plane actions such as creating a bucket [...]

## Azure Cloud HSM Hardware Audit Logging: Verifiable audit trails for security and compliance

DevFeed: [Azure Cloud HSM Hardware Audit Logging: Verifiable audit trails for security and compliance](<https://devfeed.tech/articles/azure-cloud-hsm-hardware-audit-logging-verifiable-audit-trails-for-security-and-compliance-113314.md>)

Original publisher: [Read original article](<https://azure.microsoft.com/en-us/blog/azure-cloud-hsm-hardware-audit-logging-verifiable-audit-trails-for-security-and-compliance/>)

Author: Salim Chawro

Published: 2026-10-29T16:00:00Z

Content type: release

Language: en

Sources: [Microsoft Azure](<https://devfeed.tech/sources/microsoft-azure-blog.md>)

Topics: [Logging](<https://devfeed.tech/topics/logging.md>), [audit](<https://devfeed.tech/topics/audit.md>), [Azure](<https://devfeed.tech/topics/azure.md>), [Threat monitoring](<https://devfeed.tech/topics/threat-monitoring.md>), [cloud security](<https://devfeed.tech/topics/cloud-security.md>)

Tags: [audit](<https://devfeed.tech/tags/audit.md>), [azure](<https://devfeed.tech/tags/azure.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [devops](<https://devfeed.tech/tags/devops.md>), [forensic](<https://devfeed.tech/tags/forensic.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [hybrid-plus-multicloud](<https://devfeed.tech/tags/hybrid-plus-multicloud.md>), [investigations](<https://devfeed.tech/tags/investigations.md>), [logging](<https://devfeed.tech/tags/logging.md>), [management-and-governance](<https://devfeed.tech/tags/management-and-governance.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [operations](<https://devfeed.tech/tags/operations.md>), [security](<https://devfeed.tech/tags/security.md>), [security-and-compliance](<https://devfeed.tech/tags/security-and-compliance.md>)

### AI overview

Azure Cloud HSM Hardware Audit Logging captures HSM-generated records for supported management operations, including authentication and sessions, user and administrator changes, policy and configuration updates, key lifecycle activity, and backup or restore. Events are delivered to Azure Monitor Log Analytics for monitoring and investigation workflows, including Microsoft Sentinel. Customers can also access human-readable records plus HSM-signed binary data, signatures, certificates, and verification utilities to independently check audit batches' authenticity and integrity. Logging is an immutable HSM partition policy and is automatically enabled for newly provisioned resources in regions where available; rollout is underway across public regions. Customers still need to manage monitoring access, retention, alerts, and review processes.

### Source excerpt

Security, compliance, and operations teams can use this hardware-originated evidence for monitoring, compliance reporting, and forensic investigations. The post Azure Cloud HSM Hardware Audit Logging: Verifiable audit trails for security and compliance appeared first on Microsoft Azure Blog.

## Reports of SIEM's Death Have Been Greatly Exaggerated

DevFeed: [Reports of SIEM's Death Have Been Greatly Exaggerated](<https://devfeed.tech/articles/reports-of-siem-s-death-have-been-greatly-exaggerated-107774.md>)

Original publisher: [Read original article](<https://www.huntress.com/blog/reports-that-siem-is-dead-are-exaggerated>)

Author: Ben Bernstein

Published: 2026-10-29T14:00:00Z

Content type: opinion

Language: en

Sources: [Huntress Blog](<https://devfeed.tech/sources/huntress-blog.md>)

Topics: [Security Information and Event Management (SIEM)](<https://devfeed.tech/topics/siem-security.md>), [Logging](<https://devfeed.tech/topics/logging.md>), [threat detection](<https://devfeed.tech/topics/threat-detection.md>), [alert triage](<https://devfeed.tech/topics/alert-triage.md>), [Shared Responsibility Model](<https://devfeed.tech/topics/shared-responsibility-model.md>), [Endpoint Security & XDR](<https://devfeed.tech/topics/endpoint-security-xdr.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-inference](<https://devfeed.tech/tags/ai-inference.md>), [ai-native](<https://devfeed.tech/tags/ai-native.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [approach](<https://devfeed.tech/tags/approach.md>), [availability](<https://devfeed.tech/tags/availability.md>), [awareness-training](<https://devfeed.tech/tags/awareness-training.md>), [cost](<https://devfeed.tech/tags/cost.md>), [death](<https://devfeed.tech/tags/death.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [legacy](<https://devfeed.tech/tags/legacy.md>), [logging](<https://devfeed.tech/tags/logging.md>), [model](<https://devfeed.tech/tags/model.md>), [pricing](<https://devfeed.tech/tags/pricing.md>), [reports](<https://devfeed.tech/tags/reports.md>), [security](<https://devfeed.tech/tags/security.md>), [siem](<https://devfeed.tech/tags/siem.md>), [strategy](<https://devfeed.tech/tags/strategy.md>)

### AI overview

SIEM remains useful, but the article argues that ingest-everything pricing creates high costs and alert clutter, while AI-driven on-demand querying can replace storage costs with token costs and bring retention, API availability, and compliance limits. It recommends keeping logs that help detect or investigate threats and logs required by regulations, auditors, or insurers, and dropping the rest. AI is presented as most useful after filtering, for correlating endpoint, identity, and IT logs, adding triage context, and summarizing investigations, with detections and analysts making the final decisions. Managed partners can handle broad threat detection, 24/7 triage, tuning, and remediation; organizations must supply environment-specific context, write custom detections, and agree internally on response decisions.

### Source excerpt

SIEM isn't dead. Its bloated pricing model is. Discover why legacy pricing models need to go, how AI fits in, and how to build a smarter, cost-effective security logging strategy.

## Chinese Hackers Quietly Used Low-Severity ESXi Logging Flaw as Zero-Day

DevFeed: [Chinese Hackers Quietly Used Low-Severity ESXi Logging Flaw as Zero-Day](<https://devfeed.tech/articles/chinese-hackers-quietly-used-low-severity-esxi-logging-flaw-as-zero-day-105959.md>)

Original publisher: [Read original article](<https://www.securityweek.com/chinese-hackers-quietly-used-low-severity-esxi-logging-flaw-as-zero-day/>)

Author: Ionut Arghire

Published: 2026-10-29T08:01:05Z

Content type: news

Language: en

Sources: [SecurityWeek](<https://devfeed.tech/sources/securityweek.md>)

Topics: [Logging](<https://devfeed.tech/topics/logging.md>), [bug](<https://devfeed.tech/topics/bug.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [audit](<https://devfeed.tech/tags/audit.md>), [audit-trail](<https://devfeed.tech/tags/audit-trail.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authentication-bypass](<https://devfeed.tech/tags/authentication-bypass.md>), [broadcom](<https://devfeed.tech/tags/broadcom.md>), [china](<https://devfeed.tech/tags/china.md>), [cisa](<https://devfeed.tech/tags/cisa.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [crowdstrike](<https://devfeed.tech/tags/crowdstrike.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [defect](<https://devfeed.tech/tags/defect.md>), [defects](<https://devfeed.tech/tags/defects.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [esxi](<https://devfeed.tech/tags/esxi.md>), [exploited](<https://devfeed.tech/tags/exploited.md>), [featured](<https://devfeed.tech/tags/featured.md>), [hackers](<https://devfeed.tech/tags/hackers.md>), [logging](<https://devfeed.tech/tags/logging.md>), [vmware](<https://devfeed.tech/tags/vmware.md>), [vmware-esxi](<https://devfeed.tech/tags/vmware-esxi.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>), [zero-day](<https://devfeed.tech/tags/zero-day.md>)

### AI overview

CVE-2026-41709 is an insufficient-logging flaw in VMware ESXi that lets users who already have administrator privileges perform certain operations without those actions being logged. CISA added it to its Known Exploited Vulnerabilities catalog and urged federal agencies to patch within two weeks. CrowdStrike reported that China-nexus actor Warp Panda used the flaw as a zero-day in intrusions at US organizations, including law firms, reducing audit-trail visibility in attacks through early 2026. The excerpt lists patched releases: ESXi-9.1.0.0-25370933, ESXi-9.0.2.0100-25595025, and ESXi80U3j-25429389 and newer. CISA did not provide details of observed exploitation.

### Source excerpt

CVE-2026-41709 allows attackers with administrative privileges to perform operations without being logged. The post Chinese Hackers Quietly Used Low-Severity ESXi Logging Flaw as Zero-Day appeared first on SecurityWeek.

## Elastic Cloud Serverless audit logs: Ship the trail to Observability or Security

DevFeed: [Elastic Cloud Serverless audit logs: Ship the trail to Observability or Security](<https://devfeed.tech/articles/elastic-cloud-serverless-audit-logs-ship-the-trail-to-observability-or-security-106464.md>)

Original publisher: [Read original article](<https://www.elastic.co/search-labs/blog/elastic-cloud-serverless-audit-logs>)

Author: Valentin Crettaz

Published: 2026-10-29T00:00:00Z

Content type: article

Language: en

Sources: [Elasticsearch Labs](<https://devfeed.tech/sources/elasticsearch-labs.md>)

Topics: [Elastic Cloud](<https://devfeed.tech/topics/elastic-cloud.md>), [Logging](<https://devfeed.tech/topics/logging.md>), [Threat monitoring](<https://devfeed.tech/topics/threat-monitoring.md>), [observability pipelines](<https://devfeed.tech/topics/observability-pipelines.md>), [Security](<https://devfeed.tech/topics/security.md>), [observability](<https://devfeed.tech/topics/observability.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [alerting](<https://devfeed.tech/tags/alerting.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [audit](<https://devfeed.tech/tags/audit.md>), [audit-logs](<https://devfeed.tech/tags/audit-logs.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [dashboards](<https://devfeed.tech/tags/dashboards.md>), [detection](<https://devfeed.tech/tags/detection.md>), [elastic](<https://devfeed.tech/tags/elastic.md>), [elastic-cloud](<https://devfeed.tech/tags/elastic-cloud.md>), [elastic-cloud-serverless](<https://devfeed.tech/tags/elastic-cloud-serverless.md>), [forensics](<https://devfeed.tech/tags/forensics.md>), [kibana](<https://devfeed.tech/tags/kibana.md>), [logs](<https://devfeed.tech/tags/logs.md>), [object](<https://devfeed.tech/tags/object.md>), [observability](<https://devfeed.tech/tags/observability.md>), [operations](<https://devfeed.tech/tags/operations.md>), [rules](<https://devfeed.tech/tags/rules.md>), [security](<https://devfeed.tech/tags/security.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [space](<https://devfeed.tech/tags/space.md>)

### AI overview

Elastic Cloud Serverless log delivery is generally available for shipping a source project's Elasticsearch and Kibana activity to an Observability or Security project in the same organization. Multiple sources can share a destination; ingest and retention are billed there, and retention is configurable. Five Ignore filters can drop matching events before delivery to reduce volume and cost. The stream covers saved-object changes, index access, sign-ins and access failures, with project and producer fields for attribution. Eight included alert rules watch for credential attack patterns; the first-seen identity rule needs at least a day of history. Seven dashboards include Kibana Object Forensics, Elasticsearch Data Access and Identity & Access. Enabling delivery requires Admin or Editor access on the source project. Organization administration logs are described as upcoming, not part of this release.

### Source excerpt

Eight alerting rules and seven dashboards arrive with the logs, including Kibana Object Forensics, where a deleted detection rule shows up with the person who deleted it and the space it was in.

## Modernizing Cloud Admission Control: Off the Global Read Path

DevFeed: [Modernizing Cloud Admission Control: Off the Global Read Path](<https://devfeed.tech/articles/modernizing-cloud-admission-control-off-the-global-read-path-105530.md>)

Original publisher: [Read original article](<https://hackernoon.com/modernizing-cloud-admission-control-off-the-global-read-path?source=rss>)

Author: hareendrasura

Published: 2026-10-28T21:43:39Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>), [Distributed Systems & Parallel Computing](<https://devfeed.tech/topics/distributed-systems-parallel-computing.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [versioning](<https://devfeed.tech/topics/versioning.md>), [Logging](<https://devfeed.tech/topics/logging.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>)

Tags: [admission](<https://devfeed.tech/tags/admission.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [canary](<https://devfeed.tech/tags/canary.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-admission-control](<https://devfeed.tech/tags/cloud-admission-control.md>), [cloud-computing](<https://devfeed.tech/tags/cloud-computing.md>), [cloud-infrastructure](<https://devfeed.tech/tags/cloud-infrastructure.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [failure](<https://devfeed.tech/tags/failure.md>), [fleet](<https://devfeed.tech/tags/fleet.md>), [global](<https://devfeed.tech/tags/global.md>), [local](<https://devfeed.tech/tags/local.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [modernizing](<https://devfeed.tech/tags/modernizing.md>), [site-reliability-engineering](<https://devfeed.tech/tags/site-reliability-engineering.md>), [snapshots](<https://devfeed.tech/tags/snapshots.md>), [software-architecture](<https://devfeed.tech/tags/software-architecture.md>), [system-design](<https://devfeed.tech/tags/system-design.md>)

### AI overview

The proposal removes global reads from the admission request path by publishing versioned, signed capacity snapshots to isolated cells. Each cell makes decisions from an in-memory snapshot and a transactional local ledger; freshness limits move decisions from the normal overcommit ratio to a conservative ratio, then to static 1.0 capacity with sheddable requests rejected. This keeps consumption accounting local while forecast and policy data may become stale. Snapshot validation, staged rollout, and shadow decision comparisons help limit migration and bad-publication risks. The trade-offs are reduced utilization during global-plane outages, possible stranded capacity across cells, and operating both systems during migration. The text also reports a 25% reduction in P95 tail latency and 90% fewer dependency-related system-wide incidents from prior modernization work.

### Source excerpt

Why synchronous global reads turn cloud admission control into a fleet-wide failure domain, and how signed snapshots and cell-local ledgers fix it.

## The euro-sovereignty playbook: How telcos are transforming into trusted AI factories

DevFeed: [The euro-sovereignty playbook: How telcos are transforming into trusted AI factories](<https://devfeed.tech/articles/the-euro-sovereignty-playbook-how-telcos-are-transforming-into-trusted-ai-factories-105356.md>)

Original publisher: [Read original article](<https://www.cio.com/article/4241805/the-euro-sovereignty-playbook-how-telcos-are-transforming-into-trusted-ai-factories.html>)

Author: tohara

Published: 2026-10-28T17:33:15Z

Content type: article

Language: en

Sources: [CIO](<https://devfeed.tech/sources/cio.md>)

Topics: [Sovereign AI](<https://devfeed.tech/topics/sovereign-ai.md>), [digital sovereignty](<https://devfeed.tech/topics/digital-sovereignty.md>), [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [ai regulation](<https://devfeed.tech/topics/ai-regulation.md>), [Advantages and Disadvantages of Cloud Service Models](<https://devfeed.tech/topics/advantages-and-disadvantages-of-cloud-service-models.md>), [ai security](<https://devfeed.tech/topics/ai-security.md>), [Advanced AI workflows](<https://devfeed.tech/topics/advanced-ai-workflows.md>), [Logging](<https://devfeed.tech/topics/logging.md>), [LLM security](<https://devfeed.tech/topics/llm-security.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-factories](<https://devfeed.tech/tags/ai-factories.md>), [ai-model](<https://devfeed.tech/tags/ai-model.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [banking](<https://devfeed.tech/tags/banking.md>), [border](<https://devfeed.tech/tags/border.md>), [cios](<https://devfeed.tech/tags/cios.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-environments](<https://devfeed.tech/tags/cloud-environments.md>), [control](<https://devfeed.tech/tags/control.md>), [core](<https://devfeed.tech/tags/core.md>), [corporate](<https://devfeed.tech/tags/corporate.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cross-border](<https://devfeed.tech/tags/cross-border.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [data](<https://devfeed.tech/tags/data.md>), [data-center](<https://devfeed.tech/tags/data-center.md>), [edition-us](<https://devfeed.tech/tags/edition-us.md>), [euro](<https://devfeed.tech/tags/euro.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [sovereignty](<https://devfeed.tech/tags/sovereignty.md>), [storytype-brandpost](<https://devfeed.tech/tags/storytype-brandpost.md>), [trusted-ai](<https://devfeed.tech/tags/trusted-ai.md>)

### AI overview

The article presents regional telcos as providers of sovereign AI infrastructure for organizations that need data and operations to remain under local geographic and legal control. It says localized networks and data centers can host regulated AI workloads, while HPE AI Factory systems with NVIDIA provide computing and networking, and HPE Morpheus Software with NVIDIA frameworks supports workload management, security controls, and audit logging. It recommends checking geographic isolation, data privacy, automated compliance records, and unified hybrid-cloud management before choosing a provider. These are the article's claims about an approach; it does not provide comparative performance or independent evidence that the named systems meet every requirement.

### Source excerpt

Geopolitical reality is transforming digital architecture from a relatively minor procurement detail into a core pillar of corporate risk management. With regulations such as the European Union's NIS2 Directive and the EU AI Act imposing data residency and algorithmic transparency mandates, global CIOs can no longer outsource their core intelligence infrastructure to generic public clouds. For organizations operating across strict regulatory jurisdictions, data isolation and local operational continuity are no longer secondary objectives--they are essential commercial requirements. This regulatory landscape has triggered a significant structural shift: regional telecommunications providers are rapidly evolving into sovereign AI factories. By capitalizing on their highly secure, localized networks and existing data center footprints, telcos are providing localized cloud environments engineered explicitly to keep operational data within strictly defined borders. This trend allows enterprises in highly regulated sectors--such as banking, healthcare, and public services--to leverage advanced genAI models without fear of cross-border data leakage or foreign legal interventions. The mandate for digital self-reliance The concept of sovereign AI centers on the idea that a nation or a region's data, intelligence, and underlying digital infrastructure must remain under its own geographic and legal control. When an enterprise trains an AI model on proprietary intellectual property, customer interactions, or national infrastructure data within a public cloud framework, that data often crosses regional borders. This fragmentation subjects the organization to conflicting legal jurisdictions, potential surveillance risks, and the unpredictability of foreign supply chains. For European enterprise leaders, the stakes are high. Under the NIS2 framework, corporate executives face direct personal liability for cybersecurity and data governance failures within critical entities. Consequent

## Elastic is a Strong Performer in The Forrester Wave™ for AIOps Platforms, Q4 2026

DevFeed: [Elastic is a Strong Performer in The Forrester Wave™ for AIOps Platforms, Q4 2026](<https://devfeed.tech/articles/elastic-is-a-strong-performer-in-the-forrester-wavetm-for-aiops-platforms-q4-2026-105794.md>)

Original publisher: [Read original article](<https://www.elastic.co/blog/forrester-wave-aiops-platforms-2026>)

Author: Natalie Blake

Published: 2026-10-28T00:00:00Z

Content type: release

Language: en

Sources: [Elastic Blog](<https://devfeed.tech/sources/elastic-blog-elasticsearch-kibana-and-elk-stack.md>)

Topics: [AIOps](<https://devfeed.tech/topics/aiops.md>), [AI in IT operations](<https://devfeed.tech/topics/ai-in-it-operations.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Logging](<https://devfeed.tech/topics/logging.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-coworker](<https://devfeed.tech/tags/ai-coworker.md>), [ai-powered](<https://devfeed.tech/tags/ai-powered.md>), [ai-sre](<https://devfeed.tech/tags/ai-sre.md>), [ai-stack](<https://devfeed.tech/tags/ai-stack.md>), [aiops](<https://devfeed.tech/tags/aiops.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [alignment](<https://devfeed.tech/tags/alignment.md>), [always-on-ai](<https://devfeed.tech/tags/always-on-ai.md>), [complete](<https://devfeed.tech/tags/complete.md>), [context](<https://devfeed.tech/tags/context.md>), [elastic](<https://devfeed.tech/tags/elastic.md>), [forrester](<https://devfeed.tech/tags/forrester.md>), [investigation](<https://devfeed.tech/tags/investigation.md>), [observability-log-analytics-metrics](<https://devfeed.tech/tags/observability-log-analytics-metrics.md>), [opentelemetry-log-management](<https://devfeed.tech/tags/opentelemetry-log-management.md>), [platforms](<https://devfeed.tech/tags/platforms.md>), [q4](<https://devfeed.tech/tags/q4.md>)

### AI overview

Forrester named Elastic a Strong Performer in its Q4 2026 AIOps Platforms Wave, evaluating 10 providers across 24 criteria; Elastic says it received the highest possible scores in five, including explainability, OpenTelemetry and GitOps alignment, sovereign deployment, and pricing transparency. Elastic describes its nightshift AI SRE as an always-on agent that shows its reasoning, data, alternatives, and supporting evidence for engineers to verify before approving actions. It says cost-efficient storage lets teams retain logs, traces, and metrics together, while compact environmental context helps the agent reason efficiently. The agent carries lessons from earlier incidents into later investigations and aims to surface issues beyond rule-based alerts. Elastic also emphasizes native-form telemetry and OpenTelemetry to support instrumentation changes without rebuilding pipelines or translating schemas. These are Elastic's descriptions; the article notes Forrester does not endorse products or advise selection based on its ratings.

### Source excerpt

Elastic is a Strong Performer in The Forrester Wave™: AIOps Platforms, Q4 2026. Elastic's AI is built on complete context, shows its evidence, and learns from every investigation.

## Nexus OS Fails to Send Syslog Records to a Silent Host

DevFeed: [Nexus OS Fails to Send Syslog Records to a Silent Host](<https://devfeed.tech/articles/nexus-os-fails-to-send-syslog-records-to-a-silent-host-102657.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2026/10/nexus-os-logging-silent-host/>)

Published: 2026-10-27T10:02:00Z

Content type: article

Language: en

Sources: [ipSpace](<https://devfeed.tech/sources/ipspace-net-blog-2.md>)

Topics: [Logging](<https://devfeed.tech/topics/logging.md>), [Network Configuration](<https://devfeed.tech/topics/network-configuration.md>)

Tags: [arp](<https://devfeed.tech/tags/arp.md>), [cache](<https://devfeed.tech/tags/cache.md>), [capture](<https://devfeed.tech/tags/capture.md>), [cisco](<https://devfeed.tech/tags/cisco.md>), [cisco-nexus](<https://devfeed.tech/tags/cisco-nexus.md>), [command](<https://devfeed.tech/tags/command.md>), [container](<https://devfeed.tech/tags/container.md>), [functionality](<https://devfeed.tech/tags/functionality.md>), [integration](<https://devfeed.tech/tags/integration.md>), [messages](<https://devfeed.tech/tags/messages.md>), [netlab](<https://devfeed.tech/tags/netlab.md>), [nexus](<https://devfeed.tech/tags/nexus.md>), [os](<https://devfeed.tech/tags/os.md>), [running](<https://devfeed.tech/tags/running.md>), [send](<https://devfeed.tech/tags/send.md>), [setup](<https://devfeed.tech/tags/setup.md>), [syslog](<https://devfeed.tech/tags/syslog.md>), [tests](<https://devfeed.tech/tags/tests.md>), [version](<https://devfeed.tech/tags/version.md>), [vm](<https://devfeed.tech/tags/vm.md>)

### AI overview

In a test with Cisco Nexus OS 10.6(2), syslog messages to a directly connected host were not sent while the switch's ARP cache was empty, even though the route and syslog configuration appeared valid. Pinging the host populated ARP, but the capture showed only ARP and ICMP traffic. After another configuration action generated a log entry, Nexus sent two buffered UDP syslog records; their timestamps show the first had been generated about nine minutes earlier. The observed behavior suggests Nexus buffers unsent messages but does not initiate the ARP resolution needed to deliver them to a silent host. The excerpt does not establish whether this occurs in other versions or setups.

### Source excerpt

Here's another you can't make this up SNAFU observation I made when running integration tests for netlab Syslog functionality: Cisco Nexus OS cannot send Syslog messages to a directly connected silent host. The setup is as trivial as it can get: a Cisco Nexus OS VM (running version 10.6(2)) connected to a dnsmasq container running rsyslogd. Read more ...

## One week on the APNIC honeynet: 99,000 IP addresses and 173 million events

DevFeed: [One week on the APNIC honeynet: 99,000 IP addresses and 173 million events](<https://devfeed.tech/articles/one-week-on-the-apnic-honeynet-99-000-ip-addresses-and-173-million-events-100414.md>)

Original publisher: [Read original article](<https://blog.apnic.net/2026/10/26/one-week-on-the-apnic-honeynet-99000-ip-addresses-and-173-million-events/>)

Author: Adli Wahid

Published: 2026-10-26T04:15:47Z

Content type: article

Language: en

Sources: [APNIC Blog](<https://devfeed.tech/sources/apnic-blog.md>)

Topics: [Threat monitoring](<https://devfeed.tech/topics/threat-monitoring.md>), [Logging](<https://devfeed.tech/topics/logging.md>), [password spraying](<https://devfeed.tech/topics/password-spraying.md>), [IoT botnets](<https://devfeed.tech/topics/iot-botnets.md>), [Internet Traffic](<https://devfeed.tech/topics/internet-traffic.md>), [Virtual Private Network](<https://devfeed.tech/topics/vpn.md>)

Tags: [2017](<https://devfeed.tech/tags/2017.md>), [2020](<https://devfeed.tech/tags/2020.md>), [2025](<https://devfeed.tech/tags/2025.md>), [2026](<https://devfeed.tech/tags/2026.md>), [android](<https://devfeed.tech/tags/android.md>), [backdoor](<https://devfeed.tech/tags/backdoor.md>), [botnets](<https://devfeed.tech/tags/botnets.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [events](<https://devfeed.tech/tags/events.md>), [honeynet](<https://devfeed.tech/tags/honeynet.md>), [internet](<https://devfeed.tech/tags/internet.md>), [ip](<https://devfeed.tech/tags/ip.md>), [malicious](<https://devfeed.tech/tags/malicious.md>), [measurement](<https://devfeed.tech/tags/measurement.md>), [security](<https://devfeed.tech/tags/security.md>), [services](<https://devfeed.tech/tags/services.md>), [smb](<https://devfeed.tech/tags/smb.md>), [ssh](<https://devfeed.tech/tags/ssh.md>), [tech-matters](<https://devfeed.tech/tags/tech-matters.md>), [telnet](<https://devfeed.tech/tags/telnet.md>), [vpn](<https://devfeed.tech/tags/vpn.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [web](<https://devfeed.tech/tags/web.md>)

### AI overview

APNIC's rebuilt honeynet recorded nearly 99,000 distinct source IPs and 173 million events during 21-27 September 2026. Activity ranged from SSH and Telnet credential attempts to persistent RDP and VNC retries, VPN password spraying, and probes for vulnerabilities spanning 2017-2025. Malware deliveries included Mozi and Mirai botnet files, WannaCry components associated with likely unpatched Windows systems, and cryptomining activity targeting exposed Linux and Android devices. APNIC counts distinct IPs to estimate how many devices reached its sensors, since event volumes vary widely per source; regional origin reflects compromised systems and scanning infrastructure, not necessarily attacker location. The article recommends disabling Telnet, changing default passwords, keeping SMB/RDP/VNC/database services off the public Internet, checking Linux authorized_keys for unfamiliar keys, promptly patching VPN appliances and checking for prior compromise, and blocking public access to Android Debug Bridge.

### Source excerpt

Nearly 99,000 unique IP addresses interacted with APNIC's honeynet in just one week, generating 173 million events across SSH, Telnet, SMB, VPN, web, and Android services. The results show that long-known botnets, weak credentials, and unpatched vulnerabilities continue to drive large-scale malicious activity across the Internet.

## Logging in Python

DevFeed: [Logging in Python](<https://devfeed.tech/articles/logging-in-python-99150.md>)

Original publisher: [Read original article](<https://realpython.com/python-logging/>)

Author: Philipp Acsany

Published: 2026-10-25T14:00:00Z

Content type: tutorial

Language: en

Sources: [Real Python](<https://devfeed.tech/sources/real-python.md>)

Topics: [Logging](<https://devfeed.tech/topics/logging.md>), [Python](<https://devfeed.tech/topics/python.md>), [log4j](<https://devfeed.tech/topics/log4j.md>), [pip](<https://devfeed.tech/topics/pip.md>)

Tags: [analysis](<https://devfeed.tech/tags/analysis.md>), [boolean](<https://devfeed.tech/tags/boolean.md>), [built-in](<https://devfeed.tech/tags/built-in.md>), [class](<https://devfeed.tech/tags/class.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [configure](<https://devfeed.tech/tags/configure.md>), [console](<https://devfeed.tech/tags/console.md>), [csv](<https://devfeed.tech/tags/csv.md>), [custom](<https://devfeed.tech/tags/custom.md>), [data](<https://devfeed.tech/tags/data.md>), [debug](<https://devfeed.tech/tags/debug.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [formats](<https://devfeed.tech/tags/formats.md>), [logging](<https://devfeed.tech/tags/logging.md>), [logs](<https://devfeed.tech/tags/logs.md>), [python](<https://devfeed.tech/tags/python.md>)

### AI overview

Python's standard-library `logging` module replaces ad hoc `print()` calls with severity levels and configurable destinations and formats. The tutorial shows how to configure the root logger with `basicConfig()`, filter messages by level, add timestamps, and append records to a UTF-8 file. For larger setups, named loggers use handlers to send records to destinations such as the console and files, formatters to shape output, and filters to select records. Logger levels set the lowest level handlers can receive; handlers can impose stricter thresholds, such as DEBUG to the console and WARNING to a file. Exceptions can be logged with stack traces using `exc_info=True` or `logging.exception()` inside an exception handler. The text also notes that f-strings are evaluated even when a message is discarded, while `%`-style arguments defer interpolation until needed. Compared with Python's built-in module, Loguru is described as preconfigured after installation, while `logging` requires explicit configuration.

### Source excerpt

Go beyond print() with Python logging. Create your first logs, set levels and formats, and add handlers that grow with your projects.

## PingCAP Breach Exposes Customer Records and Source Code

DevFeed: [PingCAP Breach Exposes Customer Records and Source Code](<https://devfeed.tech/articles/pingcap-breach-exposes-customer-records-and-source-code-99013.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/10/pingcap-cloud-data-breach/>)

Author: Renato Losio

Published: 2026-10-25T06:27:00Z

Content type: news

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [Credential theft](<https://devfeed.tech/topics/credential-theft.md>), [Shared Responsibility Model](<https://devfeed.tech/topics/shared-responsibility-model.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>), [Logging](<https://devfeed.tech/topics/logging.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [api-keys](<https://devfeed.tech/tags/api-keys.md>), [architecture-design](<https://devfeed.tech/tags/architecture-design.md>), [billing](<https://devfeed.tech/tags/billing.md>), [breach](<https://devfeed.tech/tags/breach.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-control](<https://devfeed.tech/tags/cloud-control.md>), [cloud-data-management](<https://devfeed.tech/tags/cloud-data-management.md>), [cloud-security](<https://devfeed.tech/tags/cloud-security.md>), [code](<https://devfeed.tech/tags/code.md>), [control](<https://devfeed.tech/tags/control.md>), [control-plane](<https://devfeed.tech/tags/control-plane.md>), [customer](<https://devfeed.tech/tags/customer.md>), [cyber](<https://devfeed.tech/tags/cyber.md>), [cyber-extortion](<https://devfeed.tech/tags/cyber-extortion.md>), [data](<https://devfeed.tech/tags/data.md>), [development](<https://devfeed.tech/tags/development.md>), [distributed-data](<https://devfeed.tech/tags/distributed-data.md>), [extortion](<https://devfeed.tech/tags/extortion.md>), [fulcrumsec](<https://devfeed.tech/tags/fulcrumsec.md>), [information](<https://devfeed.tech/tags/information.md>), [keys](<https://devfeed.tech/tags/keys.md>), [news](<https://devfeed.tech/tags/news.md>), [pingcap-cloud-data-breach](<https://devfeed.tech/tags/pingcap-cloud-data-breach.md>), [records](<https://devfeed.tech/tags/records.md>), [security-breach](<https://devfeed.tech/tags/security-breach.md>), [source](<https://devfeed.tech/tags/source.md>), [source-code](<https://devfeed.tech/tags/source-code.md>)

### AI overview

PingCAP confirmed unauthorized access and exposure of customer-related records and private source code, while the attacker's claimed 10.6 TB haul and many specific contents remain unverified. PingCAP says outside reviewers found no evidence of attacker commands or persistent access in the production systems they reviewed, and no evidence that data stored in TiDB itself was affected. Exported records included names, email addresses, organization and project associations, and SQL editor text and errors; the attacker additionally alleges exposure of API keys, connection logs, and customer database endpoints. The incident shows how query histories, support tickets, and diagnostic logs can expose sensitive customer context even when customer databases are not shown to have been accessed. PingCAP recommends replacing active TiDB Cloud management API keys and watching for targeted phishing. The excerpt notes that named companies' records do not establish that those organizations were compromised, and cites Bitget as finding no evidence of user data exposure.

### Source excerpt

PingCAP recently confirmed unauthorized access to its internal systems and the theft of source code and customer-related data. The attacker, cyber extortion group FulcrumSec, claimed to have stolen 10.6 TB of data, including TiDB Cloud control-plane records, customer SQL statements, API keys, connection logs, billing information, internal documents, and 413 private source-code repositories. By Renato Losio

## 7 Best Platforms for AI Agent Fleet Management

DevFeed: [7 Best Platforms for AI Agent Fleet Management](<https://devfeed.tech/articles/7-best-platforms-for-ai-agent-fleet-management-98729.md>)

Original publisher: [Read original article](<https://www.lyzr.ai/blog/best-platforms-for-ai-agent-fleet-management/>)

Author: Lyzr Team

Published: 2026-10-23T10:34:04Z

Content type: comparison

Language: en

Sources: [Lyzr.ai](<https://devfeed.tech/sources/lyzr-ai.md>)

Topics: [shadow AI](<https://devfeed.tech/topics/shadow-ai.md>), [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [Logging](<https://devfeed.tech/topics/logging.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [7-best](<https://devfeed.tech/tags/7-best.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-365](<https://devfeed.tech/tags/agent-365.md>), [agent-evaluation](<https://devfeed.tech/tags/agent-evaluation.md>), [agent-fleet](<https://devfeed.tech/tags/agent-fleet.md>), [agent-gateway](<https://devfeed.tech/tags/agent-gateway.md>), [agent-identity](<https://devfeed.tech/tags/agent-identity.md>), [agent-management](<https://devfeed.tech/tags/agent-management.md>), [agent-observability](<https://devfeed.tech/tags/agent-observability.md>), [agent-sprawl](<https://devfeed.tech/tags/agent-sprawl.md>), [agentcore](<https://devfeed.tech/tags/agentcore.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [best](<https://devfeed.tech/tags/best.md>), [fleet](<https://devfeed.tech/tags/fleet.md>), [fleet-management](<https://devfeed.tech/tags/fleet-management.md>), [gartner](<https://devfeed.tech/tags/gartner.md>), [management](<https://devfeed.tech/tags/management.md>), [platforms](<https://devfeed.tech/tags/platforms.md>)

### AI overview

The platforms differ mainly in how broadly they can manage agents and which fleet tasks they handle. Lyzr OpenController offers cross-cloud inventory, gateway-level policy and model changes, staged releases, rollback, and per-agent spend tracking, but can steer only agents whose traffic passes through its gateways. Microsoft Agent 365 centers on Microsoft 365; at launch, cross-cloud sync was in preview, lifecycle actions were forthcoming, and per-agent cost tracking was unavailable. Google's platform emphasizes identity, gateway controls, and production drift monitoring for Google Cloud and partner agents, with no published per-agent budgets. AWS provides immutable runtime versions and staged rollouts, while fleet-wide model swaps require scripting. Salesforce and ServiceNow focus on health, discovery, governance, and controls, but do not yet provide broad third-party rollout management. CrewAI AMP handles deployments, traces, and costs for CrewAI-built crews only. The excerpt recommends evaluating fleet inventory and coordinated model changes through a canary and rollback drill.

### Source excerpt

Gartner expects the average Fortune 500 company to have more than 150,000 AI agents in use by 2028. In 2025, the figure was under 15....

[Next page](<https://devfeed.tech/topics/logging.md?cursor=WyIyMDI2LTEwLTIzVDEwOjM0OjA0KzAwOjAwIiwgIjk2YjVjNmYyLWEzNzktNDNlNi04NDdlLWU4MDM1YmQ4YWFlYiJd>)