|
|
|
![]() |
![]() |
|
Case Study: Imperial Irrigation District and Security
Weaver
Security Weaver Eases User ID and Compliance Burdens, Helps IT Department Work Closely With Internal Auditor
Background: Situated in the Imperial and Coachella valleys in Southern California, Imperial Irrigation District (IID) delivers water to over 138,000 residential, commercial and industrial customers. Established in 1911, IID is the nation's largest irrigation district and, with more than 1,400 employees, serves one of the fastest-growing regions in the West. Challenge: Since 1998 IID has been using SAP technology to manage the company's back office accounting processes. With over 1,400 users of SAP, the company's IT department regularly had to address user authentication issues such as: who could have access to the system, what transactions were they allowed access to, and what duties could they perform? In order to strike the balance between user needs and system access compliance requirements, the IT team would have to go through many steps to run user access reports. This process proved inefficient and very time-consuming. "We have a small IT staff and so resources are very tight. But, when it came to security issues we knew that we needed to find a better solution," said Frank Hernandez, Supervisor, Corporate Infrastructure Engineering, Imperial Irrigation District. Requirements: As a California State Water District, IID does not need to comply with Sarbanes-Oxley regulations. However, IID believes in following best business practices to manage the company. Internal auditors repeatedly would ask the IT staff to generate reports manually to help examine user access to SAP and to make sure that the company was continuing to enforce proper controls. The need to run these types of detailed reports puts a tremendous strain on the IT staff, which in turn began to create tension between the IT staff and the internal auditors. Benefits: IID needed a solution that would address multiple issues:
IID examined a wide variety of security solutions but found that most were
either too expensive or too robust for their needs. At SAP's SAPPHIRE 2006
event, Hernandez was growing frustrated -- "I spoke with a number of security
vendors but none were able to meet my needs. I met with Security Weaver and, not
only did they have a solution that appeared to meet my needs, they said that
they could get us up and running that day. That's all I needed to hear."
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|