Abstract: A system and method for assigning a single use real-time privilege are disclosed. A processor validates credentials of a user based on comparing credentials data of the user with pre-stored reference data in response to receiving a request to access a target computer to execute a single process; creates a single use blockchain private key for the single process and generates the passcode in response to a successful validation of the credentials. The processor also writes request data corresponding to the private key and the passcode onto a blockchain. In response to receiving user login data and the passcode to access the target computer, the processor validates passcode by confirming that the passcode matches the request data wrote in the blockchain; and assigns a single use real-time privilege to the user for executing the single process in response to successful validation of both the passcode and the received request.

Abstract: Various methods, apparatuses/systems, and media for implementing a vulnerability management module are provided. A receiver receives a request for dynamically scanning vulnerability of a target computing device based on testable vulnerability criteria extracted from a database. A processor dynamically executes the testable vulnerability criteria from the SCCM based on the received request; creates a static SCCM advertisement with a dynamic pre/post validation check capability based on a result of the dynamically executing the testable vulnerability criteria; reports a success or a failure of the static SCCM advertisement related to the testable vulnerability criteria to indicate whether a vulnerability exists within the target computing device; and automatically remediates the vulnerability when it is determined that the vulnerability exists within the target computing device.

Abstract: Systems and methods for zero-footprint email and browser lifecycle, dependency, and configuration management are disclosed. In one embodiment, in an information processing apparatus comprising at least one computer processor, a method for implementing zero-footprint email and browser lifecycle management may include: (1) launching a restricted sandbox with no dependencies installed; (2) executing an email client or browser session with no dependencies in the restricted sandbox; (3) receiving a request for a dependency from the email client or browser; (4) halting initialization of the request; (5) validating the request; (6) retrieving an approved configuration for the dependency; (7) resuming initialization of the request; and (8) destroying contents of the restricted sandbox when the email client or browser session is complete.

Abstract: Various methods, apparatuses/systems, and media for implementing a vulnerability management module are provided. A receiver receives a request for dynamically scanning vulnerability of a target computing device based on testable vulnerability criteria extracted from a database. A processor dynamically executes the testable vulnerability criteria from the SCCM based on the received request; creates a static SCCM advertisement with a dynamic pre/post validation check capability based on a result of the dynamically executing the testable vulnerability criteria; reports a success or a failure of the static SCCM advertisement related to the testable vulnerability criteria to indicate whether a vulnerability exists within the target computing device; and automatically remediates the vulnerability when it is determined that the vulnerability exists within the target computing device.

Abstract: Systems and methods for authentication using dynamic, machine-readable authentication tokens are disclosed. According to one embodiment, an electronic multifactor authentication token may include a user input device configured to receive a user input, a location sensing device configured to receive a location-based modifier, at least one computer processor configured to generate a one-time passcode based on the user input and the location-based modifier, and an output device configured to output the one-time passcode.

Abstract: Various methods, apparatuses/systems, and media for implementing a vulnerability management module are provided. A receiver receives a request for dynamically scanning vulnerability of a target computing device based on testable vulnerability criteria extracted from a database. A processor dynamically executes the testable vulnerability criteria from the SCCM based on the received request; creates a static SCCM advertisement with a dynamic pre/post validation check capability based on a result of the dynamically executing the testable vulnerability criteria; reports a success or a failure of the static SCCM advertisement related to the testable vulnerability criteria to indicate whether a vulnerability exists within the target computing device; and automatically remediates the vulnerability when it is determined that the vulnerability exists within the target computing device.

Abstract: Systems and methods for maintaining immutable data access logs with privacy are disclosed. In one embodiment, in a cloud provider comprising at least one computer processor, the cloud provider having a plurality of clients, a method for maintaining immutable data access logs with privacy may include: (1) receiving data from a data owner, wherein the data owner is one of the clients; (2) storing the data in cloud storage; (3) executing an action or condition that impacts the data stored in cloud storage; (4) generating a log entry associated with the action or condition; (5) encrypting at least a portion of the log entry with a public key for the data owner; and (6) committing the log entry including the encrypted portion to a distributed ledger so that the committed log entry is immutable and cryptographically verifiable.

Abstract: Systems and methods for zero-footprint email and browser lifecycle, dependency, and configuration management are disclosed. In one embodiment, in an information processing apparatus comprising at least one computer processor, a method for implementing zero-footprint email and browser lifecycle management may include: (1) launching a restricted sandbox with no dependencies installed; (2) executing an email client or browser session with no dependencies in the restricted sandbox; (3) receiving a request for a dependency from the email client or browser; (4) halting initialization of the request; (5) validating the request; (6) retrieving an approved configuration for the dependency; (7) resuming initialization of the request; and (8) destroying contents of the restricted sandbox when the email client or browser session is complete.