CyberComplianceAI
InicioNoticiasIntel Center
CyberForoPrecios
Acceder
The Pulse · Live Intelligence Feed

Intel Center

Una señal es cualquier evento operacional detectado en las últimas 24h–30d: CVEs en KEV explotados activamente, advisories de vendor, exposición cloud, ransomware y avisos regulatorios. Cada señal se prioriza por gravedad, actualidad y coincidencias con tu perfil personal de inteligencia.

Para análisis editorial y noticias generales visita Noticias.

Priorizado con IA

La priorizacion, resumen y accion recomendada pueden estar enriquecidos por IA y heuristicas. La fuente original permanece visible para verificacion.

Señales registradas · last 7d
Señales (ventana)128
Última detecciónhace 3 h
Monitorizado porintelligence scouter
Acción Requerida

Sin señales clasificadas en esta categoría dentro de la ventana seleccionada.

Explotados & KEV

Sin señales clasificadas en esta categoría dentro de la ventana seleccionada. Catálogo histórico abajo.

Ventana24h7d30d7d / 30d solo en ProSeveridadCríticaAltaLimpiar filtros
Fabricante mencionadoMicrosoft10Google8Linux7Siemens5Palo Alto Networks5PHP5GitHub5Zoom4Apache3
✓

No priority signals demanding immediate attention.

La cola operativa está limpia en esta ventana. El scouter sigue monitorizando.

All128Action Required0Altas y críticas46Vendor Advisories1Cloud & Identity4Monitor77
Cloud & IdentityMEDIAAltoIncidente (prensa)NEWCRAInteligencia operacional

From exposed secrets to managed credentials: Reducing credential risk across the application lifecycle

A recent software supply chain attack affecting tens of thousands of GitHub repositories highlights a security problem that is easy to underestimate: a credential does not stop being exposed simply because it has been deleted from the latest version of the code. Researchers uncovered a campaign in which attackers inserted a malicious GitHub Actions workflow into repositories they had permission to modify. Designed to look like a routine security audit, the workflow instead searched for and exfiltrated credentials. It targeted secrets available to GitHub Actions, but also searched repository files and complete Git history for credentials associated with cloud providers and AI services. That meant credentials developers had previously committed and later removed could still be discovered. The incident is another reminder that responding to exposed credentials requires more than cleaning up source code. Organizations need to understand where credentials have been exposed, remediate those credentials and ultimately improve how they are managed. HCP Vault Radar and HashiCorp Vault can help teams address different parts of that lifecycle, moving from discovering exposed secrets to bringing credentials under centralized management. A deleted secret can still be an exposed secret Accidentally committing a credential is not an unusual scenario in software development. An API key gets added to a configuration file while testing an integration, a cloud credential helps get a prototype running, or a token is placed into a workflow to solve an immediate problem. A developer may eventually identify the mistake and remove the credential, leaving the current version of the application looking clean. But removing the plaintext value does not necessarily remediate the underlying credential. The secret can remain in Git history, the original credential may still be active, and copies may exist in other places across the development lifecycle. In this attack, that distinction was parti

Filtered for operational relevance. Powered by a curated catalog of vulnerability, CERT, vendor and threat-intelligence sources.View methodology →

CyberComplianceAI

¿Quieres esto priorizado para tu rol cada mañana?

El Morning Brief Pro filtra estas señales por tu rol (CISO, SecOps, risk), sector y framework prioritario, y las convierte en acciones recomendadas listas a las 7:00.

Probar Morning Brief Pro →Ver precio

¿Aún no quieres Pro? Recibe el resumen de cumplimiento gratis cada semana.

46signals
Altas y críticas
1signals
Advisories de Vendor
También en el Intel CenterCloud & Identity4Monitor77
Apple3
GitLab3
Salesforce3
Ivanti2
HashiCorp2

Por qué importa

Postura cloud / identity comprometida o reforzada. Revisar configuración y baseline.

Acción recomendada

Avisa a los owners de los stacks GitHub, HashiCorp.

Vendors:GitHubHashiCorpCISO · Cloud Security · SecOps
Publicado
17 nov 2026, 08:00
Actualizado
17 nov 2026, 22:01
Detectado
17 nov 2026, 22:01
Fuente
HashiCorp Blog Security
Referencia técnica
Original advisory
HashiCorp Blog Security
Prioridad · 42/100published <24h (+40) · high severity (+15) · source authority (+2) · updated <24h (+5 cap)
hace 8 horas
Cloud & IdentityMEDIAAltoIncidenteNEWInteligencia operacional

Apify rotates API tokens, prompts 2FA resets after breach

Apify has rotated critical internal secrets and revoked some third-party OAuth connections after detecting unauthorized access to its internal systems. [...]

Por qué importa

Postura cloud / identity comprometida o reforzada. Revisar configuración y baseline.

Acción recomendada

Revisa la fuente, confirma aplicabilidad y monitoriza guías posteriores.

CISO · Cloud Security · SecOps
Mapeo regulatorio · riesgo 72

El acceso no autorizado y el compromiso de credenciales exigen detectar, gestionar, clasificar y evaluar notificabilidad del incidente TIC conforme a DORA.

DORA · Art. 10 Detection (direct) · Art. 17 ICT-related incident management process (direct) · Art. 18 Classification of ICT-related incidents and cyber threats (direct)
Publicado
12 nov 2026, 14:36
Actualizado
12 nov 2026, 17:00
Detectado
12 nov 2026, 17:00
Fuente
BleepingComputer
Referencia técnica
Original advisory
BleepingComputer
Prioridad · 31/100published <7d (+25) · high severity (+15) · source authority (+2) · updated <7d (+3 cap)
hace 6 días
Cloud & IdentityMEDIAAltoIncidenteNEWInteligencia operacional

Notion says Fireworks breach exposed customer AI chat transcripts

Notion, the digital workspace platform, disclosed that a security breach at its AI infrastructure provider, Fireworks AI, exposed Notion AI chat transcripts in a small number of workspaces. [...]

Por qué importa

Postura cloud / identity comprometida o reforzada. Revisar configuración y baseline.

Acción recomendada

Avisa a los owners de los stacks Google.

Vendors:GoogleCISO · Cloud Security · SecOps
Publicado
11 nov 2026, 20:54
Actualizado
11 nov 2026, 21:01
Detectado
11 nov 2026, 21:01
Fuente
BleepingComputer
Referencia técnica
Original advisory
BleepingComputer
Prioridad · 31/100published <7d (+25) · high severity (+15) · source authority (+2) · updated <7d (+3 cap)
hace 6 días
Cloud & IdentityMEDIAAltoIncidente (prensa)HISTORICALInteligencia operacional

Secure AI credentials from discovery to remediation with Vault Radar and Vault

AI development may be changing how applications are built, but many of the security problems underneath them are familiar. Applications need credentials to connect to models, cloud services, databases, development tools, and other systems. As teams experiment with new AI services and move applications toward production, those credentials can spread across repositories and development workflows just as other secrets do. An API key gets added to a configuration file to get a prototype running. A developer uses it during testing. The application evolves, the team moves on, but the credential remains. Now the organization has two problems: How do you find credentials that have ended up where they shouldn't be, and once you find them, how do you keep them from ending up there again? That is where secret discovery and secrets management need to come together. AI adds another dimension to secrets sprawl The problem starts well before a credential is compromised. A credential that lives outside an organization's secrets management practices can be difficult to inventory, monitor, and remediate. And simply searching today's code isn't necessarily enough. Credentials can persist in Git history even after they have been removed from the latest version of a file. AI applications often depend on model providers, cloud infrastructure, vector databases, and developer tooling, all of which introduce additional credentials that need to be managed securely. HCP Vault Radar is designed to identify unmanaged secrets throughout development workflows. It scans connected data sources when they're added and as new commits and pull requests are created. Deep scanning can identify secrets in Git history, and supported secret types can include an activeness check to help teams understand which findings demand attention. That applies directly to AI development. Vault Radar currently recognizes multiple OpenAI credentials as built-in secret types, including admin, project, service account, user

Por qué importa

Postura cloud / identity comprometida o reforzada. Revisar configuración y baseline.

Acción recomendada

Avisa a los owners de los stacks HashiCorp.

Vendors:HashiCorpCISO · Cloud Security · SecOps
Mapeo regulatorio · riesgo 55

La exposición y propagación de credenciales en repositorios y flujos de desarrollo dificulta detectar vulnerabilidades y exige medidas de monitorización, análisis y remediación del riesgo TIC.

DORA · Art. 10 Detection (direct) · Art. 13 Learning and evolving (direct)
Publicado
05 nov 2026, 17:00
Actualizado
11 nov 2026, 17:01
Detectado
11 nov 2026, 17:01
Fuente
HashiCorp Blog Security
Referencia técnica
Original advisory
HashiCorp Blog Security
Prioridad · 20/100published <30d (+10) · high severity (+15) · source authority (+2) · updated <7d (+3 cap)
hace 7 días

Cobertura de fuentes degradada

64 de 72 fuentes elegibles del scouter tienen una lectura correcta en las últimas 24 h. 8 registran fallos; 0 no tienen un éxito registrado. Estas categorías pueden solaparse.

El scouter está programado cada hora. Una ejecución o la ausencia de señales no garantiza cobertura completa ni ausencia de exposición.

Estado consultado: 18/11/2026, 6:01:22 UTC · catálogo del scouter; otros conectores se actualizan por separado.