US 12,464,024 B2
SaaS security configurations distribution and management
James Mclean, Washington, DC (US); Brian Soby, Carbondale, CO (US); and Harold Byun, Reno, NV (US)
Assigned to AppOmni, Inc., San Francisco, CA (US)
Filed by AppOmni, Inc., San Francisco, CA (US)
Filed on Jun. 14, 2023, as Appl. No. 18/334,888.
Prior Publication US 2024/0422197 A1, Dec. 19, 2024
Int. Cl. H04L 9/40 (2022.01)
CPC H04L 63/20 (2013.01) 20 Claims
OG exemplary drawing
 
1. A system, comprising:
one or more memories; and
one or more processors coupled to the one or more memories and configured to:
provide first software as a service (SaaS) security configurations for a first organization that are applicable to the first organization based at least in part on first attributes of the first organization, wherein the first SaaS security configurations trigger first security actions upon detection of first relevant events;
provide second SaaS security configurations for a second organization that are applicable to the second organization based at least in part on second attributes of the second organization, wherein the second SaaS security configurations trigger second security actions upon detection of second relevant events;
receive a request to publish the second SaaS security configurations;
compare the second SaaS security configurations to the first attributes of the first organization to determine a first portion of the second SaaS security configurations that is applicable to the first organization and a second portion of the second SaaS security configurations that is not applicable to the first organization;
present, at a user interface, the first portion of the second SaaS security configurations that is applicable to the first organization;
omit from presenting at the user interface, the second portion of the second SaaS security configurations that is not applicable to the first organization;
receive, via the user interface, a request to subscribe to a selected second SaaS security configuration for the first organization; and
programmatically customize a placeholder field associated with the selected second SaaS security configuration to a first organization-specific data value.