ISO IEC 17799 2000*TRANSLATED INTO PLAIN ENGLISHSection 9: Access ControlDETAILED STANDARD |
||
|
* ISO
17799 is now OBSOLETE. Also see ISO 27001 2005. |
||
![]()
|
9.1 CONTROL ACCESS TO INFORMATION |
|
|
|
Make sure that your information access |
|
|
Make sure that your information access |
|
|
Make sure that your information access
controls |
|
|
Make sure that your information access
controls |
|
9.1.1 DEVELOP A POLICY AND RULES TO CONTROL ACCESS |
|
|
9.1.1.1 DEVELOP A POLICY TO CONTROL INFORMATION ACCESS |
|
|
|
Define and document the business requirements
|
|
|
Make sure that
your users understand the business |
|
|
Make sure that
your service providers understand the |
|
|
Develop a policy to control information access. |
|
|
Make sure that
your access control policy |
|
|
Make sure that
your access control policy defines the rules |
|
|
Make sure that
access control policy defines the security |
|
|
Make sure that access control policy defines
how information |
|
|
Make sure that
your access control policy complies |
|
|
Make sure that your
access control policy meets all
|
|
|
Make sure that
access control policy allows the use of |
|
|
Make sure that your access control policy
supports |
|
|
Make sure that
your access control policy recognizes |
|
|
Make sure that
your information access control policy |
|
9.1.1.2 DEVELOP INFORMATION ACCESS CONTROL RULES |
|
|
|
Develop rules to control access to information. |
|
|
Make sure that
your access control rules specify |
|
|
Make sure that
access control rules forbid access except |
|
|
Make sure that
access control rules distinguish between |
|
|
Make sure that
access control rules distinguish between |
|
|
Make sure that
you distinguish between user access |
|
9.2 MANAGE THE ALLOCATION OF ACCESS RIGHTS |
|
|
|
Establish a procedure to control the
allocation of |
|
|
Ensure that your access rights allocation
procedure controls |
|
|
Ensure that your access rights allocation procedure pays
|
|
9.2.1 ESTABLISH A USER REGISTRATION PROCEDURE |
|
|
|
Develop a formal procedure to control the
registration |
|
|
Make sure that
your user registration procedure |
|
|
Make sure that
your user registration |
|
|
Make sure that
your user registration procedure ensures that |
|
|
Make sure that
your user registration procedure specifies when |
|
|
Make sure that
your user registration procedure ensures that the |
|
|
Make sure that
your user registration procedure ensures that |
|
|
Make sure that
your user registration procedure ensures that the |
|
|
Make sure that
your user registration procedure ensures that users |
|
|
Make sure that
your registration procedure ensures that all users |
|
|
Make sure that
your user registration procedure ensures that |
|
|
Make sure that
your user registration procedure ensures |
|
|
Make sure that
your user registration procedure ensures |
|
|
Make sure that
your user registration procedure ensures |
|
|
Make sure that
your user registration procedure ensures |
|
|
Make sure that
your employment contracts specify the |
|
|
Make sure that
your service contracts specify the sanctions |
|
9.2.2 CONTROL THE AUTHORIZATION OF SYSTEM PRIVILEGES |
|
|
|
Establish a formal authorization process
that must be used |
|
|
Specify exactly what the special privileges
should |
|
|
Specify which staff members should have which
|
|
|
Grant system privileges only when they are needed. |
|
|
Make sure that your authorization process
ensures that system privileges |
|
|
Maintain a record of all privilege allocations. |
|
|
Reduce the need to grant privileges by
promoting |
|
|
Ensure that the same user identity is not used
to grant |
|
9.2.3 ESTABLISH A PROCESS TO MANAGE PASSWORDS |
|
|
|
Establish a formal process to manage and
control |
|
|
Make sure that your password management
process ensures |
|
|
Make sure that your password management
process ensures that |
|
|
Make sure that your password management
process ensures |
|
|
Make sure that your password management
process ensures |
|
|
Make sure that your password management
process ensures |
|
|
Make sure that your password management
process ensures |
|
|
Store passwords on a secure computer system. |
|
9.2.4 REVIEW USER ACCESS RIGHTS AND PRIVILEGES |
|
|
|
Make sure that managers review user access rights and privileges. |
|
|
Make sure that user access rights are reviewed on a regular basis. |
|
|
Make sure that access rights are reviewed whenever changes occur. |
|
|
Make sure that access privileges are reviewed more often than rights. |
|
|
Make sure that access privileges are reviewed on a regular basis. |
|
|
Make sure that access privileges are reviewed
in order to |
|
9.3 ENCOURAGE RESPONSIBLE ACCESS PRACTICES |
|
|
|
Ask authorized users to help you control
access to |
|
|
Make authorized users responsible for helping
you |
|
|
Make users aware of what they must do to control access. |
|
|
Make users aware of what they must do to protect passwords. |
|
|
Make users aware of what they must do to protect equipment. |
|
9.3.1 ENCOURAGE USERS TO PROTECT PASSWORDS |
|
|
|
Make sure that your users follow best
information |
|
|
Make sure that your users select passwords |
|
|
Make sure that users select passwords |
|
|
Make sure that users select passwords |
|
|
Make sure that users avoid selecting passwords
|
|
|
Make sure that your users follow best
information |
|
|
Make sure that users protect the |
|
|
Make sure that your users ensure that all
written |
|
|
Make sure that
users change passwords whenever the security |
|
|
Make sure that users change passwords on a regular basis. |
|
|
Make sure that users avoid using previously used passwords. |
|
|
Make sure that users change passwords more often for
|
|
|
Make sure that your users change |
|
|
Make sure that your users ensure that
passwords are not |
|
|
Make sure that users avoid sharing passwords with others. |
|
|
Make sure that users are formally authorized
to use a single password |
|
9.3.2 ENCOURAGE USERS TO PROTECT EQUIPMENT |
|
|
|
Make sure that users know how to protect unattended equipment. |
|
|
Make sure that users understand the security
requirements |
|
|
Make sure that users understand the security
procedures |
|
|
Make sure that your users understand what
their |
|
|
Make sure that your users protect their |
|
|
Make sure that your contractors know |
|
|
Make sure that contractors understand |
|
|
Make sure that your contractors understand |
|
|
Make sure that your contractors know what
their |
|
|
Make sure that your contractors protect |
|
|
Make sure that users are told to secure their
equipment or |
|
|
Make sure that users are told to log‑off
mainframe |
|
|
Make sure that users are told to protect
terminals or PCs |
|
|
Make sure that workstations and file servers
are given special |
|
9.4 CONTROL ACCESS TO COMPUTER NETWORKS |
|
|
|
Control access to internal networked services. |
|
|
Control access to external networked services. |
|
|
Control access by using the appropriate
interfaces between |
|
|
Control access by using the appropriate
interfaces |
|
|
Control access to networks by using the appropriate |
|
|
Control user access to information services. |
|
9.4.1 FORMULATE A NETWORK USE POLICY |
|
|
|
Establish a policy to control the use of networks and network services. |
|
|
Make sure that your network use policy ensures
that users are |
|
|
Make sure that your network use policy ensures
that users are |
|
|
Make sure that your network use policy ensures
that users are |
|
|
Make sure that your network use policy
identifies the networks |
|
|
Make sure that your network use policy
establishes procedures that |
|
|
Make sure that your network use policy
establishes management |
|
|
Make sure that your network use policy
establishes management |
|
|
Make sure that your network use policy is
consistent |
|
9.4.2 USE ENFORCED PATHS TO CONTROL ACCESS |
|
|
|
Reduce the opportunity for unauthorized access
to business applications |
|
|
Reduce the opportunity for unauthorized use of
information facilities |
|
|
Establish controls to restrict the route
between user terminals |
|
|
Make sure that your path controls prevent
users from |
|
|
Limit the users routing options by allocating
|
|
|
Limit the users routing options by
automatically |
|
|
Limit the users routing options by limiting |
|
|
Limit the users routing options by |
|
|
Limit the users routing options by making sure
|
|
|
Limit the users routing options by controlling
|
|
|
Use security gateways to limit routing options. |
|
|
Use firewalls to limit routing options. |
|
|
Limit external network users’ routing options
by |
|
|
Restrict network access by setting |
|
|
Restrict network access by setting |
|
|
Make sure that your enforced path controls are
|
|
9.4.3 AUTHENTICATE REMOTE USER CONNECTIONS |
|
|
|
Use authentication methods to prevent remote
users |
|
|
Carry out risk assessments to determine what
|
|
|
Use cryptographic methods to authenticate |
|
|
Use hardware tokens to authenticate remote
users |
|
|
Use challenge‑and‑response protocols to authenticate remote users. |
|
|
Use dedicated private lines to authenticate remote users. |
|
|
Use user address checking techniques to authenticate remote users. |
|
|
Use a dial‑back procedure to prevent remote
users from |
|
|
Make sure that your dial‑back procedure
ensures that an |
|
|
Test your dial‑back procedure to ensure that
an actual |
|
|
Disable the use of call‑forwarding features
whenever |
|
9.4.4 USE NODE AUTHENTICATION TO CONTROL REMOTE USERS |
|
|
|
Use node authentication methods to authenticate
remote |
|
|
Use node authentication methods to prevent |
|
9.4.5 CONTROL REMOTE ACCESS TO DIAGNOSTIC PORTS |
|
|
|
Control access to the diagnostic ports found
|
|
|
Make sure that your control of diagnostic
ports prevents unauthorized |
|
|
Use procedures and key locks to control access to your diagnostic ports. |
|
|
Make sure that your port control procedure
ensures that authorization |
|
9.4.6 SEGREGATE INTERNAL AND EXTERNAL NETWORKS |
|
|
|
Establish controls to segregate your internal
networks |
|
|
Make sure that your network controls prevent
external partners |
|
|
Make sure that your network controls prevent
unauthorized external |
|
|
Make sure that your external network controls
segregate |
|
|
Divide your networks into separate |
|
|
Establish secure perimeters between internal
|
|
|
Establish secure gateways to control user
access |
|
|
Configure your gateways to filter traffic
between internal |
|
|
Configure your gateways to block unauthorized
access |
|
|
Make sure that your gateways have been
configured in |
|
|
Make sure that your network segregation
practices |
|
9.4.7 RESTRICT CONNECTION TO SHARED NETWORKS |
|
|
|
Establish controls to restrict the users' |
|
|
Establish controls to restrict the users' ability to
connect |
|
|
Use network gateways to filter traffic |
|
|
Make sure that your shared network connection restrictions
|
|
|
Make sure that your shared network connection restrictions
|
|
|
Review and update your shared network |
|
|
Apply network connection restrictions to your email communications. |
|
|
Apply network connection restrictions to one‑way file transfers. |
|
|
Apply network connection restrictions to both‑ways file transfers. |
|
|
Apply network connection restrictions to interactive access. |
|
|
Apply network connection restrictions
by limiting |
|
9.4.8 ESTABLISH SHARED NETWORK ROUTING CONTROLS |
|
|
|
Establish network routing controls to ensure
that information |
|
|
Make sure that your network routing controls
are |
|
|
Use network address translation techniques |
|
9.4.9 VERIFY THE SECURITY OF NETWORK SERVICES |
|
|
|
Use public or private network services. |
|
|
Make sure that you have a clear description of
the |
|
|
Verify the security features of all the
network |
|
9.5 RESTRICT ACCESS AT OPERATING SYSTEM LEVEL |
|
|
|
Develop methods at the operating system level
|
|
|
Make sure that you can verify the identity of each authorized user. |
|
|
Make sure that you can identify and verify the |
|
|
Maintain a record of successful and unsuccessful access attempts. |
|
|
Use appropriate methods to authenticate users. |
|
|
Make sure that good quality passwords are used to authenticate users. |
|
|
Regulate how long users can be connected. |
|
|
Use challenge‑response methods to control access. |
|
9.5.1 USE AUTOMATIC TERMINAL IDENTIFICATION TECHNIQUES |
|
|
|
Use automatic terminal identification
techniques |
|
|
Use automatic terminal identification
techniques to |
|
|
Use automatic terminal identification
techniques when |
|
|
Install or attach identifiers to terminals in
order to be |
|
|
Take steps to secure terminal identifiers. |
|
9.5.2 ESTABLISH TERMINAL LOG-ON PROCEDURES |
|
|
|
Establish terminal log‑on procedures to |
|
|
Make sure that your log‑on procedures minimize
the opportunity |
|
|
Make sure that your log‑on procedures make it
difficult for unauthorized |
|
|
Make sure that your log‑on procedures ensure
that application |
|
|
Make sure that your log‑on procedures warn users that the
|
|
|
Make sure that your log‑on procedures make |
|
|
Make sure that your log‑on procedures ensure
|
|
|
Make sure that your log‑on procedures handle
|
|
|
Make sure that
your log‑on procedures limit the number |
|
|
Make sure that log‑on procedures limit the
number of unsuccessful |
|
|
Make sure that log‑on procedures limit
unsuccessful log‑on attempts by |
|
|
Make sure that your log‑on procedures force a
time delay |
|
|
Make sure that log‑on procedures limit the
minimum and |
|
|
Make sure that log‑on procedures ensure that
unsuccessful |
|
|
Make sure that log‑on procedures ensure that
the date |
|
|
Make sure that log‑on procedures ensure that
the details |
|
9.5.3 IDENTIFY AND AUTHENTICATE ALL USERS |
|
|
|
Assign a unique identifier (ID) to each user. |
|
|
Make sure that personal identifiers conceal
the user's |
|
|
Make it clear that personal identifiers are
for personal |
|
|
Make sure that personal identifiers can
be used to |
|
|
Establish controls to regulate and limit the
assignment |
|
|
Make sure that the assignment of group IDs or
job specific |
|
|
Make sure that accountability is still
maintained |
|
|
Establish authentication procedures to |
|
|
Use passwords to identify and authenticate users. |
|
|
Use cryptographic methods and authentication
|
|
|
Use objects such as smart cards or memory |
|
|
Use biometric authentication technologies |
|
9.5.4 SET UP A GOOD PASSWORD MANAGEMENT SYSTEM |
|
|
|
Make sure that your password management system |
|
|
Make sure that password management system
ensures |
|
|
Make sure that your password management system
|
|
|
Make sure that your password management system
includes |
|
|
Make sure that your password management |
|
|
Make sure that your password management |
|
|
Make sure that your password management system
|
|
|
Make sure that your password management system
|
|
|
Make sure that your password management |
|
|
Make sure that your password management system
|
|
|
Make sure that your password management system
|
|
|
Make sure that your password management system
ensures |
|
9.5.5 CONTROL THE USE OF ALL SYSTEM UTILITIES |
|
|
|
Restrict and control the use of any utilities
that could be |
|
|
Use authentication procedures to restrict |
|
|
Define and document authorization levels that
are |
|
|
Ensure that only a few trustworthy persons are
|
|
|
Authorize and control ad hoc system utility usage. |
|
|
Limit the availability and use of all system utilities. |
|
|
Maintain a complete log of system utility usage. |
|
|
Keep application software separate from utilities. |
|
|
Remove all unnecessary software utilities. |
|
|
Remove all unnecessary system software. |
|
9.5.6 PROVIDE DURESS ALARMS TO PROTECT USERS |
|
|
|
Provide duress alarm systems to users who |
|
|
Carry out a risk assessment to determine |
|
|
Developed procedure that describe how |
|
|
Define responsibilities that describe how |
|
9.5.7 USE TIME-OUTS TO PROTECT INACTIVE TERMINALS |
|
|
|
Prevent unauthorized access to inactive
terminals by ensuring that they |
|
|
Make sure that terminals in high risk areas
and locations automatically |
|
|
Make sure that your time‑out feature ensures
that terminal |
|
|
Make sure that your time‑out feature ensures
that application |
|
|
Prevent unauthorized access to inactive PCs
in lower risk areas |
|
9.5.8 RESTRICT TERMINAL CONNECTION TIMES |
|
|
|
Reduce the opportunity for unauthorized access
to terminals |
|
|
Reduce the opportunity for unauthorized access
to sensitive |
|
|
Reduce the opportunity for unauthorized access
to terminals by |
|
|
Reduce the opportunity for unauthorized access
to terminals |
|
|
Reduce the opportunity for unauthorized access
to terminals |
|
9.6 MANAGE ACCESS TO APPLICATION SYSTEMS |
|
|
|
Ensure that only authorized users are |
|
|
Ensure that only authorized users
are allowed |
|
|
Make sure that access to your application
systems |
|
|
Make sure that
your application systems control |
|
|
Make sure that your application systems
control user |
|
|
Make sure that application systems are
protected |
|
|
Ensure that your application systems do not
compromise |
|
|
Ensure that your application systems restrict
access to the |
|
9.6.1 REGULATE ACCESS TO APPLICATIONS AND INFORMATION |
|
|
|
Make sure that access to application system
|
|
|
Make sure that your business application |
|
|
Use menus to regulate and control access to |
|
|
Edit your application system documentation in |
|
|
Use formal access rights to restrict access
to |
|
|
Make sure that sensitive application outputs
are reviewed |
|
|
Make sure that sensitive application outputs
are |
|
9.6.2 ISOLATE SENSITIVE APPLICATION SYSTEMS |
|
|
|
Isolate your sensitive application systems. |
|
|
Use dedicated computers to run your |
|
|
Make sure that sensitive application systems
share |
|
|
Make sure that all trusted application systems
|
|
|
Make sure that application owners have
documented |
|
|
Make sure that owners of sensitive application
|
|
9.7 MONITOR SYSTEM ACCESS AND USE |
|
|
|
Monitor your information systems in order to
verify |
|
|
Monitor your information systems in order to
|
|
|
Monitor information systems in order to
evaluate |
|
|
Record deviations from your access control policy. |
|
|
Make sure that
your records can prove |
|
9.7.1 ESTABLISH AND MAINTAIN SYSTEM LOGS |
|
|
|
Establish information system audit logs that |
|
|
Make sure that
audit logs are used |
|
|
Make sure that your audit logs record user IDs. |
|
|
Make sure that your audit logs record terminal identities. |
|
|
Make sure that your audit logs record terminal locations. |
|
|
Make sure that your
audit logs |
|
|
Make sure that your
audit logs |
|
|
Make sure that
your audit
logs record |
|
|
Make sure that your
audit logs are |
|
|
Make sure that
your audit
logs comply |
|
|
Make sure that your
audit logs support |
|
|
Make sure that
audit logs can be used |
|
|
Make sure that you archive audit logs in order
|
|
9.7.2 MONITOR INFORMATION PROCESSING FACILITIES |
|
|
9.7.2.1 ESTABLISH PROCEDURES TO MONITOR FACILITIES |
|
|
|
Establish procedures to monitor the use |
|
|
Make sure that your usage monitoring
procedures are designed to |
|
|
Carry out a risk assessment for each facility
in order |
|
|
Monitor authorized access to your |
|
|
Monitor authorized access by tracking user IDs. |
|
|
Monitor authorized access by tracking the |
|
|
Monitor authorized access by tracking |
|
|
Monitor authorized access by tracking |
|
|
Monitor authorized access by tracking |
|
|
Monitor privileged operations and activities. |
|
|
Monitor privileged operations and activities
|
|
|
Monitor privileged operations and activities
|
|
|
Monitor privileged operations and activities
by |
|
|
Monitor unauthorized access to your information processing facilities. |
|
|
Monitor unauthorized access by tracking failed access attempts. |
|
|
Monitor unauthorized access by tracking access policy violations. |
|
|
Monitor unauthorized access by tracking |
|
|
Monitor unauthorized access by tracking alerts
|
|
|
Monitor information system alerts and failures. |
|
|
Monitor console alerts and messages. |
|
|
Monitor network management alarms. |
|
|
Monitor system log exceptions. |
|
9.7.2.2 REVIEW THE RESULTS OF MONITORING ACTIVITIES |
|
|
|
Review regularly the results of your monitoring activities. |
|
|
Review the results that monitor high risk
information processing |
|
|
Review the results that monitor the most
critical application |
|
|
Review results that monitor the use of valuable information. |
|
|
Review results that monitor the use of sensitive information. |
|
|
Review results that monitor the use of critical information. |
|
|
Review results that monitor areas that have
|
|
|
Review results that monitor areas that have
|
|
|
Review results that monitor systems that are
|
|
|
Review results that monitor systems that |
|
9.7.2.3 STUDY LOGS TO IDENTIFY SECURITY EVENTS |
|
|
|
Review logs on a regular basis in order to |
|
|
Allocate the responsibility for regular log reviews. |
|
|
Ensure that log reviewers are independent of |
|
|
Establish methods that you can use to study
large |
|
|
Use system utilities or audit tools to
interrogate large |
|
|
Take steps to secure your logging facilities. |
|
|
Establish controls to prevent operational |
|
|
Establish controls to ensure
that log file media |
|
|
Establish controls to
prevent log |
|
|
Establish controls to
prevent unauthorized |
|
|
Establish controls to
prevent changes to the |
|
|
Establish controls to prevent log files from being edited. |
|
|
Establish controls to prevent log files from being deleted. |
|
|
Establish controls to prevent the de‑activation of your logging facilities. |
|
9.7.3 PROTECT LOGS BY SYNCHRONIZING CLOCKS |
|
|
|
Protect the credibility of your logs by
ensuring |
|
|
Make sure that your clocks are set |
|
|
Establish a procedure to check computer |
|
9.8 PROTECT MOBILE AND TELEWORKING ASSETS |
|
|
|
Protect your mobile computing equipment. |
|
|
Make sure that your security initiatives
address the |
|
|
Make sure that mobile security initiatives
address |
|
|
Take steps to protect your teleworking equipment. |
|
|
Take steps to protect your teleworking sites. |
|
|
Make sure that your security initiatives
address the |
|
9.8.1 PROTECT MOBILE EQUIPMENT AND INFORMATION |
|
|
|
Protect the information processed by mobile computing equipment. |
|
|
Protect the information processed by notebooks. |
|
|
Protect the information processed by palmtops. |
|
|
Protect the information processed by laptops. |
|
|
Protect the information processed by mobile phones. |
|
|
Establish a policy to address the risks
associated with using |
|
|
Make sure that your mobile equipment security
policy instructs |
|
|
Make sure that your mobile equipment security
policy instructs |
|
|
Make sure that your mobile equipment security
policy provides |
|
|
Make sure that your mobile equipment security
policy addresses |
|
|
Make sure that your mobile equipment security
policy |
|
|
Make sure that your mobile equipment security
policy ensures |
|
|
Make sure that your mobile equipment security
policy |
|
|
Make sure that your mobile equipment security
policy ensures |
|
|
Make sure that your mobile equipment security
policy |
|
|
Develop mobile equipment security |
|
|
Make sure that your mobile equipment security
policy |
|
|
Provide equipment to enable your mobile |
|
|
Make sure that mobile equipment backups |
|
|
Make sure that your mobile equipment security
|
|
|
Protect your mobile equipment |
|
|
Use access control mechanisms to regulate |
|
|
Make sure that your mobile access control
mechanisms |
|
|
Protect your mobile equipment against theft. |
|
|
Protect all mobile equipment that handles |
|
|
Make sure that mobile equipment that handles
important |
|
|
Provide mobile computer security training |
|
|
Make sure that your mobile computer training
|
|
|
Make sure that mobile computer training and
awareness |
|
9.8.2 PROTECT TELEWORKING EQUIPMENT AND INFORMATION |
|
|
|
Secure your remote teleworking sites. |
|
|
Develop a policy to control teleworking. |
|
|
Develop procedures to control teleworking. |
|
|
Develop standards to control teleworking. |
|
|
Prevent the theft of equipment used by |
|
|
Prevent the theft of information available to
|
|
|
Prevent the unauthorized disclosure of
information |
|
|
Prevent unauthorized remote access |
|
|
Prevent remote workers from misusing |
|
|
Make suitable arrangements to support your |
|
|
Make sure that all teleworking activities and
arrangements |
|
|
Make sure that all teleworking activities and
arrangements |
|
|
Make sure that all teleworking security
controls |
|
|
Make sure that all necessary security controls
and |
|
|
Make sure that teleworking sites are
physically |
|
|
Make sure that teleworking buildings are
secure |
|
|
Make sure that the local environment is secure
before |
|
|
Make sure that communications between
teleworking |
|
|
Make sure that your teleworking security
controls consider the |
|
|
Prevent unauthorized access to your
information |
|
|
Provide suitable teleworking |
|
|
Make sure that teleworkers know what type of
|
|
|
Make sure that teleworkers know the hours |
|
|
Make sure that teleworkers know what |
|
|
Make sure that teleworkers know what kinds of
|
|
|
Make sure that the communications equipment
given to |
|
|
Establish methods for securing remote access
to |
|
|
Establish physical security for your teleworking sites. |
|
|
Establish rules that prevent family members
and |
|
|
Make sure that teleworkers receive suitable
software |
|
|
Establish teleworking back‑up procedures. |
|
|
Establish business continuity |
|
|
Establish audit and security monitoring
methods |
|
|
Establish procedures to control how
teleworking |
|
|
Establish procedures to control how
authorization |
|
|
Establish procedures to control how your |
|
|
Establish procedures to control how your |
![]()
|
PRAXIOM RESEARCH GROUP
LIMITED |
|||
|
Updated on December 22, 2011. First published on October 28, 2004. |
|||
Disclaimer
and Limitation of Liability
The
publisher and authors have used their best efforts in designing and
developing this electronic publication. We make no representation or
warranties
with respect to accuracy or completeness of the contents of
this publication and
specifically disclaim any implied warranties or
merchantability or fitness for any
particular purpose and shall in no
event be liable for any loss of profit or any
other commercial damage,
including but not limited to special, incidental,
consequential, or
other damages.
Legal
Restrictions on the Use of this Page
Thank
you for visiting this page. You are, of course, welcome to view our
material as often as you wish, free of charge. And as long as you
keep intact
all copyright notices, you are also welcome to print or make one
copy of this
page for your own personal, noncommercial, home use. But, you are not
legally authorized to print or produce additional copies or to
copy and paste
any of our material onto another web site or to republish it in
any way.
Copyright © 2004-2011 by Praxiom Research Group Limited. All Rights Reserved.
![]()