Tip

Sample security policy for end users, part six



Here is the sixth part of a sample security policy for end users, submitted by searchSecurity member Nap van Zuuren. Give it a read and tell us what you think by rating it at the bottom of the page. And, don't miss the rest of the policy; follow the link below.

XV. Appendix B

Acknowledgment of Receipt for SecureID (Token)

This form is used to acknowledge receipt of SecureID Token.

Procedure
Complete the following steps:
1. Read the Software/Hardware Policy.
2. Sign and date this form in the spaces provided below.
3. Return this page only to the assigned staff (2).
- The return of this page can also be carried out by e-mail after PGP signing of this page.

RSA SecureID (Token no: x )

You are personally responsible for protecting the authentication factors (SecureID (Key Fob Token and Personal Identification Number (PIN)) entrusted to you. Keep your PIN secret and protect your SecurID (Key Fob) against loss and theft. The authentication factors are strictly personal and may never be issued anonymously (e.g. "SysAdmin") or to a group (e.g. "XYZ, Inc. NOC"). If an unauthorized person learns your PIN and obtains your SecurID(Key Fob), this person can assume your identity. Any action this intruder takes is attributed to you in the system's security log. For your own protection and that of the system, always take the following precautions:

    Requires Free Membership to View


- Never reveal your PIN or user password to anyone. Do not write them down.
- If you think someone has learned your PIN, notify the relevant YYY SOC Manager or Security Administrator, who will clear the PIN immediately. At your next login you will have to receive or create a new PIN to use.
- Exercise care not to lose your SecurID (Key Fob) or to allow it to be stolen. If your Key Fob is missing, tell the relevant YYY SOC Manager or Security Administrator immediately. It will be disabled so that it is useless to unauthorized users.
- Do not let anyone access the system under your identity (that is, log in with your PIN and a token code from your SecurID (Key Fob).
- It is essential to 's security that you follow your system's standard logoff procedures. Failure to log off properly can create a route into the system that is completely unprotected.
- Your RSA SecurID (Key Fob) token contains delicate and sophisticated instrumentation. The token casing, LCD and silicon chip will break if abused. Protect your key fob from physical abuse. Do not immerse it in liquids, do not expose it to extreme temperatures, and do not put it under pressure or bend it.

I hereby acknowledge receipt of the above numbered SecureID (Key Fob) Token and its associated PIN, and I acknowledge receipt of the instructions and agree to abide by the rules for use.

Signature: x
Printed Name: x
Date: x
Company: x


This sample policy is continued in Part Seven.


This was first published in December 2001

There are Comments. Add yours.

 
TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.