csmstr - Omega Engineering

SECURITY BASICS
CRIMSON USER MANUAL - MODULAR CONTROLLER
access those objects that demand those rights to be present. Rights are divided into System
Rights and User Rights, with the former controlling access to facilities within the Crimson
software, and the latter being available for general use. For example, User Right 1 might be
used within your database to control access to production targets; only users whom you want
to be able to vary such things would then be assigned this right.
ACCESS CONTROL
Objects that are subject to security have an associated access control setting…
This setting allows you to specify whether the item can be accessed by anyone, by any
operator whose identity is known, or by users with specific user rights. The access control
setting also allows you to specify whether a tag can be changed by a program running as a
result of something other than user action. This facility allows you to guarantee that no
background changes occur to sensitive data, even if a programming error attempts to make
such a change.
WRITE LOGGING
Tags also have a write logging property...
This indicates whether changes made to a tag by users or by programs should be logged. This
facility allows you to create an audit trail of changes to your system, thereby simplifying fault
finding and providing quality-control information as to process configuration. Note that care
should be taken when logging changes made by programs, as certain database may log
unmanageable amounts of data in such circumstances.
DEFAULT ACCESS
To speed the configuration process, Crimson also provides the ability to specify default
access and write logging parameters for mapped tags, internal tags and display pages. The
differentiation between mapped and unmapped tags is important in systems where all changes
PAGE 256
http://www.redlion.net/controller