Abstract: In some aspects, the techniques described herein relate to a method including calling, by a first event driven function associated with a spoke account, an inventory interface of the spoke account; writing, by the first event driven function, inventory data received from the inventory interface to a messaging queue, wherein the messaging queue is associated with a hub account; receiving, by a second event driven function, the inventory data from the messaging queue, wherein the second event driven function is associated with the hub account; writing, by the second event driven function, the inventory data to a database, wherein the database is associated with the hub account; executing, by a third event driven function, a query of the database, wherein the query retrieves the inventory data, and wherein the third event driven function is associated with an administrative account; and displaying the inventory data via a front-end application.

Abstract: Various methods, apparatuses/systems, and media for implementing a release automation dashboard module are disclosed. A database that stores a set of Sarbanes-Oxley (SOX) audit rules. A processor is coupled to the database via a communication network. The processor creates a release; checks the release for violations against the set of Sarbanes-Oxley (SOX) audit rules; validates that the release is scanned for cyber vulnerabilities in accordance with an organization's established practices; and authorizes deployment of the release based on a determination that the one or more features from the release does not violate the set of SOX audit rules and that the one or more features from the release meet a predetermined threshold for the cyber vulnerabilities.

Abstract: Various methods, apparatuses/systems, and media for implementing a release automation dashboard module are disclosed. A database that stores a set of Sarbanes-Oxley (SOX) audit rules. A processor is coupled to the database via a communication network. The processor creates a release; checks the release for violations against the set of Sarbanes-Oxley (SOX) audit rules; validates that the release is scanned for cyber vulnerabilities in accordance with an organization's established practices; and authorizes deployment of the release based on a determination that the one or more features from the release does not violate the set of SOX audit rules and that the one or more features from the release meet a predetermined threshold for the cyber vulnerabilities.

Abstract: Various methods, apparatuses/systems, and media for vulnerability feedback mechanism are provided. An application receives data from a build automation tool. This data includes links to source code in a version control system (VCS) and security scans. A processor creates a task and adds the task to an application processing queue. The application retrieves security scan data from security tools. The application retrieves production scan data from the VCS, The processor compares the security scan data with the production scan data; determines, based on comparing, whether the security scan data includes new vulnerability data that is not currently included in the production scan data; and automatically transmits an electronic notification to a code developer device when it is determined that the security scan data includes new vulnerability data and that the task needs resolution.