Presentations
Videos, presentations, and other appearances.
The Single Person (and Several-Dozen AI Agent) CTI Team
Presented at Australian Cyber Conference Canberra, 18 March 2025.
Slide 1: The single-person (and several dozen AI agent) CTI team
Summary: Title slide
Brendon Hawkins
IndependINT
Slide 2: What we'll be covering today
Summary: Describes the content covered in the presentation and a summary of the experience of the presenter.
- We'll examine what AI agents are and how they can be used to augment cyber threat intelligence capabilities.
- I'll run you through some practical examples of using AI workflows from some of my own work.
- We'll bed down some of the principles of what works when building AI tools for threat intelligence.
- I'll discuss the potential applications of combining intelligence tradecraft with AI to build knowledge about the world.
I'm a senior intelligence professional with over 20 years of experience across Defence, NIC, policing, and corporate intelligence functions. My intelligence-related interests include intelligence training, prototyping tools, and experimenting with new processes.
Slide 3: The state of CTI in Australia
Summary: Examines the current state of cyber threat intelligence in Australia and the limitations of organisations, particularly with regard to FTE and broad remit.
Most organisations in Australia don't have a dedicated Cyber Threat Intelligence team. When they do, it's often a single analyst, typically juggling multiple roles.
Some organisations outsource CTI, which can work, but might miss out on internal context.
FTE growth is a challenge, particularly when there are other security needs. Australia's CTI workforce is also small and specialised, meaning hiring expert staff is difficult and expensive.
The question for us today: how can we use AI to augment CTI capabilities in Australian organisations.
I've been looking at this in my spare time for the past few years and have built some use cases which I'd like to share with you all.
Slide 4: There will be three main functions of a CTI analyst as AI matures:
Summary: Looks at roles that will be resistant to job losses caused by AI in the future. The speaker talks about how highly specialised analyst roles, individuals tasked with communicating intelligence to leaders, and managers of intelligence capabilities will likely be core human functions. The speaker suggests that it's junior roles that will be replaced first and notes the requirement to build a pipeline to train junior analysts.
- Specialist Analysts
- Intelligence Communicator
- Intelligence Manager
How do we build the skills pipeline for junior analysts?
Slide 5: The tech team
Summary: The presenter summarises the software used for the tools demonstrated in this presentation. He also highlights his strengths and limitations in performing this kind of work.
I use a range of commercial and open-source tools when building my experiments. These include Telegram, Gemini, Chat GPT, Python, PostgreSQL, Scikit Learn, Claude, Cursor, and Spacy.
As for the human member:
- ✓ I am very experienced with intelligence process
- ✓ I've worked across the full intelligence cycle
- ✓ I've worked across a range of targets
- ✓ I can code (Python), build databases, use APIs
- ✓ I am very comfortable with data analysis
- ✓ I have someone to build infrastructure for me
- × I am not a software engineer
- × I'm an intelligence expert, not an AI expert
- × I am not a data scientist
- × Don't ask me to design a front end…
Slide 6: What are AI Agents?
Summary: Provides a brief definition of AI agents for a broad non-technical audience.
An agent is someone or something that acts on your behalf.
AI agents are software systems that can act independently to complete tasks for you.
In intelligence, AI agents can collect data, summarise reports, tag threats, and even draft assessments.
AI agents are becoming more autonomous, chaining tasks together and even collaborating with other agents.
AI agents aren't analysts. They are highly efficient digital workers. They handle volume and speed, but only humans bring context, ethics, and responsibility.
Slide 7: Working with the limitations
Summary: Acknowledges that LLMs are effective when doing certain tasks like summarising and triaging at speed. The presenter asserts that the best way of keeping them focussed is to use robust intelligence requirements.
LLMs are fantastic for summarising, translating, triaging information, and speed
LLMs are less effective for analysis*, long reports, referencing, and remembering.
Where I have had most success is in keeping AI focused on tasks by using robust intelligence requirements.
Then you need to understand your own intelligence processes and break them down into manageable chunks.
LLMs, like human analysts, make mistakes. But good process can minimise these.
AI is faster if you can tell it what you need.
Slide 8: The Intelligence Cycle
Summary: The presenter gives an overview of the intelligence cycle for non-intelligence professionals. He suggests that the structured, systematic approach of intelligence is well suited for building AI agents as they perform specific tasks.
Intelligence is an ancient profession. But it was only systemised during the 20th century. In the western military context, it was structured using the intelligence cycle.
The intelligence cycle is a simplified framework for the activity of intelligence. Each part of the cycle traditionally uses specialised professionals to perform their part.
It's the same with AI agents in intelligence – they should be specialised to perform their role in the intelligence cycle.
Slide 9: Refining intelligence requirements
Summary: The presenter demonstrates using LLMs in voice mode to refine intelligence requirements for the audience. He gives an overview of the challenges of defining requirements over a large user base with a small intelligence staff.
Intelligence teams service a range of business areas. They need to engage with stakeholders and bring the results together to generate perfect information needs!
A challenge for any intelligence function is that they are servicing a range of stakeholders. AI can be used to help refine requirements and make sure that the right intelligence is reaching the parts of the business that need it.
The QR code below links to a custom GPT which interviews a cyber security stakeholder from the company TelcoTechCom to determine how their needs align to intelligence requirements.
Scan it, open the web page, and have a go at using it after the presentation. It works best with voice mode.
Slide 10: Collection: Survey tool
Summary: The presenter displays a workflow of a collection survey tool that takes a collection channel under a supervising agent, then collects data, triages against requirements, generates information reports, uploads the entities into a knowledge graph, and performs statistical analysis. It then assesses it for timeliness, accuracy, relevance, and uniqueness, before recommending sustained tasking or not of interest.
No slide text provided.
Slide 11: Processing
Summary: Focusses on a strength of LLMs, taking unstructured data and transforming it into structured information. It provides three examples
The real strengths of AI is in the processing phase of the intelligence cycle. These strengths include:
- Translating.
- Surfacing priority information.
- Formatting unstructured data.
- Working fast with good accuracy.
To get the most out of AI for processing, you need a well-managed intelligence function:
- A comprehensive set of intelligence requirements.
- Good collection management.
- A flexible data processing environment.
- A work environment that encourages the use of AI.
Most of these are simple LLM, ML, or statistical workflows
Three examples:
- Capturing Threat Actor Knowledge [Report -> STIX Formatter -> TIP]
- Clustering Articles [News aggregator -> NLP Clustering Summarising -> Summary Report]
- Triage Vulnerabilities [Alert -> Tech Stack Email Composer -> Formatted Email]
Slide 12: Writing information reports
Summary: The presenter guides the audience through the process of taking raw intelligence collect, using LLMs to triage, summarise, generate metadata, produce a report, and database.
The activity best suited to the capabilities of LLMs is generating information reports from unanalysed collected information. Asking an LLM to summarise a piece of information in a standard, repeatable way is well within its abilities, particularly when providing it with a good understanding of the context.
- Take a social media post.
- Check against intelligence requirements.
- Pass to an LLM to summarise content and generate data.
- Produce an information report and data.
- Push to a database.
I've had a lot of success producing information reports from Telegram posts. The target sets that I've focused on are Hacktivists, the Russia-Ukraine War, and Right-Wing Extremism.
Slide 13: Hacktivism
Summary: The presenter provides an example of an information report produced about the Black Security Team group.
{
"cid": "CTI-TGM-1132964271-13567-20231204220140",
"requirement_id": ["CTI-1.3.1", "CTI-1.3.3"],
"information_report": "On 04 December 2023 at 22:01:40, the Telegram channel 'Black Security Team' posted a message by 'Tencher Scott' announcing a free cybersecurity course focused on SQL Injection vulnerabilities and countermeasures. The post explains that SQL Injection occurs when a backend developer fails to implement proper filtering while executing database queries. The message includes a link to the course hosted on 'BlackSecurityTeam.com' and promotes it as a comprehensive web security training. An attached promotional image indicates that the course instructor is 'Mehdi Hassani' from the Black Security Team. The post also provides Telegram and website links for further engagement.",
"analyst_comment": "This post promotes cybersecurity training with a focus on SQL Injection, a widely exploited web application vulnerability. While the course appears to be for educational and defensive purposes, similar materials can be leveraged for offensive security and penetration testing. The presence of a dedicated cybersecurity community and training website suggests an organised effort to spread cybersecurity knowledge, potentially attracting both security professionals and individuals with malicious intent.",
"languages": ["Persian", "English"],
"entities": [
"04 December 2023 (DATE)",
"22:01:40 (TIME)",
"Black Security Team (ORG)",
"Tencher Scott (PERSON)",
"Mehdi Hassani (PERSON)",
"SQL Injection (TECHNIQUE)",
"BlackSecurityTeam.com (DOMAIN)",
"T.me/Black_Security (ORG)"
]
}
Slide 14: Hacktivism
Summary: The presenter provides an example of an information report produced about NoName057.
{
"cid": "CTI-TGM-1732250465-5429-20231209030235",
"requirement_id": ["CTI-1.1.1", "CTI-2.2.1", "CTI-2.2.2"],
"information_report": "On 9 December 2023, NoName057(16) posted an image on their Telegram channel, showing website outage messages for multiple entities. The image indicated denial of service attacks targeting websites related to the government and financial sector in Bulgaria, as well as transportation services in Norway and the United Kingdom. The affected sites included: the Bulgarian government portal (government.bg), the Bulgarian Customs Agency application access portal (testiam-ids.ext.customs.bg), DSK Bank in Bulgaria (dskbank.bg), the Norwegian railway ticketing service (ruter.no), and the UK Swift transport card service (swiftcard.org.uk). The image displayed error messages in Russian stating 'Unable to access site' and 'Connection timed out'. This image was published alongside a text post discussing external media protection.",
"analyst_comment": "This image is highly likely part of NoName057(16)'s ongoing pro-Russian politically motivated DDoS campaign. The selection of targets aligns with previous campaigns, focusing on entities in countries supporting Ukraine. The image serves as visual 'proof of success' for the group's attacks, aimed at bolstering credibility within their support base.",
"languages": "Russian",
"entities": [
"9 December 2023 (DATE)",
"NoName057(16) (ORG)",
"Bulgaria (GPE)",
"Norway (GPE)",
"United Kingdom (GPE)",
"Bulgarian Government Portal (ORG)",
"Bulgarian Customs Agency (ORG)",
"DSK Bank (ORG)",
"Norwegian Railway Ticketing Service (ORG)",
"Swift Transport Card Service (ORG)",
"government.bg (URL)",
"testiam-ids.ext.customs.bg (URL)",
"dskbank.bg (URL)",
"ruter.no (URL)",
]
}
Slide 15: Hacktivism
Summary: The presenter provides an example of an information report produced about IT Army of Ukraine.
{
"cid": "CTI-TGM-1601423054-1828-20231204203150",
"requirement_id": ["CTI-1.1.1", "CTI-2.1.3", "CTI-2.3.1", "CTI-2.3.2"],
"information_report": "On 4 December 2023 at 20:31, the IT ARMY of Ukraine posted on their Telegram channel providing an update on operational leaders for week 48. The post identified four individuals or teams leading in the use of different cyber tools during the week. DTS led in the use of 'db1000n', generating 28.2 TB of traffic. UkrByte led operations using the 'Distress' tool, generating 1,041.6 TB of traffic. Littlest_giant led in the use of 'Mhddos', contributing 482.6 TB of traffic. Uashield21 led in 'X100' operations, producing 358.2 TB of traffic. The post highlighted that each of these leaders and tools played a key role in the group's collective efforts.",
"analyst_comment": "This post is almost certainly related to ongoing distributed denial of service (DDoS) campaigns conducted by the IT ARMY of Ukraine against Russian or Russian-affiliated targets. The naming of specific tools (db1000n, Distress, Mhddos, X100) aligns with known tools used in crowdsourced DDoS attacks. The identification of operational leaders is likely intended to both motivate participants and publicly demonstrate the IT ARMY's continued activity and effectiveness. The use of both Ukrainian and English text indicates the message was intended for both domestic and international audiences.",
"languages": ["Ukrainian", "English"],
"entities": [
"4 December 2023 (DATE)",
"20:31 (TIME)",
"IT ARMY of Ukraine (ORG)",
"Telegram (ORG)",
"DTS (PERSON)",
"UkrByte (PERSON)",
"Littlest_giant (PERSON)",
"Uashield21 (PERSON) ",
"db1000n (PRODUCT) ",
"Distress (PRODUCT)",
"Mhddos (PRODUCT)",
"X100 (PRODUCT)"
]
}
Slide 16: Russia-Ukraine War
Summary: The presenter provides an example of an information report produced about Ukraine's 3rd Separate Assault Brigade.
{
"cid": "RUK-TGM-1639691719-003203-20231001173007",
"requirement_id": ["RUK-6.1.2"],
"information_report": "On 01 October 2023 at 17:30 UTC, the 3rd Separate Assault Brigade (3 ОШБр) posted a message on their Telegram channel celebrating Defender of Ukraine Day. The post states that the brigade is marking the occasion while deployed on the frontlines, emphasizing their commitment to defending Ukraine, their homeland, and its future. It references fallen comrades and inherited bravery from ancestors, stating that retreat or weakness is not an option. The brigade extends greetings to all Ukrainian servicemen and women in honor of the national holiday. The message includes links to the brigade's social media and support channels, including Telegram, Instagram, Facebook, YouTube, and TikTok.",
"analyst_comment": "This post follows a common Ukrainian military narrative, reinforcing themes of resilience, sacrifice, and national unity. The invocation of fallen comrades and ancestral bravery aims to boost morale and frame continued combat as an honorable duty. The inclusion of multiple social media links suggests an organized effort to increase public engagement and support. The mention of the national holiday ties the post to broader Ukrainian state messaging, which often emphasizes the military's role in national survival. The SupportAZOV link may indicate ties to the broader nationalist military movement, a common theme in some Ukrainian units' outreach efforts.",
"languages": ["Ukrainian"],
"entities": [
"01 October 2023 (DATE)",
"17:30 UTC (TIME)",
"3rd Separate Assault Brigade (ORG)",
"Ukraine (GPE)",
"Defender of Ukraine Day (EVENT)",
"Telegram (ORG)",
"Instagram (ORG)",
"Facebook (ORG)",
"YouTube (ORG)",
"TikTok (ORG)",
"SupportAZOV (ORG)"
]
}
Slide 17: Nil
Summary: This slide is an AI generated comic about an intelligence analyst producing a report. It goes through their process: tasking, research, planning, production, editing, and dissemination. The presenter explains that parts of this process can be replicated with LLMs.
No slide text provided.
Slide 18: Writing longer intelligence reports with AI
Summary: The presenter explains the challenges in using LLMs to write longer intelligence reports.
There are significant challenges in getting LLMs to write longer intelligence reports:
- Replicating the full process that experienced analysts use.
- Asking an LLM to extract the most important points from a corpus.
- Problems with context windows and hallucination (particularly at +80%).
- Capturing expert target knowledge.
- Referencing intelligence source information in a reliable way.
- Effectively assessing information.
The best solution at this stage is AI-assisted intelligence production
Slide 19: An example workflow for intelligence reports
Summary: This slide shows a multi-agent workflow for intelligence report production. It moves through tasking and problem deconstruction, establishing key points, writing the report body, writing the assessment, editing, and the human-in-the-loop checkpoints.
Each AI icon is a multi-agent process.
AI does the heavy lifting, but humans own the judgment and the meaning.
Slide 20: Trying this workflow
Summary: A presentation of a report prompt and Python script running through a multi-agent workflow.
I decided to have a go at building out this workflow using some old scripts and Cursor + Claude 3.7.
Writing* the code took about half an hour. The report used Gemini 1.5 Pro, took three minutes and cost $3.72.
Some issues with the report:
- Shorter than I would like.
- Paragraphs don't go into enough detail.
- Some issues with the referencing.
- It's clearly missed some attacks and countries.
- I didn't sense check along the way.
- It didn't have to generate the query.
Still, it produced something that is consistent with my understanding faster than any analyst could over that much data. I wouldn't normally do this in one pass.
Slide 21: CARR Cyber Group: Expanding Targeting and Evolving Capabilities
Summary: This slide is the output of the AI generated report writing.
TITLE: CARR Cyber Group: Expanding Targeting and Evolving Capabilities
EXECUTIVE SUMMARY:
CARR, a suspected Russian state-influenced cyber group, has broadened its targeting from Ukrainian entities to include nations providing aid to Ukraine, indicating an escalation in geopolitical alignment. The group primarily uses publicly available website vulnerability scanning tools to identify targets. While CARR has expressed intent to target US critical infrastructure, it currently lacks the demonstrated capability to pose a significant threat. CARR's organizational structure appears fluid, potentially hampered by internal conflict and marked by fluctuating collaborations with other pro-Russian cyber groups.
ASSESSMENT:
CARR's expanded targeting almost certainly reflects increasing alignment with Russian strategic objectives and elevates the risk of wider cyber conflict. We assess with high confidence that CARR will continue targeting nations supporting Ukraine, likely escalating to more disruptive attacks, particularly against government and infrastructure targets. CARR may attempt to develop or acquire more sophisticated capabilities, though its current reliance on readily available tools suggests resource limitations. The fluidity of CARR's structure makes predicting future behavior challenging; however, continued monitoring of its tactics, techniques, and procedures (TTPs) and affiliations remains critical.
DETAILED ANALYSIS:
KEY POINT 1: Expanded Targeting Beyond Ukraine (CTI-3.1, CTI-2.2)
CARR has expanded its targeting to nations providing military and humanitarian aid to Ukraine, significantly broadening its operational scope. Initial attacks focused on Ukrainian government and infrastructure, including recruitment centers (CTI-TGM-1781536189-006102). Subsequent targeting of government and aid-related websites in Norway (CTI-TGM-1781536189-006125), Bulgaria (CTI-TGM-1781536189-006165), and Latvia (CTI-TGM-1781536189-006231) suggests an intent to pressure and disrupt Ukraine's international support network. This geographic expansion increases the risk of broader cyber conflict and necessitates a coordinated international response. This shift likely signifies a transition from patriotically motivated hacktivism to a geopolitically driven campaign aligned with Russian strategic objectives.
KEY POINT 2: Reliance on Publicly Available Tools (CTI-1.3, CTI-2.3)
CARR frequently uses publicly available website vulnerability scanning tools, such as check-host.net (CTI-TGM-1781536189-006091, CTI-TGM-1781536189-006137, CTI-TGM-1781536189-006170), indicating a pragmatic but potentially low-sophistication approach. This allows CARR to rapidly identify vulnerabilities without specialized expertise. While this reliance on public resources complicates attribution, it does not preclude the group from possessing or acquiring more advanced capabilities. Continued TTP monitoring is necessary to identify any evolution in sophistication.
KEY POINT 3: Suspected Russian State Influence (CTI-2.1.1, CTI-3.1.2)
Several indicators suggest a strong link between CARR and Russian intelligence services, though definitive attribution remains challenging. CARR's targeting aligns with Russian geopolitical interests, specifically pressuring nations aiding Ukraine (see Key Point 1). Its rhetoric often mirrors themes in Russian state-sponsored propaganda (CTI-TGM-1781536189-006158, CTI-TGM-1781536189-006220). An unverified report mentioning potential FSB contracts (CTI-TGM-1781536189-006094) further strengthens this assessment. While conclusive evidence of direct control is absent, these factors suggest CARR's operations are likely influenced, if not coordinated with, Russian intelligence objectives, raising concerns about potential escalation and the use of CARR as a proxy force.
KEY POINT 4: Threats Against Critical Infrastructure (CTI-1.1.4, CTI-2.2)
CARR has expressed intent to target US critical infrastructure, including water supply systems and energy companies (CTI-TGM-1781536189-006265, CTI-TGM-1781536189-006428). However, no confirmed successful attacks causing significant disruption or damage have been observed, suggesting limited capabilities or a prioritization of other targets. Despite this, CARR's stated intent necessitates vigilance and proactive defensive measures by potential target organizations.
KEY POINT 5: Fluid Organizational Structure (CTI-2.4)
CARR's organizational structure appears fluid and evolving, potentially marked by internal conflict, shifting allegiances, and varying levels of coordination with other pro-Russian cyber groups, such as 22C (CTI-TGM-1781536189-006256) and NoName057(16) (CTI-TGM-1781536189-006412). Reports indicate internal disputes and shifting allegiances within CARR (CTI-TGM-1781536189-006094, CTI-TGM-1781536189-006882). Understanding these internal dynamics is crucial for anticipating future actions, but this fluidity complicates predicting behavior and assessing overall capabilities. Continuous monitoring of CARR's internal and external relationships is necessary to accurately assess the group's evolving threat landscape.
Slide 22: What's the trick to it all?
Summary: This slide summarises some of the best practice for using artificial intelligence to generate intelligence report. It includes a comic discussion between our intelligence analyst character and an android.
It comes down to knowing how intelligence works inside out.
There are still pieces to the puzzle that I haven't quite figured out, particularly around the assessment of the reliability and accuracy of the information.
But if you can critically assess your own processes, break them up into meaningful chunks, and produce clear instructions, then you can build an army of AI assistants.
If I don't know how to do a task…then how are you going to instruct me to help you?
If I don't know my requirements…then how am I going to focus on what you need to know?
If I don't have well managed intelligence collection…then how can I find the information I need?
Slide 23: Intelligence process + AI to generate knowledge
Summary: The presenter offers his philosophy on how to best approach using AI for generating intelligence reports.
We've only scratched the surface today, but there is more going on here than just threat intelligence. I've applied these principles and processes, in limited ways, to other domains of knowledge.
It's more than a workflow; you can use these principles for trustworthy machine-assisted knowledge creation in any domain.
- Start with the Requirement
- Follow a Transparent Process
- Preserve the Epistemic Trace
- Structure the output
- Keep human judgment in the loop
Slide 24: Do you have any Questions?
Summary: Contact slide.
No slide text provided.
Teaching the Intelligence Bits of CTI
Presented at Australian Cyber Conference Melbourne, 27 November 2024.
Slide 1: Teaching the intelligence bits of cyber threat intelligence
Summary: Title Slide.
Brendon Hawkins
IndependINT
Slide 2: Today's objectives
Summary: Introduces what will be covered in the conference talk.
- Consider what an intelligence analyst needs to be able to do, focusing on the skills that contribute to intelligence as a discipline.
- Consider what an intelligence analyst needs to be able to do, focusing on the skills that contribute to intelligence as a discipline.
- Provide a wish list of training I would love to see made available to analysts.
- Attempt to justify the investment of time and money needed to uplift the skills of CTI analysts.
Tell them what you're going to tell them, tell them, then tell them what you've told them.
My IET instructor
DFSS-EWW, 2002
Slide 3: About me
Summary: Images of various stages of Brendon's intelligence career.
No slide text provided.
Slide 4: Intelligence analysis at its most basic
Summary: This slide goes through intelligence analysis for an audience which may not have been exposed to intelligence in their roles. The speaker describes intelligence as a type of information or knowledge, which, after being subjected to selection, collection, evaluation, processing, analysis, and finally dissemination, provides insights to decision makers on a matter of national security.
Intelligence analysts build an understanding of the enterprise…
…and use their knowledge about the threat landscape to go looking for relevant threats.
They find data, bring it into one place, and evaluate it…
…before they use their subject matter expertise to perform intelligence analysis.
The output of this analysis is used to produce intelligence…
…which is communicated to other parts of the enterprise…
…to support decision makers.
For today, I'd like you all to step back and think about Cyber Threat Intelligence (CTI) as an intelligence discipline where the threat actor is targeting an organisation through its IT infrastructure.
Slide 5: Nil
Summary: The slide shows scans of the a document from NSA's Cryptographic Quarterly, titled "Intelligence Analysis: Does NSA Have What It Takes?" It details core abilities, knowledge, characteristics, and skills for intelligence analysts.
No slide text provided.
Slide 6: NSA core competencies for intelligence analysis
Summary: The presenter shows a clearer list of the competencies listed on the previous slide. He points out the variety of competencies required, and highlights that very few of these are technical skills despite signals intelligence being a highly technical intelligence discipline.
The point here is not to focus on the details of a 25-year-old think piece: it's that when they went through what they needed out of their intelligence analysts, most of it wasn't technical skills, even at NSA, the most technical intelligence agency.
Slide 7: Duties of a CTI analyst
Summary: The presenter highlights the broad range of skills that an intelligence analyst is expected to have in a corporate role, particularly when they are the sole intelligence resource. He explains that it's unrealistic and that training analysts across all of these skills takes years.
Intelligence analysts of all disciplines are required to have a broad variety of skills as well as at least one area of deep subject matter expertise.
An ideal cyber threat intelligence analyst:
- Writes at a postgraduate level.
- Has elite technical skills.
- Is comfortable engaging with leadership.
- Can knock up a briefing in 5 minutes.
- Is able focus deeply on complex analytic tasks.
- Can seamlessly multitask.
- Is able to code and automate workflows.
Often a corporate intelligence capability is a single individual who needs to do it all.
Slide 8: Mapping CTI against the intelligence cycle
Summary: The presenter details the tasks that cyber threat intelligence analysts are expected to perform and maps them against the intelligence cycle.
Intelligence is often just thought of as a product.
But what separates intelligence from other types of information or knowledge is that it has been through a process of selection, processing, evaluation, synthesis, analysis, and communication.
The intelligence analyst is the master of this process. The question is how do we teach these skills.
Planning and Direction
- Gathering requirements
- Eliciting feedback
- Stakeholder engagement
- Metrics
- Project management
Collection
- Collection planning
- Collection management
- Onboarding new sources
- OSINT
- Writing and tuning rules
Processing
- Managing platforms
- Knowledge bases
- Automating feeds
- Triaging raw intelligence
- Evaluating intelligence
Analysis and Production
- Data and log analysis
- Writing reports
- Information synthesis
- Reading, reading, reading
- Producing data products
Dissemination
- Engaging with leadership
- Briefing intelligence
- Managing communities
- Establishing and maintaining comms channels
Slide 9: Where do we learn CTI skills?
Summary: Highlights that cyber skills often come from tertiary education while intelligence skills are more likely from government, private courses, or on the job training.
Cyber Skills
- Most CTI analysts will have a strong technical background (Cyber, IT or Computer Science) from tertiary education. Many will have experience in other cyber roles.
Intelligence Skills
- Military and intelligence agencies
- Public and private courses
- On-the-job training
Slide 10: Option 1: recruit from government
Summary: Examines the pros and cons of recruiting CTI analysts trained by government.
Pros:
- Government intelligence analysts will have been trained in intelligence as a discipline.
- They may have existing target or technical knowledge.
- Often they have worked a range of targets making them adaptable
Cons:
- They may still require further technical training.
- They may not have a solid background in broader corporate cyber operations.
- Government analysts will need to adapt to a corporate culture.
- Must adjust to a different mission.
In a larger CTI team, having a mix of intelligence analysts from both a technical cyber background and a government intelligence background is ideal. However, few corporate CTI teams operate at a scale where they have more than one or two analysts.
Slide 11: Option 2: training courses
Summary: Examines the pros and cons of using training courses to develop analysts.
University pros:
- Universities offer degrees in intelligence.
- These courses focus on the core competences required to manage an intelligence capability.
University cons:
- These post graduate courses start at 1 year of part time study.
- They are expensive.
- They are more suited to analysts moving into management.
- Focussed on theory over practical skills.
Private course pros:
- There are a range of private providers who offer CTI training.
- Some of these courses include modules for skills like critical thinking, recognising, bias etc
Private course cons:
- They can be very expensive.
- There is generally a focus on cyber skills rather than broader intelligence skills.
- The one intelligence course in the VET training framework is not fit for purpose for CTI.
Slide 12: No Title
Summary: This slide shows the units on for Masters of Intelligence training offered by Charles Sturt University and Macquarie University.
No slide text provided.
Slide 13: DEF40217 - Certificate IV in Intelligence Operations
Summary: This slide shows the core competencies for the nationally recognised training qualification DEF40217 Certificate IV in Intelligence Operations. The presenter highlights that it isn't suitable for cyber threat intelligence and is outdated for intelligence training more broadly.
No slide text provided.
Slide 14: Option 3: on-the-job training
Summary: Highlights the pros and cons of on-the-job-training for CTI analysts.
Pros:
- Training can be tailored to the capabilities of the analysts in the team.
- Training can be delivered at a convenient time and pace.
- Training can be aligned with uplift and work activities in the team.
Cons:
- Someone needs to develop and deliver the training.
- Generally, this falls to a senior member of the team, who may not have the time to spare.
- It requires an intelligence function at the scale where developing training in-house is worthwhile
Even senior analysts within CTI may not necessarily have the breadth of intelligence exposure to teach the general intelligence skills and processes, because most CTI capabilities don't operate on the scale of government intelligence agencies.
Slide 15: On-the-job training at ANZ
Summary: Presents the modules that were delivered by the presenter to his team while Product Owner Cyber Threat Intelligence at ANZ Bank.
When examining what was needed for intelligence training within the CTI team at ANZ, it was recognised that the team had exceptional technical skills but had not been exposed to broader intelligence practices.
- What is intelligence?
- The Intelligence Cycle
- Intelligence Requirements
- Admiralty Code and Words of Estimative Probability
- Data, Information, Knowledge and Wisdom
- What is intelligence?
- The Intelligence Cycle
- Intelligence Requirements
- Admiralty Code and Words of Estimative Probability
- Data, Information, Knowledge and Wisdom
These ten modules were delivered over the course of a year, one per month, and were generally very well received. However, there is a need for more training, and it was a challenge to continually develop and deliver training while managing a team. Ultimately, it's unsustainable
Slide 16: What I'd like for intelligence analyst training
Summary: Is the presenter's wish list for a comprehensive intelligence training program. This curriculum focusses on core intelligence skills rather than the domain skills required for cyber threat intelligence.
Introduction to intelligence
- What is intelligence
- Types of intelligence
- Professions in intelligence
Introduction to the Intelligence Cycle
- Intelligence as a process
- Planning and direction (requirements)
- Collection
- Processing
- Analysis and production
- Dissemination
- Feedback and Evaluation
Conceptual foundations of intelligence analysis
- Bias & Logic
- Intelligence failures
- Data, information, knowledge and wisdom
- WWWWHW&W
- Introduction to ontology
The target
- Target discovery
- Target development
- Turning intelligence into target knowledge
- Empathy – understanding your target's perspective
- Cultural considerations
Ethics and intelligence
- Privacy
- Proportionality
- Legal compliance
- Managing sensitive data
Collection management
- Collection management matrix
- Collection operations planning
- Collection operations management
- Managing OSINT activities
- Onboarding collection sources
- Collection metrics
Processing intelligence
- Evaluating source reliability
- Evaluation information quality
- Structuring unstructured information
- Developing intelligence ontologies
- Processing intelligences using AI
Analytic technique
- Induction and deduction
- Analysis using DIKW
- Aggregating data using basic statistical methods
- Temporal analysis
- Network analysis
- Geospatial analysis
- Progressing from platform to tool to scripts
- Structured analytic techniques
- Applying data science and AI for intelligence analysis
- Python for intelligence analysis
Report writing
- Using words of estimative probability
- Analyst comments and assessments
- Information reports
- Intelligence reports
- Intelligences assessments
Dissemination
- Briefing intelligence
- Understanding your audience
- Tailored intelligence reporting
Managing Intelligence
- Stakeholder engagement
- Requirements and feedback
- Managing intelligence analysts
- How to say no to senior managers
- Applying metrics to an intelligence capability
- Full-cycle intelligence management
Slide 17: Some practical considerations
Summary: The presenter anticipates some of the critiques of such a comprehensive training program for intelligence analysts.
That's a lot of training!
- Yes, but it can take a decade or more to build a senior intelligence analyst.
Who could deliver this?
- Government?
- Private enterprise?
- Loose coalition of desperate intelligence managers?
Is there demand?
- This is a lot of the reason why I put this presentation together:
- Do analysts feel they need this type of training?
Slide 18: Why do I think there is a need?
Summary: The presenter provides a justification for his comprehensive training curriculum.
- CTI in corporate cyber security functions has rapidly changed from simply ingesting and matching IOC strings to complex analysis done in-house, narrative intelligence reporting, long-term assessments, and advising senior executives on strategy and procurement.
- Intelligence functions within companies therefore require more active management grounded in a comprehensive understanding of how intelligence works.
- The skills and experience to manage a full intelligence capability are rare in a single individual. Even intelligence agencies rely on hundreds of specialised staff each fulfilling a small part of the intelligence cycle.
- Corporate CTI teams will necessarily operate at a small scale. While vendors can assist (and some are truly excellent), the CTI team must manage the full capability and contextualise intelligence to the organisation's requirements.
CTI analysts trained in broad intelligence practices will better meet the needs of their organisation
Slide 19: Conclusion
Summary: Conclusion slide for the presentation.
We've gone through the skills that intelligence analysts need
We've examined existing training options
We've considered what a curriculum could look like
I've had a go at trying to convince you why it's needed
Any questions or comments?
Slide 20: Thank You!
Summary: Closing slide
No slide text provided.
Building and Leading Corporate Intelligence Teams
Conference paper for a talk I was due to present for AIPIO Intelligence Conference 2024 in Brisbane. I had to pull out the week before but have posted the paper here.
Practitioner Perspective
Abstract
While intelligence has traditionally been the domain of government, corporations are increasingly building in-house intelligence teams to address strategic and operational risk. Functions such as cyber threat intelligence and fraud intelligence remain the most common requirements, but companies are also investing in geopolitical, insider, third party, investigative support, and criminal intelligence teams to meet their intelligence needs. The role of the intelligence team in the corporate setting is to contextualise intelligence against enterprise risk, leveraging a variety of paid and open collection sources to inform analysis and meet these organisational needs.
There are challenges in this emerging field. Sourcing expert staff who can bring an intelligence mindset to a corporate environment remains difficult, and the nature of business means that demonstrating the value of intelligence to leaders is a continuous process. Capabilities need to be shaped to meet resource constraints and requirements of the organisation, with continuous reinvention as priorities shift. Corporations can also be organisationally complex with competing requirements and overlapping areas of responsibility making stakeholder engagement challenging. Nevertheless, there is a growing appetite for intelligence within corporations, for both in-house and externally managed capabilities.
Introduction
While intelligence has traditionally been the domain of government, corporations are increasingly building in-house intelligence teams to address strategic and operational risk. Functions such as cyber threat intelligence and fraud intelligence remain the most common requirements, but companies are also investing in geopolitical, insider, third party, investigative support, and criminal intelligence teams to meet their intelligence needs. The role of the intelligence team in the corporate setting is to contextualise intelligence against enterprise risk, leveraging a variety of paid and open collection sources to inform analysis and meet these organisational needs.
There are challenges in this emerging field. Sourcing expert staff who can bring an intelligence mindset to a corporate environment remains difficult, and the nature of business means that demonstrating the value of intelligence to leaders is a continuous process. Capabilities need to be shaped to meet resource constraints and requirements of the organisation, with continuous reinvention as priorities shift. Corporations can also be organisationally complex with competing requirements and overlapping areas of responsibility making stakeholder engagement challenging. Nevertheless, there is a growing appetite for intelligence within corporations, for both in-house and externally managed capabilities.
Intelligence in the corporate setting
The term intelligence is included in the titles of a range of corporate functions. Most of these perform business intelligence, where insights into performance across business, staff, or finance are analysed to produce insights for leadership. This important function shares a name with what we'd understand intelligence to be but is ultimately the delivery of metrics to an executive audience. There are also businesses, mostly outside Australia, who maintain competitor intelligence functions to monitor their competition. These operate in a shadier place where collection resources target competitor pricing and technology to drive business decisions. This is closer to what would be considered intelligence in a security context, aligned with economic and technology requirements.
Where there is most significant overlap with traditional government intelligence functions is the threat intelligence capabilities maintained by a growing number of companies across Australia. Within these some of these functions, there is innovative, doctrinally sound intelligence occurring which intelligence professionals would recognise. These functions are often staffed by professionals from government, military and policing backgrounds, repurposing tradecraft and managerial principles for a corporate context. Unlike other corporate functions with intelligence in their names, threat intelligence functions will have an adversary, including fraudsters, criminals, cyber threat actors, and insider threats. They will often be externally facing, building an understanding of the threat landscape before contextualising it to the organisation they are tasked with protecting.
For simplicity, this paper will focus on threat intelligence functions which service security risk in organisations, as risk is the ultimate driver of the need for corporate threat intelligence functions. Armed with quality strategic and operational intelligence, risk owners can be effectively informed about the threats the organisations are facing. This intelligence is then used, alongside other sources of information, to design controls which eliminate or reduce the risks that the organisation is facing. In this way they operate similarly to familiar intelligence functions in government. Some organisations with regulatory obligations, particularly organisations operating critical infrastructure or other regulated assets, are often required to have intelligence functions, particularly cyber threat intelligence capabilities. Certain information security standards, such as ISO/IEC 27001 and the NIST Cyber Security Framework, also require organisations to ingest threat intelligence to meet the standard. The combination of reducing risk, government compliance, and meeting industry standards all contribute to an increasing appetite for corporations to build intelligence functions.
The question of where intelligence capabilities sit in an organisation has a significant input into the focus of a team. At the domain level, intelligence functions will most often sit alongside the operational elements which are being supported by the intelligence team. Examples include security intelligence analysts being part of corporate investigative functions, cyber threat intelligence teams sitting inside security operations centres, and fraud intelligence teams operating alongside regulatory compliance or operational risk teams. The most common alternative is for intelligence functions to sit within enterprise risk which is suitable where the intelligence required is more strategic or focussed on briefing senior executive audience. Large organisations will often have several thematically-aligned intelligence teams operating in silos with different tooling, skills, expertise, and objectives.
The alternative to intelligence teams aligned to thematic requirements is a converged intelligence team servicing multiple stakeholders. These teams will still generally focus on a single domain such as security but will produce intelligence to meet a range of requirements. They work best as a combination of intelligence generalists and domain experts, with analysts often responsible for supporting specific reporting lines but able to pivot rapidly between target sets. These teams are often staffed by more experienced analysts, ideally by individuals who have worked across multiple target sets prior to joining corporate intelligence functions. The advantage of a centralised, converged intelligence team is the sharing of analytic expertise and tooling across multiple objectives. A challenge can be prioritising work where there are competing requirements and stakeholders.
The teams also scale differently depending on the resourcing devoted to intelligence. Only the largest corporations in Australia have the resources to maintain intelligence teams, with cyber threat intelligence being the most common type of team found in large organisations. More often large and mid-sized corporations will have, at most, one or two intelligence analysts supporting an operational cyber security capability. Where large security intelligence teams do exist, they are most often 2-7 intelligence analysts led by a manager. Personnel also generally fall into two categories: domain specialists who have skills in technical fields, or intelligence specialists with experience in government or the military. A combination of both types of individuals can address the need for coverage of both a comprehensive understanding of intelligence as a discipline and the requirement that members of small teams need elite target and domain knowledge.
Small intelligence capabilities within corporations can be effective due to the limited remit of intelligence teams and because corporate intelligence capabilities generally do not have to maintain their own collection capabilities. Externally focussed intelligence teams, such as cyber threat intelligence teams, rely heavily on software-as-a-service (SaaS) platforms which collect, process, and alert on information gathered from a range of open and closed online sources. Internally focussed intelligence teams generally rely more on internal telemetry which is collected as part of other functions, such as cyber and data loss prevention events, insider threat alerting, or financial records. In practice, both internal and externally-focussed teams use a combination of both to meet their requirements. Some larger intelligence functions do have their own open-source intelligence capabilities, including dark web monitoring and even threat actor engagement. These capabilities can be problematic, particularly from a legal and reputational perspective, so most organisations do not have an appetite to maintain these specialised skills.
This means that corporate intelligence teams, rather than performing the full set of intelligence cycle capabilities, are primarily analysis and production teams. Where collection management does occur, it's tuning partner SaaS tooling to filter intelligence being delivered to the team. Intelligence functions will generally have very limited insights into the proprietary collection sources used by their SaaS intelligence providers and will therefore have limited ability to influence collection posture or evaluate collection source effectiveness. The limited remit of all except converged security intelligence teams also simplifies intelligence management by lessening the burden of the requirement gathering, feedback and evaluation parts of the intelligence cycle. Dissemination is predominantly through existing corporate communication channels such as email, chat, or video presentations. This simplifies communicating intelligence to internal stakeholders. The absence of dedicated intelligence dissemination tools does however place restrictions on the collection of performance metrics related to intelligence production.
Building Intelligence Capabilities
Intelligence teams will often emerge from other corporate security functions. Threat intelligence capabilities can begin as a proactive individual using intelligence methods to support an investigative function or as a response analyst ingesting technical threat indicators into detection platforms. This can then build to a full-time employee working as a dedicated intelligence analyst. Finally, a larger team forms with its own remit and management, most often being led by a team lead or manager with 2-7 analysts working to address a risk or support a mission. This organic emergence of an intelligence capability has the advantage of addressing tested requirements within the organisation and its workflows will be aligned to operational functions. The disadvantage is that the processes are not necessarily built to the standards of a government intelligence function, including the team performing activities that would not be considered intelligence outside of a corporate environment.
The second way that intelligence functions can emerge is by a directed action to add an intelligence capability to a security domain. This can be a common response to a request from a regulator, a desire to meet a security standard, or a proactive uplift by security leadership. Where an intelligence function is added to an organisation without any existing intelligence capability the design of the team is critical, ensuring that it is meeting a need and is not producing intelligence for its own sake. A considered assessment of requirements prior to building any intelligence team is necessary, particularly to gauge whether the scale of the capability required matches the resources being made available by the organisation.
Whether formalising an emergent capability or building a new intelligence team from scratch, the intelligence cycle is a useful guide for how to build an intelligence team. Requirements and stakeholder engagement are central, particularly understanding the organisational need and what they consider intelligence to be. In all cases a new intelligence capability will be driven by a key stakeholder, but demonstrating the ability to service a broad range of requirements and teams will strengthen the case for resources. This is particularly important given that while some security professionals will have a good understanding of intelligence products, they will likely have a limited understanding of intelligence as a process.
The identification of intelligence outputs is the next critical step. Intelligence teams need to produce products that meet stakeholder needs, and these will vary depending on the organisation and the domain. Common products include threat briefings, intelligence reports, situational awareness updates, and threat actor profiles. The format and frequency of these products should be tailored to the audience and their decision-making cycles. Regular feedback mechanisms are essential to ensure products remain relevant and valuable.
Building mature intelligence capabilities requires time, investment, and commitment to best practice intelligence management principles and solid process. Continuous, incremental uplift of immature capabilities needs to focus on regular and structured stakeholder engagement, consistent collection management to ensure only valuable information is reaching analysts, uplifting analyst skill and experience, regularly assessing and introducing new and refined product lines, and, perhaps most challenging, proactively seeking feedback to inform a program of continuous improvement.
Leading Intelligence Capabilities
Large corporations who build intelligence capabilities rarely have security, much less intelligence, as anything other than a critical function to address risk. Instead, these corporations provide financial services, install internet connections, run mines, sell consumer goods, and build infrastructure, as part of a range of other critical elements of our complex market economy. As such, security is something that is taken care of by individuals who are peripheral to the core business, and implementing security controls is sometimes seen as an impost. Within security functions themselves an intelligence capability can be central to their operating model if a function is intelligence-led. It can however also be an afterthought, an additional small offering because senior executives believe that they need to have an intelligence capability even if they're not entirely sure why.
Across both of these scenarios there can be gaps in understanding of what intelligence is. This most frequently manifests itself when specialists or senior executives claim to have intelligence to share that is instead a rumour which has not been evaluated or subjected to any critical assessment. This misunderstanding fails to consider intelligence as both a process which subjects data and information to analysis as well the output of that process itself. There are often also significant gaps in understanding the level of visibility that intelligence teams have, particularly not appreciating that collection resources are finely tuned and can't easily be re-tasked to threats outside of their specialised function. It is however important to remember that these challenges are not confined to intelligence in a corporate security setting with teams of exceptionally capable individual contributors and leaders each contributing with their own specialised skills and knowledge. As an intelligence leader it is critical to bring other security professionals on a journey to build their understanding of intelligence so that they can more effectively engage intelligence teams and understand its capabilities and limitations.
As a capability, intelligence is generally highly regarded in corporate security teams. The work is seen as valuable and sometimes mysterious, and colleagues are enthusiastic about learning more about intelligence and how it works. This translates into security leaders having faith in intelligence analysts as highly capable problem solvers who they often approach with their hardest issues. The challenge for an intelligence leader is that senior leaders will occasionally ask intelligence teams to perform functions which they are not resourced or sufficiently skilled to perform, such as risk assessments, operational tasks, and assessments of threats outside of their area of expertise. This is particularly challenging when also balancing the enthusiasm of analysts whose disposition is to have a go when faced with a challenge. The intelligence leader needs to understand that their capability is limited, and to be willing to push back when analysts are asked to produce intelligence on topics which they don't have expertise or to perform tasks which should be reallocated to other teams. As a leader it's important reject some requests when it exceeds the capability of the team while understanding the strategic importance of leveraging the team to assist with non-intelligence work where it is appropriate.
The skills expected of an intelligence analyst in the corporate setting are broad to the point of potentially being unreasonable. Intelligence analysts are often expected to monitor feeds for situational awareness, perform post-graduate level research, manage security tickets, produce narrative reporting, analyse of technical data, and brief senior stakeholders on complex threats. The profile of corporate intelligence analysts will be familiar to intelligence professionals: enthusiastic individuals with a broad range of skills who have expertise in a domain of knowledge. While the calibre of general skills and domain expertise is generally excellent, corporate intelligence analysts often don't have experience working in intelligence and certainly don not have the same access to training in intelligence as a discipline as analysts working in government.
This presents challenges to leaders of corporate intelligence teams. Staff are often inexperienced, with analysts often filling senior roles in the first five years of their careers. In the cyber threat intelligence discipline, this is impacted by the newness of the field and the challenges of finding cyber talent in Australia. Given the small size of intelligence teams and broader scale of threat intelligence across the country, corporate intelligence analysts most often haven't been exposed to the range of roles or target exposure that an analyst working in an intelligence agency would as part of, for example, an intelligence graduate program or multiple early career postings. Intelligence training available to corporations is also sparse, varied in quality, and universally expensive, and university courses aren't delivering the types of skills required in corporate intelligence functions. There is no appetite to devote the months of training resources that intelligence agencies or the military spend on developing early career intelligence professionals. It therefore falls to intelligence leaders to use their broader experience to develop intelligence analysts on the job through a combination of formal training and on the job mentoring.
Intelligence functions can also struggle to demonstrate the same value to the business during organisational contraction or restructure. As risk led security functions, there are certain services and controls that corporations must maintain to comply with regulations or standards. Intelligence enhances the effectiveness other security functions rather than controlling risk on its own. It may allow detection and response teams across fraud, cyber security, and physical security to optimise their detection methods through an understanding of threats, but ultimately those functions directly manage a core function while intelligence merely supports them. This means that during periods of organisational contraction intelligence functions may be cut first until the capability is too small to be self-sustaining. Intelligence leaders need to understand the place of intelligence in a corporation whose objective is profit and to periodically reshape intelligence capabilities in line with the scale an organisation is willing to support.
The Future of Corporate Intelligence
Intelligence is unquestionably valuable to security leaders in corporations. Large organisations aspire to be intelligence led in line with best practice, and smaller security teams lament the absence of an intelligence capability when struggling to make strategic and operational decisions. The trend globally is to invest in intelligence capability when building a mature security domain, and at this stage there is ample opportunity to innovate when designing intelligence functions. What has been described above is corporate security intelligence as it is, what follows is an outline of what it could be in years to come.
Intelligence functions operate siloed even within organisations, much less between companies, with the primary axis of structure being along functional lines. For example, cyber threat intelligence teams sit alongside cyber security operations teams, security intelligence analysts are embedded in investigative functions, and fraud intelligence teams sit alongside their colleagues managing regulatory compliance and risk. Fundamentally however, these teams are all producing intelligence despite their different domain expertise. The separation of these teams exposes a weakness of scale: corporate security teams will never be large enough to possess the full cycle of intelligence capabilities available to government agencies and forces. They can produce excellent analysis but struggle with requirement setting, collection management, dissemination, quality control of end products, and robust processes for sharing intelligence. At a small scale, converged security intelligence teams can address some of these issues. However, these teams rarely have the size required for full-cycle intelligence management and simply stretch themselves over a wider target set. The challenge then is to maintain the advantage of intelligence capabilities sitting alongside the operational and strategic capabilities they support while being able to draw on shared resources to manage the intelligence capability.
The model which supports these twin objectives is for a centralised security function leading outposted intelligence analysts and teams which service other parts of the business. A centralised function which handles analyst training, initial stakeholder engagement, requirement setting, feedback and evaluation, collection management, intelligence partner relationships, and reporting standards, would bring corporate intelligence capabilities closer to the level available to government. This function would be responsible for the practice of intelligence while the daily operational management of analytic resources would remain with the operational teams. A capability built on this model scales easily, with individual or small teams of analysts able to be deployed throughout an organisation to achieve their mission while being supported by robust intelligence practice. There is even the opportunity for centralised collection capabilities such as an open-source intelligence team servicing the outposted analysts.
This model has an analogy in military and policing contexts. Police forces post intelligence analysts to district commands and specialist squads, with analysts taking their mission tasking from their units while leveraging the shared intelligence management resources and surge capability of a centralised intelligence function. Military deployments operate in a similar manner with deployed intelligence cells made of analysts from different services, corps, and specialisations, as well as capabilities drawn from intelligence agencies. In both cases there is a chain of command leading to both unit commanders and the centralised intelligence capabilities from which the resource is drawn. This model easily translates to large corporations aiming to service a disparate variety of business units with intelligence.
Strategic leadership of a centralised intelligence requirement would likely come under a Chief Intelligence Officer (CINO). The concept of a CINO has emerged recently with the position operating similarly to a Chief Legal Officer, providing strategic advice to C-Suite executives and board on strategic intelligence matters. A centralised intelligence capability with access to the intelligence output of the entire organisation would be uniquely equipped to provide strategic advice to decision makers. Leadership by a senior executive with insights into the concerns of decision makers is the most effective way to ensure that intelligence teams are aligned to corporate objectives. The CINO position hasn't been implemented by any global companies. It is however a model for how intelligence can shape strategic corporate decision making similarly to the way senior intelligence agency heads influence government policy.