|
|
Microsoft® Windows® Security Assessment
In addition to performing Server Security Configuration Assessments, GNS can also assess Microsoft® Windows® 2000/XP/Vista environments, including important applications such as IIS, SQL Server, and Apache. We also perform configuration assessments of routers. We have performed Host Security Configuration Assessments for systems ranging from small workgroup server to e-commerce web servers and financial databases hosts. We have compiled a comprehensive set of audit points based on our experience with penetration testing. Our knowledge base stays current with emerging technology, so that our Host Security Configuration Assessments check for the latest security patches and configuration methods for the latest applications. Our experienced consultants accurately determine where the highest-risk problems occur and how to address those issues at a policy level. Finally, our techniques use customised scripts that can be run by your administrators to collect data for assessment.
Our experienced consultants accurately determine where the highest-risk problems occur and how to address those issues at a policy level.
GNS’ methodology is created from established public guidelines and our consultants’ experience. We have developed tools to automate the collection of data. We use these scripts to help identify high-risk mis-configurations or omissions in your company’s server builds. Drawing from our experience, we test the overall risk of the host rather than just check a list of specific vendor-recommended points. As a result, we are able to identify the controls that most need improvement to reduce the risk faced by the host.
We thoroughly check the adequacy of security controls on the features and functions listed for numerous operating systems and devices:
- Microsoft Windows 2000/XP, VISTA (including Solaris™, Linux™, Tru-64, and AIX), and Novell®
- Specific applications such as IIS, SQL Server, and Apache
Microsoft Windows 2000/XP and VISTA Hosts
Each host is measured against the security practices from our methodology. We create a measurement of risk that is comparable between different operating systems and applications.
Account Management and Security
Password storage mechanisms for adequate restrictions
Password generation and management controls
Users' accounts have appropriate permissions
All users have unique accounts
Identify domain or server account policies for password rules, login time restrictions and intruder detection and lockout
Test password policy using password crackers such as LOphtcrack or John the Ripper
File Management and Security
- Permissions are correct for system, application, data, and user files
- Shares do not expose unnecessary data
- Shares are restricted to appropriate users and groups
- File integrity is monitored (Tripwire, md5 checksums, etc)
- Anti-virus software is installed, up to date and functioning
Patch Level
- An environment and procedure exists for testing patches before deploying to production systems
- Security-related patches for the operating system have been applied
- Security-related patches for applications have been applied
Network Security
- No unnecessary protocols are enabled
- Only business-related services are running
- Common services have been adequately secured (FTP, HTTP, NFS, RPC services, X Windows)
- Host-level firewall or other network access-control mechanism is enabled, where appropriate
- Modem security follows established policy
Logging and Auditing
- Default operating system auditing has been augmented
- Applications are configured to generate log data and log files are backed up
- Logs are periodically assessed for suspicious activity
- System times are synchronised with a central server
General Security Management
- Ensure that applications are executed with a least privilege concept
- Check potential for startup executables and scripts that may provide a back-door vulnerability based on insecure permissions or implementation
- Identify extent and type of trust relationships between domains
- Identify extent and type of trust relationships between individual systems
Detection of Previous Intrusion
- Look for the presence of common Trojans and back doors
- Check suspicious file permissions
- Check suspicious user accounts, such as an account with a blank password, excessive rights, not audited
External Controls (where applicable)
- Physical security
- Back-up strategy
- UPS
- Fire suppressions
- Environment (AC, Humidity)
Host Application Assessment - IIS, SQL Server, Apache
GNS also assesses the installation and configuration of major applications such as Microsoft IIS and SQL Server. These applications often represent a high risk to the network because of their history of vulnerabilities and their internet connectivity.
- Secure configuration
- Separation of privileges
- Recommended practices
- Logging and auditing
Router and Switch Host Assessment
These assessments begin with the methodology described above to assess the configuration of the underlying host. Additional checks are performed to assess the particular function of the router and switch. The methodology targets high-level concepts by tracking specific, detailed points:
- Access control lists that restrict packet flow
- Configurations to prevent or minimise spoofing attacks
- Filtering rules that restrict traffic destined for the router or firewall
- Check authentication methods for remote and local access and determine the adequacy of these controls
- Determine whether per-port security is enabled to eliminate unauthorised spanning, where applicable (Cisco switches)
- Examine authentication mechanisms for routing table updates
- Examine routes, especially static ones, for security concerns
- Examine the adequacy and security of logging configurations
- Ensure installation of recent software updates
- Examine hosts for unnecessary services and examine services configuration for appropriate security controls
GNS’s methodology not only points out specific points that should be addressed to reduce a host’s risk exposure, it also provides recommendations for how to bring up the baseline for deploying servers. These risk-reduction recommendations protect the system from known vulnerabilities and often eliminate exposure to zero-day exploits which reduces the scope of a compromise.
|
|