Skip to main content

Documented use cases

A need, an integration and its limits

One anonymized requirement for OpenCTI and firewall feeds: constraints, proposed setup and limits.

A stated need and proposed setup, not measured customer results.

Requirement

Documented integration requirement

Regional Network Operator

Telecommunications & Infrastructure

A documented OpenCTI and firewall feed requirement

An anonymized requirement: ingest intelligence into two OpenCTI instances and prepare hourly firewall TXT updates within an approximate 600,000-IP capacity.

Read the requirement and limits
600 000
Approximate client IP capacity
1 h
Requested refresh cycle
2
Planned OpenCTI instances

Evaluation

What to verify in your own evaluation

  1. 01

    Useful additional indicators compared with current sources

  2. 02

    Available source attribution and indicator timestamps

  3. 03

    Successful imports, pagination and handling of incomplete data

  4. 04

    Time spent on integration, maintenance and analyst review

Questions

What does this example establish?

It records one client’s requirement, existing tools and integration constraints. It does not prove a security outcome or a saving.

What does it add to existing tools?

Compare the feed with your internal tools and CERT sources. Overlap alone is not added value: look for useful extra indicators or less integration work.

How should value be measured?

Fix a sample, baseline, period and success criterion first. Then measure useful extra indicators, source dates, import behavior and operational effort.

Evaluate the feed in your tools

Tell us your tool, what your current data lacks and your success criterion. Feeds are included in Pro and Enterprise.