Method and system for synchronously generated security waiver interface
Abstract
A method and system of rendering security events in execution of a software application in a communication network. The method comprises receiving, at a memory of a server computing device, a waiver parameter specification identifying a waiver parameter in association with a recipient client device, the waiver parameter pertaining to a security violation event in accordance with a set of predetermined security policy violations, monitoring, via a processor of the server computing device, for the waiver parameter being generated, and generating, based on the monitoring, a waiver notification interface providing capability for including at least a set of successful pipeline execution results as evidence that the security violation event has been resolved.
Claims
exact text as granted — not AI-modifiedWhat is claimed is:
1 . A method of rendering a security event in execution of a software application in a server computing device communicatively coupled to a plurality of client computing devices, the method comprising:
receiving, at a memory of the server computing device, a waiver parameter specification identifying at least one waiver parameter in association with at least one recipient client device of the plurality of client computing devices, the at least one waiver parameter pertaining to a security violation event in accordance with a set of predetermined security policy violations; monitoring, via a processor of the server computing device, for the at least one waiver parameter being generated in accordance with the with the security violation event; and generating, based on the monitoring, a waiver notification interface providing capability for including at least a set of successful pipeline execution results as evidence that the security violation event has been resolved.
2 . The method of claim 1 further comprising transmitting the waiver notification interface to the at least one recipient client device.
3 . The method of claim 2 wherein the waiver notification interface renders, via the at least one recipient client device, an option to create a new waiver in relation to the set of predetermined security policy violations.
4 . The method of claim 3 wherein the new waiver relates to an anticipated security policy violation.
5 . The method of claim 3 wherein the waiver notification interface is configured to render at least one of: the new waiver, a modification to the waiver parameter, and an acknowledgement action pertaining to enactment of the new waiver.
6 . The method of claim 1 wherein the waiver notification interface is generated upon the waiver parameter exceeding a threshold waiver parameter value.
7 . The method of claim 6 wherein the threshold waiver parameter value is specified in the waiver parameter specification.
8 . The method of claim 6 wherein the threshold waiver parameter value is based at least in part upon a variance from a prior waiver parameter in a prior execution of the software application.
9 . The method of claim 6 wherein the threshold waiver parameter value is based at least in part upon a security performance indicator (security KPI) value.
10 . The method of claim 1 wherein the monitoring comprises at least one application program interface (API) call to the software application during the execution.
11 . A server computing device coupled to a plurality of client computing devices in a communication network, the server computing device comprising:
a processor; a memory storing a set of instructions, the instructions when executed in the processor, causing the processor to implement operations comprising:
receiving, at a memory of the server computing device, a waiver parameter specification identifying at least one waiver parameter in association with at least one recipient client device of the plurality of client computing devices, the at least one waiver parameter pertaining to a security violation event in accordance with a set of predetermined security policy violations;
monitoring, via a processor of the server computing device, for the at least one waiver parameter being generated in accordance with the with the security violation event; and
generating, based on the monitoring, a waiver notification interface providing capability for including at least a set of successful pipeline execution results as evidence that the security violation event has been resolved.
12 . The server computing device of claim 11 further comprising transmitting the waiver notification interface to the at least one recipient client device.
13 . The server computing device of claim 12 wherein the waiver notification interface renders, via the at least one recipient client device, an option to create a new waiver in relation to the set of predetermined security policy violations.
14 . The server computing device of claim 13 wherein the new waiver relates to an anticipated security policy violation.
15 . The server computing device of claim 13 wherein the waiver notification interface is configured to render at least one of: the new waiver, a modification to the waiver parameter, and an acknowledgement action pertaining to enactment of the new waiver.
16 . The server computing device of claim 11 wherein the waiver notification interface is generated upon the waiver parameter exceeding a threshold waiver parameter value.
17 . The server computing device of claim 16 wherein the threshold waiver parameter value is specified in the waiver parameter specification.
18 . The server computing device of claim 16 wherein the threshold waiver parameter value is based at least in part upon a variance from a prior waiver parameter in a prior execution of the software application.
19 . The server computing device of claim 16 wherein the threshold waiver parameter value is based at least in part upon a security performance indicator (security KPI) value.
20 . The server computing device of claim 11 wherein the monitoring comprises at least one application program interface (API) call to the software application during the execution.Cited by (0)
No later patents cite this yet.
References (0)
No backward citations on record.