Professional Documents
Culture Documents
3.3. Scalability 7
6. Additional Resources 10
While Exchange has seen many improvements to security controls and management tools over the past few years,
Exchange auditing is not easily accomplished using native tools, including added features in Microsoft Exchange
2010. Changes to Exchange can introduce security risks, undesired behaviors, errors and problems for end users
as well as any applications requiring use of the messaging infrastructure. Proper MS Exchange auditing can reduce
the risk of security features being disabled or turned off, sensitive data compromise, and non-compliance with
internal and external regulatory requirements.
An effective Microsoft Exchange audit includes measuring the risks associated with managing a production IT
environment and addressing those risks in a secure, reliable and controlled audit trail of all changes 24x7x365. MS
Exchange auditing of objects and permissions is required to secure and manage the messaging infrastructure. This
provides a broad range of benefits most notably including accountability, compliance and operational stability at
all times and is difficult if not impossible using even the most current native tools.
Consider the network administrator conducting routine operations who needs help managing a remote Exchange
Server in the organization. In order to recruit some assistance, they add a local admin to the server to the Exchange
Enterprise Administrators group, giving that individual full access to the server and its settings. This local admin
decides to change the database store of local mailboxes to a new SAN drive, however, the configuration is
performed incorrectly. Users at this location are unable to access their mail. Frustration and anger quickly sets in.
Without an Exchange auditing solution in place, this organization will have to work harder and faster to find the
problem costing time and some of the reputation of the IT group. With auditing, this information could have been
quickly and easily discovered saving potentially hours of troubleshooting.
Establishing risk factors is the single most important step in securing any IT environment. Doing so will ensure
that everyone involved from end-users to senior management understands what is at risk. This creates a conscious
awareness of all things critical to sustaining normal business operations within the messaging infrastructure.
Regularly revisiting these risk factors will serve to adjust them appropriate to needs and condition changes.
Once the risk factors have been identified, the next step is to secure them. For Exchange Server, permissions limit
rights to sensitive data stored in mailboxes. Effectively managing every aspect of user and administrator interaction
with the messaging environment reduces risk while granting the appropriate access needed to communicate
effectively and consistently.
Change may sometimes bring unpredictable results, one of which is unintentionally creating conditions that
disrupts mail delivery. Exchange auditing provides actionable and historical forensic information to ensure risk
factors are managed appropriately while delivering consistent email services to the end-users.
Environments that rely on ticket-based change management systems, or other change approval processes may
still experience security problems if the information submitted is later found to have been inaccurate or intentionally
misleading. One of the easiest ways to improve Exchange security is to extract and review change information
automatically on a regular basis.
Demonstrating compliance is an exercise in presenting this information to auditors upon request and to the level
of details as is interpreted by the law or standard and subject to the individual auditor’s discretion. Auditing
Exchange provides the Who, What, When, and Where information most frequently requested by auditors and
almost equally important is the need to store this information for sometimes up to 7 years or more to be considered
compliant. For Exchange this is extremely difficult and an entirely manual process with native functionality and
thus gives rise to the demand for additional tools, especially in large environments with multiple levels of IT
administration.
Exchange auditing offers the opportunity to see before and new values for modified configuration settings and
permissions that can greatly improve an administrator’s response times to recover from changes that result in
harm or that introduce unnecessary risks. Additionally, by maintaining an historical record of changes over time,
further analysis can be used to uncover less obvious problems or inefficiencies. Being able to make changes to
Exchange is necessary to adjust to meet business and operational goals, however, the ability to look back at the
impact those changes had is the difference between ensuring a consistent, stable and safe environment for users
and loosing visibility and control over the systems charged with delivery of critical messaging services. The ease
with which changes are made can create a false sense of security with regards to the impacts those changes may
bring and thus reinforces the need to have an Exchange auditing and reporting tool to improve overall enterprise
messaging manageability.
Exchange reporting tools are also unavailable for audit data making the collection and reporting steps of change
auditing for configuration changes difficult and time consuming. There is also a risk of losing audit data if event
Once native information is analyzed by an administrator experienced with system events and messages, the
interpretation then would need to result in a decision to act or, accept the change and information as having met
the intended goal and did not result in a deficiency or unacceptable compromise. Evaluating using native Windows
and Exchange tools requires the same activity as collecting the information and thus requires similar investments
in time and effort.
Combine these factors and the result is native change auditing is not feasible in most types of environments. The
following information is a collection of must-have Microsoft Exchange auditing features. Additional deployment
considerations are provided as well.
Additional scripting and/or a third-party Exchange Server monitoring tool may also be employed to pre-configure
systems in preparation of collecting event data. Furthermore, if audit data is not collected regularly, there is a risk
of losing this information due to event log automatic overwrites or disk space issues. This is an important required
feature to change auditing because without it, timely auditing is nearly impossible.
While it is possible to store event and audit data locally on Exchange servers where the events are taking place,
the preferred method will be to centralize this information in a data store that is both secure and readily available.
This leads to numerous additional benefits over time as the need to analyze and report on this information becomes
part of daily routine for the IT administrator or group responsible for the overall health of the Exchange messaging
services.
Collection of information must also be reliable. Occasionally, each piece of the change auditing system should have
a periodic check to ensure information is consistent when collected. The most advanced methods of reliably
During collection, preference should be given to methods that leverage the existing Windows and Exchange event
logs as opposed to injected agents or modified core system code for audit data extraction. Doing so will eliminate
any potential system stability issues or future incompatibility problems. Relying solely on event log data introduces
problems because this information is frequently incomplete.
To completely understand an event, information from all sources involved must be aggregated and analyzed as a
whole. Securing this information for short and long-term storage is also an important consideration and thus best-
practices for securing audit data should be included pre-deployment such that no single power-user has access to
or the ability to delete or tamper with information. Access to this information should be heavily restricted and
monitored.
Scalability
To audit Exchange changes in the enterprise, the solution must be scalable to adjust to a constantly changing
environment without the need for dramatic steps. Implementation and ongoing use of MS Exchange auditing will
be simplified when no additional software or extensive reconfigurations are required when adjusting to messaging
changes within the organization.
Exchange auditing should keep pace with all granular changes as the overall topology of the network, domain
controllers and Active Directory changes to ensure consistent control to best serve end-users and provide an
invaluable audit trail for the IT staff. This scalability needs to be facilitated easily.
Without the ability to produce clear information on change history for day-to-day modifications to Exchange objects
and settings, such as, who changed mailbox permissions or if there has been a deleted connector, sustaining
compliance, stability and security will be impossible and many opportunities to improve these functions will be
surrendered.
With Exchange messaging environments, using Microsoft SQL Server to store data and leverage SQL Reporting
Services proves obvious choices for storing and reporting on data. SQL Server with Reporting Services (SQL SRS)
can be downloaded for free from Microsoft. The ability to customize ad-hoc and predefined third-party reports will
accelerate an effective change auditing implementation by saving time and providing configuration options to suit
the majority of needs. Using reports on a daily basis ensures complete visibility over the entire IT infrastructure
Administrators and users with excessive permissions present serious threats to the organization in the form of
reviewing confidential information without permission. This threat is especially severe for publicly traded
companies where financial information if leaked from the CFO’s mailbox can have legal repercussions.
An internal employee having a look at confidential financial statements before they become public may buy or sell
stock in the company using this insider information. The necessity to audit non-owner mailbox access is critical for
this reason as well as numerous similar situations where confidential information may pose serious harm.
Human resources also withholds sensitive company and employee information as such is the case during major
restructuring, or acquisitions where an employee could learn of upcoming layoffs or terminations in advance of
this information becoming public. The unauthorized employee could warn coworkers or cause panic and unrest in
the organization. This example further illustrates the grave dangers associated with non-owner mailbox access
and highlights the need to have this important feature as part of any Exchange auditing solution.
Additional Considerations
Preferred solutions (and providers) should offer plug-in or add-on modules and software to help form a cohesive
and comprehensive management suite to maximize the potential benefits of change auditing. Some additional
types of systems may include firewalls, switches, database servers, SANs, storage appliances and other Microsoft
technologies such as SQL and SharePoint and especially Active Directory and Group Policies.
Real-time alerting and object restore features will also add great value to any selected Exchange auditing tools.
Change auditing is a critical information collection and reporting layer to overall SIEM objectives and must have a
high level of interoperability with SIEM systems and services in order to achieve maximum effectiveness. SIEM
implementations range from in-house, customized systems to massive modular deployments providing
management capabilities for nearly all IT resources in an environment.
IT Governance is a term often used to describe the overall mission of an IT organization within the broader context
of the organization as a whole. It’s meant to provide a means by which core activities and services provided by IT
align with overall organizational directives and goals.
Risk-Management is a term found more and more frequently in press and publications to challenge the status of
security for appropriately describing how organizations approach keeping their resources stable and secure. More
recently, the increased visibility of mobile devices and cloud computing as part of an organization’s IT strategy
present new challenges to traditional models of thought on security and how best to provide that in an increasingly
mobile world where borders to IT infrastructure have blurred greatly.
Keeping these new terms in mind while approaching Exchange auditing will help keep IT objectives in line with
organizational messaging objectives and needs as requirements change.
The automatic collection and reporting on Exchange changes not only surpasses native capabilities in Windows but
expands upon them eliminating the time and effort spent collecting change audit information manually or through
complex scripting thereby making this information both reliable and actionable. Furthermore, it has the ability to
sustain compliance through historical reporting for up to 10 years and more and extend Exchange auditing into
SIEM systems for improved IT control and protection of these investments.
In addition to Exchange auditing, Netwrix offers applications for Active Directory, Office 365, Windows file servers,
EMC storage devices, NetApp filer appliances, SharePoint, SQL Server, VMware and Windows Server. Empowered
with the RESTful API and user activity video recording, the Netwrix Auditor platform delivers visibility and control
access all of your on-premises or cloud-based IT systems in a unified way.
To learn more about Netwrix Auditor for Exchange, please read its overview or download a free 20-day trial.
Additional Resources
Information security professionals and trends - http://www.infosecisland.com
Popular explanation and resources for Change Management and Change Auditing concepts and terminology
http://en.wikipedia.org/wiki/Change_management_auditing
Copyright © Netwrix Corporation. All rights reserved. Netwrix is trademark of Netwrix Corporation and/or one or more of its subsidiaries and may be registered
in the U.S. Patent and Trademark Office and in other countries. All other trademarks and registered trademarks are the property of their respective owners.