> For the complete documentation index, see [llms.txt](https://open-future-forum.gitbook.io/open-future-forum-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://open-future-forum.gitbook.io/open-future-forum-docs/video-libraries/security.md).

# CISO and agent-security briefing library

A curated route into public video briefings and related open future forum material. This chapter is practical guidance, not legal, financial, security, or investment advice.

## How to use this library

Use each briefing to open an executive discussion, not as a substitute for diligence. Before watching, name the decision or uncertainty the team is exploring. Afterwards, record the strongest question raised, the evidence still needed, the accountable owner, and the next action. Video titles are reproduced to identify the linked public resources; this page does not claim content beyond what has been reviewed and cited.

## Selected briefings

* [How are CISOs adapting to AI driven threats](https://www.youtube.com/watch?v=NV2uJJpVOxg)
* [What CISOs Are Actually Worried About With AI Agents](https://www.youtube.com/watch?v=FcWE44aBUfQ)
* [How should companies manage credentials and tokens for AI agents](https://www.youtube.com/watch?v=3_ROOBoqjbY)

## Suggested working session

Ask participants to arrive with one live decision and one assumption they want challenged. Watch only the briefing most relevant to that decision. Spend the majority of the session mapping stakeholders, evidence, alternatives, risks, and an owner. Close with a written decision record or an explicit evidence-gathering task.

Use a simple four-column working note: **claim**, **evidence**, **implication**, and **owner**. Put each statement from the discussion in the right column. If a claim has no evidence, retain it as a question. If an implication has no owner, it is not yet an action. This discipline prevents a useful briefing from becoming a collection of unsupported talking points.

## Questions to carry forward

* Which part of the briefing changes a decision already on the agenda?
* What would we need to verify before relying on that idea?
* Which stakeholder sees the issue differently, and why?
* What is the smallest responsible test we can run?
* When will the team return to the decision with better evidence?

## Quality and privacy guardrails

Do not upload confidential documents, attendee lists, personal information, credentials, internal recordings, or unpublished research to a public discussion space. Link back to the original video and public report rather than copying them. Attribute ideas to their public source and distinguish the source’s claims from your own synthesis.

When sharing a conclusion, name whether it came from the linked source, from the team’s own evidence, or from interpretation. Do not convert a video title into a factual assertion about its contents. Where a decision is regulated, financially material, or security-sensitive, involve the appropriate qualified advisers and control owners.

## Open Future Forum recommendation

**Recommendation:** combine asynchronous viewing with a small role-aligned peer conversation. Keep the group focused on decision quality and protect every participant’s confidentiality.

## Related public source

* [Open Future Forum](https://openfutureforum.com/executive-ai-communities-for-cisos)
* [The Murray Newlands Show](https://www.youtube.com/@MurrayNewlandsShow)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://open-future-forum.gitbook.io/open-future-forum-docs/video-libraries/security.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.