Page History

...

Configurations include any deployable objects that are used for job execution with Agents, such as workflows, jobs etc.
Basically the deployment of jobs that include e.g. calls to OS commands, scripts and binaries, to any Agents should be considered a code injection to a remote machine that requires authentication and authorization.
Therefore a configuration is required to be signed by a responsible person:
- this guarantees that workflows, jobs etc. are authorized for deployment by individuals who are in charge of this task.
- this guarantees non-reputability of deployments.
JOC Cockpit offers different security levels for deployment tasks.

Secure Deployment

To deploy configuration objects includes to transfer e.g. workflows and jobs to a Master in a given environment.
This step can be simplified for e.g. development environments when frequent changes occur to configuration objects and deployments are performed with a single mouse click.
This step can be more complex if a sharing of responsibilities is included, e.g. to roll-out configuration objects from a development environment to a test or production environment. This situation is called a roll-out and is explained with the subsequent chapter.
A secure deployment is adjusted to security requirements in a given environment. Therefore the JOC Cockpit can be operated in different Security Levels.
- Security Levels "low" and "medium" allow simplified deployment and are suitable for environments with modest security requirements.
- Security Level "high" takes more effort and is targeted towards organisations with more elaborate security requirements.
Security Levels are put in place during installation of JOC Cockpit. Each instance of JOC Cockpit can be operated in one of the Security Levels only. There is no fallback from a Security Level "high" to a "medium" or "low" security level. Changing the Security Level requires to reinstall JOC Cockpit.

...