Authentication System Attack Detection with Dynamic User Baselines

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional techniques for detecting cyberattacks in software service authentication systems fail to identify attacks using a low number of requests, leading to false positives and inadequate security, particularly in environments using the Kerberos authentication protocol.

Innovation Solution

A cyberattack detection system that monitors user activity patterns to identify anomalies by comparing current software service requests with a user's historical access pattern, using a user activity profile to distinguish between legitimate and malicious activity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional attack detection techniques are used, then the system can detect attacks with high request numbers, but it fails to identify attacks using low request numbers, leading to false positives and inadequate security

Engineering Contradiction:
Improveattack detection accuracyVSAvoidanomaly detection precision
Core Design Contradiction:
ReliabilityVSMeasurement precision

Solution Approach 1:

The patent transforms the detection approach by changing from fixed threshold parameters to dynamic baseline parameters. Instead of using static request count thresholds, the system establishes user-specific baseline patterns through monitoring normal activity over time, then detects anomalies by comparing current activity against these personalized baselines. This parameter transformation enables accurate detection of both high-volume and low-volume attacks without false positives.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The system performs preliminary monitoring and baseline establishment before actual attack detection begins. By collecting and analyzing normal user activity patterns during an initial period, the system prepares user-specific profiles that serve as reference points for future anomaly detection. This preliminary action ensures that when attacks occur, the system already has accurate expectations of normal behavior for comparison.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If the system monitors all user activity in detail, then it can detect low-request attacks, but this increases computational complexity and processing overhead

Engineering Contradiction:
Improvedetection coverageVSAvoidmonitoring system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts only the essential characteristics needed for anomaly detection from complete user activity data. Instead of analyzing every single request in detail, the system identifies and monitors key parameters such as request frequency, targeted resources, and temporal patterns. This extraction approach maintains comprehensive detection coverage while significantly reducing computational complexity by focusing only on the most discriminating features.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The monitoring system is segmented into distinct functional components: data collection, baseline establishment, anomaly detection, and response generation. Each component handles specific tasks independently, allowing the system to process user activity efficiently without requiring complex centralized analysis. This segmentation reduces overall system complexity while maintaining comprehensive monitoring capabilities.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12413606B2Techniques for detecting cyberattacks on an authentication system
Publication Date: 2025.09.09 RAPID7 INC
  • US12413606B2 patent drawing
  • US12413606B2 patent drawing
  • US12413606B2 patent drawing

AI summary

Some embodiments provide techniques for detecting cyberattacks against a software service authentication system that authorizes access to software services. The techniques access a user activity profile specifying values of parameters indicating the user's pattern of requesting access to unique software service(s). The techniques monitor the activity of the user over a time period to obtain software request data indicating request(s) by the user to access software services in the time period. The techniques determine, using the software service request data and the user activity profile, whether computing activity of the user during the time period is anomalous.