Five Steps to Integrate SAP into Your Enterprise Defense Framework

Email     |     Share  
1 | 2 | 3 | 4 | 5 | 6 | 7
Next Next

Compliance Framework

Include SAP in Your Compliance Framework

News about data theft, loss, and misuse makes headlines. The subject generates a large amount of publicity in a wide variety of industries, such as insurance, energy, banking and health care sectors, which generate, store and process a particularly large amount of sensitive information. If data containing compliance-regulated information is stolen or breached, the threat of negative headlines, penalties and/or loss of reputation grows exponentially.

SAP modules can contain information impacted by corporate governance mandates and a variety of regulatory requirements and standards, from the U.S. Health Insurance Portability and Accountability Act (HIPAA) and Sarbanes-Oxley Act (SOX) to export control regulations, like ITAR and EAR. Compliance regulations often require companies to show that they can track and monitor who accessed a particular type of sensitive data and what actions they took with it. To gain control over compliance-sensitive data, organizations should be able to oversee access and movement of regulated data, inside and outside SAP, including mobile and cloud channels. Movement of compliance-regulated data both inside and outside the enterprise borders should be made an integral part of an overall security and SAP audit.

In an age where digitizing information is the norm, organizations large and small rely on a myriad of applications, systems, and tools to create, collaborate, analyze, and report large volumes of data critical to the success of their businesses.  One such tool, SAP, is used by a remarkable 282,000 customers around the world to run their businesses.

In addition to being an enterprise resource planning (ERP) tool, SAP is also a primary storage vault for a vast amount of sensitive and business-critical data. The data stored in SAP ranges from personally identifiable information (PII) such as Social Security numbers and financial metrics (such as unreleased quarterly results) to bill of material (BOM) information – often related to products that are subject to export control regulations (EAR and ITAR) and trade secrets.

SAP represents a mission-critical piece of IT infrastructure companies spend a lot of time and effort protecting, but many often fail to integrate SAP and its sensitive data into their overall data protection strategy. A comprehensive enterprise defense model is a key requirement in today’s age of digitized data, and ERP software should be an incremental part of that ecosystem. In this slideshow, SECUDE highlights five steps organizations should take to ensure SAP is integrated in their security framework.

 

Related Topics : Unisys, Stimulus Package, Security Breaches, Symantec, Electronic Surveillance

 
More Slideshows

Security117-190x128.jpg 5 Steps to Protect Executives from a Whale-Phishing Attack

Whaling is a type of spearphishing targeting "big fish" in an organization with access to sensitive, highly-valuable information. ...  More >>

Security116-190x128.jpg 5 Common Failures Companies Make Regarding Data Breaches

Five common failures companies make when preparing for, and responding to, a data breach, as well as guidance for companies on how they can tackle these issues. ...  More >>

Security115-290x195 Data-Centric Approach Starves Data-Hungry Cybercriminals

Incorporating security capabilities such as encryption, better control and management and a data security framework will help alleviate the burden breaches place on the organization and people's lives. ...  More >>

Subscribe to our Newsletters

Sign up now and get the best business technology insights direct to your inbox.