Establishing and maintaining security - Revision history

Admin: link repair

2017-07-25T23:04:07Z

link repair

← Older revision		Revision as of 23:04, 25 July 2017
Line 164:		Line 164:
	===Adding and removing security from files===		===Adding and removing security from files===
	<p>		<p>
	To secure a file, issue the <var>[[SECURE ~~FILE~~ command\|SECURE ~~FILE~~]]</var> command, which ensures that a user cannot access a file illegally by running a <var class="product">Model 204</var> program with its own password table.</p>		To secure a file, issue the <var>[[SECURE command: File\|SECURE]]</var> command, which ensures that a user cannot access a file illegally by running a <var class="product">Model 204</var> program with its own password table.</p>
	<p>		<p>
	A special field in the password table serves as the key for securing files. When a secured file is opened, the key is compared with a copy placed in the file by the <var>SECURE</var> command. The file is accessed only if the two passwords match. The comparison with the key is performed even when the file is opened as part of a group.</p>		A special field in the password table serves as the key for securing files. When a secured file is opened, the key is compared with a copy placed in the file by the <var>SECURE</var> command. The file is accessed only if the two passwords match. The comparison with the key is performed even when the file is opened as part of a group.</p>

JAL: link repair

2017-04-07T21:37:24Z

link repair

← Older revision		Revision as of 21:37, 7 April 2017
Line 171:		Line 171:
	<p>		<p>
	For additional information about		For additional information about
	the <var>SECURE</var> and <var>DESECURE</var> commands, see [[~~Security~~#SECURE command, definition format\|SECURE command, definition format]].		the <var>SECURE</var> and <var>DESECURE</var> commands, see [[Model 204 security features#SECURE command, definition format\|SECURE command, definition format]].
	</p>		</p>
	<p>		<p>
Line 249:		Line 249:

	<li>To initiate record security, set the <var>OPENCTL</var> parameter in the <var>CREATE</var> command for the file and describe the special record security field in the <var>INITIALIZE</var> command.		<li>To initiate record security, set the <var>OPENCTL</var> parameter in the <var>CREATE</var> command for the file and describe the special record security field in the <var>INITIALIZE</var> command.
	For more information about these commands, see [[~~Security~~#Creating files with file security\|Creating files with file security]] and [[Initializing files#Initializing a record security file\|Initializing a record security file]].		For more information about these commands, see [[Model 204 security features#Creating files with file security\|Creating files with file security]] and [[Initializing files#Initializing a record security file\|Initializing a record security file]].
	</li>		</li>

Line 274:		Line 274:
	<p>		<p>
	The way access levels are determined for files that are also members of groups is summarized in		The way access levels are determined for files that are also members of groups is summarized in
	[[~~Security~~#Determining user access levels\|Determining user access levels]]. </p>		[[Model 204 security features#Determining user access levels\|Determining user access levels]]. </p>

	===Field access types===		===Field access types===
Line 335:		Line 335:
	<li>Certain privileges (such as <var>SECURE</var> and <var>DESECURE</var>) associated with file and group passwords indicate the user privileges that pertain to the procedures for that file or group.</li>		<li>Certain privileges (such as <var>SECURE</var> and <var>DESECURE</var>) associated with file and group passwords indicate the user privileges that pertain to the procedures for that file or group.</li>

	<li>To assign user class and procedure class mappings (see [[~~Security~~#Procedure security\|Procedure security]]) to file and group passwords, use the <var>LOGCTL</var> command to add the mappings to the password table.		<li>To assign user class and procedure class mappings (see [[Model 204 security features#Procedure security\|Procedure security]]) to file and group passwords, use the <var>LOGCTL</var> command to add the mappings to the password table.
	<p>		<p>
	Use <var>LOGCTL</var> to add, delete, or change the user class for procedures defined for a file or group. </p></li>		Use <var>LOGCTL</var> to add, delete, or change the user class for procedures defined for a file or group. </p></li>

JAL: pdf now converted to wiki

2015-01-29T16:20:15Z

pdf now converted to wiki

← Older revision		Revision as of 16:20, 29 January 2015
Line 8:		Line 8:
	explains how to maintain the CCASTAT data set, which contains a password table of encrypted user and file security information. </p>		explains how to maintain the CCASTAT data set, which contains a password table of encrypted user and file security information. </p>
	<p>		<p>
	For information about <var class="product">Model 204</var> and standard commercial security interfaces, refer to ~~the <var class="book">Rocket Model 204~~ Security ~~Interfaces Manual</var>~~. </p>		For information about <var class="product">Model 204</var> and standard commercial security interfaces, refer to [[:Category:Security interfaces\|Security interfaces]]. </p>

	==File security==		==File security==
	<p>		<p>

JALWiccan: Automatically generated page update

2014-11-06T17:08:11Z

Automatically generated page update

← Older revision		Revision as of 17:08, 6 November 2014
Line 379:		Line 379:
	</ul>		</ul>

	[[Category:System ~~Manager~~]]		[[Category:System management]]
	[[Category:Security management]]		[[Category:Security management]]

JALWiccan: Automatically generated page update

2014-11-05T17:23:45Z

Automatically generated page update

← Older revision		Revision as of 17:23, 5 November 2014
Line 380:		Line 380:

	[[Category:System Manager]]		[[Category:System Manager]]
	[[Category:~~Managing security~~]]		[[Category:Security management]]

JAL at 21:03, 29 October 2014

2014-10-29T21:03:34Z

← Older revision		Revision as of 21:03, 29 October 2014
Line 380:		Line 380:

	[[Category:System Manager]]		[[Category:System Manager]]
			[[Category:Managing security]]

JAL at 22:09, 20 October 2014

2014-10-20T22:09:32Z

← Older revision		Revision as of 22:09, 20 October 2014
Line 48:		Line 48:
	<tr>		<tr>
	<td>X'8000'</td>		<td>X'8000'</td>
	<td>Use privileged commands such as INITIALIZE, SECURE, and DESECURE. The user can also reset file parameters if ad hoc update privileges (X `2000') are obtained.</td>		<td>Use privileged commands such as INITIALIZE, SECURE, and DESECURE. The user can also reset file parameters if ad hoc update privileges (X '2000') are obtained.</td>
	</tr>		</tr>

Line 188:		Line 188:
	<tr>		<tr>
	<td>Public</td>		<td>Public</td>
	<td>When a public group is opened, default group privileges are defined on the PRIVDEF parameter in the group definition.</td>		<td>When a public group is opened, default group privileges are defined on the <var>PRIVDEF</var> parameter in the group definition.</td>
	</tr>		</tr>

	<tr>		<tr>
	<td>Semipublic</td>		<td>Semipublic</td>
	<td>When a semipublic group is opened without a password or with an invalid password, default group privileges are defined on the PRIVDEF parameter in the group definition.</td>		<td>When a semipublic group is opened without a password or with an invalid password, default group privileges are defined on the <var>PRIVDEF</var> parameter in the group definition.</td>
	</tr>		</tr>

Line 249:		Line 249:

	<li>To initiate record security, set the <var>OPENCTL</var> parameter in the <var>CREATE</var> command for the file and describe the special record security field in the <var>INITIALIZE</var> command.		<li>To initiate record security, set the <var>OPENCTL</var> parameter in the <var>CREATE</var> command for the file and describe the special record security field in the <var>INITIALIZE</var> command.
	For more information about these commands, see [[Security#Creating files with file security\|Creating files with file security]] and [[Initializing ~~a file~~#Initializing a record security file\|Initializing a record security file]].		For more information about these commands, see [[Security#Creating files with file security\|Creating files with file security]] and [[Initializing files#Initializing a record security file\|Initializing a record security file]].
	</li>		</li>

	<li>Record security can be overridden if the user has been granted the record security override privilege at login time (the X `04' bit must be set) and the user's file password also contains the record security override privilege (X '4000'). </li>		<li>Record security can be overridden if the user has been granted the record security override privilege at login time (the X'04' bit must be set) and the user's file password also contains the record security override privilege (X'4000'). </li>

	<li>Record security can be overridden for a file in a permanent file group if login and group privileges (X '4000') allow it. </li>		<li>Record security can be overridden for a file in a permanent file group if login and group privileges (X '4000') allow it. </li>
Line 261:		Line 261:
	The field-level security feature (FLS) controls access to the individual fields of a <var class="product">Model 204</var> file, if access to a record is allowed by previous file-level and record-level security checks. </p>		The field-level security feature (FLS) controls access to the individual fields of a <var class="product">Model 204</var> file, if access to a record is allowed by previous file-level and record-level security checks. </p>
	<p>		<p>
	Every field definition (created by the [[Defining fields manually\|DEFINE FIELD command]]) can have a security level from 0 to 255 associated with it.		Every field definition (created by the [[Defining fields manually\|DEFINE FIELD command]]) can have a security level from 0 to 255 associated with it. </p>
	<p>		<p>
	A level of 0 implies no security for the field; 255 implies the highest security. Field access types are described in the following sections.</p>		A level of 0 implies no security for the field; 255 implies the highest security. Field access types are described in the following sections.</p>
Line 372:		Line 372:
	<li>Terminal lists are variable length, allowing you to add terminals even if you exceed the original number planned for. </li>		<li>Terminal lists are variable length, allowing you to add terminals even if you exceed the original number planned for. </li>

	<li>If you specify ALL for a password table entry, the terminal list takes up no space beyond the basic entry.</li>		<li>If you specify <var>ALL</var> for a password table entry, the terminal list takes up no space beyond the basic entry.</li>

	<li>A list representing NONE takes two bytes.</li>		<li>A list representing <var>NONE</var> takes two bytes.</li>

	<li>To compute the length of a list containing numbers, divide the highest specified number by eight and rounding up to a multiple of two. </li>		<li>To compute the length of a list containing numbers, divide the highest specified number by eight and rounding up to a multiple of two. </li>

JAL: /* Adding and removing security from files */

2014-10-20T21:55:27Z

Adding and removing security from files

← Older revision		Revision as of 21:55, 20 October 2014
Line 166:		Line 166:
	To secure a file, issue the <var>[[SECURE FILE command\|SECURE FILE]]</var> command, which ensures that a user cannot access a file illegally by running a <var class="product">Model 204</var> program with its own password table.</p>		To secure a file, issue the <var>[[SECURE FILE command\|SECURE FILE]]</var> command, which ensures that a user cannot access a file illegally by running a <var class="product">Model 204</var> program with its own password table.</p>
	<p>		<p>
	A special field in the password table serves as the key for securing files. When a secured file is opened, the key is compared with a copy placed in the file by the SECURE command. The file is accessed only if the two passwords match. The comparison with the key is performed even when the file is opened as part of a group.</p>		A special field in the password table serves as the key for securing files. When a secured file is opened, the key is compared with a copy placed in the file by the <var>SECURE</var> command. The file is accessed only if the two passwords match. The comparison with the key is performed even when the file is opened as part of a group.</p>
	<p>		<p>
	To reverse the security placed upon a file by the SECURE command, issue the <var>[[DESECURE command: File\|DESECURE]]</var> command.</p>		To reverse the security placed upon a file by the <var>SECURE</var> command, issue the <var>[[DESECURE command: File\|DESECURE]]</var> command.</p>
	<p>		<p>
	For additional information about		For additional information about
	the SECURE and DESECURE commands, see [[Security#SECURE command, definition format\|SECURE command, definition format]].		the <var>SECURE</var> and <var>DESECURE</var> commands, see [[Security#SECURE command, definition format\|SECURE command, definition format]].
	</p>		</p>
	<p>		<p>
	To change the key in the password table, issue the <var>[[LOGKEY command\|LOGKEY]]</var> command.		To change the key in the password table, issue the <var>[[LOGKEY command\|LOGKEY]]</var> command.
	</p>		</p>

	==Group security==		==Group security==
	<p>		<p>

JAL: /* Using LOGCTL to modify the file password table */

2014-10-20T21:53:58Z

Using LOGCTL to modify the file password table

← Older revision		Revision as of 21:53, 20 October 2014
Line 135:		Line 135:
	<p>		<p>
	The <var>[[LOGCTL command: Modifying file entries in the password table\|LOGCTL]]</var> command allows you to add or delete file entries in the password table. For example, the following command adds a file to the password table:</p>		The <var>[[LOGCTL command: Modifying file entries in the password table\|LOGCTL]]</var> command allows you to add or delete file entries in the password table. For example, the following command adds a file to the password table:</p>
	<p class="code">LOGCTL A :~~file-name~~		<p class="code">LOGCTL A :<i>filename</i>
	</p>		</p>
	<p>		<p>

Admin: 1 revision: converted system mgr pages

2014-10-17T20:27:49Z

1 revision: converted system mgr pages

← Older revision	Revision as of 20:27, 17 October 2014
(No difference)