Detail Report v0.1
Detail Report v0.1
Complete Report
This report contains the following sections:
Executive Summary o o o o o o o Introduction Background: Assessment Process and Scope Situation Analysis Scorecard Security Initiatives Areas of Analysis Assessment Analysis Appendices o o o Questions and Answers Glossary Interpreting the Graphs Infrastructure Applications Operations People
Assessment in Detail
A Microsoft partner can review this report with you and help with developing a detailed action plan for implementing the recommendations. If you do not have an existing relationship with a Microsoft partner, you may wish to view a list of Microsoft Partners for Security Solutions at https://solutionfinder.microsoft.com/.
The Microsoft Security Assessment Tool is designed to help you determine the level of risk your computing infrastructure faces and the steps you have taken to mitigate that risk, and to offer suggestions of additional steps you can take to help further reduce your level of risk. It is not a replacement for an audit by a professional security consultant. Use of the Microsoft Security Assessment Tool is governed by the terms of the End-User License Agreement (EULA) which accompanied the software, and this report is subject to the exclusions, disclaimers, and limitations of liability contained in the EULA. This report is for informational purposes only. Neither Microsoft Corporation, its suppliers, or partners make any representation or warranty of any kind, whether express or implied, concerning the Security Assessment Tool, or the use, accuracy, or reliability of the results of the Assessment and information contained in this report.
Executive Summary
Introduction
This Microsoft Security Assessment Tool is designed to assist you with identifying and addressing security risks in your computing environment. The tool employs a holistic approach to measuring security strategy by covering topics across people, process, and technology. Findings are coupled with recommended mitigation efforts, including links to more information for additional guidance if needed. These resources may assist you in learning more about the specific tools and methods that can help increase the security of your environment. This summary section is intended to give IT and senior managers a snapshot of the company's overall security posture. Detailed findings and recommendations can be found in the detailed report following.
Situation Analysis
This section graphically represents the concepts described above for your organization, based on the answers you provided. As a reminder: BRP is a measure of the risk related to the industry and business model of the company DiDI is a measure of the security defenses used across people, process, and technology to help mitigate identified risks to the business
Results:
Areas of Analysis
Infrastructure Applications Operations People Risk-Defense Distribution Security Maturity
Risk-Defense Distribution
This chart indicates differences in the Defense-in-Depth score, organized by Area of Analysis.
60 50 40 30 20 10 0 Infrastructure -10
In general, it is best to have a DiDI rating on par with the BRP rating for the same category. An imbalance either within a category or across categoriesin either directionmay indicate the need to realign your IT investments.
BRP DiDI
Applications
Operations
People
Security Maturity
Security maturity is inclusive of controls (both physical and technical), the technical acumen of IT resources, policy, process, and maintainable practices. Security maturity can be measured only through the organization's ability to effectively use the tools available to create a maintainable security level across many disciplines. A baseline of security maturity should be established and used to define areas of focus for the organization's security programs. Not all organizations should strive to reach the optimized level, but all should assess where they are and determine where they should be, in light of the business risk they face. For example, a company with a low-risk environment may never need to advance beyond the upper range of the Baseline level or the lower range of the Standardized level. A
Security Maturity
A measure of a company's practices against industry best practices for maintainable security. Each company should strive to align its maturity level, and associated security strategy, relative to the risks taken in doing business: Some proactive security measures deployed as first-line defenses; operations and incident response still very reactive Multiple layers of defense deployed in support of a defined strategy Effectively protecting the right things the right way and ensuring ongoing utilization of best practices
Scorecard
Based on your answers to the risk assessment, the following ratings have been applied to your defensive measures. The Assessment Detail and Prioritized Action List sections of this report include further detail for each, including the findings, best practices, and recommendations. Legend: Meets best practice Needs improvement Severely lacking
Infrastructure
Perimeter Defense Firewall Rules and Filters Anti-virus Anti-virus - Desktops Anti-virus - Servers Remote Access Segmentation Intrusion-Detection System (IDS) Wireless Authentication Administrative Users Internal Users Remote-Access Users Password Policies Password Policies - Administrator Account Password Policies - User Account Password Policies - Remote-Access Account Inactive Accounts Management and Monitoring Incident Reporting & Response Secure Build Physical Security
Operations
Environment Management Host Management Host - Servers Management Host - Network Devices Security Policy Data Classification Data Disposal Protocols & Services Acceptable Use User Account Management Governance Security Policies Patch & Update Management Network Documentation Application Data Flow Patch Management Change Management and Configuration Backup and Recovery Log Files Disaster Recovery & Business Resumption Planning Backup Backup Media
Applications
Microsoft Security Assessment Tool ITC Services Completed: 17-Sep-11 12:52 PM Deployment and Use Load-Balancing Clustering Application & Data Recovery Third-party independent software vendor (ISV) Internally Developed Vulnerabilities Application Design Authentication Password Policies Authorization & Access Control Logging Input Validation Software Security Development Methodologies Data Storage & Communications Encryption Encryption - Algorithm
People
Requirements & Assessments Security Requirements Security Assessments Policy & Procedures Background Checks Human Resources Policy Third-Party Relationships Training & Awareness Security Awareness Security Training
Security Initiatives
The following areas fall short of best practices and should be addressed to increase the security of your environment. The Assessment Detail and Prioritized Action List sections of this report include further detail for each, including the findings, best practices, and recommendations.
High Priority Third-party independent software vendor (ISV) Remote Access Third-Party Relationships Application & Data Recovery Remote-Access Users
Medium Priority Segmentation Wireless Firewall Rules and Filters Log Files Internally Developed
Low Priority Management Host Servers Management Host Network Devices Backup Anti-virus - Desktops Anti-virus - Servers
Assessment in Detail
This section of the report provides the detailed findings for each category, as well as best practices, recommendations, and references for additional information. Recommendations are prioritized in the following section.
Areas of Analysis
The following table lists the areas that were included for high-level analysis in this security risk assessment and describes each area's relevance to security. The Assessment Detail section of this document describes your organization's security posture (based on answers you gave during the assessment) in each of these areas and provides industry-recognized best practices and recommendations for achieving those practices. Category Importance to security
Infrastructure Perimeter Defense Perimeter defense addresses security at network borders, where your internal network connects to the outside world. This constitutes your first line of defense against intruders. Rigorous authentication procedures for users, administrators, and remote users help to ensure that outsiders do not gain unauthorized access to the network through the use of local or remote attacks. Management, monitoring, and proper logging are critical to maintaining and analyzing IT environments. These tools are even more important after an attack has occurred and incident analysis is required.
Authentication
Applications Deployment & Use When business-critical applications are deployed in production, the security and availability of those applications and servers must be ensured. Continued maintenance is essential to help ensure that security bugs are patched and that new vulnerabilities are not introduced into the environment. Design that does not properly address security mechanisms such as authentication, authorization, and data validation can allow attackers to exploit security vulnerabilities and thereby gain access to sensitive information. Integrity and confidentiality of data is one of the greatest concerns for any business. Data loss or theft can hurt an organization's revenue as well as reputation. It is important to understand how applications handle business critical data and how that data is protected.
Application Design
Operations Environment The security of an organization is dependent on the operational procedures, processes and guidelines that are applied to the environment. They can enhance the security of an organization by including more than just technology defenses. Accurate environment documentation and guidelines are critical to the operation team's ability to support and maintain the security of the environment. Corporate security policy refers to individual policies and guidelines that exist to govern the secure and appropriate use of technology and processes within the organization. This area covers policies to address all types of security, such as user, system, and data. Good management of patches and updates is important to securing an organization's IT environment. The timely application of patches and updates is necessary to help protect against known and exploitable vulnerabilities. Data backup and recovery is essential to maintaining business continuity in the event of a disaster or hardware/software failure. Lack of appropriate backup and recovery procedures could lead to significant loss of data and productivity.
Security Policy
Assessment Analysis
This section is divided into the four major areas of analysisInfrastructure, Applications, Operations, and People.
Infrastructure
Infrastructure security focuses on how the network should function, what business processes (internal or external) it must support, how hosts are built and deployed, and how the network will be managed and maintained. Effective infrastructure security can help provide significant improvements in the areas of network defense, incident response, network availability, and fault analysis. By establishing a sound infrastructure design that is understood and followed, an organization can identify areas of risk and can design methods of threat mitigation. The assessment reviews highlevel procedures that an organization can follow to help mitigate infrastructure risk by focusing on the following areas of infrastructure security:
Perimeter Defense Firewalls, Anti-virus, Remote Access, Segmentation, Intrusion Detection Systems, Wireless Security Authentication Administrative, Internal & Remote Users, Password Policies, Inactive Accounts Management & Monitoring Incident Reporting & Response, Secure Build, Physical Security
Perimeter Defense Subcategory Firewall Rules and Filters Best Practices Firewalls are a first-line defense mechanism and should be placed at all network border locations. Rules implemented on firewalls should be highly restrictive and set on a host-by-host and service-by-service basis. When creating firewall rules and router ACLs (Access Control Lists), focus on first protecting access control devices and the network from attack.
+ Enforce data flow by use of network ACLs and firewall rules. + Test firewall rules and router ACLs to determine whether or not existing rules contribute to Denial of Service (DoS) attacks. + Deploy one or more DMZs as part of a systematic and formal firewall development. + Place all Internet accessible servers there. Restrict connectivity to and from the DMZs.
Findings Your answers indicate that not only have you deployed firewalls at network borders, you have also taken an extra precaution by creating one or more DMZ segments to protect Internetaccessible resources.
Recommendations Review firewall policies regularly and prune old or improper rules. Implement rules for controlling inbound and outbound access and consider implementing egress filtering to prevent unnecessary outbound connections. Limit internal users' direct access to DMZ segments as it is not likely they would work with the host computers that reside in the DMZ on a regular basis. Limit access from the core network into the DMZ segment to only specific hosts or administrative networks.
You have indicated that firewalls are not deployed at each office location.
You have indicated that hostbased firewall software is not used to protect servers.
You have indicated that the firewall is not tested regularly to ensure proper performance.
Immediately deploy firewalls or other network-level access controls at each office location, and frequently test and verify that all firewalls are working properly. As an extra layer of defense, consider installing host-based firewalls on all servers, and consider extending this software to all desktops and laptops in the organization also. Institute regular testing of your firewall. Ensure that functionality is working as expected not only from external traffic, but that the firewall is also behaving as expected towards internal traffic.
Subcategory Anti-virus
Best Practices Deploy anti-virus solutions throughout the environment on both the server and desktop levels. Deploy specialized anti-virus solutions for specific tasks such as file server scanners, content screening tools, and data upload and download scanners. Configure anti-virus solutions to scan for viruses both entering and leaving the environment. Anti-virus solutions should be implemented first on critical file servers and then extended to mail, database, and Web servers. For desktops and laptops an anti-virus solution should be included in the default build environment. If you are using Microsoft Exchange, use the additional anti-virus and
Microsoft Security Assessment Tool ITC Services Completed: 17-Sep-11 12:52 PM content filtering-capabilities it offers at the mailbox level.
Best Practices Findings Your answer indicates that antivirus solutions have been deployed at the desktop level. Recommendations Continue the practice. Implement a policy that requires users to regularly update virus signatures. Consider adding the anti-virus client in the default workstation build environment.
Best Practices Findings Your answer indicates that you have deployed anti-virus solutions at the server level. Recommendations Continue the practice. Consider actively managing anti-virus clients on the servers from a centralized management console for configuration and signature deployment. If you are using Microsoft Exchange, consider using the additional anti-virus and content filtering capabilities at the mailbox level.
Best Practices Workstations are a critical factor in the defense of any environment, especially if there are remote and roaming users that connect to the environment. Tools such as personal firewalls, anti-virus, and remote-access software should be present and properly configured on all workstations. Implement a policy which requires periodic review of these tools to make sure their configurations reflect changes in applications and services being used, but at the same time still keep the workstation resistant to attacks.
Remote Access
Findings You have indicated that the VPN is not capable of limiting connectivity to a quarantine until all necessary security checks have been passed.
Recommendations Treating your wireless network as untrusted and requiring users to use VPN or similar technologies to connect to corporate resources is the best solution to maintain data integrity, but does not prevent unauthorized users from connecting. Consider using WPA
Microsoft Security Assessment Tool ITC Services Completed: 17-Sep-11 12:52 PM authentication and MAC address restrictions in order to limit access to authorized users. Consider deploying multifactor authentication for remote users connecting over the Internet to corporate resources. Regularly audit the access list for all the users on the VPN device.
Remote Access
Subcategory Segmentation
Your answers indicate that employees and/or partners remotely connect to the internal network and that you have taken the important step of implementing VPN for this access, but you have not incorporated multifactor authentication as a second line of defense. Best Practices Use segmentation to separate specific extranets from vendor, partner, and customer access. Each external network segment should allow only specific application traffic to be routed to the specific application hosts and ports that are used to supply services to customers. Ensure that network controls are in place to restrict access to only what is required for each third-party connection. Restrict access to and from the network services being provided, and restrict access between network segments.
Segmentation
Findings Your response indicates that Internet-facing services are hosted on your organization's network
Segmentation
You have indicated that the network has more than one segment.
Segmentation
Your answer indicates that you have already implemented network segmentation in your environment.
Segmentation
You have indicated that hosts are not grouped into network segments based on providing only the necessary services for the users that connect. Best Practices
Recommendations Ensure that firewalls, segmentation and intrusiondetection systems are in place in order to protect the company's infrastructure from Internetbased attacks. Continue using network segmentation in order to better manage network traffic and limit access to resources based on user requirements. Continue to enhance the network based on listed best practices. Each extranet should be in its own segment, with restricted access between the network segments and internal corporate resources. The network should be designed so that only machines that need to connect to each other are able to, and segmented by function and service to allow for easier tracing of attacks.
Subcategory
Microsoft Security Assessment Tool ITC Services Completed: 17-Sep-11 12:52 PM Intrusion-Detection System Both network- and host-based intrusion-detection systems should be (IDS) deployed to detect and notify of attacks against corporate systems. Findings Recommendations Intrusion-Detection System You have indicated that you are Consider deploying either host(IDS) not using intrusion-detection or network-based intrusionhardware or software. detection systems. Subcategory Best Practices Wireless Best practice for wireless implementation should include ensuring that the network does not broadcast its SSID; that WPA encryption is used; that the network is fundamentally treated as untrustworthy. Findings Recommendations Wireless You have indicated that wireless In order to minimize the risk connectivity to the network is associated with wireless available networks, the implementation should include non-broadcast of SSID, WPA encryption, and treating the network as untrusted. Wireless Your response is that you have Changing the default SSID is the changed the SSID on the access first step in securing your point from the default. wireless network. However, this needs to be combined with further best practices in order to minimize risk. These include non-broadcast of SSID, WPA encryption, and treating the network as untrusted. Wireless You have indicated that you have Disabling SSID broadcast is part disabled broadcasting of the of the best practice for securing SSID on the access point. wireless, but needs to be combined with WPA encryption, and treating the network as untrusted. Wireless You have indicated that you are If you are currently using no not using WEP encryption in your encryption, consider using WPA wireless environment. to prevent wireless network traffic from being 'sniffed' and read as clear text. Wireless You have indicated that you are WPA is currently the most secure using WPA encryption in your encryption standard, but it can wireless environment. still be broken. Consider using additional encryption (such as VPN) to further secure data. Wireless You have indicated that you are Consider using WPA not using MAC restrictions in authentication in addition to MAC your wireless environment. filtering in order to prevent unauthorized computers from connecting to the network. Wireless You have indicated that the Consider migrating your wireless wireless network is not treated as network to an untrusted network untrusted. segment and requiring the use of VPN or similar technologies in
Microsoft Security Assessment Tool ITC Services Completed: 17-Sep-11 12:52 PM order to better preserve data integrity.
http://technet.microsoft.com/ enus/network/bb545879.aspx
Authentication Subcategory Administrative Users Best Practices For administrative accounts, implement a strict policy that requires the use of complex passwords that meet the following criteria: + Alphanumeric + Upper and lower case + At least one special character + Minimum length of 14 characters To further mitigate the risk of a password attack, implement the following controls: + Password expiration + Account lockout after 7 to 10 failed login attempts + System logging In addition to implementing complex passwords, consider implementing multifactor authentication. Implement advanced controls around account management (do not allow account sharing) and account-access logging.
Administrative Users
Findings You have indicated that users have been granted administrative access to their workstations. You have indicated that separate logins are not used for secure administration of systems and devices within the environment.
Administrative Users
Recommendations Consider removing administrative access for users, in order to limit the ability to modify the secure build. Consider requiring separate accounts for administrative/management activity, and ensure that administrative credentials are changed frequently.
Best Practices For user accounts, implement a policy that requires the use of complex passwords that meet the following criteria: + Alphanumeric + Upper and lower case + At least one special character + Minimum length of 8 characters To further mitigate the risk of a password attack implement the following controls:
Microsoft Security Assessment Tool ITC Services Completed: 17-Sep-11 12:52 PM + System logging In addition to complex passwords, consider implementing multifactor authentication. Implement advanced controls around account management (do not allow sharing of accounts) and account-access logging.
Best Practices Implement complex password controls for all users of remote access, whether this access is granted through the use of dial-up or VPN technologies. A password is considered to be complex if it meets the following criteria: + Alphanumeric + Upper and lower case + At least one special character + Minimum length of 8 characters Implement an additional factor of authentication for accounts that are granted remote access. Also consider implementing advanced controls around account management (do not allow sharing of accounts) and account access logging. In the case of remote access, it is especially important to protect the environment through the use of strong account management practices, sound logging practices, and incident detection capabilities. To further mitigate the risks of brute-force password attacks, consider implementing the following controls:
+ Password expiration + Account lockout after 7 to 10 failed login attempts + System logging Remote-access services should also take into account systems that will be used to access the network or hosts. Also consider implementing controls around hosts that are allowed to access the network via remote access.
Remote-Access Users
Findings You have indicated that employees are able to remotely connect to the network.
Remote-Access Users
You have indicated that contractors are not able to remotely connect to the network.
Recommendations If you have not already done so, consider using a multifactor authentication system for remote access, and limit access to only those employees that have a business need for remote connectivity. By not allowing remote access, you reduce your overall risk. However if remote access is planned or implemented in the
Microsoft Security Assessment Tool ITC Services Completed: 17-Sep-11 12:52 PM future, be sure to follow best practice when deploying the remote-access solution in order to minimize the risk associated with that access. By not allowing remote access, you reduce your overall risk. However if remote access is planned or implemented in the future, be sure to follow best practice when deploying the remote-access solution in order to minimize the risk associated with that access.
Remote-Access Users
You have indicated that third parties are not able to remotely connect to the network.
Best Practices The use of complex passwords for all accounts is a basic element of Defense-in-Depth. Complex passwords should be 8 to 14 characters in length, with alphanumeric and special characters. Minimum length, history maintenance, lifetime, and pre-expiration of passwords should all be set to provide additional defenses. In general, password expiration should be set to the following: + Maximum length 90 days + New accounts must change password at login + Password history of 8 passwords (8 days minimum) In addition to complex passwords, multifactor authentication is important, especially for administrative and remote user accounts. Account lockout, after 10 failed login attempts, should be enabled on all user accounts. The controls around account lockout can vary from simply being focused on blocking brute-force password attacks to requiring administrator intervention to unlock. It is considered a best practice to enable lockout for administrative accounts, at least for network access. This would not allow the account to be locked out at the console, only from across a network. This may not be appropriate for all organizations, especially those with remote locations. For remote-access accounts, it is best to require an administrator to unlock the account, as attacks could remain undetected for a significant amount of time if other means are not being used to track authentication failures. Consider the following guidelines when implementing controls around account lockout:
+ Lockout after 7 to 10 failed login attempts for administrative and remote-access accounts + Lockout after at least 10 failed login attempts for regular user accounts + Require administrative access to re-enable for administrator and remote-access accounts and automatically re-enable regular user accounts after 5 minutes
Password Policies
Typically the restrictions around creating passwords for administrators should be greater than those for normal accounts. On Windows systems, administrative accounts (and service accounts) should be set with passwords that are 14 characters in length and use alphanumeric and special characters.
Password Policies
Findings Your answer indicates the absence of formal controls to enforce password policies on all accounts.
Recommendations Consider implementing complex passwords based on listed best practices for all types of accounts. Consider implementing password expiration for all account types based on the listed best practices.
Subcategory Password Policies Administrator Account Subcategory Password Policies - User Account Subcategory Password Policies - RemoteAccess Account Subcategory Inactive Accounts Inactive Accounts
Best Practices
Best Practices
Best Practices
Inactive Accounts
Inactive Accounts
Best Practices Continue to monitor and manage inactive accounts. Institute a process to include an immediate notification procedure to all system administrators for terminated staff members to ensure their accounts are disabled immediately, especially their remote access accounts. Consider implementing a process to review the current accounts of staff that transfer to another department within the organization. Review this open item with your IT staff or a security partner. Input the most appropriate answer to this question in the MSAT for further information. Regularly monitor relevant vendors' sites for virus signature updates and download updates to a quarantined area for testing in a lab environment. Verify that the updates do not cause any conflicts with deployed operating systems or applications before rolling out to production. Auto-update features for anti-virus solutions should be disabled on all systems to prevent potentially damaging files from being deployed before they are tested. For anti-virus applications, consider deploying a central console that will facilitate reporting on which systems are out-of-date or have software features disabled. In the case of remote users who do not regularly connect to the
Microsoft Security Assessment Tool ITC Services Completed: 17-Sep-11 12:52 PM corporate network, consider using an auto update feature.
Inactive Accounts
Inactive Accounts
Terminated staff accounts should be disabled in a timely manner, to ensure that the terminated users or other users could use the account to gain unauthorized access. If system administrators are not aware of changes in the status of a user due to transfer, they will not change or remove system or physical accesses. This could lead to unauthorized or excessive access by transferred users. Findings Recommendations You have indicated that you do Review this open item with your not know the answer to this IT staff or a security partner. question Input the most appropriate answer to this question in the MSAT for further information.
Authentication - Resources
Windows Server 2008 Windows Server 2008 is the most secure Windows Server yet. The operating system has been hardened to help protect against failure and several new technologies help prevent unauthorized connections to your networks, servers, data, and user accounts. Network Access Protection (NAP) helps ensure that computers that try to connect to your network comply with your organization's security policy. Technology integration and several enhancements make Active Directory services a potent unified and integrated Identity and Access (IDA) solution and Read-Only Domain Controller (RODC) and BitLocker Drive Encryption allow you to more securely deploy your AD database at branch office locations. A central component of the Windows platform, Active Directory directory service provides the means to manage the identities and relationships that make up network environments. Windows Server 2003 makes Active Directory simpler to manage, easing migration and deployment. Windows Server Active Directory is already used by companies around the world to gain unified management of identities and resources across the enterprise network. Active Directory enables organizations to centrally manage and track information about users and their privileges. In addition, Active Directory Lightweight Directory Services (ADLDS), an LDAP directory service, provides organizations with flexible support for directory-enabled applications. Integration with Microsoft Federated Identity, Strong Authentication, Information Protection and http://www.microsoft.com/wi ndowsserver2008/en/us/over view.aspx
http://technet.microsoft.com/ enus/network/bb643123.aspx
Certificates
Management and Monitoring Subcategory Incident Reporting & Response Incident Reporting & Response Best Practices Continue to have and follow formal incident response and reporting procedures. Institute procedures for the reporting of and response to security incidents, issues, and concerns. Designate an emergency response team that includes representatives from several disciplines including technology, human resources, and legal for responding to all security incidents and issues. Consider implementing a full incident response program that includes incident response teams, containment management, event correlation and analysis, and incident response procedures. Review this open item with your IT staff or a security partner. Input the most appropriate answer to this question in the MSAT for further information. Maintain a build process with all vendor patches and recommended lockdown configuration. Test this process regularly. Use host-hardening procedures to patch and properly configure services and applications on each host. Disable all nonessential services and applications. Workstations should be hardened by installing recommended patches, removing all unnecessary services and packages, and auditing file permissions. Incorporate host-hardening steps into standard workstation build procedures.
It is important to follow documented incident reporting and response process to ensure that all issues and incidents are reviewed and assessed in a consistent manner. It is important for all users to understand their responsibility to report any security issues or incidents and for them to have a clearly defined process for reporting these issues. Findings Recommendations Your answers indicate that there Create a secure build for each
Microsoft Security Assessment Tool ITC Services Completed: 17-Sep-11 12:52 PM Response is no formal image or documentation used in building workstations. Subcategory Secure Build Secure Build Best Practices Findings You have indicated that personal firewalls have been installed on all workstations in the environment. You have indicated that the build processes for infrastructure devices have been documented.
type of workstation. Update these regularly with the latest service packs, hot fixes, and other hardening techniques.
Secure Build
Secure Build
You have indicated that your system builds do not include host-hardening procedures. You have indicated that there is no client-side remote access software installed on workstations that remotely connect to corporate resources.
Secure Build
Secure Build
You have indicated that the build processes for servers have been documented. You have indicated that diskencryption software is not used in the environment. You have indicated that the build processes for workstations and laptops have been documented.
Secure Build
Secure Build
Secure Build
Secure Build
You have indicated that remote control/management software is not used in the environment. You have indicated that a password-protected screen saver is used in the environment. You have indicated that modems are not used in the environment.
Secure Build
Recommendations Consider deploying personal firewalls initially on all mobile desktops. By default, block all access to the workstation from the outside. Implement a documented build process for infrastructure devices, and ensure that the build is kept current as new patches are released. All systems should be built following SANS, NIST, NSA, or other standard procedures for host-hardening. Consider deploying remote access client software on all individual workstations, if remote connectivity is required. Configure the client software to match the remote access server policy. Implement a documented build process for servers, and ensure that the build is kept current as new patches are released. Consider using disk encryption software in order to prevent data compromise in the event of machine theft. Implement a documented build process for workstations and laptops, and ensure that the build is kept current as new patches are released. Continue the practice of not using remote control/management software. Continue the practice of requiring all users to have a passwordprotected screen saver with a short time-out period. Continue disabling modem and dial-up access in order to reduce the risk of having machines able to be directly dialed into.
Microsoft Security Assessment Tool ITC Services Completed: 17-Sep-11 12:52 PM Subcategory Best Practices Physical Security Continue to implement physical security access controls. Physical Security Institute physical access controls to guard against unauthorized persons gaining access to the building and to sensitive information. Consider reassessing all physical access controls to ensure they are adequate and are being complied with. Increase staff awareness of the personnel access control policy and encourage the challenging of unrecognized individuals. Physical Security All computer systems should be secured to prevent easy theft. Servers and networking equipment should be secured in locked cabinets in locked rooms with controlled access. Physical Security Physical access should be stringently controlled, preventing unauthorized individuals access buildings, sensitive data and systems. With such access they could alter system configurations, introduce vulnerabilities into the network, or even destroy or steal equipment. Findings Recommendations Physical Security Your response indicated that Continue use of physical physical security controls have controls, and consider extending been deployed to secure your them to all computer equipment, organization's assets. if that has not already been done. Physical Security You have indicated that an alarm Consider installing an alarm system has not been installed to system in order to detect and detect and report break-ins report break-ins. Physical Security Your response indicates that all Continue to implement physical or some of the following are security access controls. implemented. (employee and visitor badges, visitor escorts, visitor logs, entrance controls) Physical Security You have indicated that Continue the practice of securing networking equipment is in a network equipment in a locked locked room with restricted room, and ensure access is access. limited only to those who have a business need. Physical Security Your response indicates that all Continue to implement physical or some of the following are security access controls. implemented. (employee and visitor badges, visitor escorts, visitor logs, entrance controls) Physical Security You have indicated that network Having network equipment in a equipment is also in a lockable lockable cabinet/rack further cabinet or rack. protects against unauthorized tampering. Ensure that access to keys/combinations is limited to only those who have a business need. Physical Security Your response indicates that all Continue to implement physical or some of the following are security access controls. implemented. (employee and visitor badges, visitor escorts, visitor logs, entrance controls)
Microsoft Security Assessment Tool ITC Services Completed: 17-Sep-11 12:52 PM Physical Security You have indicated that servers are in a locked room with restricted access.
Physical Security
Physical Security
Your response indicates that all or some of the following are implemented. (employee and visitor badges, visitor escorts, visitor logs, entrance controls) You have indicated that servers are also in a lockable cabinet or rack.
Continue the practice of securing servers in a locked room, and ensure access is limited only to those who have a business need. Continue to implement physical security access controls.
Physical Security
Physical Security
You have indicated that workstations are not secured with cable locks You have indicated that laptops are not secured with cable locks You have indicated that sensitive printed materials are not stored in locked file cabinets.
Physical Security
Having servers in a lockable cabinet/rack further protects against unauthorized tampering. Ensure that access to keys/combinations is limited to only those who have a business need. In order to prevent theft, consider securing workstations with cable locks. In order to prevent theft, consider securing laptops with cable locks. Sensitive documents should be kept in locked cabinets in order to prevent theft and disclosure of sensitive information.
Certificates
http://www.microsoft.com/wi ndows/products/windowsvist
Windows Defender works with Internet Explorer 7 to help make conscious choices installing software on your PS by providing always-on protection and monitoring of key system locations watching for changes that signal the installation and presence of spyware. Windows Firewall is a critiacal first line of defense to protect your computer against many types of malicious software. It can help stop malware before it infects your computer. Windows Firewall comes with Windows Vista and is turned on by default to protect your system as soon as windows starts. Windows Security Center alers you when your security software is out of date or when your security settings should be strengthened. It displays your firewall settings and tells you whether your PC is set up to receive automatic updates from Microsoft. Protect, maintain, and manage your computer with Windows Live OneCare, the always-on PCcare service from Microsoft. Working quietly in the background on your computer, OneCare protects against viruses, spyware, hackers, and other unwanted intruders. New features allow for multi-PC management to form a circle of protection, printer sharing support, and centralized backup of up to three PCs covered under the same OneCare subscription. Internet Security and Acceleration (ISA) Server 2006 is the integrated edge security gateway that helps protect IT environments from Internetbased threats while providing users with fast and secure remote access to applications and data.Deploy ISA Server 2006 for Secure Remote Access, Branch Office Security, and Internet Access Protection.
Windows Firewall
http://onecare.live.com/stand ard/en-us/default.htm
ISA Server
ADFS
Microsoft Active Directory Federation Services (ADFS) provides the interoperability required to simplify the broad, federated sharing of digital identities and policies across organizational boundaries. Seamless yet secure, customers, partners, suppliers, and mobile employees can all securely gain access to the information they need,
IPSec
http://technet.microsoft.com/ enus/network/bb531150.aspx
802.1
Applications
A thorough understanding of application security requires in-depth knowledge of the basic underlying application architecture as well as a solid understanding of the application's user base. Only then can you begin identifying the potential threat vectors. Given the limited scope of this self assessment, a complete analysis of application architecture and thorough understanding of the user base is not possible. This assessment is meant to help you review applications within your organization and assess them from a security and availability standpoint. It examines technologies used within the environment to help enhance Defense-in-Depth. The assessment reviews the high level procedures an organization can follow to help mitigate application risk by focusing on the following areas of application security:
Deployment & Use Load-Balancing, Clustering, Application & Data Recovery, Third Party Independent Software Vendor, Internally Developed, Vulnerabilities Application Design Authentication, Password Policies, Authorization & Access Control, Logging, and Input Validation Data Storage & Communications Encryption
Deployment and Use Subcategory Load-Balancing Load-Balancing Best Practices Findings You have indicated that load balancers are currently deployed in the environment. Recommendations Periodically audit the configuration of your load balancers and run diagnostics on a regular basis to make sure they are functioning properly.
Best Practices Findings Your response indicates that clustering is deployed in your environment. Best Practices Findings You have indicated that your Recommendations Implement a formal policy which requires periodic testing of the cluster failover mechanisms.
Microsoft Security Assessment Tool ITC Services Completed: 17-Sep-11 12:52 PM organization has line of business applications applications should be periodically evaluated for security, backed up regularly, fully documented, and have contingencies in place in case they fail. Perform full backups regularly. Perform regular tests of the backup and recovery mechanism that permits restoration of the application to a normal operating state.
Your response indicates that regular testing of application and data recovery is not performed.
Best Practices The third-party independent software vendor (ISV) should regularly provide patches and upgrades for their application, and they should explain the purpose of patches and any impact you may expect in terms of the functionality, configuration, or security of the application being patched. The third-party ISV should clearly identify critical patches so that they can quickly be applied. The third-party ISV should explain all of the application's security mechanisms and provide up-to-date documentation. The organization should be aware of any configuration requirements necessary to ensure the highest level of security.
Findings You have indicated that third party vendors have developed one or more of the key applications in your environment.
Your responses indicate that your third-party ISV provides you with regular software upgrades and security patches for applications developed by them.
Recommendations Ensure that the third party who has developed your key software will continue to support that software, provide updates in a timely manner, and can provide you with source code in the event that the third party can no longer support the application. Continue to work with the third party application vendor to address all application and security issues in the deployed applications. When a patch is made available, thoroughly test the patch in a lab environment before deploying it into production. Obtain the application hardening documentation from the ISV if it exists, and audit the applications configuration settings.
Microsoft Security Assessment Tool ITC Services Completed: 17-Sep-11 12:52 PM Third-party independent You have indicated that you do software vendor (ISV) not know the answer to this question
Review this open item with your IT staff or a security partner. Input the most appropriate answer to this question in the MSAT for further information.
Best Practices The in-house development team should regularly provide patches and upgrades for their application, and they should explain the purpose of patches and any impact you may expect in terms of the functionality, configuration, or security of the application being patched The development team should clearly identify critical patches so that the organization can quickly apply them. The development team should explain all of the application's security mechanisms and provide up-to-date documentation. The organization should be aware of any configuration requirements necessary to ensure the highest level of security. Consider contracting with an independent third party to review the application's architecture and deployment and identify any security issues of concern.
Internally Developed
Findings You have indicated that your organization does not use custom macros for office applications.
Recommendations Continue to not use custom Office macros, because using custom macros requires that the security settings in Office are downgraded, exposing your office applications to malicious documents.
Subcategory Vulnerabilities
Best Practices All known security vulnerabilities should be identified and patched. Regularly monitor vendor and third-party security sites for new vulnerability information and available patches. If there are any known security vulnerabilities that do not have available patches, determine when a patch will be available and develop an interim mitigation plan to address that vulnerability. Consider using a third party to conduct periodic assessments to evaluate the application's security design. A third-party assessment may also turn up areas where additional security mechanisms are beneficial.
Vulnerabilities
Findings Your response indicates that there are currently no known security vulnerabilities in any of the applications being used in your environment.
Recommendations Regularly monitor the vendor site and other security sites for vulnerabilities relevant to the application. Give thought to conducting an
Microsoft Security Assessment Tool ITC Services Completed: 17-Sep-11 12:52 PM independent assessment so that a third party can evaluate the application's security design and identify areas where additional security mechanisms may be needed.
http://msdn.microsoft.com/en -us/library/aa969774.aspx
Application Design Subcategory Authentication Best Practices The application should implement an authentication mechanism whose strength is commensurate with requirements governing security of data or access to functionality. Applications that rely on passwords should provide for password complexity constraints that include character mix (alpha, numeric, and symbols), minimum length, history maintenance, enforced lifetime, pre-expiration, and dictionary checking. The application should log failed login attempts, excluding the password. Each component that provides access to data or functionality should verify the existence of proper authentication
Microsoft Security Assessment Tool ITC Services Completed: 17-Sep-11 12:52 PM credentials. Administrative access to systems should be protected with the strongest forms of authentication available. Typically the restrictions around password creation for administrators should be greater than those for normal accounts. In addition to strong passwords with good password policies, for added security multifactor authentication should be considered.
Best Practices The use of strong passwords is a basic element of Defense-in-Depth. Strong passwords should be 8 to 14 characters in length, with alphanumeric and special characters. Minimum length, history maintenance, lifetime, and pre-expiration of passwords should all be set to provide additional defenses to password strength. In general, password expiration should be set to the following: + Maximum length 90 days + New accounts must change password at login + Password history of 8 passwords (8 days minimum) Administrative access to systems should be protected with the strongest forms of authentication available. Typically, the restrictions around password creation for administrators should be greater than those for normal accountsif normal accounts require a password length of 8 characters, then administrative accounts should have 14character passwords. Account lockout, after 10 failed login attempts, should be enabled on all user accounts. The controls around account lockout can vary from simply being focused on blocking brute-force password attacks to as complex as requiring administrator intervention to unlock. Consider the following guidelines when implementing controls around account lockout: + Account lockout after at least 10 failed login attempts for user accounts + Require administrative access to re-enable accounts for critical applications and automatically re-enable regular user accounts after 5 minutes for other applications + 30-minute length to cache failures for regular user accounts
Password Policies
Findings Your response indicates that no password controls are implemented for key applications.
Recommendations It is important to implement a policy for password controls. All external applications and critical internal applications that handle sensitive data should have password policies. Consider implementing a policy that requires complex passwords, password expiration,
Microsoft Security Assessment Tool ITC Services Completed: 17-Sep-11 12:52 PM and account lockout after at least 10 failed login attempts.
Best Practices Applications should implement an authorization mechanism that provides access to sensitive data and functionality only to suitably permitted users or clients. Role-based access controls should be enforced at the database level as well as at the application interface. This will protect the database in the event that the client application is exploited. Authorization checks should require prior successful authentication to have occurred. All attempts to obtain access without proper authorization should be logged. Conduct regular testing of key applications that process sensitive data and of the interfaces available to users from the Internet. Include both "black box" and "informed" testing against the application. Determine if users can gain access to data from other accounts.
Findings Your response indicates that key applications do not restrict access to sensitive data and functionality based on privileges assigned to the account.
Recommendations Work with the application vendor (ISV or in-house development team) to implement authorization and access control mechanisms within the application, initially for critical external applications and then internal applications. Authorization functionality enables administrators to group users into roles, and define specific permissions for each role. Based on verification of credentials users are allowed to access data based on assigned privileges.
Subcategory Logging
Best Practices Logging should be enabled across all applications in the environment. Log file data is important for incident and trend analysis as well as for auditing purposes. The applications should log failed and successful authentication attempts, changes to application data including user accounts, severe application errors, and failed and successful access to resources. When writing log data, the application should avoid writing sensitive data to log files.
Logging
Findings Your answers indicate that there are currently no logs created by applications in the environment.
Recommendations Work with the application vendor (ISV or in-house development team) to implement logging for key applications. When writing log data, the application should avoid writing sensitive data. Critical events, such as those mentioned in the Best Practices section, should be logged.
Best Practices The application may accept input at multiple points from external sources, such as users, client applications, and data feeds. It should perform validation checks of the syntactic and semantic validity of the input. It should also check that input data does not violate limitations of underlying or dependent components, particularly string length and character set. All user-supplied fields should be validated at the server side.
Input Validation
Findings Your answers indicate that there are no mechanisms deployed for input data validation in applications being used in the environment.
Recommendations Work with the application vendor (ISV or internal development team) to implement mechanisms to validate incoming data to prevent malicious or malformed data from being processed by the applications. These modules should initially be implemented for external applications. The validation constraints to input data should accept data that is syntactically and semantically correct and should not rely solely on screening of input for invalid characters.
Subcategory Software Security Development Methodologies Software Security Development Methodologies Software Security Development Methodologies
Best Practices Continue to use software security development methodologies. Institute to use of software security development methodologies to increase the security of your applications. When using consultants or vendors in any phase of your development cycle, ensure that they are trained on the software security development methodology your organization uses or one your organization recommends.
Microsoft Security Assessment Tool ITC Services Completed: 17-Sep-11 12:52 PM Software Security Your organization's full development staff should be trained on the Development Methodologies software security development methodology your organization has chosen. This includes Development Managers, Developers, Testers and Quality Assurance Staff. Software Security With the evolving security threat landscape, it is important to update Development Methodologies your software security development methodology training and threat modeling training on an annual basis. Your development staff would be required to take updated security development training each year. Software Security The use of security software testing tools improves your team's ability Development Methodologies to write secure code more effectively. Output from the use of your testing tools should be incorporated into your required annual training. Findings Recommendations Software Security Your response indicates that Institute a software security Development Methodologies your organization does not development methodology provide software security training program to improve your methodology training for your staff's ability to develop secure development staff. code. Software Security Your response indicates that Institute to use of security Development Methodologies your organization is not using software testing tools as an security software testing tools as instrumental part of all your a part of their security security development plans. development process.
Data Storage & Communications Subcategory Encryption Best Practices Sensitive data should be encrypted or hashed in the database and file system. The application should differentiate between data that is sensitive to disclosure and must be encrypted, data that is sensitive only to tampering and for which a keyed hash value (HMAC) must be generated, and data that can be irreversibly transformed (hashed) without loss of functionality (such as passwords). The application should store keys used for decryption separately from the encrypted data. Sensitive data should be encrypted prior to transmission to other components. Verify that intermediate components that handle the data in clear-text form, prior to transmission or subsequent to receipt, do not present an undue threat to the data. The application should take advantage of authentication features available within the transport security mechanism. Examples of widely accepted strong ciphers are 3DES, AES, RSA, RC4, and Blowfish. Use 128-bit keys (1024 bits for RSA) at a minimum.
Encryption
Findings Your responses indicate that your applications do not currently encrypt data while in storage or in transmission.
Recommendations For applications processing sensitive data, consider encryption using an industrystandard encryption algorithm
Microsoft Security Assessment Tool ITC Services Completed: 17-Sep-11 12:52 PM both during data transmission and in data storage. Subcategory Encryption - Algorithm Best Practices The application should use industry-standard cryptographic algorithms with keys of appropriate sizes and cryptographic modes appropriate to the need. Industry recognized strong ciphers include 3DES, AES, RSA, Blowfish, and RC4. A minimum key size of 128 bits (1024 bits for RSA) should be used.
Operations
This area of analysis examines the operational practices, procedures, and guidelines followed by the organization to help enhance Defense-in-Depth. This assessment examines policies and procedures that govern system builds, network documentation, and the use of technology within the environment. It also includes supporting activities required to manage the information and procedures used by the administrators and operations staff within the environment. By establishing operational practices, procedures, and guidelines that are understood and followed, an organization can potentially enhance its Defense-in-Depth posture. The assessment reviews high level procedures an organization can follow to help mitigate operations risk by focusing on the following areas of operations security:
Environment Firewall Rules & Filters, Administrative Users, Management Host, Disaster Recovery & Business RP, Third Party Relationships Security Policy Data Classification & Disposal, Protocols & Services, Acceptable Use, User Account Management, Governance, Security Policies Patch & Update Management Network Documentation, Application Data Flow, Patch & Change Management Backup & Recovery Log Files, Backup, and Restore
Environment Subcategory Management Host Best Practices When management packages are used, the administrative consoles should be hardened and physically secured. Harden the management workstations used to manage the network servers and devices. Use SSH or VPN connections to protect clear-text protocols. Management workstations should be dedicated to specific network and host administrators. Test all management systems that utilize SNMP to ensure that they are patched to the latest version and do not use default community strings. Shared systems do not store any management-specific data. Shared workstations are not used to administer network devices or hosts.
Microsoft Security Assessment Tool ITC Services Completed: 17-Sep-11 12:52 PM Subcategory Management Host - Servers Management Host - Servers Best Practices Findings Your answers indicate that a dedicated management computer exists for servers. Best Practices Recommendations Consider using SSH or VPN for securing clear text management protocols.
Findings You indicated that a dedicated management computer for administering network devices has been deployed.
Recommendations Test all management systems that utilize SNMP to ensure that they are patched to the latest version and do not use default community settings.
Environment - Resources
Windows Vista - User Account Controls User Account Controls in Windows Vista improves the safety and securty of your computer by preventing dangerous software form making changes to your computer withue your explicit consent. This also helps in prohibiting users from installing rougue programs, changing system settings and performing other tasks that are the province administrators. Data Classification and protection deals with how to apply security classifications levels to the data either on a system or in transmission. http://www.microsoft.com/wi ndows/products/windowsvist a/features/details/useraccoun tcontrol.mspx
Security Policy Subcategory Data Classification Data Classification Best Practices Continue to implement data classification with corresponding protection guidelines. Define a corporate data classification scheme and provide all staff with appropriate training and guidance regarding data classification. Define useable handling and protection requirements corresponding to data classification levels. Review this open item with your IT staff or a security partner. Input the most appropriate answer to this question in the MSAT for further information. It is important to have a data classification scheme with corresponding data protection guidelines. Insufficient information
Data Classification
Data Classification
Microsoft Security Assessment Tool ITC Services Completed: 17-Sep-11 12:52 PM classification and segregation can allow staff, business partners, or the public access to information that is sensitive or that they do not have a need-to-know. This could lead to loss of brand image or corporate embarrassment owing to unauthorized disclosure of sensitive information. Scarce resources used to secure information may also be misallocated without proper information classification. Without the staff knowing what company sensitive information is and how to protect this data, there is a high likelihood that this information may be exposed to unauthorized persons. Findings Recommendations You have indicated that you do Review this open item with your not know the answer to this IT staff or a security partner. question Input the most appropriate answer to this question in the MSAT for further information. Best Practices Continue to implement data disposal processes. Define and implement procedures for the management and disposal of information in both hard copy and electronic form, such as that contained on floppy disks and harddrives. Review this open item with your IT staff or a security partner. Input the most appropriate answer to this question in the MSAT for further information. Formal procedures should exist so that all users know the proper practices for disposing of electronic and hardcopy information. By not providing guidance and processes for securely destroying information, the confidentiality of information could be compromised. Findings Recommendations You have indicated that you do Review this open item with your not know the answer to this IT staff or a security partner. question Input the most appropriate answer to this question in the MSAT for further information. Best Practices Clearly document the standards and practices regarding which protocols and services are allowed by the organization. Accesscontrol lists should be verified to ensure that all services allowed have a business need for the level of access granted. Identify specific IP addresses/ranges wherever possible. Servers should have their services limited to only those required by the business need. Specifics for protocol version and minimum encryption strength should also be stated in these guidelines. Enforce accepted protocol usage through the use of perimeter devices (routers, gateways, firewalls, etc.), strong authentication, and encrypted communications. Findings Recommendations Your response indicates that you Audit the documentation for have documented guidelines that allowed protocols and services govern which protocols and and check that it conforms to the services are allowed on the configured ACLs and firewall corporate network. rules on the respective devices. Publish this information on the corporate intranet, and
Data Classification
Data Disposal
Data Disposal
Data Disposal
Microsoft Security Assessment Tool ITC Services Completed: 17-Sep-11 12:52 PM implement policies that govern making changes to the guidelines.
Subcategory Governance
Governance
Best Practices An Acceptable Use policy exists to govern the appropriate use of corporate networks, applications, data, and systems. The policy should also cover digital media, printed media, and other intellectual property. Best Practices Individual user accounts should be created for all persons needing access to IT resources. Accounts should not be shared among users. By default, accounts should be created with the minimum required privileges enabled. Network and server administrators should have privileged (administrator) as well unprivileged accounts. Password strength should be enforced and regularly audited and all account modifications should be logged. As an individual's role changes, all account privileges should be reviewed and modified as necessary. When employment is terminated, all accounts should be disabled or removed. Best Practices Third-party audits should be performed regularly to ensure compliance with all current legal and civil governance requirements (e.g., HIPAA for healthcare; Sarbanes-Oxley for SEC-regulated firms). Findings Recommendations You have indicated that your Policies are rules and practices organization does not have that specify how the computing policies to govern the computing environment can be properly environment. used. Without any policies, there is no mechanism to define or enforce controls in the environment. Immediately plan to develop the necessary policies in accordance with applicable standards and company management. Best Practices Security policies should be defined with input from management, IT, and HR; empowered by the corporate executives; and frequently updated to reflect current best practice (such as CoBIT).
Patch & Update Management Subcategory Network Documentation Best Practices Current and accurate physical and logical diagrams of the external and internal networks should always be available. Any changes made to the environment should be reflected in the corresponding diagrams in a timely manner.
Microsoft Security Assessment Tool ITC Services Completed: 17-Sep-11 12:52 PM Access to the latest diagrams should be restricted to the IT operations team.
Network Documentation
Findings Your answer indicates that logical network diagrams exist for your environment and they are kept up-to-date.
Recommendations Review the policy that governs updates to the network diagrams. If change control policy exists for the environment, include updates to the diagram as a formal step in the change control policy. Make certain the latest diagrams are only available to restricted personnel, primarily the IT operations and security team.
Best Practices Application architecture diagrams should depict major components and data flows that map the flow of critical data through the environment, including the systems through which the data passes and how the data is manipulated. As changes are made to the application or the environment that hosts the application, the diagrams should be updated in a timely manner.
Findings Your response indicates that application architecture and dataflow diagrams exist for both the internal and external applications in your environment.
Recommendations Review the policy that governs updates to the application diagrams. If change control policy exists for the environment, include updates to the diagram as a formal step in the change control policy.
Best Practices Security patches and configuration changes should be deployed in a timely fashion (defined by corporate security policy) from when they become available. Whether developed internally or supplied by a third-party, patches and updates should be thoroughly tested in a lab environment before being rolled into production. Additionally, each system should be tested after the patch has been applied to identify conflicts which are unique to that system and may require rollback of the patch. Systems should be categorized to allow for scheduling based on groupingscritical systems and those exposed to higher traffic should be patched first.
Patch Management
Microsoft Security Assessment Tool ITC Services Completed: 17-Sep-11 12:52 PM policies currently exist which govern patch & update management for operating systems and applications. for operating systems and applications based on the listed best practices. Patch external and Internet systems first, critical internal systems next, and then noncritical systems. Develop a policy to notify remote users when patches are available, so that their systems get updated as well.
Best Practices Any changes to the production environment should first be tested for security and compatibility before being released into production, and full documentation should be kept of the configuration of all production systems. Findings Recommendations You have indicated that your Consider implementing a formal organization does not have a change and configuration change and configuration management process to test and management process. document all updates before deployment.
http://technet.microsoft.com/ en-us/wsus/default.aspx
Microsoft Security Assessment Tool ITC Services Completed: 17-Sep-11 12:52 PM Backup and Recovery Subcategory Log Files Best Practices Log files are configured to allow for recording all planned activity without overwriting entries. An automated process should be set up to rotate log files on a daily basis and offload the logs to a secure server within the management network. Access to log files and configuration settings should be restricted to prevent modification and deletion. Log files should be reviewed regularly to ensure that suspicious or anomalous activity is identified. Review should include systems operation, maintenance, and security. Event correlation software and trend analysis should be used to enhance review capability.
Log Files
Findings You have indicated that log files are not rotated in your environment.
Log Files
You have indicated that log files are reviewed regularly in your environment.
Log Files
You have indicated that access to log files is not protected in your environment.
Log Files
You have indicated that logs are not written to a centralized log server.
Recommendations Set up an automated process that rotates log files on a daily basis and offloads the logs to a secure server within the management network. Consider storing the log files in a database so that the security team can perform trend analysis and have access to protected logs in the event an incident occurs. Consider having the log files from the DMZ and core network servers monitored by MOM (Microsoft Operations Manager). In the event of critical log-file entries being generated, MOM will send alerts to the appropriate members of the team. Consider protecting all operating system log files and application log files on the servers in the DMZ and core networks by limiting file access permissions. Consider logging to a centralized log server in order to preserve data in case a production server is compromised.
Subcategory Disaster Recovery & Business Resumption Planning Disaster Recovery & Business Resumption Planning
Best Practices Continue to maintain and test disaster recovery / business resumption plans. Require disaster recovery plans to be developed, documented, implemented, and subjected to periodic reviews, tests, and updates. Develop Business Continuity Plans that include staff, locations, as well as systems and other technology issues. Review this open item with your IT staff or a security partner. Input the most appropriate answer to this question in the MSAT for further
Microsoft Security Assessment Tool ITC Services Completed: 17-Sep-11 12:52 PM Disaster Recovery & Business Resumption Planning information. Disaster Recovery and Business Resumption plans should be well documented and up-to-date, to ensure recovery in an acceptable timeframe. Plans (including restore from backup for applications) should be regularly tested to validate correctness and completeness. Business Continuity Plans should focus on the entire environment; physical, technological, and staff. Findings Recommendations You have indicated that log files The security team should review are not reviewed regularly in your the log files every day to look for environment. suspicious or anomalous activities. Consider having the log files from the DMZ and core network servers monitored by MOM (Microsoft Operations Manager). In the event of critical log-file entries being generated, MOM will send alerts to the appropriate members of the team. You have indicated that you do Review this open item with your not know the answer to this IT staff or a security partner. question Input the most appropriate answer to this question in the MSAT for further information. Best Practices Full backups should be performed at regular intervals. If feasible, partial intermediary backups should be made between full backups. The backup strategy should address the worst-case scenario of a complete system and application restore. For critical applications, the restore process should result in a fully functioning application in minimal time. Findings Recommendations Your answer indicates that Audit the backup mechanisms critical assets in your and ensure that all critical assets environment are being backed are being backed up regularly. up on a regular basis. Periodically test the restore functionality to verify recoverability from the backup media. Best Practices Detailed policies should exist to govern the storage and handling of backup media. These policies should address issues such as:+ Onsite/Offsite Storage + Media Rotation + Security Controls + Personnel Access Controls Removable backup media should be stored in locked, fire-proof cabinets and only authorized personnel should have access to these cabinets. Offsite storage locations should be used to offer greater
Subcategory Backup
Backup
Microsoft Security Assessment Tool ITC Services Completed: 17-Sep-11 12:52 PM recoverability in the event of disaster.
Backup Media
Findings Your response indicates that no policies exist to address the storage and handling of backup media.
Recommendations Develop policies and procedures for storage and handling of backup media based on the listed best practices. These policies should initially address data for critical systems that are required for business continuity.
Best Practices Backup and restore procedures should be tested regularly to identify faulty media and improve the chance of a successful restore in the event of an outage. Detailed procedures for restoring different systems, including applications, should be well-documented. Audit all the backup and restore documents to ensure all the critical systems necessary for business continuity are covered.
Findings Your answer indicates no policies exist for the regular testing of backup & restore procedures.
Recommendations Develop a policy that calls for regular testing of backup and restore procedures. This process should be well documented so that in the event of a disaster, responsible personnel from the IT department can perform restore operations. Backup & restore procedures should be developed initially for the critical systems required for business continuity and then for other less critical systems and data.
People
Security efforts in an organization often overlook organizational aspects that are critical to helping the organization maintain overall security. This section of the assessment reviews those processes within the enterprise governing corporate security policies, Human Resources processes, and employee security awareness and training. The People Area of Analysis also focuses on dealing with security as it relates to day-to-day operational assignments and role definitions. The assessment reviews high- level procedures an organization can follow to help mitigate people risk by focusing on the following areas of people security:
Requirements and Assessments Security Requirements & Assessments Policy and Procedures Background Checks, HR Policy, Third-Party Relationships
Microsoft Security Assessment Tool ITC Services Completed: 17-Sep-11 12:52 PM Training and Awareness Security Awareness & Training Requirements & Assessments Subcategory Security Requirements Best Practices The organization identifies individuals with subject-matter expertise in security to be involved in all security-related discussions and decisions. The organization identifies what it needs to protect based on the value of the asset, as well as the level of security needed to protect it. All threat vectors are included in the analysis. The resulting strategy balances cost and benefit of the protections, and may include transfer or acceptance of risk as an option. Security requirements, derived from both business and technical representatives, are documented and published for all parties to review and address in future designs. Differences between classes of applications and data may result in different end requirements being identified. Findings Recommendations You have indicated that your Assigning criticality levels to organization does not have a each component of the model for assigning criticality computing infrastructure allows levels to each component of the for the most resources to be computing environment. applied to those determined to be most critical, with those less critical systems receiving less resources. Consequently scarce security resources are most efficiently applied to those systems that need them the most. Best Practices Third-party assessments should be conducted to gain a valuable and objective view of an organization's security posture. Third-party assessments might also prove beneficial in meeting regulatory, customer, partner, and vendor requirements. Assessments should cover infrastructure, applications, policies, and audit procedures. These assessments should focus not solely on identifying vulnerabilities, but also on auditing for non-secure configurations and extraneous access privileges. Security policies and procedures should be reviewed and evaluated for gaps.
Security Requirements
Security Assessments
Findings You have responded that no independent security assessments are performed by third parties.
Recommendations Start by performing selfassessments on critical network and application infrastructure. Consider developing a plan that calls for regularly scheduled third-party assessments for critical network and application infrastructure. Incorporate results from the
Microsoft Security Assessment Tool ITC Services Completed: 17-Sep-11 12:52 PM assessments into improvement projects.
Security Assessments
You have indicated that security assessments for your organization are not performed by internal staff
Consider performing frequent security audits by internal staff, but augment these audits with input from a trusted third party.
Policy & Procedures Subcategory Background Checks Best Practices Background checks should be performed to identify any potential issues, thus reducing the risk exposure to the organization and to other employees. This step also helps identify any potential issues and gaps in the candidate's resume. The hiring process should include a review of the candidate's employment and legal history. A candidate's skills should be evaluated against detailed job descriptions and task requirements to understand strengths and weaknesses.
Background Checks
Findings Your answer indicates that your organization does not currently conduct background checks as a regular component of the hiring process.
Recommendations Initiate a policy that requires background and credit checks for all new critical position hires. Eventually, extend this policy to include all new hires, regardless of position.
Best Practices Formal exit procedures ensure that all the necessary steps are undertaken when an employment contract is terminated. These procedures should exist to handle both friendly and unfriendly employee exits. These procedures should include: + Notification to all departmentsHuman Resources, IT, Physical Security, Help Desk, Finance, etc. + Escorting the employee from the premises + Termination of all accounts and network access + Collection of company propertylaptop, PDA, electronic media, confidential documents, etc.
Findings Your response indicates that no formal employee exit policy exists within your organization.
Recommendations Immediately begin work with the HR department to develop a formal employee exit policy.
Microsoft Security Assessment Tool ITC Services Completed: 17-Sep-11 12:52 PM There should be separate policies for friendly and unfriendly terminations. The most critical component of this policy is to ensure termination of all physical access and IT privileges for the employee.
Best Practices To help reduce the risk of exposure, formal policies and procedures should exist to govern relationships with third parties. These policies and procedures help to identify security issues and the responsibilities of each party in mitigating them. These policies should include: + Level of connectivity and access + Data presentation and manipulation + Roles and responsibilities (including authority) of each party + Management of the relationshipsetup, ongoing, and termination.
Third-Party Relationships
Findings You have indicated that systems are configured by internal staff. You have indicated that your organization manages the computing environment itself.
Third-Party Relationships
Third-Party Relationships
Recommendations Systems should be configured by internal staff following a tested build image. Based on business needs, either self management or outsourcing can be viable solutions. If the management is outsourced, security requirements should be addressed in the contract, and service-level agreements (SLAs) used to enforce compliance with those requirements. Formal policies and procedures for all different types of the thirdparty relationships should be developed and agreed upon across the organization. Involve the various business teams responsible for the relationships while framing these policies. Well-developed policies will reduce the organization's risk of exposure.
Training & Awareness Subcategory Security Awareness Best Practices A security awareness program helps employees contribute to a
Microsoft Security Assessment Tool ITC Services Completed: 17-Sep-11 12:52 PM company's overall security posture by keeping them up-to-date on security risks. Knowledgeable employees are your best source for reporting security issues. An effective awareness program should take into account all aspects of securityincluding application, network, and physicalwhile providing clear guidelines for what employees should do if they witness things that appear to jeopardize the security of any of these elements. Implement policies that regulate employee usage of company resources. Awareness programs should be a part of new employee orientation. Updates and refresher courses should be conducted regularly to ensure all employees are aware of the most current practices and risks. Periodic testing should be implemented to ensure employees have absorbed the material.
Security Awareness
Findings You have indicated that you do not have an individual or group responsibility for security at your organization.
Security Awareness
Your response indicates that no security awareness program exists at your organization.
Recommendations Designate a person or group with expertise in security to be responsible for security for the company, and require that this individual/team is consulted before changes are made to the computing environment. Consider implementing a formal security awareness program to keep employees informed about IT related security risks. Implement policies that regulate employee usage of company resources and technology and include security awareness as part of new employee orientation. Knowledgeable employees are your best source for reporting security issues.
Best Practices Work with business owners to determine the acceptable downtime for critical applications. Based on those findings take appropriate measures to meet or even surpass those requirements. Availability and performance of Web-based applications is improved by deploying load balancers in front of the Web servers. To balance server load, a load balancer distributes requests to different nodes within a server cluster with the goal of optimizing system performance. If one Web server in a server cluster fails, then the request is directed to another server to handle the request, providing
Microsoft Security Assessment Tool ITC Services Completed: 17-Sep-11 12:52 PM high availability. Determine acceptable downtime for critical file shares and databases from business owners. Test the failover mechanisms for the applications, and determine if the amount of downtime is acceptable. To minimize downtime, a clustering mechanism should be deployed. Each instance of the clustered application participates in the same security domain, i.e., shares a common user and group database. Management operations within the cluster of machines and within the application instances take effect both in the individual instance and across its peers. Applications that rely on special knowledge of the clustering environment--such as through interactions with load balancers--recognize and handle all foreseeable exception conditions. Appropriate responses include alerting operations staff and effecting a smooth failover. The backup strategy should address worst-case scenarios of a complete system and application restore. For critical applications, the restore process should result in a fully functioning application in minimal time. Perform regular tests of the backup/recovery mechanism that permits restoration of the application to a normal operating state.
Security Training
Findings Your answer indicates that your organization does not currently offer subject matter related training to employees.
Recommendations Develop a plan initially for the IT team and development engineers as needed based on your business model to attend appropriate security related training. Jumpstart the plan by having the team attend external training in the form of seminars and topic-specific security training. Draft plan to include some basic level of training for all employees in future.
(ISC)2 - CISSP, SSCP Certifications ISACA - CISM, CISA Certifications CompTIA - Security+
http://technet.microsoft.com/
Treating your wireless network as untrusted and requiring users to use VPN or similar technologies to connect to corporate resources is the best solution to maintain data integrity, but does not prevent unauthorized users from connecting. Consider using WPA authentication and MAC address restrictions in order to limit access to authorized users.
Applications > Deployment and Use > Application & Data Recovery
Any Line of Business applications should be periodically evaluated for security, backed up regularly, fully documented, and have contingencies in place in case they fail.
If you have not already done so, consider using a multifactor authentication system for remote access, and limit access to only those employees that have a business need for remote connectivity.
Medium Priority Infrastructure > Perimeter Defense > Segmentation Ensure that firewalls, segmentation and intrusion-detection systems are in place in order to protect the company's infrastructure from Internet-based attacks.
In order to minimize the risk associated with wireless networks, the implementation should include non-broadcast of SSID, WPA encryption, and treating the network as untrusted.
Immediately deploy firewalls or other network-level access controls at each office location, and frequently test and verify that all firewalls are working properly.
Consider having the log files from the DMZ and core network servers monitored by MOM (Microsoft Operations Manager). In the event of critical log-file entries being generated, MOM will send alerts to the Operations > Backup and Recovery > Log Files appropriate members of the team.
Continue to not use custom Office macros, because using custom macros requires that the security settings in Office are downgraded, Applications > Deployment and Use > Internally exposing your office applications to malicious documents. Developed Low Priority Consider using SSH or VPN for securing clear text management Operations > Environment > Management Host protocols. - Servers Test all management systems that utilize SNMP to ensure that they are patched to the latest version and do not use default community Operations > Environment > Management Host settings. - Network Devices Audit the backup mechanisms and ensure that all critical assets are being backed up regularly. Periodically test the restore functionality to verify recoverability from the backup media.
Continue the practice. Implement a policy that requires users to regularly update virus signatures. Consider adding the anti-virus Infrastructure > Perimeter Defense > Anti-virus client in the default workstation build environment. - Desktops Infrastructure > Perimeter Defense > Anti-virus Continue the practice. Consider actively managing anti-virus clients - Servers on the servers from a centralized management console for
Appendices
Questions and Answers
The following answers were provided for input into this assessment. Assessment Question Business Risk Profile Number of desktops and laptops in use at your company: Number of servers in use at your company: Does your company maintain a full-time connection to the Internet? Do customers and vendors access your network or internal systems via the Internet? Does your company host application services, such as a portal or a Web site, for external customers or partners? Does your organization deploy services that are used by both external and internal clients in the same network segment? Do external partners or customers connect directly to your company's internal, back-end systems for the purposes of data access, record updates, or other information manipulation? Has your organization deployed the same back-end infrastructure components, such as databases, to support both external applications and internal corporate services? Does your organization allow employees or contractors to connect remotely to the internal corporate network? Does your organization allow employees to deploy nonproduction systems, such as personal Web servers or computers housing "pet projects," on the general corporate network? Aside from backup tapes/media, does your organization allow confidential or proprietary data off-site for processing? Would a compromised system's security significantly impact your company's ability to conduct business? Does your company share office space with other More than 500 More than 25 servers Yes Yes Yes Yes Your Answer
No
Yes
Yes No
Yes
Yes No
No No
Yes No Yes No No No
Yes
Both internal employees and external customers, vendors, and partners Both from within the internal network and remotely No
No
Yes
I don't know
Yes
Yes
Yes Yes
No No
No
Yes Yes
No
No Yes
Yes No No Yes E-mail servers Perimeter hosts (gateways, proxies, relays, etc.) Desktops Servers
Is remote access to the company's network available? Select who is able to connect remotely to the network: Is virtual private network (VPN) technology being used to provide secure connectivity to corporate resources for these remote users? Is the VPN capable of limiting connectivity to a quarantine network until the client has passed all necessary security checks? Is multi-factor authentication (tokens, smart cards, etc.) required for remote users? Does the network have more than one segment? Is network segmentation used to separate external customer and extranet services from corporate resources?
No
No Yes Yes
Yes
Yes Changing the default/preset network name (also known as Service Set Identifier, or SSID) on the access point Disabling broadcast of the SSID Enabling Wi-Fi Protected Access (WPA)
Do controls exist to enforce password policies on various types of accounts? Does your organization have processes for reviewing inactive administrative, internal use, vendor and remote user accounts? Does your company configure its systems itself or is this done by the hardware supplier/reseller? Which of the following are built based on either an image or a formal documented configuration?
No No
Configured by internal staff Workstations and laptops Servers No Password-protected screen saver No Yes Networking equipment (switches, cabling, Internet connection) is in a locked room with restricted access Networking equipment is also in a lockable cabinet/rack Servers are in locked room with restricted access Servers are also in lockable cabinets/racks
Does this configuration include 'host hardening' procedures? Which of the following solutions have been installed on employee workstations and laptops? Does your organization have formal incident response procedures? Have physical security controls been deployed to secure the company's assets? Which of the following security controls are used?
Does the third-party vendor provide regular software upgrades, security patches, and documentation on security mechanisms? (is it still supported) What software security development methodologies are practiced at your company? (Select all that apply) Does your organization know of security vulnerabilities that currently exist in any of the applications being used in the environment? Does your company provide security training for your development and testing staff? Does your company rely on software tools as part of the test and audit process for secure software development? Do controls exist to enforce password policies in key applications? Do key applications in your environment have mechanisms enabled to restrict access to sensitive data and functionality? Do key applications in your environment record messages in log files for analysis and auditing purposes? Is input data validated by the deployed applications? Do key applications encrypt sensitive and business critical data that they process? Operations Does the company manage the environment itself, or outsource? Does the organization use dedicated management hosts for secure administration of systems and devices within
None No
No No No
Are separate login accounts used for normal activity vs. administrative/management activity? Does the organization grant users administrative access to their workstations and/or laptops? Is the firewall tested regularly to ensure it performs as expected? Does your organization maintain Disaster Recovery and Business Resumption Plans? Does a model exist for assigning criticality levels to each component of the computing environment? Do policies exist to govern the computing environment? Does a documented process exist for host builds? If yes, which types? (For what host types does a documented build process exist?) Do documented guidelines exist that govern which protocols and services are allowed on the corporate network? Select the option that applies. Does your organization have a formal, well-documented process for the disposal of data on electronic media and hardcopy form? Does your organization have a data classification scheme with associated data protection guidelines? Does a change and configuration management process exist? Does an established patch and update policy and process exist? Does an established policy exist to govern the updating of signature-based detection products? Do accurate logical diagrams and supporting configuration documentation exist for the network infrastructure and hosts? Do accurate application architecture and data flow diagrams exist for key applications? For which types of applications do diagrams exist: Is logging enabled in the environment to record events on hosts and devices? Does the organization take measures to protect the information contained within logs? Does the organization review log files regularly?
No
No No No None Yes
Yes Both internal and external applications Yes Log files are rotated frequently to ensure sufficient space is available No
Glossary
The glossary addresses standard security industry terms and concepts included in this report. Additional terms outside of this report may also be included. Term AoAs Applications Definition Areas of Analysis which are infrastructure, applications, operations, and people. A software program that provides functionality to an end user. Requires an operating system to run. Examples include word processor, spreadsheet, and database programs. Software and hardware technologies that protect the computing environment from malicious software. A measurement of the risk to which an organization is exposed, based on the business environment and industry in which it competes. A measurement of the security defenses used across people, process, and technology to help mitigate the risks identified for a business. A portion of the network that is separated from the internal network by a firewall and also connected to the
Multifactor authentication
Operations People
Process