Quote for the day:
“If you want to be inventive, you have to be willing to fail.” -- Jeff Bezos
🎧 Listen to the audio debrief on YouTube
▶ Play Audio DigestDuration: 18 mins • Perfect for listening on the go.
Giving agents bounded autonomy
Artificial intelligence agents are evolving rapidly, but their
unpredictability has led to some unintended consequences. To make these tools
genuinely useful without letting them cause harm, we need to apply firm
boundaries to their independence. This means treating AI programs much like
teenagers: granting them limited freedom to act on our behalf while
establishing hard rules that cannot be bypassed. A practical example of this
is financial limits. Rather than forcing a person to approve every tiny
transaction an agent makes to access data or services, systems like Amazon Web
Services now let users set a strict allowance. An agent might be given a
specific budget and a time limit to complete a task. It has the freedom to
choose how to spend that small budget, but the hard limits are enforced
completely outside the software model itself. However, technical capability is
not the same as judgment. An agent might be able to execute complex tasks, but
it lacks human intuition and basic reasoning. Therefore, we should allow
agents to act independently only on inexpensive and easily reversible tasks.
As these tools prove they can operate reliably within their limits, we can
gradually expand their freedom, ensuring their authority never outpaces their
actual judgment.Setting security level targets under IEC 62443
Setting security level targets under the IEC 62443 standard is not about
collecting compliance badges but defining the practical resistance a system,
zone, or conduit needs against specific threat profiles. For operational
technology environments, particularly within small and medium enterprises,
establishing a well-reasoned target ensures that engineering and security
teams make balanced decisions regarding segmentation, authentication, and
remote access. This approach prevents both underprotection and
overengineering. A successful security level target must be rooted in actual
risk, process criticality, and business context rather than generic templates.
It is essential to differentiate the intended target from the ultimately
achieved protection level. Organizations should utilize practical threat
modeling to understand realistic attack paths and potential impacts on
availability and safety. Furthermore, targets must remain achievable, taking
into account the limitations of legacy equipment, maintenance workflows, and
supplier access requirements. Applying a single target across an entire estate
or ignoring local operational constraints often leads to friction and bypassed
controls. Instead, cross-functional engineering and security teams should
collaborate to define appropriate, zone-specific targets that directly inform
technical requirements under the IEC 62443 standard. By documenting the
rationale behind each decision, companies can build a defensible, maintainable
security architecture that effectively mitigates real-world industrial risks
today.
DevOps Questions After We Broke The Release Handshake
The recent incident involving a broken release process revealed that a
successful deployment status does not guarantee a working service. Despite
passing local checks and database migrations, a missing network policy
prevented a new service from functioning, highlighting a failure in
communication between teams. To prevent this, release dependencies are now
explicitly declared in the service repository, making them visible and
verifiable before promotion. Rather than relying on a central platform team to
approve every release and understand the operational details of every service,
product teams now manage their own deployments. They are granted targeted,
restricted access to production environments for troubleshooting, while the
platform team focuses entirely on maintaining the delivery tooling and shared
infrastructure. Alerting has been streamlined to notify the specific team
responsible for the failing layer, minimizing irrelevant alerts and focusing
completely on direct user impact. Furthermore, while the organization uses
delivery metrics to identify friction in the deployment pipeline, they
deliberately avoid ranking teams to prevent unhelpful gamification. The team
is also cautiously evaluating automated traffic shifting for certain services,
though they recognize it is not necessary for every routine workload.
Ultimately, the primary objective is to simplify incident investigation by
providing a single, unified view of each deployment.From surveillance to operational intelligence: Rethinking safety and security in data centers
Data centers are moving away from traditional security models that rely solely on passive video surveillance. Instead, facilities are beginning to adopt more advanced methods that turn basic monitoring into functional operational intelligence. In the past, cameras and sensors were primarily used for recording incidents or tracking unauthorized access after an event occurred. Now, these systems are integrated with data analytics to provide a real time understanding of both security and daily facility operations. By connecting physical security tools with network infrastructure, operators can actively monitor environmental conditions, track the movement of personnel, and identify potential safety hazards before they cause disruptions. This shift means that security hardware no longer serves just one purpose. It acts as a continuous source of valuable information that helps managers improve efficiency, maintain compliance, and reduce risks across the entire site. Gathering this kind of practical intelligence allows teams to respond to issues faster and allocate resources more effectively. Ultimately, rethinking safety in this way bridges the gap between simply protecting a building and actively managing its internal operations. A comprehensive approach ensures that data centers remain secure while also supporting the demanding requirements of modern technology infrastructure in a reliable manner.Deepfake detection evolving beyond onboarding into continuous financial trust
The article discusses how deepfake detection is moving beyond just a one-time
identity check into a continuous system that monitors users throughout their
entire session. Traditional static verification methods are now viewed as
obsolete because financial platforms lose significant amounts of money to
fraud that occurs after a user has already logged in. To combat this,
companies are introducing tools that provide real-time, ongoing protection.
For example, IngenID has updated its systems to continuously verify a caller's
identity and flag manipulated audio exactly as it happens during a full
conversation, rather than just at the beginning. Similarly, Resemble AI is
exploring how continuous deepfake detection can support compliance rules
against money laundering during sensitive transactions and account recovery
processes. Furthermore, a report from J.P. Morgan Payments and Accenture
emphasizes that relying on a static defense is ineffective. Instead, they
advocate for behavioral analytics, ongoing multi-factor authentication, and
collective information sharing among organizations. As fraudsters rely on
advanced artificial intelligence to execute sophisticated attacks at a larger
scale, the identity verification market is evolving into a more layered
security architecture. To stay ahead of these growing threats, organizations
must shift away from standalone products and combine deepfake detection with
liveness checks and broader fraud prevention capabilities.What Singapore’s new digital infrastructure bill mean to CISOs
Singapore has introduced the Digital Infrastructure Bill to enforce stricter
resilience standards on major data center and cloud operators. Prompted by
severe recent outages, including a 2023 banking disruption caused by a cooling
failure, the legislation requires large foundational infrastructure providers
to secure operating licenses. To keep these licenses, operators must implement
strong business continuity plans, maintain physical and digital security, and
promptly report service disruptions or cyber incidents. Failure to comply can
result in severe financial penalties, including fines up to one million
dollars or ten percent of their annual local turnover. A major focus of the
new law is sustainability, making energy and water efficiency mandatory
criteria for operators. As power consumption rises, providers must actively
shift toward low carbon and renewable energy sources. The bill also introduces
complex overlapping reporting duties, meaning global operators will need
clear, regional response plans to manage different regulatory timelines. For
enterprise customers like banks and retail platforms, the shift from voluntary
guidelines to strict laws means they should update their service contracts.
Customers need to include clear clauses and indemnities that hold providers
responsible for compliance failures. Ultimately, the bill marks a significant
step toward making digital infrastructure as reliable and heavily regulated as
public utilities.
Today's leaders must completely rethink how they guide their teams through
constant change, especially with the arrival of artificial intelligence.
Instead of viewing change as a single event with a clear finish line, they
must build ongoing adaptability into their daily operations. Organizations
only have so much capacity to absorb new initiatives at once. When leaders
ignore this limit and pile on multiple projects, they risk exhausting their
teams. Rather than pushing harder, successful managers set clear priorities
and fund projects in small, measurable stages. When employees find their own
tools to get work done, it is a signal of unmet needs rather than just a
security problem. Approaching these workarounds with curiosity helps companies
build better guidelines together. Trust is also absolutely essential,
particularly when new systems can act independently. Leaders must ensure that
new technology is transparent and understandable, while openly addressing how
it will affect employee roles and career paths. Finally, what looks like
resistance is often just exhaustion. People are more willing to adapt when
leaders communicate clearly about what matters most and what can wait. By
sharing ownership of these changes across the entire business, leaders can
confidently guide their teams forward with steady, focused support.
5 hard truths of change management
Today's leaders must completely rethink how they guide their teams through
constant change, especially with the arrival of artificial intelligence.
Instead of viewing change as a single event with a clear finish line, they
must build ongoing adaptability into their daily operations. Organizations
only have so much capacity to absorb new initiatives at once. When leaders
ignore this limit and pile on multiple projects, they risk exhausting their
teams. Rather than pushing harder, successful managers set clear priorities
and fund projects in small, measurable stages. When employees find their own
tools to get work done, it is a signal of unmet needs rather than just a
security problem. Approaching these workarounds with curiosity helps companies
build better guidelines together. Trust is also absolutely essential,
particularly when new systems can act independently. Leaders must ensure that
new technology is transparent and understandable, while openly addressing how
it will affect employee roles and career paths. Finally, what looks like
resistance is often just exhaustion. People are more willing to adapt when
leaders communicate clearly about what matters most and what can wait. By
sharing ownership of these changes across the entire business, leaders can
confidently guide their teams forward with steady, focused support.
“Ignorance Is Bliss” Is Our Acceptable Use Policy
In a recent episode of the CISO Series Podcast, hosts David Spark and Edward
Contreras, along with guest Rob Allen from ThreatLocker, discuss practical
approaches to modern security challenges. The conversation first addresses the
growing issue of vulnerability management, where artificial intelligence is
discovering software flaws faster than they can be cataloged or patched.
Rather than the security team absorbing all the pressure, Contreras suggests a
shift toward shared accountability. By providing tailored, manageable reports
directly to the engineering teams responsible for the code, organizations can
distribute the workload more effectively. Allen adds that since patching
cannot always keep up, businesses must simply assume vulnerabilities exist and
operate with appropriate safeguards. The discussion then moves to the problem
of unauthorized artificial intelligence programs and acceptable use policies.
While some experts recommend offering sanctioned tools and clear guidelines,
Allen argues this approach often fails because employees will naturally seek
out any tool that makes their job easier. Relying on written policies or
expecting staff to correct issues on their own is generally ineffective.
Instead, he emphasizes the need for direct, technical control, advocating for
systems that block unapproved applications by default and only allow access to
specific tools after formal approval.
Why Platform Engineering Must Evolve for the Agentic Era
The recent article from SD Times explores how the rise of artificial
intelligence agents is shifting the focus of platform engineering. While the
fundamental goals remain the same, the main consumers of these platforms are
changing from human developers to automated software agents. Most companies
are currently adding AI capabilities onto older systems designed for human
speeds, which creates governance issues and fragmented controls. To address
this, the field must transition to a new phase where platforms treat agents as
primary users. This means that application programming interfaces, identity
management, and security policies must be easily readable and usable by
machines. Essential elements like graphics processing units and vector
databases should be integrated as standard parts of the infrastructure rather
than special additions. A major change involves cost management. Because
automated agents can consume resources much faster than humans, financial
tracking must shift from monthly reports to real-time enforcement to prevent
sudden budget overruns. Ultimately, organizations need to combine their
software delivery systems and their safety guardrails into a single, unified
control setup. By doing this, engineering teams can maintain the established
principles of clear and effective paths and self-service while safely
supporting the faster, automated workloads of the future.Why adding more security tools could make businesses less secure
Many companies in Australia and New Zealand are spending more on
cybersecurity, but this increased investment is leading to a hidden problem of
complexity. For years, the standard reaction to new threats has been to buy
another security product. However, this approach leaves security teams
managing dozens of overlapping systems, each generating its own data and
alerts. Instead of providing a clear picture of risk, this buildup of
technology creates friction. It forces teams to spend time managing tools
rather than identifying threats, and leaves executives unsure if the business
is actually safer. The solution lies in simplifying the approach. Instead of
constantly adding new products, companies are starting to look at
consolidating their systems and bringing their data together. This shift
changes how investments are judged, moving away from counting the number of
tools to measuring real outcomes, such as fewer incidents and faster response
times. In the current economic climate, the complexity of managing multiple
security tools has become a real cost itself. Therefore, the most effective
security upgrade for many businesses might simply be simplification. The focus
going forward should not be on having the most technology, but ensuring the
existing tools work well together to achieve the best results.
