AI coding agents need a safe place to work; Eclipse is building the sandbox to give it to them
As AI coding tools evolve from simple assistants into autonomous agents that execute commands and modify software, they require more freedom to be productive. However, unrestricted access poses significant risks, such as exposing credentials or making unintended changes to systems. To address this problem, the Eclipse Foundation recently introduced Eclipse Enclave 1.0, an open source sandbox that provides a safe, isolated environment for AI coding agents to operate. Instead of forcing developers to supervise every single action, which defeats the entire purpose of automation, Enclave allows these agents to work independently within strictly defined boundaries. Developers can grant access only to the specific files, tools, and web resources needed for a particular task, keeping sensitive information like API keys completely out of reach. The platform even supports running multiple agents in parallel on entirely separate tasks without any interference. Originally built as an internal tool by EclipseSource, this vendor neutral infrastructure successfully shifts the developer role from constant supervision to higher level planning and review. While sandboxing cannot eliminate every risk associated with autonomous code generation, Enclave offers a practical framework to manage those risks while remaining independent.
CISO Conversations: Patti Degnan – Part of the Job Is Deciding What Not to Do
Patti Degnan’s journey to becoming the Chief Information Security Officer at Glow, an AI-powered endpoint security firm, began unexpectedly after her identity was stolen in 2006. This personal incident sparked a deep interest in data privacy, leading her through internal audit roles and eventually into senior security leadership positions at companies like Symantec and Notion. Degnan firmly believes that effective cybersecurity leadership requires a strong desire to lead and the ability to align security strategies with overall business goals. While technical knowledge is highly valuable, she argues that a CISO does not need to be a hands-on developer; instead, they must excel at communicating complex technical risks to non-technical stakeholders across the organization. When building her teams, she prioritizes a candidate's ability to take real ownership of problems rather than simply collecting certifications. Addressing the widespread issue of industry burnout, Degnan emphasizes that a crucial part of leadership is deciding what not to do. By setting clear priorities, automating routine tasks with artificial intelligence, and encouraging necessary time off, she helps her team maintain the personal resilience required to manage constant security challenges.
Why Visibility Without Action is Failing OT/IoT Security
For years, securing operational technology and connected devices relied on a simple idea: if you can see it, you can secure it. However, simply identifying a vulnerable device creates a dangerous gap between discovering a problem and actually fixing it. Today's automated threats move far too quickly for manual responses. Relying on alerts alone fails because security teams quickly become overwhelmed, and these specialized devices often lack standard operating systems that make updates easy. To close this gap, organizations must move beyond passive monitoring and adopt automated systems that handle routine security tasks like patching, updating passwords, and renewing certificates. These systems can work directly with the devices at scale, effectively blocking threats before they take hold. Yet, because these industrial systems control physical environments where a faulty update could halt production or cause damage, complete automation is too risky. A qualified human professional must always remain in the loop to carefully review and approve these critical changes. Ultimately, simply watching your network is no longer enough; true security requires automated action firmly guided by human judgment to protect physical operations safely.
Is Coding with AI Actually Faster and Cheaper?
Recent studies reveal that coding with artificial intelligence indeed accelerates development, though the overall impact on software delivery is more measured than hype suggests. Research tracking over half a million developers shows a massive jump in code commits, but a much smaller increase in actual software releases. While individual programmers generally complete tasks faster using these tools, the time saved during the initial coding phase often shifts into the review, testing, and auditing stages. Consequently, building software feels less stressful and somewhat quicker, but it is not an overnight revolution that drastically slashes production timelines. Regarding costs, the financial benefit largely depends on the capability of the AI model being used. Economic simulations demonstrate that highly capable agents offset the price of their tokens by producing fewer errors and reducing the need for human supervision. In contrast, cheaper but less effective models can quickly become expensive due to the necessary retries and bug fixes. Ultimately, capable AI tools do make coding faster and more cost-effective, yet the full expense of securely delivering and maintaining enterprise software has not dramatically collapsed across the broader tech industry.
Why Strong Board Governance Requires Knowing When To Hit The Brakes
Effective board governance comes down to knowing precisely when to accelerate and when to hit the brakes. While many board members default to either cheerleading risky moves to please founders or stalling progress under the guise of risk management, exceptional directors master tempo control. To navigate high-stakes decisions effectively, boards should rely on three key principles: reversibility, information asymmetry, and the difference between trajectory and inflection. If a decision is easily reversible or simply speeds up a proven strategy, the board should accelerate the process. Conversely, if a move represents a permanent pivot or management lacks the necessary on-the-ground expertise, the board must intervene and force a deliberate pause to evaluate risks. For instance, rushing an aggressive international expansion without proper local knowledge can drain capital, whereas a strategic pause for thorough diligence can turn potential failure into a durable revenue stream. Ultimately, a board member’s true value lies not in asking the most questions, but in discerning strategic inflection points from mere noise, protecting capital while ensuring the enterprise scales with confidence and discipline.
A game you cannot win unless you have a quantum computer
Google researchers have successfully demonstrated "quantum contextuality" on a large scale, proving that quantum computers can solve specific problems impossible for classical systems. To illustrate this, they use a "magic square" puzzle where two players must fill a grid following contradictory rules. In classical physics, players lose because a pre-determined table cannot satisfy all conditions. However, using entangled qubits on Google's Willow quantum processor, the system won the game 98.3% of the time, easily beating the absolute classical limit of 88.9%. This happens because in quantum mechanics, the answers do not exist before measurement; instead, they are generated at the moment they are observed based on their context. The researchers tested these contextual properties across systems of up to 105 qubits, proving that this phenomenon survives as quantum computers scale up in size. Beyond solving theoretical games, these tests provided a highly sensitive benchmark for identifying subtle hardware errors that standard tests miss. This research confirms that contextuality, rather than just entanglement alone, is a fundamental engine driving the computational advantage of quantum machines, paving the way for more accurate quantum algorithms in fields like chemistry and materials science.
How to Secure IT/OT Convergence Without Breaking Operations
As manufacturing environments increasingly connect their information technology and operational technology systems, securing this overlap has become a serious challenge. Most cyberattacks that reach factory floors actually begin in the standard IT network, exploiting pathways created by integrated tools or third-party vendor access. The core issue is that these two environments operate with entirely different priorities and timelines. Standard IT focuses on speed and regular updates, while operational systems prioritize continuous uptime and safety, often relying on legacy equipment that runs for decades and cannot accept modern software patches. Because standard security controls do not translate well to factory floors, companies must adopt frameworks designed specifically for physical operations. This involves prioritizing process safety, implementing strict network segmentation, and managing remote access with time-limited, closely monitored sessions rather than open connections. Using digital certificates helps authenticate connected devices, ensuring only trusted equipment accesses the network. Furthermore, new global compliance standards are shifting how companies buy equipment, requiring manufacturers to embed security features directly into the design phase. By understanding these distinct operational constraints, organizations can better protect their critical infrastructure without disrupting daily production.
Chaos, then control: the maturity model most AI rollouts skip over
When engineering teams roll out new artificial intelligence tools, they often notice a strange gap: a few people achieve massive productivity gains, while most just use the tools like a fancy autocomplete. According to a five-stage maturity model, this happens because leaders skip the messy but essential middle steps of a proper rollout. The process should start by letting chaos reign as people experiment, followed by discovering what actually works, codifying those discoveries into shared practices, scaling them across the entire group, and only then reorganizing the team around the new reality. Unfortunately, eager to show quick financial returns, many organizations simply buy the software licenses, wait for the dust to settle, and immediately try to restructure roles based on guesses. To truly succeed, leaders need to pause and closely study their most adventurous engineers during the initial rollout. By identifying their successful habits and translating them into a clear, shared set of daily practices, companies can actively teach the rest of the team how to improve. That unglamorous middle work is the only reliable way to turn scattered individual wins into lasting team-wide success.
Your liveness check passed. Was there ever a camera?
Passing a biometric identity check does not always mean a real person is sitting in front of a camera. While many security systems are built to catch someone holding a printed photo or mask up to a lens, criminals are now bypassing cameras entirely. By feeding fake videos or doctored images directly into the verification software, they can open fraudulent accounts with ease. These injection attacks require a different type of testing and defense than traditional physical spoofs. For smaller banks and businesses without dedicated fraud teams, it is crucial to ask technology vendors directly about their specific protections against these camera bypass methods. Instead of relying solely on the facial image, organizations should examine the broader context of the session, such as device data and location signals. Staff should be given clear guidelines on what to look for when a system flags a suspicious entry, rather than being expected to spot artificial images by eye alone. Placing temporary limits on new accounts can also reduce risk. Ultimately, treating a passed facial scan as absolute proof of physical presence is a blind spot that modern security programs must correct.
Learning the language of machine learning
MIT Associate Professor Jacob Andreas is working to make artificial intelligence more transparent by teaching machine learning models to explain their own internal processes using everyday human language. Currently, many neural networks operate as "black boxes," meaning their decision-making is difficult to audit or understand. Andreas and his research group are addressing this by developing techniques that allow AI systems to accurately describe what they have learned from their training data. Instead of relying on external tools to decipher a model's behavior, his approach trains the models to talk about themselves and their reasoning directly. His team also focuses on building systems that can learn from simple descriptions rather than millions of examples, similar to how humans learn from a single recipe. Because the field of AI evolves rapidly, often reinventing itself every few years, Andreas continuously updates his courses so students understand the foundational mechanics behind the technology. Ultimately, his research aims to build trustworthy, interpretable AI systems that can honestly communicate their capabilities and limitations, helping to establish a clearer scientific understanding of how models behave in the real world.