Abstract: Various methods, apparatuses/systems, and media for automatically protecting sensitive information data entering application logs, events, metrics, traces, or other outputs are disclosed. A processor receives source code associated with an application being developed; parses the source code and identifies variables or fields in the source code that include sensitive information data; applies artificial intelligence or machine learning algorithm to the source code to automatically identify variables that contain the sensitive information data based on the identified variables or fields and annotating accordingly. Each annotation is a hint that data associated with corresponding annotation is confidential and sensitive information that should not be published, logged, or printed.

Abstract: The invention relates to a build validation engine for a software build process. According to an embodiment of the present invention, a computer implemented system a build validation engine further configured to perform the steps comprising: receiving inputs from a software platform, the inputs comprising a build identifier and a mode indicator; initiating, via the build validation engine, validation of a plurality of configuration file categories for a software build; identifying and applying, via the build validation engine, a set of configuration rules, the set of configuration rules associated with each configuration file category and further comprising server class validation, inputs validation, indexes validation and props validation; and determining whether a successful build is achieved and if a successful build is not determined, failing the build and deleting corresponding deployment bundles.

Abstract: The invention relates to a build validation engine for a software build process. According to an embodiment of the present invention, a computer implemented system a build validation engine further configured to perform the steps comprising: receiving inputs from a software platform, the inputs comprising a build identifier and a mode indicator; initiating, via the build validation engine, validation of a plurality of configuration file categories for a software build; identifying and applying, via the build validation engine, a set of configuration rules, the set of configuration rules associated with each configuration file category and further comprising server class validation, inputs validation, indexes validation and props validation; and determining whether a successful build is achieved and if a successful build is not determined, failing the build and deleting corresponding deployment bundles.