Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

You cannot contain sensitive communications inside systems designed to expose connections. Most enterprise collaboration platforms were built for speed: • faster sharing • broader access • seamless integrations • constant synchronization That architecture improves convenience. It also expands visibility. Automatic contact syncing. Third-party integrations. Persistent metadata. External routing layers....

358,373 Aufrufe • vor 5 Monaten •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

What is Quant Network's Overledger? Overledger is Quant’s (Quant) interoperability platform, designed to connect different blockchains and traditional systems through a common API layer. It tries to make different blockchain networks communicate without forcing developers to build separate integrations for every chain. (1) Overledger acts as a universal API gateway. Developers can use standardized APIs to interact with supported blockchains instead of learning and maintaining separate infrastructure for each network. (2) It works as a translation layer between different blockchain environments. Quant describes Overledger as a “universal translator,” allowing applications to communicate across different DLT architectures through a common interface. (3) This is where Overledger differs from the typical bridge model. Instead of every application relying on a separate bridge between two chains, Overledger provides a common interoperability layer that can connect multiple networks. That can reduce the need for point-to-point integrations, which become increasingly complex as more blockchains enter the ecosystem. (4) Overledger can also power multi-chain applications. Quant calls these mApps, applications designed to operate across multiple distributed ledgers rather than being locked to one blockchain. The platform can also handle transaction signing, asset transfers, and other blockchain interactions through its APIs. (5) But Overledger does not completely eliminate bridges. Quant also provides its own bridge infrastructure for transferring assets between networks, using standardized APIs and smart contracts. Since June 2026, this has also expanded into Quant Fusion, a multi-ledger rollup connecting dozens of blockchains. The bigger idea is that the applications can have interoperability via an infrastructure layer as opposed to establishing the connections all over again.

BSCN

19,056 Aufrufe • vor 2 Monaten

In 2025, the AgentFlayer exploit highlighted a new category of risk in AI systems. It was not a traditional breach involving stolen credentials or broken encryption. Instead, it demonstrated how an autonomous AI agent could be manipulated into executing unintended actions by processing malicious instructions embedded inside content it automatically processes. The incident did not expose a flaw in one specific integration. It revealed a structural weakness in how many modern AI agents are built. Today’s agents are no longer passive language models. They read documents automatically, scan emails, connect to SaaS tools, access cloud storage, and execute actions across multiple systems. To be useful, they are granted meaningful permissions. That capability creates value, but it also expands the attack surface. Most agent environments operate in a trusted, plaintext execution model. Data is encrypted at rest and in transit, but it is typically decrypted during inference so the model can process it. That runtime visibility is where potential risk lies. In a zero-click scenario like AgentFlayer, an attacker can embed hidden instructions inside a document that the AI processes automatically. Because the agent may have access to connected systems such as Google Drive, Slack, or GitHub, it can potentially be influenced to retrieve sensitive information or perform unintended actions. The user does not need to click a malicious link or approve a suspicious request. Therefore, the core issue is that during execution, the system may have access to sensitive data and broad privileges, meaning whoever controls the execution environment ultimately controls access to that data. Now consider a different architectural approach. If a system is designed so that data remains protected during execution, the risk profile changes. On Nesa, privacy is enforced at the execution layer through Equivariant Encryption. Computation can occur on encrypted data, reducing the visibility surface during runtime. Sensitive inputs and models do not need to be exposed in plain text to infrastructure operators for inference to occur. This does not eliminate prompt injection, logic manipulation, or tool misuse. Encryption alone cannot prevent an agent from being instructed to take an unintended action if it has been granted that permission. What it does do is materially reduce confidentiality risk. By limiting access to readable sensitive data during execution and reducing unilateral visibility at the infrastructure layer, the potential blast radius of a successful manipulation attempt is constrained. As AI agents become more autonomous and embedded into enterprise workflows, security must move deeper into architecture. The goal is not to claim invulnerability. It is to reduce trust concentration and contain systemic exposure when failures occur. AgentFlayer was not simply a one-off exploit. It was a reminder that in autonomous systems, execution-layer design determines how risk propagates.

Nesa

17,038 Aufrufe • vor 8 Monaten