Abstract: Techniques for scanning a machine learning (ML) model, which is received over a network, are disclosed. Information associated with the ML model is received. A container image is accessed, based on the information associated with the ML model. A software container is loaded using the container image. The ML model is loaded within the container. A plurality of system calls from the ML model within the container is detected. One or more system calls of the plurality of system calls are categorized as suspicious, e.g., based on the one or more system calls being outside a normal or expected behavior of the ML model. Responsive at least in part on categorizing the one or more system calls of the plurality of system calls to be suspicious, the ML model is tagged as possibly being malicious. A result indicative of the ML model being tagged as possibly being malicious is output.

Abstract: Techniques for test orchestration are disclosed. A system executes multiple test execution plans, using instances of a same test container image that encapsulates a test environment and instances of at least two different test support container images that are specified by different user-defined test configurations and each configured to perform, respectively, one or more test support operations. To execute each of the test execution plans, the system generates a respective instance of the test container image and one or more test support containers. A particular test execution plan includes generating a test support container that is specified in a corresponding user-defined test configuration and that is different from any test support container specified in another user-defined test configuration.

Abstract: Techniques for test orchestration are disclosed. A system executes multiple test execution plans, using instances of a same test container image that encapsulates a test environment and instances of at least two different test support container images that are specified by different user-defined test configurations and each configured to perform, respectively, one or more test support operations. To execute each of the test execution plans, the system generates a respective instance of the test container image and one or more test support containers. A particular test execution plan includes generating a test support container that is specified in a corresponding user-defined test configuration and that is different from any test support container specified in another user-defined test configuration.