Security Levels

In this sample security_defines.cfg, we specify a set security defines--attentive, cautious, worried, paranoid. Use these together with the '#ifdef <define>' directive to raise or lower your system monitoring security levels.

Adjust security defines to do more resource-intensive things on more powerful computer systems, to run more, and more thorough, security checks on each mission-critical system, and to respond to special security situations--for example, when your systems or network are under attack, or you suspect unusual hacker activity.

///////////////////////////////////////////////////////////////////////////////
//
// security_defines.cfg -- security levels
//
///////////////////////////////////////////////////////////////////////////////

attentive       TRUE    // the lowest security level
                        // (actually, we suppose that 'attentive FALSE'
                        // and every other security #define set to FALSE
                        // signifies the lowest security level);
                        // by default, we are attentive on all systems

cautious                // the second security level
#  if missioncritical | cssys
                TRUE
#  else
                FALSE
#  endif

worried                 // the third security level
#if missioncritical
                TRUE
#else
                FALSE
#endif

paranoid                // the fourth, and highest, security level
                FALSE   // by default, we are not at "red alert" on any
                        // system

#ifdef cautious
#  setdef attentive = TRUE      // or:  #define attentive
#endifdef

#ifdef worried
#  setdef attentive = TRUE
#  setdef cautious = TRUE
#endifdef

#ifdef paranoid
#  setdef attentive = TRUE
#  setdef cautious = TRUE
#  setdef worried = TRUE
#endifdef

///////////////////////////////////////////////////////////////////////////////

For more examples, see Samples.