A system for performing test data management is disclosed. The system includes a data library having one or more databases, the one or more databases undergo a onetime data transfer to a data store, a performing test data management non-transitory storage media residing on the one or more databases, the performing test data management non-transitory storage media includes a means for performing artificial intelligence that resides on the performing test data management non-transitory storage media, a processor system, and a plurality of components and functions residing on the performing test data management non-transitory storage media, the components and functions include a first data transfer function, a data explorer component, a second data transfer function, a data modeler component, a third data transfer function, a data validation component, a fourth data transfer function, a main transfer function, and a data generator component. The system includes a corresponding method as well.

A system and method for scrubbing data to be shared between organizations to test a joint solution, and for preventing the introduction of unscrubbed data. Each organization captures a subset of data, which may be customer data from a line of business. The first organization scrubs its data according to scrubbing rules, and then passes the scrubbed data to its test environment, while the second organization passes its unscrubbed data to its test environment. The scrubbed data is communicated to the second organization and is applied to the unscrubbed data in order to scrub it, and then communicate it to the first organization. Both organizations use the scrubbed data in their respective test environments to test the joint solution or joint testing. Scrubbing the data may involve scrubbing only specific data fields containing sensitive information.

An effective system for verifying safety of an artificial intelligence system includes a feature quantity information accepting unit which accepts feature quantity information that includes values of plural feature quantities, that are assumed as those used in an artificial intelligence system, in each of plural first test data used for a test for verifying safety of the artificial intelligence system; and a judgment unit which judges a first combination, that is a combination that is not included in the plural first test data, in combinations of values that plural feature quantities may take, or a second combination, with it plural correct analysis results that should be derived by the artificial intelligence are associated, in the combinations of the values that the plural feature quantities may take.

A computer security system includes a test management system and associated communication architecture that enables creation of customized tests of computer security application features. A server stores a test script in a custom scripting language. The test script includes a set of control statements that may be organized in a decision tree to control facilitation of the test. Clients poll the server to independently obtain and execute the control statements. Execution of the control statements control which clients participate in a test, which feature will be tested in the test, and what telemetry data will be collected from the clients to evaluate the test. The server evaluates the telemetry data to determine an outcome of the test and determines whether to further distribute or roll back the tested feature based on the test outcome. The testing can be utilized to rapidly and robustly deploy features that will enhance computer security.

A pipeline (e.g., a DevOps or DevSecOps pipeline) may include utilities corresponding to stages within the pipeline. A device may execute the pipeline on a version of a codebase, where the version of the codebase is associated with an immutable identifier of a version control management system. The device may generate metadata for one or more of the utilities of the pipeline based executing the pipeline on the version of the codebase. The device may store the metadata at a database, where the immutable identifier is designated as a primary key for the stored metadata. The device may verify the metadata at one or more gates of the pipeline based on a comparison of the stored metadata to a set of policy information associated with the one or more gates.

An operation management server (20) includes: an associating unit (21) configured to associate an updated content of configuration information of a CMDB (30) with a test scenario corresponding to the updated content; a setting unit (22) configured to set a target system (40) according to the updated content of the configuration information of the CMDB (30); and a test executing unit (23) configured to execute a system test on the set target system (40) based on the test scenario associated with the updated content. This configuration provides an operation management server and a development operation support system capable of easily executing a system test, and a method and a program thereof.

The present disclosure provides a method, system, and device for verifying a software release. To illustrate, as software (e.g., one or more files or artifacts) completes one or more stages of a development process, one or more digital signatures are generated. The one or more digital signatures are generated using private keys that correspond to the stage of the development process that is completed. The one or more digital signatures, and one or more public keys corresponding to the private keys, are sent to a node device. Upon receipt of the one or more digital signatures and the public keys (e.g., as part of a software release), the node device verifies the digital signatures before processing the software.

A system and method for scrubbing data to be shared between organizations to test a joint solution, and for preventing the introduction of unscrubbed data. Each organization captures a subset of data, which may be customer data from a line of business. The first organization scrubs its data according to scrubbing rules, and then passes the scrubbed data to its test environment, while the second organization passes its unscrubbed data to its test environment. The scrubbed data is communicated to the second organization and is applied to the unscrubbed data in order to scrub it, and then communicate it to the first organization. Both organizations use the scrubbed data in their respective test environments to test the joint solution or joint testing. Scrubbing the data may involve scrubbing only specific data fields containing sensitive information.

The present disclosure provides a method, system, and device for verifying a software release. To illustrate, as software (e.g., one or more files or artifacts) completes one or more stages of a development process, one or more digital signatures are generated. The one or more digital signatures are generated using private keys that correspond to the stage of the development process that is completed. The one or more digital signatures, and one or more public keys corresponding to the private keys, are sent to a node device. Upon receipt of the one or more digital signatures and the public keys (e.g., as part of a software release), the node device verifies the digital signatures before processing the software.

In accordance with embodiments, there are provided techniques for managing functionality changes of a database platform of a service provider. The techniques facilitate implementing changes to the database platform while minimizing work flow reductions to users of the database platform. To that end, one embodiment of the present invention delays implementation of the changes for a duration of time to provide users of the database platform an opportunity to adjust behavioral interaction with the database platform. In accordance with another embodiment of the present invention, users may implement the functional changes to determine any adverse impact on work flow, before the functional changes become permanent. In another embodiment, the users may be afforded an opportunity to selectively enable and disable the functionality changes before the duration of time expires.