Intelligence Requirements.
An Intelligence Requirement tells Liberty91 which threat topics matter to you, so the platform can prioritise, contextualise, and report on the right things. A financial organization might care about infostealers and exploit kits, while a government entity in the Middle East focuses on regional cyber espionage. You pick the topics, and a dedicated agent learns each one and applies it to every event that comes in.
What is an Intelligence Requirement?
It is a topic of material interest, drawn from the Intelligence Library or created by you. Liberty91 keeps a library of ready-made requirements and uses them in the background to analyse every event. Grounding analysis in these topics is one of the main ways the platform keeps reporting relevant and reduces hallucination.
Standing vs organization-specific requirements
You assign requirements at two levels:
- Standing Intelligence Requirements apply to every organization in your account. Use these when all of your organizations care about the same topic.
- Organization-specific requirements apply only to the organizations you assign them to, so a manufacturing unit and an investment unit can track very different things.
Anything you set as an Intelligence Requirement becomes part of that organization's profile. If there is news about it, it appears in that organization's morning report, and you can attach an alert rule to it.
How Intelligence Requirements learn over time
Each requirement is self-learning. When a new event arrives, Liberty91 first checks it for mentions of assets, threat actors, regions, and topics. If the topic looks relevant, the matching requirement is called in to help assess and contextualise the event. If the event is relevant enough, it is added to that requirement's knowledge base, weighted by a source reliability and data accuracy rating based on the NATO Admiralty scale.
Your private requirement sits on top of the global one. It inherits everything the global agent knows from open sources, then adds the premium reports and documents you bring in yourself. Those private additions stay in your account and never leak into anyone else's.
Worked example: an infostealer report
- A new report about an infostealer is ingested. The orchestrator agent reads it and decides it is relevant to the global "Infostealers" requirement.
- The orchestrator calls that requirement in to assess and contextualise the report.
- The requirement rates the source as usually reliable and the data as probably true (code B2 on the Admiralty scale), then adds the report to its knowledge base at that weight.
- A user with an alert on infostealer reporting receives a contextualised report in their inbox.
- A day later, another user uploads a trusted-group report on a different campaign. Because that report was shared privately, it enriches only that user's private requirement layer, not the global one. Their stakeholders receive an alert in that user's own branding.
Frequently asked questions
What is the difference between a standing and an organization-specific Intelligence Requirement?
A standing requirement applies to every organization in your account. An organization-specific one applies only to the organizations you assign it to.
Can I create my own Intelligence Requirement?
Yes. If the topic is not in the Intelligence Library, create a new requirement and a dedicated agent starts learning it for you.