TISC Data Processing Functional Flow

  • Release version: Yokohama
  • Updated January 30, 2025
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of TISC Data Processing Functional Flow

    The Threat Intelligence Security Center (TISC) automates the collection and processing of threat intelligence data to reduce manual effort for Threat Intel Analysts. Data is collected through scheduled ingestion from preconfigured sources, manual imports, or manual record creation within the application. The collected data undergoes normalization, de-duplication, and aggregation before being stored in the Threat Intel library.

    Show full answer Show less

    Key Features

    • Data Collection Methods: Includes automated ingestion from multiple sources, manual data imports by analysts, and manual record creation.
    • Source Tables: Store data from multiple sources, with records created per source entity.
    • Aggregated Records: Consolidate data related to specific entities by combining information from all associated source records.
    • Inbound Filtering: Applies configurable filtering rules to incoming source records to determine if they should be filtered out. Filtered records are marked and tracked with the applied filter rule.
    • De-Duplication Process: Validates incoming source records against existing records for duplication based on entity-specific fields and relationships. Duplicate records are marked accordingly to avoid redundant data.
    • Aggregation: Updates aggregated records by combining field values from multiple source records according to predefined system criteria.

    Practical Use for ServiceNow Customers

    By leveraging TISC’s automated data processing flow, ServiceNow customers can streamline threat intelligence management, ensuring data accuracy and reducing manual workload. The system’s filtering and de-duplication mechanisms maintain data quality, while aggregation provides a consolidated view of threat entities. Customers can expect improved efficiency in managing threat data and enhanced capabilities for threat analysis and response.

    Threat Intelligence Security Center (TISC) provides a solution that automates the data collection and processing which helps reduce the burden on Threat Intel Analysts by avoiding manual steps involved.

    Threat Intelligence Security Center (TISC) collects intelligence using one of the following methods:

    1. Ingestion from data sources that are preconfigured and run on a schedule.
    2. Threat Intel Analysts importing data using the Import Intelligence feature.
    3. Manually creating individual records within the application.
      Note:
      The data collected in the application will be processed to normalize, de-duplicate, and aggregate the information before loading into Threat Intel library.

    Basic terminology used in Data Processing

    1. Source Tables: The Source tables contains the data related to the entities that are fetched from multiple sources, and then the records will be created by each source.
    2. Aggregated Records: The Aggregated records tables contains the data related to a specific entity by aggregating the data from all the source records of a specific entity.

    TISC Data Flow

    1. On a successful execution of import intelligence/Data Source, the records would be created in the corresponding source tables.
    2. Once data comes into source table, the data goes through Filtering logic to validate if the record should be filtered based on configured Inbound Filtering Rules. (Let’s consider SourceRecord1 as a source record for our explanation).
    3. If the record gets filtered by any of the configured Inbound Filtering Rules, the corresponding source record (SourceRecord1) is marked as Filtered and rule which filtered the record can be found in Applied Filter Rule.
    4. Let’s assume the source record (SourceRecord1) aggregates to AggregateRecord1.
    5. If the record is not filtered, the record is marked for de-duplication by setting processing status to Ready for De-Duplication.
    6. De-Duplication logic validates the below:
      1. Whether incoming source record (SourceRecord1) is duplicate of any existing source records for AggregateRecord1.
      2. Any of the existing source records for AggregateRecord1 is a duplicate of incoming source record (SourceRecord1).
    7. Every entity has specific fields and relationships based on which the source record is validated for Duplication.
    8. If incoming source record (SourceRecord1) is a duplicate of any existing source record of AggregateRecord1, the incoming source record (SourceRecord1) is marked as Duplicate.
    9. If any of the existing source record (Existing Source Record1) of AggregateRecord1 is identified as duplicate of incoming source record (SourceRecord1), then existing source record (Existing Source Record1) is marked as Duplicate and incoming source record (SourceRecord1) is marked for aggregation by setting the processing status to Ready for Aggregation.
    10. As part of aggregation, fields of aggregated record AggregateRecord1 will be updated based on values from multiple source records will be aggregated as per the predefined criteria defined in the system.
    Data Processing in TISC