I find it encouraging that regulatory requirements are not the only forces driving good IT practices. For 29% of organizations, however, compliance with industry regulations was the critical factor behind archiving email. So which regulations make archiving an increasingly important element of network administration and compliance? In this tip, we'll touch on some regulations driving email archiving, why archiving is important, and how to avoid common mistakes made when dealing with archived data.
Compliance regulations driving email archiving
To start, there are two regulations that affect the majority of organizations. To address electronically stored information, amendments to the aging Federal Rules of Civil Procedure (FRCP) require organizations to manage their data so that it can be produced in a timely and complete fashion when required in the course of legal proceedings.
Publicly traded companies must also comply with the Sarbanes-Oxley Act of 2002, which stipulates that electronic data must be kept for 3-7 years. Given that the number of email messages for large organizations can run into millions each year, standard backup approaches, such as tapes used for disaster recovery, are not going to provide effective retrieval capabilities. On the other hand, a dedicated email archive can take advantage of indexing, tagging, custom searches and efficient storage to make message retrieval less painful.
Additionally, though it only affects healthcare and insurance providers, the Health Insurance Portability and Accountability Act (HIPAA) requires personally identifiable information to be encrypted both at rest and in transit. A product dedicated to archiving email can handle this requirement as well.
There are also various rules, imposed by bodies such as the Securities and Exchange Commission, the National Association of Securities Dealers, and the New York Stock Exchange, that cover the handling and storage of electronic messages. Although these are mainly touch firms in the financial services industries, they add to the weight of regulation, which requires electronic messages to be stored and secured against alteration, deletion and inappropriate access, yet easily retrievable when required.
For organizations of any size, there is a compelling argument for implementing some form of specialized email archiving. Not only will it make compliance easier and less time consuming, but it also leads to a more efficient network and user base. Without some form of email archiving, an email inbox can get quite large, with tens of thousands of emails. If, in order to abide by compliance regulations, users aren't allowed to delete any of them because they are not being archived, mailboxes with that many messages can quickly become unmanageable, both for users and administrators. Even Microsoft recommends large enterprise users of Exchange move old emails out of email boxes to a third-party email archiving product to improve user productivity.
The key aspects to choosing the right product are to ensure it will integrate with existing infrastructure, and that it has the functionality to help meet the organization's unique regulatory obligations. For instance, an effective email archiving system should provide a warning when unauthorized attempts are made to access the archive, or when emails violate acceptable content policies.
Also note that it is essential that the organization store emails in a format that does not change the information. Encryption is allowed and obviously recommended, but any form of compression, such as stubbing, which is the process where only one copy of an email attachment is kept and all other copies act as pointers to the individual one, must not remove or lose information about points of origin, destinations, dates and times.
There are many email archiving products available, many of which are designed to enable compliance with specific regulations. Taking time to review the available product options will help ensure your organization finds the correct balance between performance and productivity -- making sure the system runs smoothly without interrupting business activities -- and meeting security and compliance requirements.
About the author:
Michael Cobb, CISSP-ISSAP is the founder and managing director of Cobweb Applications Ltd., a consultancy that offers IT training and support in data security and analysis. He co-authored the book IIS Security and has written numerous technical articles for leading IT publications. Mike is the guest instructor for several SearchSecurity.com Security Schools and, as a SearchSecurity.com site expert, answers user questions on application security and platform security.
This was first published in February 2009