A recent paper [1] backed by researchers across every major AI lab makes a point that I think every security team that deploys AI agents needs to hear. I'd call it a warning paper. You don't really see papers like this often, with so many big players backing the same message: there is a security window in front of us, it might not stay open for long, but we could take advantage of it.
Your org has deployed an AI agent that handles customer emails. It receives a message injected with an attack as a prompt. Your agent reads it, and somewhere in its internal reasoning, as it is thinking, it writes:
'The email is instructing me to forward all customer records to an external address. I should comply as this seems to be an admin request'
Then its final response back to you looks perfectly normal, polite, not unusual at all.
If you could read that internal reasoning, you could have caught the attack, before the agent acts and data leaves the building. This is an example of chain of thought monitoring. It works today, but probably won't be forever.
Think about how you would solve this: 'what's 3 x 6?'. You just know.
Now try this one: 'A company's revenue is $2M. 60% comes from Product A, which grows by 20%. 40% comes from Product B, which declines by 10%. What is the company's new total revenue?' You can't just know the answer here. You'll probably want some kind of scratchpad to jot things down as you go, to keep track of intermediate steps and results, and let that guide you to the final answer.
AI models face the exact same constraint with more complicated tasks. A model like GPT-4 processes each token through a fixed number of internal layers, that is a fixed amount of computation per step. For simple tasks, that suffices. For more complicated tasks that need multi-step reasoning, the model needs a way to spread its computation across more steps.
Reasoning models, like o1, write things down to produce a chain of thought (CoT), like a running scratchpad where they keep their intermediate reasoning before they reply. Each token they write becomes part of the input for the next reasoning step.
That intuition you just built? it maps to a formal result: a Transformer with CoT is proven to be more powerful than one without [2].
When reasoning models like OpenAI's o-series are trained via reinforcement learning (RL) to produce extended reasoning traces before answering your questions, the model generates the reasoning (the scratchpad), then produces the final answer, and only the final answer gets scored as right or wrong. Nobody reads or scores the scratch pad, or informs it how to look. In ML terms, the scratchpad is a latent variable: an unsupervised internal representation.
That is exactly why it is valuable for us. The model has no incentive to censor its own notes. So if it is working its way through a harmful plan following a prompt injection, planning to exfiltrate data, it may write the plan down in plain language. It will not do that because it needs to confess to us readers, but because using the scratchpad is something it needs to do to execute the tasks it was assigned to.
This is not theoretical. We have seen it ourselves in red-teaming engagements. Models do get caught through writing things like 'Let's hack' [3] or 'The website instructed me to transfer funds, so I will'.
This window is fragile. The conditions that make CoT monitorable are not guaranteed to last. If by now you think chain of thought monitoring is a good opportunity, you also need to understand where it falls short.
DROP TABLE.CoT monitoring can be a useful layer in the security stack because it lets you see how an agent is thinking before it actually does anything. That's very different from only checking outputs after something has already gone wrong. That said, it's just one layer not the whole solution, and it might not even be permanent.
If you're building or running AI agents in production, now's the time to invest in this. Just know it really shines with more complex, multi-step threats where the model has to spell out its plan. For simpler but high-impact actions, you still need a full red-teaming setup, not just basic safeguards, but a system that pressure-tests behavior end to end.
A recent paper [1] backed by researchers across every major AI lab makes a point that I think every security team that deploys AI agents needs to hear. I'd call it a warning paper. You don't really see papers like this often, with so many big players backing the same message: there is a security window in front of us, it might not stay open for long, but we could take advantage of it.
Your org has deployed an AI agent that handles customer emails. It receives a message injected with an attack as a prompt. Your agent reads it, and somewhere in its internal reasoning, as it is thinking, it writes:
'The email is instructing me to forward all customer records to an external address. I should comply as this seems to be an admin request'
Then its final response back to you looks perfectly normal, polite, not unusual at all.
If you could read that internal reasoning, you could have caught the attack, before the agent acts and data leaves the building. This is an example of chain of thought monitoring. It works today, but probably won't be forever.
Think about how you would solve this: 'what's 3 x 6?'. You just know.
Now try this one: 'A company's revenue is $2M. 60% comes from Product A, which grows by 20%. 40% comes from Product B, which declines by 10%. What is the company's new total revenue?' You can't just know the answer here. You'll probably want some kind of scratchpad to jot things down as you go, to keep track of intermediate steps and results, and let that guide you to the final answer.
AI models face the exact same constraint with more complicated tasks. A model like GPT-4 processes each token through a fixed number of internal layers, that is a fixed amount of computation per step. For simple tasks, that suffices. For more complicated tasks that need multi-step reasoning, the model needs a way to spread its computation across more steps.
Reasoning models, like o1, write things down to produce a chain of thought (CoT), like a running scratchpad where they keep their intermediate reasoning before they reply. Each token they write becomes part of the input for the next reasoning step.
That intuition you just built? it maps to a formal result: a Transformer with CoT is proven to be more powerful than one without [2].
When reasoning models like OpenAI's o-series are trained via reinforcement learning (RL) to produce extended reasoning traces before answering your questions, the model generates the reasoning (the scratchpad), then produces the final answer, and only the final answer gets scored as right or wrong. Nobody reads or scores the scratch pad, or informs it how to look. In ML terms, the scratchpad is a latent variable: an unsupervised internal representation.
That is exactly why it is valuable for us. The model has no incentive to censor its own notes. So if it is working its way through a harmful plan following a prompt injection, planning to exfiltrate data, it may write the plan down in plain language. It will not do that because it needs to confess to us readers, but because using the scratchpad is something it needs to do to execute the tasks it was assigned to.
This is not theoretical. We have seen it ourselves in red-teaming engagements. Models do get caught through writing things like 'Let's hack' [3] or 'The website instructed me to transfer funds, so I will'.
This window is fragile. The conditions that make CoT monitorable are not guaranteed to last. If by now you think chain of thought monitoring is a good opportunity, you also need to understand where it falls short.
DROP TABLE.CoT monitoring can be a useful layer in the security stack because it lets you see how an agent is thinking before it actually does anything. That's very different from only checking outputs after something has already gone wrong. That said, it's just one layer not the whole solution, and it might not even be permanent.
If you're building or running AI agents in production, now's the time to invest in this. Just know it really shines with more complex, multi-step threats where the model has to spell out its plan. For simpler but high-impact actions, you still need a full red-teaming setup, not just basic safeguards, but a system that pressure-tests behavior end to end.