Nucleus Security

Security in the Nucleus Environment

Nucleus can address a wide range of security issues ranging from login and password, command prompt, and application security down to the field level - on a user by user basis. Exceptional levels of granularity and custom controls are possible.

Nucleus provides a Unix like security scheme encompassing both group and individual permissions.

• Account
• Command
• File - Read
• File - Write
• File - Delete
• Verb - Execute permission
• TCL access
• Screen Access
• Every file change, every command and every action can be placed under audit controls.
• Traditional security can be defined for any procedure based on read/write/delete
• Nucleus security can be invoked for any Traditional program

At the Nucleus command line:
All user entered TCL or command line commands are checked prior to pricessing. Only commands that a user has permission to access, are processed.

• Permissions can be specifically granted to a an individual
• Permissions can be specifically granted to a group profile.
• Access permissions can be restricted on a group basis
• Access permissions can be restricted on an individual user basis
• Access to MENU's can be excluded on an individual basis
• Access to MENU's can be granted on an individual basis

From a Nucleus screen:
Inherent in the Nucleus model, all screens developed in Nucleus automatically incorporate security validations based on:

• Group defined permissions
• Group excluded permissions
• User defined permissions
• User excluded permissions

Nucleus security can allow or prevent users (or groups) fron:

• Reading a file
• Writing to a file>
• Deleting records from a file
• Accessing a system

If a user (or group) has been defined to exclude read privileges for a file, a Nucleus screen based on the defined file will not operate for that user (or group of users)

• If the individual does not have file access permission if required, access is denied
• If the individual does not have screen access permission, access is denied

System Security with the Nucleus Environment
Permissions for individual tasks can be easily integrated into existing source code by a simple CALL.
Traditional system security can be implemented WITHOUT using any of the Nucleus 4GL features at runtime.

In addition to the security inherent in the Nucleus environment, there are subroutines that can be CALLED from existing Traditional applications, to incorporate extensive Task Level security features.

Nucleus environmental management includes numerous applications to track the usage of programs, subroutines, and even PROC's.

GROUP security can be incorporated at FILE, VERB, PROGRAM and MENU levels.

An extensive group of operations security tools, enable and/or protect entry to any menu, as well as the selection of any menu option.

Facilities exist to document the use of any PROC, program or MD item in your system. This can help to determine when/OR IF a program is used. Nucleus security is a freestanding product and can be used as a stand-alone security environment for traditional systems.

Documenting program usage:
Nucleus provides a set of ‘toe tagging’ routines, which can be used to analyze the usage of programs in an application environment. These purpose of these ‘toe tags’, is to determine:

• If a program is used
• Who uses it
• How often it may be used
• When was it was last used
• The number of times it was used since 'toe tagging' began
• If a program or proc is still actively used

Many additional security features are available.
Call +1 (954) 791-8575 or toll-free +1 (886) 882-1888 for details.
Extensive documentation is available at our documentation site