Patent No. US11418393 (titled "Remediation Of Detected Configuration Violations") was filed by Appomni Inc on Jul 26, 2021.
’393 is related to the field of cybersecurity, specifically the automated remediation of configuration violations in cloud-based services. Modern enterprises rely on numerous SaaS platforms, each with its own security settings. Manually managing these settings across different platforms is complex and error-prone, leading to potential security breaches and compliance issues. The patent addresses the problem of efficiently identifying and resolving these configuration discrepancies.
The underlying idea behind ’393 is to automate the process of detecting and fixing configuration violations by comparing actual settings against prescribed settings defined in an organization's internal reference information. This involves querying data source servers for their current configurations, comparing them to desired configurations (policies, best practices, etc.), and then automatically or manually applying remediations to correct any discrepancies. The system also maintains an audit log to track all actions taken.
The claims of ’393 focus on a system, method, and computer program product for detecting and remediating configuration violations at a data source server. The core process involves receiving an indication to perform an audit against a policy, obtaining stored mappings, querying the data source server for configured security attributes , obtaining prescribed security attributes , comparing these attributes based on policy type and role group, determining if a violation exists based on the comparison, providing a remediation, and storing an audit log of the remediation events.
In practice, the system operates by first defining policies that specify the desired security configurations for various elements within a SaaS platform. When a violation is detected, the system can automatically generate API commands to correct the misconfiguration, or it can generate a manual remediation plan for a security administrator to implement. The choice between automatic and manual remediation can be based on the severity of the violation or the availability of an API for automated correction. The audit log provides a record of all actions taken, ensuring accountability and facilitating compliance reporting.
The invention differentiates itself from prior approaches by providing a centralized system for managing security configurations across multiple SaaS platforms. Unlike manual processes that are time-consuming and prone to error, this system automates the detection and remediation of violations, reducing the risk of security breaches and improving compliance posture. The use of internal reference information allows organizations to customize the system to their specific security policies and best practices, making it a flexible and adaptable solution.
In the early 2020s when ’393 was filed, systems commonly relied on centralized security information and event management (SIEM) platforms to aggregate and analyze security alerts. At a time when security automation was gaining traction, security administrators typically relied on manual processes to triage and remediate detected security violations. When hardware or software constraints made real-time analysis and automated remediation non-trivial, security teams often struggled to manage the high volume of alerts generated by security systems.
The examiner approved the application because the prior art of record did not teach or suggest the specific combination of steps for detecting a violation associated with a configuration at a data source server. This combination includes receiving an indication to perform an audit with respect to a policy, obtaining stored mappings corresponding to the policy, querying the data source server for configured security attributes of elements associated with the data source server with respect to a role group of the policy using the stored mappings, obtaining prescribed security attributes corresponding to the stored mappings, comparing the configured security attributes and the prescribed security attributes corresponding to the stored mappings based at least in part on a policy type and the role group of the policy, and determining that the violation exists based at least in part on the comparison between the configured security attributes and the prescribed security attributes, in light of other features described in independent claims 1, 12 and 20.
This patent includes 18 claims, with claims 1, 11, and 18 being independent. The independent claims are directed to a system, a method, and a computer program product, respectively, all generally focused on detecting and remediating violations associated with configurations at a data source server. The dependent claims generally elaborate on the specifics of violation detection, remediation processes (both automatic and manual), and severity determination.
Definitions of key terms used in the patent claims.

The dossier documents provide a comprehensive record of the patent's prosecution history - including filings, correspondence, and decisions made by patent offices - and are crucial for understanding the patent's legal journey and any challenges it may have faced during examination.
Date
Description
Get instant alerts for new documents