Tuesday, 25 December 2012

Service Pack and Hot Fix


That security is also important is the service packs and hot fixes. If for example you are using windows, then you should check the Microsoft website. You must have a policy that explains how it is done. Because there is no one specific way to deal with service packs and hot fixes, you have to determine for themselves what is best for your organization.

Here are some questions that need to be answered at the time you make a policy:

  • Who is checking service packs and hot fixes new?
  • How many times has it done?
  • At the time the patch is installed, whichever comes first machine installed (if the process is automated o)?
  • Who installed the patch?
  • Is the patch installed dapa during the day, evening, or weekend?




read more reviews later on label create network documentation

user rights


Another important aspect of computer security is access control. Usually, the right of access to a given resource tends to shut rather than individual users. Therefore, enter a list of all the groups in your security guide. List must contain a description of the group and what permissions are required so that the user can be a member of the group.

make the list is not an lightly and should be maintained continuously. You will benefit with the document. First, by having the data group permissions in writing. You can see that everything is consistent. This is a surefire way to ensure that no one is to change the group permissions. Should do checks at specified intervals.

Another advantage could be a weapon in the face of a stubborn manager. Suppose the marketing manager asked that people put in all groups. At the time answered not, he can just say that you have no basis for rejecting his request.

One way to overcome these managers face is to take your security. and shows a black and white counts where there the phrase "to be a member of the Administrators group, the user must ...".


read more reviews later on label create network documentation


Sunday, 23 December 2012

Security Template


At the time talking about policy and security measures, we tend to think about things like minimum password length and the length of time the log on. Two it is certainly an aspect of security policy and unquestionably should be included in your security guide.

However, try to stay away from questions like "password must be at least eight character". We certainly do not want to use the same security policy between IT staff and other users. IT staff have access to a higher than another user and thus require more stringent security. Similarly, some of the servers storing the information is more important than the other servers and require a more stringent level of security. Because of these differences, it should use the security template.

Security Template is a file containing predefined settings that can applied to a group. One in the security guide, you could have mentioned

  • Administrators use template A.
  • Manager uses templates B.
  • User using templates C.

Next, you can specify the settings within each template. This includes the password length, password expiration, and all other security settings.

You also need to specify the template to be applied to the device. At the very least, you will need one template for workstations, one for members of the server, and one for the domain controller. If you have a server application then you may want to create a template for them. Keep in mind that the template workstation should not allow users to install unauthorized software or deleting system files. Template domain controller must protect Active Directory.

One more step that needs to be done. You should periodically check the contents of the template, and having integrity proven template, use the template to audit the existing setting. Free security you should mention how many times it was done, who did it, to whom the results are given, and what to do if there is any inconsistency.



read more reviews later on label create network documentation


Saturday, 22 December 2012

administrative security guide


User security administration is a little more difficult than your user security. most people tend to think security is to prevent hackers and viruses. Although it is true, another aspect of security is to protect users from themselves and protect the network from users who do not know what they are do.

You have to design a strict security system. Therefore, administrative documentation should be more lengthy and detailed. There is no right way or wrong way to make your administrative security. each organization has different needs. One company may require policy and procedureThe 200-page security, while smaller companies may suffice to five pages.

What is contained in it is entirely up to you.



read more reviews later on label create network documentation


Free Security End User


Free flow of explaining what to do user-related security. However, if it is small and many foreign terms, and even then it is not hard to read a lot of users who want to take the time to read and try to understand the guidelines.

Guidelines for the end user could be just one page that describes the basic security policy. Documents can contain for example:

  •  change passwords every 30 days,
  •  Do not write passwords carelessly or tell anyone else,
  •  Do not install software onto company computers,
  •  Do not connect the device to the network restricted,
  •  All submissions must be approved by the computer supervisor prior to submission to the purchasing department,
  •  Do not use company computers than affairs of the company,
  •  etc.

read more reviews later on label create network documentation


flag counter

Flag Counter