Domino offers executing workloads in a tightly controlled environment, such as software package versions, by enforcing sensitive workloads to use only approved environments.
Domino Compute Environments can remain frozen and unmodifiable to guarantee that only specific packages and versions are used for modeling or analysis. Environment Restriction ensures that users can’t use an Environment modified after it has been certified as restricted. Only an admin can mark a revision of an Environment as Restricted.
To enforce that a Domino Project only uses Restricted Environments, mark the Project as Restricted when you create the Project. Once a Restricted is classified as Restricted, it cannot be reverted to unrestricted. This ensures that every action in a Restricted Restricted uses a Restricted Compute Environment at all times.
Learn more about restricted environments.
Software package installation via popular installation tools such as Python pip or R package installation from CRAN can be blocked in restricted environments.
Learn more about preventing ad hoc package installation.