User Guide Functional Overview Requirements Architecture System Installation NetEye Additional Components Installation Setup The neteye Command Director NetEye Self Monitoring Tornado Business Service Monitoring IT Operation Analytics - Telemetry Geo Maps NagVis Audit Log Shutdown Manager Reporting ntopng Visual Monitoring with Alyvix Elastic Stack IT Operations (Command Orchestrator) Asset Management Service Level Management Cyber Threat Intelligence - SATAYO NetEye.Cloud Strategy Monitoring SOC System Administrator SOC Attacker Centric Cyber Threat Intelligence - SATAYO NetEye Update & Upgrade Backup and Restore How To NetEye Extension Packs Troubleshooting Security Policy Glossary
module icon Cyber Threat Intelligence - SATAYO
About SATAYO Threat Intelligence and Security Operations
NetEye.Cloud Strategy Monitoring SOC System Administrator SOC Attacker Centric Cyber Threat Intelligence - SATAYO Introduction to NetEye Monitoring Business Service Monitoring IT Operation Analytics Visualization Network Visibility Log Management & Security Orchestrated Datacenter Shutdown Application Performance Monitoring User Experience Service Management Service Level Management & Reporting Requirements for a Node Cluster Requirements and Best Practices NetEye Satellite Requirements TCP and UDP Ports Requirements Additional Software Installation Introduction Single Node Cluster NetEye Master Master-Satellite Architecture Underlying Operating System Acquiring NetEye ISO Image Installing ISO Image Single Nodes and Satellites Cluster Nodes Configuration of Tenants Satellite Nodes Only Nodes behind a Proxy Additional NetEye Components Single Node Cluster Node Satellites Nodes only Verify if a module is running correctly Accessing the New Module Cluster Satellite Security Backup and Restore Identity and Access Management External Identity Providers Configure federated LDAP/AD Emergency Reset of Keycloak Configuration Advanced Configuration Roles Single Page Application in NetEye Module Permissions and Single Sign On Within NetEye Importing User Federation Groups inside another Group Importing OIDC IdP Groups inside another Group Resources Tuning Advanced Topics Basic Concepts & Usage Advanced Topics Monitoring Environment Templates Monitored Objects Import Monitored Objects Data Fields Deployment Icinga 2 Agents Configuration Baskets Dashboard Monitoring Status Icinga2 Features VMD Permissions Notifications Jobs API Configuring Icinga Monitoring Retention Policy NetEye Self Monitoring Concepts Collecting Events Add a Filter Node WHERE Conditions Iterating over Event fields Retrieving Payload of an Event Extract Variables Create a Rule Tornado Actions Test your Configuration Export and Import Configuration Example Under the hood Development Retry Strategy Configuration Thread Pool Configuration API Reference Configure a new Business Process Create your first Business Process Node Importing Processes Operators The ITOA Module Configuring User Permissions Telegraf Metrics in NetEye Telegraf Configuration Telegraf on Monitored Hosts Visualizing Dashboards Customizing Grafana The NetEye Geo Map Visualizer Map Viewer Configuring Geo Maps NagVis Audit Log Overview Shutdown Manager user Shutdown Manager GUI Shutdown Commands Advanced Topics Overview User Role Management Cube Use Cases ntopng and NetEye Integration Permissions Retention Advanced Topics Overview User Roles Nodes RDP Client Building Tools Editor: Interface Overview Editor: Script Building Editor: Managing Scripts Designer: Interface Overview Designer: Interface Options Designer: Component Tree Selector: Interface Overview Test Case Management Dashboard Use Cases Overview Architecture Authorization Kibana Elasticsearch Cluster Elasticsearch Configuration Replicas on a Single Node Elasticsearch Performance tuning Overview Enabling El Proxy Sending custom logs to El Proxy Configuration files Commands Elasticsearch Templates and Retentions El Proxy DLQ Blockchain Verification Handling Blockchain Corruptions El Proxy Metrics El Proxy Security El Proxy REST Endpoints Agents Logstash Elastic APM Elastic RUM Elastic XDR Log Manager - Deprecated Overview Authorization in the Command Orchestrator Module Configuring CLI Commands Executing Commands Overview Permissions Installation Single Tenancy Multitenancy Communication through a Satellite Asset collection methods Display asset information in monitoring host page Overview Customers Availability Event Adjustment Outages Resource Advanced Topics Introduction The Intelligence We Produce Mitre Attack Coverage Getting Started Settings SATAYO Items Intelligence Requirements Managed Service Request Form FAQ Changelog SATAYO Community NetEye.Cloud as a SaaS solution Accessing NetEye.Cloud Monitoring with NetEye.Cloud Monitoring Environment Business Service Monitoring VMD SOC System Administrator (AdS) Access to NetEye and Elastic Elastic Dashboards Elastic Discover Elastic Alerts Elastic Rules Introduction to SOC Attacker Centric Service Description NetEye SIEM About SATAYO Threat Intelligence and Security Operations Before you start Update Procedure Single Node Upgrade from 4.46 to 4.47 Cluster Upgrade from 4.46 to 4.47 Satellite Upgrade from 4.46 to 4.47 DPO machine Upgrade from 4.46 to 4.47 Create a mirror of the RPM repository Sprint Releases Feature Troubleshooting Backup and Restore Tornado Networking Service Management - Incident Response IT Operation Analytics - Telemetry Identity Provider (IdP) Configuration NetEye Cluster on Microsoft Azure Introduction to NEP Getting Started with NEPs Online Resources Obtaining NEP Insights Available Packages Advanced Topics Upgrade to NetEye 4.31 Setup Configure swappiness Restarting Stopped Services Enable stack traces in web UI How to access standard logs Director does not deploy when services assigned to a host have the same name How to enable/disable debug logging Activate Debug Logging for Tornado Modules/Services do not start Sync Rule fails when trying to recreate Icinga object How to disable InfluxDB query logging Managing an Elasticsearch Cluster with a Full Disk Some logs are not indexed in Elasticsearch Elasticsearch is not functioning properly Reporting: Error when opening a report Debugging Logstash file input filter Bugfix Policy Reporting Vulnerabilities Glossary

Threat Intelligence and Security Operations

Effective Security Operations rely on the ability to transform large volumes of external information into timely, relevant, and actionable intelligence. To achieve this, the company has built a consistent and repeatable process that integrates Threat Intelligence into daily security operations.

This operational approach directly supports the capabilities described in About SATAYO and complements the External Visibility with SATAYO model by ensuring that externally observed threats, exposures, and adversary activity are continuously analyzed and translated into consumable intelligence.

Threat Intelligence Lifecycle as a Foundation

The Threat Intelligence Lifecycle defines a sequence of phases that guide the production and operational use of intelligence. These phases are tightly connected and form a continuous loop, ensuring that intelligence remains aligned with evolving threats and organizational priorities.

The lifecycle phases adopted by the company include:

  • Planning

  • Collection

  • Processing

  • Analysis

  • Dissemination

  • Feedback

Each phase plays a critical role in ensuring that Threat Intelligence supports decision-making and operational readiness.

Planning Phase: Priority Intelligence Requirements

The journey begins with the Planning phase, during which Priority Intelligence Requirements (PIRs) are defined.

A Priority Intelligence Requirement (PIR) is a specific, high-level question or information need that guides the collection, analysis, and dissemination activities of a Threat Intelligence program. PIRs represent the most important intelligence priorities for the organization, directly supporting risk management, operational decisions, and strategic awareness.

PIRs are not static. They are periodically reviewed and updated to reflect changes in the threat landscape, business priorities, technologies, and organizational perimeter.

Collection Phase: Intelligence Sources

Once PIRs have been defined, the process continues with the Collection phase. During this phase, information relevant to the identified intelligence requirements is gathered from multiple sources.

These sources may include, but are not limited to:

  • Open-source intelligence

  • Technical telemetry

  • Dark web and underground sources

  • Human-driven intelligence gathering

The collected information constitutes the raw input used in subsequent phases of the Threat Intelligence Lifecycle.

Processing Phase: From Raw Data to Usable Information

The primary goal of the Processing phase is to transform raw data into a usable, standardized, and accessible format suitable for analysis.

Raw data often arrives in heterogeneous formats and with varying levels of reliability. Examples include logs, indicators of compromise (IoCs), malware samples, dark web posts, and social media content. During the Processing phase, this data is:

  • Cleaned, by removing noise and duplicates

  • Normalized, by converting it into a consistent schema

  • Enriched, by correlating it with contextual information and metadata

  • Stored, by indexing it and making it searchable for analysts and automated systems

This phase ensures that analysts and automated tools operate on consistent and reliable datasets.

Analysis Phase: Producing Intelligence

During the Analysis phase, processed information is evaluated and contextualized to produce intelligence that directly addresses the defined PIRs.

Analysis may be performed by human analysts or, for repetitive or well-structured cases, by AI-based systems. The objective is to move beyond raw data and produce insights that explain what is happening, why it matters, and what the potential impact is.

Within its daily operations, the Threat Intelligence team produces multiple types of intelligence, including:

  • Attack Surface Intelligence Continuous discovery and monitoring of exposed assets such as domains, IP addresses, applications, and cloud services to identify vulnerabilities and potential entry points.

  • Technologies Intelligence Analysis of technologies used across the organization or its sector to assess exposure, detect outdated systems, and anticipate threats targeting specific software stacks or services.

  • Dark Web Forum Intelligence Monitoring underground forums and marketplaces to identify emerging threats, leaked data, or threat actor activity targeting the organization or its industry.

  • Brand Intelligence Detection of brand misuse such as phishing domains, fake websites, fraudulent social media profiles, or logo abuse.

  • Supply Chain Intelligence Assessment of cyber risks related to third-party vendors and partners that could indirectly impact the organization.

  • Threat Actor Intelligence Profiling and tracking threat actors, including their motivations, capabilities, infrastructure, and tactics.

  • Vulnerabilities Intelligence Identification and prioritization of vulnerabilities by correlating technical data with real-world exploitation trends.

  • Virtual HUMINT Intelligence Human-driven intelligence collection in digital environments such as closed forums or chat groups to gain insight into threat actors’ intentions and plans.

Dissemination Phase: Making Intelligence Actionable

After analysis, intelligence enters the Dissemination phase. The company focuses on distributing intelligence in formats that are both consumable and operationally actionable.

A significant portion of intelligence is disseminated through structured tickets that provide detailed analysis and supporting evidence. These tickets may include indicators of compromise or attack, such as IP addresses, domains, URLs, hashes, hostnames, or email accounts.

Indicators are made available through multiple channels:

  • In raw format, enabling direct consumption by security controls. For example, IP indicators can be ingested by firewall devices to automatically enforce blocking rules.

  • In enriched and correlated format, through platforms such as MISP. This enables integration with SIEM systems and supports continuous threat hunting activities.

Concrete operational actions enabled by dissemination include automated blocking, credential resets following data breaches, and continuous detection of indicator-related events in monitored environments.

Feedback Phase: Continuous Improvement

The Feedback phase is a critical but often overlooked part of the Threat Intelligence Lifecycle. It ensures that intelligence production remains aligned with real operational needs and delivers measurable value.

For the company, this phase includes structured, bimonthly meetings with clients. During these sessions:

  • PIRs are reviewed and refined

  • The client’s threat landscape is discussed

  • The monitored organizational perimeter is validated and updated

This is particularly important in environments where organizational boundaries change frequently due to acquisitions or the adoption of new technologies.

Supporting Integration Through RFI

To further support the integration of Threat Intelligence into Security Operations, the company provides a Request for Information (RFI) module.

The RFI module enables different teams to submit structured analysis requests on specific topics to the Threat Intelligence team. This mechanism promotes cross-team collaboration, builds trust, and reinforces the role of Threat Intelligence as a practical and valuable component of daily security operations.