The process I followed to complete this homework was to format my paper, Google the words IT Security Policy Manuals, Google some specific organization’s Policy Manuals, review the topics found in the search, choose three documents, look at each document, and answer the questions asked in the assignment
The structure for the University of Connecticut IS manual starts out with the table of contents. The table of contents is a big checklist of what might be included in a policy manual.
One of the first sections of the manual discusses its purpose. It discusses who will manage access and who will deal with the most common aspects of security. In the purpose section it is made clear that the policies will be amended through an ongoing process. The Purpose section outlines the boundaries for acceptable behavior and guidelines for best practices in certain work situations. It offers clear instructions to employees as to how they are expected to act. They outline the importance of including policies that address legal and ethical safety. In the purpose section they also outline who will manage the IT resources to protect from threats.
In the Connecticut manual the next section that is listed is the contact information. This section explains the head people responsible for security issues. The Chief Information Security Officer (CISO) manages the University’s information security activities.
One of the next sections explains how the policies will be enforced and what type of
Note. Policy will be included on the existing work instructions document. (Task assigned to Sergio Delgadillo)
During SDLC phase one, the initiation phase, “the need for a system is expressed and the purpose of the system is documented” (NIST, 2008). Some of the expected outcomes from this phase would be a project plan and schedule; system performance specifications outlining the operational requirements, system design documents, and a document that defines roles and responsibilities. The corresponding RMF step, security categorization, establishes the foundation for security standardization among information systems and provides a vital step towards integrating security into the information system (NIST, 2008). During this step, the type(s) of information processed by the information system are identified and the information system is categorized to determine the level of protection requirements to put in place. Some of the expected outputs of this step include a security project plan and schedule, documented system boundary, the system categorization, and the security roles and responsibilities. These two process steps are very similar except the focus of RMF is on information security related functions. In some cases, SDLC produces the expected outputs that RMF requires, and the security professionals only require a copy of the documentation for their records. For example, the system design document often depicts the system boundary. The reason this step is so critical is that it
Due to policy changes, personnel changes, systems changes, and audits it is often necessary to review and revise information security policies. Information security professionals are responsible for ensuring that policies are in line with current industry standards.
| The security controls for the information system should be documented in the security plan. The security controls implementation must align with the corporate objectives and information security architecture. The security architecture provides a resource to allocate security controls. The selected security controls for the IS must be defined and
Management defines information security policies to describe how the organization wants to protect its information assets. After policies are outlined, standards are defined to set the mandatory rules that will be used to implement the policies. Some policies can have multiple guidelines, which are recommendations as to how the policies can be implemented. Finally, information security management, administrators, and engineers create procedures from the standards and guidelines that follow the policies.
1. The rationale and history for the existence of such policies and guidance documents (Ref. 1.3, 1.4)
No outside vendors, such as LEXIPOL, are used. The only outside sources that may be consulted are similar policies from other CALEA accredited departments of similar size and model policies from other law enforcement associations, such as the International Chiefs of Police (IACP). All policies are issued as General Orders and are numbered by Roman numerals. The policy manual is broken down into sections and policies are grouped into the appropriate section. The department also uses Standard Operating Procedures (SOP’s) that are not included in the policy manual. The SOP’s are usually more restrictive and do not give an officer much discretion. These procedures deal with common tasks that officers are required to perform and set out the way the department wants these tasks
Procedures also outline how to deal with disciplinary issues, allegations of abuse, managing risk, deal with grievance or death, respond to emergencies that we have in which supports us on how we work effectively and correctly which allows us to give the best level of care we can give to individuals.
National policies and regulations
Describe how to complete and maintain documentation in accordance with organisational procedures, in relation to:
Your Policy manual should provide a review of the systems and policies for communicating information on health, safety and security to staff, clients and visitors in accordance with the legislative requirements (Diagrams and flowcharts can be used here).
The themes that are common among each policy are security and protection of vital information and a desire to ensure that the reader understands what kind of information is being offered (Managing - Beth, 2007; Managing, 2002; Managing - Georgetown, 2007). There are no significant differences between the policies in the sense of what they protect against and what they provide. The main difference is that some of the policies are longer than others and some of them are presented differently. For example, the policy of Georgetown University Medical Centers is provided all on one page, with hyperlinks the reader can click in order to be taken to different parts of the document (Managing - Georgetown, 2007). The other two policies open in separate documents and all of the information is provided within those documents, with one being seven pages shorter than the other (Managing, 2007; Managing, 2002). While there is no specific benefit either way, it is up to the company as to how it wants to present the information and how it wants other people to access that information.
Crawford went over procedures and responsibilities of the policy along with areas that will be prohibited once the policy goes into effect August 2016.
A Policy and Procedure Manual is a vital to the efficiency, morale, and all overall productivity of any company. This manual informs the employees of the company’s vision and purpose and the steps needed to incorporate that vison into their everyday duties and tasks; therefore, producing continuity and efficiency within the company by eliminating confusion and empowering the employees with knowledge and a sense of belonging and pride. The company’s mission, strategy, and vision are married to a successful system of policies and procedures, thus creating a foundation for a lucrative an efficient business with employees that are equipped, informed, and happy.