Under Sarbanes-Oxley regulations, as well as a number of other compliancy requirements, a publicly traded company's management is made personally accountable for their company's actions including the effectiveness of their internal auditing.
In fact, this has now extended to the NCAA, who has ruled that the transmission and receipt of SMS/Text messages and PIN messages without an audit trail is in violation of their mandate.
SMS and PIN messages never pass through your email systems and therefore will NOT be archived by your email archiving solution. Full audit compliancy has been difficult and time consuming at best.
To date, in order for an organization using BlackBerry* SmartPhones to be regulatory compliant, they have had to deactivate messaging capabilities that are unable to be archived, such as SMS and PIN messages.
Also, finding phone log information has been excessively time-consuming and frustrating.
Retain For BlackBerry Enterprise Server
Retain for BlackBerry Enterprise Server ensures that management is compliant with regulatory legislation by providing BlackBerry* Archiving and Auditing capabilities for the BlackBerry* Enterprise Server.
Retain For BlackBerry Enterprise Server also allows you to be easily compliant and with minimal effort. You can enable functionality to your BlackBerry* SmartPhones that you previously had to disable. Make your users happy and stay compliant at the same time.
It is important to note that a large percentage of BlackBerry* SmartPhone users assume that PIN messages are secure and untraceable.
Organizations can now conduct confidential SMS, PIN and phone call log investigations while simultaneously reducing their liability with regard to the retention and alteration of electronic data.
For more information on Retain, see:
For more information about GWAVA's complete line of GroupWise Products, see:
For information on GWAVA Webinars, see: https://gwava.on.intercall.com/confmgr/index.jsp?d...
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.