ISO IEC 17799 2000TRANSLATED INTO PLAIN ENGLISHSection 6: Personnel Security ManagementDETAILED STANDARD |
||
ISO 17799 2000 is now OBSOLETE. See ISO 27002 2013. |
6.1 CONTROL PERSONNEL RECRUITMENT PROCESS |
|
|
Prevent personnel from misusing your information processing facilities. |
|
Protect information processing facilities by reducing risk of human error. |
|
Protect your information processing facilities by reducing the risk of theft. |
|
Protect your information processing facilities by reducing the risk of fraud. |
|
Address information security issues during the recruitment process. |
|
Make sure that your employment contracts include security provisions. |
|
Monitor how well personnel comply with contractual security provisions. |
|
Make sure that all new users of information
processing |
|
Make sure that all new users of information
processing |
|
Make sure that new third party users of
information processing |
6.1.1 INCLUDE SECURITY IN YOUR JOB DESCRIPTIONS |
|
|
Make sure that job descriptions assign the
responsibility |
|
Make sure that job descriptions assign the
responsibility |
|
Make sure that job descriptions assign the
responsibility |
|
Make sure that job descriptions assign the
responsibility |
6.1.2 CHECK THE BACKGROUNDS OF JOB APPLICANTS |
|
|
Verify the backgrounds of people who apply
|
|
Check out the character references provided
|
|
Verify the professional and academic
qualifications |
|
Confirm the personal identity of people
|
|
Perform credit checks for all personnel who
will |
|
Perform periodic credit checks for all
personnel |
|
Verify the backgrounds of all contractors who
will |
|
Verify the backgrounds of all temporary
employees who |
|
Make sure that contracts with personnel
recruitment agencies |
|
Make sure that your contracts with personnel
recruitment agencies |
|
Make sure that new and inexperienced staff,
who have |
|
Make sure that your managers evaluate the
|
|
Make sure that managers review the work of all
staff |
|
Make sure that managers monitor how personal
|
|
Make sure that managers monitor how personal
financial |
|
Make sure that managers monitor how personal
lifestyle |
|
Make sure that your managers monitor how
personal |
|
Make sure that your managers comply with the
legal |
6.1.3 USE CONFIDENTIALITY OR NON‑DISCLOSURE AGREEMENTS |
|
|
Make sure that all new employees sign
confidentiality |
|
Make sure that confidentiality and
non‑disclosure agreements |
6.1.4 USE EMPLOYMENT CONTRACTS TO PROTECT INFORMATION |
|
|
Make sure that
your employment contracts define |
|
Make sure that your employment contracts
specify the actions that you |
|
Make sure that your employment contracts
|
|
Make sure that your employment contracts
clarify |
|
Make sure that employment contracts define
employees’
|
|
Make sure that your employment contracts
define your |
|
Make sure that
your employment contracts make it clear |
|
Make sure that
your employment contracts make it clear |
|
Make sure that
your employment contracts make it clear |
6.2 PROVIDE INFORMATION SECURITY TRAINING |
|
|
Make sure that
your users are aware of |
|
Make sure that
users are capable of |
|
Make sure that you teach users how
|
|
Make sure that
you teach your users how to use |
|
Make sure that
you teach your users how to |
6.2.1 CONTROL YOUR INFORMATION SECURITY TRAINING |
|
|
Teach employees and
other users about your security |
|
Teach
employees and other users about their legal |
|
Teach employees and
other users about your business |
|
Teach employees and other users how to use
your information |
6.3 RESPOND TO INFORMATION SECURITY INCIDENTS |
|
|
Make sure that your organization tries to
minimize |
|
Make sure that people are required to report all security incidents. |
|
Make sure that people know how to report security incidents. |
|
Make sure that people know how to use reporting procedures. |
|
Make sure that people report information security incidents. |
|
Monitor your information security incidents. |
|
Make sure that your organization learns
|
|
Set up an official
disciplinary process that you can use |
6.3.1 REPORT INFORMATION SECURITY INCIDENTS |
|
|
Make sure that security incidents are reported to management. |
|
Develop a formal incident reporting procedure. |
|
Make people aware of your reporting procedure. |
|
Set up a feedback
mechanism to ensure that incident |
|
Make sure that
you use reported incidents to teach people
|
|
Develop a formal incident response procedure. |
6.3.2 REPORT SECURITY THREATS AND WEAKNESSES |
|
|
Make sure that people are required to report
all suspected |
|
Make sure that people report all information security threats. |
|
Make sure that people are required to report
all |
|
Make sure that people report all
|
|
Make sure that
people have been told not to try |
6.3.3 CONTROL YOUR SOFTWARE MALFUNCTIONS |
|
|
Develop a procedure for reporting software malfunctions. |
|
Make sure that your malfunction reporting
procedure expects |
|
Make sure that your software malfunction
reporting procedure |
|
Make sure that your reporting procedure
ensures that the |
|
Develop a procedure for responding to software malfunctions. |
|
Make sure that software malfunction response
procedure |
|
Make sure that your response procedure ensures
that |
|
Make sure that your software malfunction
response procedure |
|
Make sure that your software malfunction
response procedure ensures |
|
Make sure that your malfunction response
procedure ensures that |
6.3.4 LEARN FROM YOUR SECURITY INCIDENTS |
|
|
Develop mechanisms that you can use to learn
|
|
Monitor and quantify the types of security incidents. |
|
Monitor and quantify the costs of security incidents. |
|
Make sure that you can identify recurring security incidents. |
|
Make sure that you can identify high impact security incidents. |
|
Make sure that you use what you learn about
your |
|
Make sure that you use what you learn about
security |
6.3.5 DEVELOP A DISCIPLINARY PROCESS |
|
|
Develop a formal process that you can use
|
|
Make sure that your disciplinary process
ensures |
|
Ensure that your disciplinary process acts as a deterrent. |
Praxiom Research Group Limited help@praxiom.com 780-461-4514 |
|||
Updated on March 27, 2014. First published on October 28, 2004. |
|||
Legal
Restrictions on the Use of this Page
Copyright © 2004 - 2014 by Praxiom Research Group Limited. All Rights Reserved. |