- New attack fells Internet Explorer
- Steve Jobs is a man of a few words
- Oddball gifts for uber geeks
- Global warming research exposed after hack
- Google adding IPv6 to YouTube
Establishing and maintaining security policies across a corporate network is a necessary hassle. The good news is that PoliVec's suite of security tools - Builder, Scanner and Enforcer - smoothes out the process. Builder is the best component of the suite, providing an easy way to develop strong security policies. Enforcer is a more complicated tool, requiring quite a bit of configuration, a process that could be simplified.
PoliVec Builder has a graphical user interface that helps you quickly develop an enterprise security policy according to best practices for physical security, e-mail security, network access, remote access, authentication, incident response and security training. You also can define your own policy statements. Builder even includes templates to help organizations develop policies that adhere to regulations such as the Health Insurance Portability and Accountability Act and the Gramm-Leach-Bliley Act, which governs financial institutions.
Starting with Policy Editor, you select policies and best practices as the first step in developing a policy document. Many of the policies have attributes that can be customized for your organization.
The best feature in Builder is the ability to create implementation standards based on your policy. Implementation standards are detailed instructions that show administrators how to configure their servers to adhere to the security policy.
PoliVec Scanner taps into the policy document to audit systems and determine if they are configured correctly. Scanner analyzes systems for password policies, registry settings, audit trail settings, trust relationships, Windows NT File System (NTFS) settings and account management. Scanner also includes a password cracker to test end-user passwords to ensure they follow defined policies. By analyzing registry settings, Scanner also can determine which security patches are missing from the system.
You can schedule scans to run automatically and can customize the password-cracking dictionary to include key words that end users might be inclined to use in their password.
Security policies from Builder can be imported to use as the baseline for scanning. Customized policies also can be defined and used as the basis for a scan. One caveat is that Scanner only works with Windows NT, 2000 and XP machines.
The results of the audit are all stored centrally. You can generate multiple reports, such as displaying the audit results of a scheduled scan, audit results for a specific group of systems, or comparing trend information of several audits for one system.
One of the best features of Scanner is its ability to correct identified issues on remote systems in real time from the central console. Issues such as improper NTFS permissions, incorrect password policies, and incorrect account settings can be changed immediately, conforming the system to your organization's security policy.
Comment