Unfortunately, organizations make this a one-time "security project" and never examine the settings again.
Don't let your organization's data become inadvertently exposed by changes to your authority scheme.
More organizations are seeing the business requirement to secure critical data. Whether it's human resources information, payroll information, or credit card information, organizations are making the effort to set database access controls to appropriate settings—either "deny by default" (*PUBLIC *EXCLUDE) or "read only" (*PUBLIC *USE).
Unfortunately, organizations make this a one-time "security project" and never examine the settings again. Unless these settings are examined regularly, there's no assurance that the settings remain set to (or are in compliance with) your organization's security policy requirements. This leads to a rise in ""organizational risk" (the risk of loss resulting from inadequate or failed internal processes).
Consider these examples. An organization finds all of the files containing credit card information, sets them to *PUBLIC *EXCLUDE and uses adopted authority so that application users can continue to access the files containing the encrypted data. Another organization (a bank) secures its account information with authorization lists, setting them to *PUBLIC *EXCLUDE and only adding users who need access to the files from outside of the application (via ODBC, for example). In both cases, care is taken to authorize only the users who need access to the files. But also in both cases, no processes are put into place that require examination of these authorities. The results? In both cases, when I examined the authorities, users and groups had been authorized beyond the original list. Unfortunately (in both cases), no one knew when the new authorities were added, and no one reviewed the authorities for appropriateness.
How does this happen? I see two primary causes. One, a new application or process is added, and another process profile needs to be added to the list, usually without approval of the data owner or database architect and usually with *ALL authority even though something less, such as *USE, is sufficient. Two, a problem is being debugged. The *PUBLIC authority of the authorization list is set from *EXCLUDE to *ALL in attempt to resolve the problem. Because this rarely resolves the problem, the debugging effort moves to another part of the system and the altered authority is forgotten. Thus, data that used to be secure no longer is, and the vulnerable data remains that way until someone like me comes along and looks at the organization's security configuration.
More and more frequently, I see that data is unknowingly left vulnerable. Policy Minder makes it easy to check these authorities regularly. With Policy Minder, organizations need not wonder whether their data remains secured appropriately; they can be assured of it…painlessly.
How Policy Minder Helps
With Policy Minder, you can create a library template to define how objects are to be secured. You might want to define the security scheme for all application objects or for just selected files containing critical data. Once the template is created, you can run or schedule regular compliance checks. Using the exception report generated, you can easily identify whether changes have been made to the security scheme of any object. If no changes have been made, a one-page report is generated that states that everything is in compliance. You needn't look further or check anything manually. You know that the security scheme for these objects remains set correctly.
If you're using authorization lists, Policy Minder identifies any new users or groups added to or removed from a list. It also identifies whether any authorities have been changed. And just as with the library templates, a regularly scheduled compliance check will generate an exception report that will quickly show you what, if any, changes have been made.
Feel Secure
I admit to being rather passionate about making sure data is secured appropriately! That’s why I find it frustrating when an organization has taken the time to implement a more restrictive security scheme only to see it opened up because application objects and authorization list authorities aren't reviewed regularly.
Don't let your hard work be undermined. Don't let your organization's data become inadvertently exposed by changes to the authority scheme that open up a restrictive security policy. Don't raise your organization's operational risk by neglecting to regularly check these authority settings. Create a library, directory, or object template to maintain the appropriate settings on your critical application objects. Use the authorization list category to ensure that authorities have not been changed and that users or groups have not been added to the list without appropriate review and approval.
If you want more information on SkyView Policy Minder, a customized ROI analysis, or a 30-day free trial, contact us.
Carol Woodbury is IBM i Security SME and Senior Advisor to Kisco Systems, a firm focused on providing IBM i security solutions. Carol has over 30 years’ experience with IBM i security, starting her career as Security Team Leader and Chief Engineering Manager for iSeries Security at IBM in Rochester, MN. Since leaving IBM, she has co-founded two companies: SkyView Partners and DXR Security. Her practical experience and her intimate knowledge of the system combine for a unique viewpoint and experience level that cannot be matched.
Carol is known worldwide as an author and award-winning speaker on security technology, specializing in IBM i security topics. She has written seven books on IBM i security, including her two current books, IBM i Security Administration and Compliance, 3rd Edition and Mastering IBM i Security, A Modern, Step-by-Step Approach. Carol has been named an IBM Champion since 2018 and holds her CISSP and CRISC security certifications.
MC Press books written by Carol Woodbury available now on the MC Press Bookstore.
 |
||
 |
|
IBM i Security Administration and Compliance: Third Edition Don't miss the newest edition by the industry’s #1 IBM i security expert. List Price $71.95 Now On Sale
|
 |
|
Mastering IBM i Security Get the must-have guide by the industry’s #1 security authority. List Price $49.95 Now On Sale
|
More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.
TRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now! Request Now.
Forms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.
Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:
Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:
LATEST COMMENTS
MC Press Online