Windows network security Actually, we're only five steps short.

Network security is no longer just a user network will think about the problem, today's network situation complex, network security more to consider the detailed and thoughtful. I remind you peer-to-peer users, in fact, the Windows network security experience we are only five steps.

1. Must have local security policy

Enhancing each individual's system security is important because there is no Group Policy in this setting and you have to rely on Windows Local security policy. You can access your local security policy settings through the window Control Panel or by running Secpol.msc or secpol.msc.

Keep in mind that the key settings you need to do include: Enable logging of audit failure events, require logon using the Ctrl+alt+del key, create a password policy, enable a text message that notifies the user attempting to log on, inform the user of acceptable usage policies when the user logs on, and do not display the last user's name.

2. Need to approve sharing

In a peer-to-peer environment, you also need to communicate to everyone in your network about sharing. If not, keep the minimum rules in mind and set a shared license so that users can browse and see what they are allowed to see.

3. File permission is very important

According to the same principle of shared approval, a file license is required on every system locally to ensure that only authorized people can open, modify, and delete files.

4. Encrypt Offline Files

The need for Windows offline file encryption is common in peer-to-peer environments, especially for mobile users. If you use this feature, be sure to use these Windows guides to encrypt your files. It is best to consider using the PGP Desktop Pro or Securestar drivecrypt encryption software to partially encrypt or encrypt your hard drive to ensure your mobile data is secure.

5. Evaluate your network security

It is also important to regularly evaluate your peer-to-peer network security. Make sure to keep the following things in mind when evaluating:

• Implement local Security policy consistency checks for each system. The use of free and commercially available software tools will allow for such checks to be completed.

• Check local user accounts that are not owned by each system.

• Verify that your shared and file permissions are appropriate for each system.

• Find folders and hard disks that should not be shared, or find folders and hard disks that should not exist. This is a very common thing in peer-to-peer networks. Hard disk and folder sharing is normal in a peer-to-peer network.

• No matter what tools you use, when testing, make sure that you implement an identified scan (logged in as a standard user, administrator, or both) and an unrecognized scan (use only 0 session connections without logging in). This will give you an idea of what the network is really about, what is wrong with the configuration, and how undisciplined insiders or external hackers can see what's in your system.

So we can solve this security problem very well.