×
[searchandfilter taxonomies="search"]

How Automation of Oracle EBS Access Review Helps You Save Time and Cost 

By Shiv Sujir • March 18, 2022

Oracle EBS applications may have hundreds or even thousands of users logging in daily to access data, generate reports, and perform transactions. These users have multiple roles with varying levels of authorizations that keep changing depending on their job requirements. From a compliance and security point of view, it is essential for any organization to know who has access to what. The purpose of a periodic access review is to first ascertain this data, analyze it, and make informed decisions about user roles, authorizations, and the various risks involved with access. While the process might be straightforward, it can be very time-consuming. This is where automation can make a significant difference to your access review process.

Why Access Reviews Are Tedious

For most organizations, a user access review exercise is done at least once a year. Usually initiated by the internal audit department, the access review process requires business owners to review the Oracle EBS access rights of their respective teams. As a result, the process is highly manual, cumbersome, and time-consuming.

Business owners need to fill out documentation that involves fields like usernames, employment status, role information in relation to the tasks, and access rights. Now imagine going through this process for every single Oracle EBS application and user in the company. For large enterprises, the user numbers could easily be in the thousands. The result? Business managers end up signing off on documentation that they don’t fully understand. And there is a real possibility that the data is simply not accurate.

The next part becomes even more complex when business owners, security teams, or auditors navigate through the pile of data collected to get any meaningful information. The entire process is a huge administrative overhead that ultimately does not deliver enough value for the time invested.

Streamline Oracle EBS Access Reviews with Automation

When you have a large number of users accessing various Oracle EBS applications, the periodic access review process can be a substantial administrative undertaking. A viable solution to this challenge is deploying an access review automation solution that reduces the manual work, eases the process for business managers, and provides data that is useful for your security and audit teams.

Benefits of User Access Review Automation

Reminders: Let’s face it. Business managers have a lot on their plate already. Conducting an access review is not really on the top of their to-do list. Automation allows you to send out reminders to all relevant business managers and reviewers to undertake reviews. Reviewers can also be informed about any open reviews that need to be completed. This reduces the administrative burden of keeping tabs on the reviews and following up on the review status.

Directly Review Uploads: With an automated solution, your reviewers can directly update their assignments as they check them. They no longer need to send the updated review forms to IT staff, making the process simpler for both parties. Your IT and audit teams also have a full view of all completed and pending reviews.

Audit and Risk: Since the process is automated, a complete audit trail of the review is maintained. Any de-provisioning required because of a review can also be fully automated. This helps satisfy your internal auditors and makes data readily available for external auditors. Also, the user access data collected during the review can be directly plugged into risk management solutions to assess application risk, data risk, and compliance levels.

Overall, automation allows you to simplify and streamline your Oracle EBS access review process. It reduces the administrative burden of multiple departments that are involved. As a result, companies can save time and costs while extracting reliable access data that can be used to make critical decisions to achieve compliance and mitigate risk.

Automate Oracle EBS Periodic User Access Reviews with Appsian

Appsian’s Periodic Access Review is an automated access review solution that integrates with your Oracle EBS applications to provide a seamless review experience for all stakeholders. It eliminates manual processes and allows you to undertake Process Owner, Supervisor, and custom reviews of Oracle EBS users.

With automated reminders and escalations built-in, you can conduct multiple reviews at any time, resulting in substantial time and cost savings. The solution also maintains a complete audit trail to provide evidence for your auditors. As well as full visibility of risk so that better, more informed decisions can be made during the review process.

Schedule a demo with our Oracle EBS experts to understand the automated review process and how it can simplify your user access reviews.

Put the Appsian Security Platform to the Test

Schedule Your Demonstration and see how the Appsian Security Platform can be tailored to your organization’s unique objectives

How FTC Updates to “Safeguards Rule” Impact Higher Education Institutions

By Michael Cunningham • March 11, 2022

On December 9, 2021, the Federal Trade Commission (FTC) published a final rule amending the requirements for safeguarding customer information under the Gramm-Leach-Bliley Act (GLBA) (the Safeguards Rule). The Safeguards Rule has long specified cybersecurity standards under which financial institutions must maintain customer information, including higher education institutions (thanks to their participation in the federal student financial aid program). This is a significant development for our Higher Ed customers because it effectively mandates any Title IV participating institution to follow the updated guidelines.

Obligatory disclaimer: This article isn’t legal advice. Instead, it is a high-level look at new security regulations that affect our higher education customers. Therefore, we recommend that you seek guidance from your legal department and other relevant experts.

Key Security Elements of the Updated Safeguards Rule

While the amendments still allow some flexibility, they now include detailed criteria that higher education institutions must implement. This includes more detailed requirements for developing and establishing an information security program. Here’s a brief look at some of the security elements from the updated Safeguards Rule that higher education institutions should be aware of:

  • 314.4(c) Implement and maintain technical and physical access controls on customer information to limit access to authorized users and limit those users’ access to the scope of their authorizations.
  • 314.4(c) Implement measures to “monitor and log the activity of authorized users” and to detect when they have accessed, used, or tampered with customer information outside the scope of their authorization.
  • 314.4(c) “Implement multi-factor authentication for any individual accessing any information system.”
  • 314.4(d)(2)—Implement continuous monitoring of “information systems” (as defined in 314.2) or annual penetration testing with vulnerability assessments at least every six months.
  • 314.4(f)(3)—Periodically assess the information security risks that your institution’s service providers present and the adequacy of the safeguards they deploy to ensure that they are following the provisions of the Rule.
  • 314.4(f)(3)—Periodically assess the information security risks that your institution’s service providers present and the adequacy of the safeguards they deploy to ensure that they are following the provisions of the Rule.

Appsian can help organizations with these requirements. Here’s how:

  • Implementing fine-grained, dynamic (ABAC) controls while continuing to leverage the role-based controls that are already defined and in-use across the organization.
  • Implementing dynamic MFA, not just at the perimeter but also at the application, transaction, and data level (inline.)
  • Granular Activity Logging to provide visibility into data access and usage trends
  • Real-time user activity monitoring to ensure that security controls are properly enforced
  • Audit trail to aid investigation and remediation efforts

What Else is Included in the Updated Safeguards Rule

In addition to specific security controls, the amendments also include new requirements for risk assessments and new accountability and reporting requirements to boards of directors. We encourage you to review the revised regulations because some parts of the amendments may be more relevant to your institution’s needs than others. (pages 109–128 of this PDF document specifically cover the new rule)

Effective Date of the Updated Safeguards Rule

Due to the time required to implement many of the described provisions, the effective date of most above-described elements is December 9, 2022.

Next Steps

You don’t want to wait until the last minute to implement any of these security mandates. Contact us today to learn how we can help ensure that your information security program meets these new federal requirements.

Sources, References, and Further Reading: 

Put the Appsian Security Platform to the Test

Schedule Your Demonstration and see how the Appsian Security Platform can be tailored to your organization’s unique objectives

How Native SAML/SSO Integration Enhances Oracle EBS Security

By Shiv Sujir • March 11, 2022

Oracle EBS provides a suite of applications that perform several sensitive transactions like payroll processing, order processing, and financial reporting. This makes it crucial for security teams to protect and control access to these applications. However, one major hurdle in securing Oracle EBS is the lack of native SAML/SSO integration.

Enterprises today are facing challenges that are synonymous with modernization and digital transformation, especially when it comes to legacy applications like Oracle EBS. As the number of remote users increases, there is a significant rise in access risk. Without the necessary internal application controls, security teams also have to worry about data exposure and compliance requirements. One of the simplest ways to minimize this risk is by regulating application access through a Single Sign On solution – which can be done easily when your applications support SAML.

Unfortunately, the lack of native SAML/SSO support in Oracle EBS means that enterprises need to either custom-develop access control solutions or invest in additional Oracle products. In both cases, there is a significant increase in costs, complexity, and operational overheads.

Customization Creates More Problems Than Solutions

For large enterprises with sizeable development teams, creating a customized solution to manage Oracle EBS identity and access seems logical. However, customization brings a whole set of challenges that go well beyond the initial coding.

To begin with, customizing code for a third-party application needs specialized knowledge, which means you need a team with specific coding skills. Such projects often require additional hardware and web servers to be set up within the application environment. Once complete, maintaining the custom solution with regular product updates and testing these updates to ensure business continuity increases the workload of the application management and development teams. And finally, without a standardized support model, you will need to keep a support team on the ready.

Considering these technical challenges, the resource requirements, and the cost overheads, customizing a solution for Oracle EBS access management is just not a feasible option in the long run.

Security Benefits of Oracle EBS Native SAML/SSO Integration

Most enterprise security teams strive to provide access to applications using a Single Sign On (SSO) solution enabled by SAML. However, the lack of native SAML support in Oracle EBS can mean losing out on some key security benefits. From the user’s perspective, SSO creates a seamless login experience, reduces password fatigue, and increases productivity. But from a security point of view, there are three main reasons why you should be integrating SAML into Oracle EBS. They include:

Single Point of Authentication

Integrating SAML allows you to bring all your Oracle EBS users under a single Identity Provider (IdP). Coupled with an SSO solution, this creates a single point of authentication that eliminates the need for maintaining, synchronizing, and updating multiple user directories. It also improves ease of access and enhances the user experience.

A Centralized System for User Provisioning

ERP admin teams deal with thousands of access requests. Granting users access separately for Oracle EBS not only complicates the process but also could lead to over-provisioning, segregation of duties conflicts, and compliance violations. A centralized system makes it simpler to manage user access rights by allowing security and admin teams to provision and de-provision Oracle EBS users along with other applications.

Better Password Management

Since there is only one point of access, security teams can enforce password formats that are more resistant to brute-force attacks and stealing. Users can also be forced to change passwords regularly to enhance access security. A side benefit of having a single point of access is that users are more likely to remember their password rather than write it down.

Native SAML Integration with Appsian

To enable SSO, Oracle EBS customers typically have to make additional investments in Oracle Access Manager (OAM), Oracle Internet Directory (OID), and Oracle Unified Directory (OUD). Appsian is an Oracle-certified partner that offers a simple zero code SAML solution that natively integrates with Oracle EBS. It provides a plugin/extension with no coding, no alteration to existing EBS functionalities, no maintenance, and no additional product licenses.

With Appsian, enterprises can execute a robust identity policy across all users, devices, and Oracle ERP applications. Admins can quickly provision and de-provision users across all enterprise applications while maintaining strict password management policies enforced by your IdP. By delivering the SAML integration layer, Appsian connects Oracle EBS to your identity management solution and your enterprise SSO (ex. OKTA, AD, etc.) without complexity and operational overheads.

Schedule a demo with our ERP experts to learn how you can secure access to your Oracle EBS applications with Appsian.

Put the Appsian Security Platform to the Test

Schedule Your Demonstration and see how the Appsian Security Platform can be tailored to your organization’s unique objectives

MFA Is A “Critical Security Baseline” for Your Zero Trust Strategy

By Michael Cunningham • March 3, 2022

Following up on last year’s Executive Order to help improve the nation’s cybersecurity posture, the White House released a 30-page zero trust strategy document outlining several measures federal agencies must enact to secure systems and limits the risk of security incidents. 

The White House noted that the growing threat of sophisticated cyberattacks (for example, SolarWinds, ransomware, and Log4j vulnerability) underscores that the Federal Government “can no longer depend on conventional perimeter-based defenses to protect critical systems and data.” 

And neither should you. 

Instead, the Federal Government will focus on multifactor authentication as a critical part of its security baseline. In fact, strong authentication, as provided by a strong and dynamic MFA, is a necessary component of any zero trust strategy.  

What’s Good for the Feds is Good for the States 

If you’re a state or local government, I recommend that you review the White House’s zero trust strategy document. You won’t be bound by their mandated timelines, but the document is full of best practices and sound advice. Briefly, the security goals are based on the maturity model developed by the Cybersecurity and Infrastructure Security Agency. CISA’s zero trust model describes five complementary areas of effort (Image Source: White House):  

CISA Five Pillars for Zero Trust Strategy

Again, all good advice. I want to point out two key actions mandated by CISA related to multifactor authentication: 

  1. Federal Agencies “must employ centralized identity management systems for agency users that can be integrated into applications and common platforms.”
  2. MFA must be enforced at the application layer instead of the network layer.

Unfortunately, the majority of our clients in the government sector use ERP applications like PeopleSoft, SAP ECC, and Oracle EBS whose native architecture does not allow for the seamless integration of MFA solutions that can be A) integrated at the field/transaction levels of workflows or B) deployed dynamically with each unique context of access.  

These traditional ERP applications use static security controls to govern access. These controls fail to provide protection beyond the traditional perimeter-based security because they do not leverage contextual attributes. Put another way, these ERP systems do not allow a seamless integration of MFA solutions and make it challenging to achieve strong authentication for zero trust. 

Centrally Managed MFA to Enable Zero Trust Security with Appsian 

Fortunately, requiring dynamic MFA that is integrated inside ERP applications is one of the most common use cases our Appsian Security Platform solves.  

The platform can enforce zero trust security policies that can dynamically secure data and regulate access based on contextual attributes (e.g., IP address, time of day, location, user security clearance, data classification, device used, max dollar amounts, etc.). Additionally, Appsian can help bring your zero trust strategy to life with: 

  • Context-Aware Access Controls (with ABAC) – Fine-grained controls help you set dynamic access permissions for users down to the transaction and field level 
  • Step-Up Authentication – Integrate enterprise MFA at field level for re-authentication when a user requests access to sensitive data 
  • Transaction Monitoring & Control – Monitor high-risk transactions and automatically remove privileged access rights to stop potentially high-risk user activity
  • Data Masking – Enforce full, partial, or click-to-view data masking to obscure sensitive data and protect against unnecessary data exposure
  • Logging & Analytics – Capture detailed logs to get real-time visibility and insights into user access, IP address of frequent transactions, asset inventory, and other vital data.

Contact Appsian today for a demo to learn how we develop native integrations between Oracle and SAP ERP applications and some of the top MFA providers in the market. 

Put the Appsian Security Platform to the Test

Schedule Your Demonstration and see how the Appsian Security Platform can be tailored to your organization’s unique objectives

[Customer Story] How Appsian Solved University of Nebraska’s Unique SAML Authentication & IdP Configuration

By Esha Panda • March 3, 2022

The University of Nebraska uses PeopleSoft Campus Solutions for its student information system and wanted to streamline authentication for students, faculty, and staff across eight separate campus locations. So, they turned to a single sign-on integration solution from Appsian that enhanced security practices but was flexible enough to allow the eight campuses to retain the Identity Provider (IdP) of their choice.

Centralized SAML Authentication & Scalability: The Missing Pieces

When the University approached Appsian for a SAML SSO, they were currently using a custom, home-grown solution. This solution was not scalable in the long term and created a significant amount of complexity.

Our team realized that the University of Nebraska was struggling with three key challenges –

  • The University uses two instances of PeopleSoft – One for the University System (five campuses) and one for the State College System (three campuses).
  • Each campus has its own PeopleSoft Internet Architecture (PIA) within its designated instance of PeopleSoft.
  • The University utilizes eight different Identity Providers (IdPs) across all locations.

To streamline the SAML authentication process and improve the user experience across multiple applications, the University had to reduce the overall number of authentications by centralizing authentication management from a common platform. The University’s IT security leadership was impressed with Appsian’s ability to provide continuous support and offer creative and sustainable alternatives to offer the best solution for SAML integration.

Solving the University’s Unique IdP Configuration

The University’s security team was looking for PeopleSoft SAML integration to deliver a single sign-on solution that met their unique configuration requirements. Appsian’s solution was attractive to them since it was native to PeopleSoft. It enabled all eight campuses to retain the IdP of their choice. In addition, they could map to any one of the eight PIA instances.

“Instead of viewing our unique configuration as “the client’s problem,” Appsian looks for creative and sustainable alternatives to provide the best solution,” said William Barrera Fuentes, Director of the Nebraska Student Information Systems.

We enabled some unusual configurations that ensured all eight campus locations (and PIAs) could keep using their IdPs without sacrificing security or flexibility. Their team was happy that the cost of ownership did not increase by deploying additional infrastructure to support SSO and SAML authentication.

Native SAML Compatibility for PeopleSoft & Secure SSO With Appsian

Appsian’s PeopleSoft customer base includes multiple organizations in the education sector like the University of Nebraska looking for a configurable SSO solution with no custom development. With Appsian’s PeopleSoft SSO Connector, organizations can:

  • Leverage existing investment in SSO solutions to authenticate PeopleSoft sessions via SAML-based Identity Providers
  • Access PeopleSoft via deep link navigation (sent by email or other communication channels)
  • Support multiple IdPs concurrently for consolidated systems with separate user groups
  • Deploy your multiple IdP’s SSO in PeopleSoft as quick as 7 days with no additional hardware or custom coding

Schedule a demo with our experts to learn how Appsian integrates native SAML functionality in PeopleSoft to deliver a seamless Single Sign-On.

Customer Profile:

The University of Nebraska is the state’s only public university system, consisting of five campuses, each with a distinct role and mission. Together the campuses enroll 51,000 students and employ 16,000 faculty and staff who serve the state and world through education, research, and outreach.

Related Reading: University of Nebraska Case Study 

Put the Appsian Security Platform to the Test

Schedule Your Demonstration and see how the Appsian Security Platform can be tailored to your organization’s unique objectives

[Podcast] Automated Controls for Compliance – How and Why

By Michael Cunningham • March 2, 2022

Appsian’s Vice President of Product Strategy & Customer Experience, David Vincent, appears in the latest episode of Brilliance Security Magazine Podcast. The focus of the conversation between David and host Steven Bowcut is automated controls for compliance. 

Their wide-ranging conversation also includes the challenges associated with manually maintaining compliance, how automated controls can affect compliance, some leading practices for effective data security & privacy compliance, and more.

Listen to the full episode here:

 

Episode Highlights

Organizations still face challenges associated with manually maintaining compliance. David first explained how automated controls can reduce and alleviate the amount of manual effort involved with compliance. Next, David took a deep dive into some of the leading practices that organizations are using to implement and establish effective data security & privacy compliance programs, including:

  • Establish effective security and data privacy policies as part of the compliance program.
  • Centralize your effort to manage Security, Risk & Compliance across all your business application to realize greater efficiency, productivity, transparency, and cost savings.
  • Enable defense-in-depth by maintaining effective control at the three most important levels of an application – Access to application, access to the transactions, and access.
  • Enable policy enforcement and dynamic controls at the access, transaction, and data level with the Attribute-Based Access Control security model.
  • Ensure you have an appropriate balance of effective detective, preventative, responsive, and recovery controls capabilities to manage threats.
  • Constantly understand your compliance risk exposure with a fully automated Continuous Risk Assessment process.
  • Constantly understand your compliance control effectiveness with a fully automated Continuous Control Assessment process that test 100% of your transaction populations 24/7/365.
  • Perform Control Rationalization across all your business applications to reduce redundant controls that lead to excessive costs.
  • Perform Control Optimizations to replace manual controls with automated controls.
  • Enable a common control framework across your business applications for all of your compliance programs to realize greater efficiency and cost savings.
  • Monitor the two most important key performance indicators for risk and compliance: residual risk levels compared to your risk appetite levels to determine if you need to improve the operating effectiveness of your controls
  • Enable effective Vulnerability Management to quickly identify and resolve your vulnerabilities to avoid threats, and
  • Conduct independent assessments of your Risk, Control, and Vulnerability Assessments to continuously improve your capabilities.

Appsian is helping organizations achieve their audit risks, compliance program objectives. Appsian provides automated controls for compliance and helps organizations achieve their audit, risks, and compliance program objectives. We provide automation, analytics, and standardization to help organizations improve their efficiency and lower their costs to achieve those objectives.

Contact us for a demonstration today.

Put the Appsian Security Platform to the Test

Schedule Your Demonstration and see how the Appsian Security Platform can be tailored to your organization’s unique objectives

Internal SOX Controls: A Quick Overview

By Shiv Sujir • January 31, 2022

What is Internal SOX Controls?

The Sarbanes-Oxley (SOX) Act of 2002 was established as federal law to ensure accurate financial reporting by public companies and protect the intended users, such as lenders, investors, and government organizations, from financial statement errors and fraud and malpractice.

The Act includes 11 sections, out of which sections 302 and 404 are the most relevant to internal SOX controls. SOX section 302 defines the corporate responsibility for certifying the financial reports. Section 404, known as Management Assessment of Internal Controls, specifies requirements for maintaining and monitoring internal controls related to the company’s financial reports.

What is An External SOX Audit?

Section 404 requires businesses to have an annual audit of internal SOX controls performed by an independent external auditor. The purpose of the external audit is to enhance the degree of confidence of the intended users in the accuracy and completeness of the company’s financial reports, including balance sheets, income statements, cash flow statements, and statements of shareholders’ equity.

4 Key SOX Compliance Requirements

Any company that needs to comply with SOX must meet the following requirements annually. While each organization may establish its own compliance best practices, the ultimate goal is to meet four key requirements.

Management Responsibility:

SOX requires a company’s CEO and CFO to personally certify that all records are complete and accurate. Specifically, they must confirm that they accept personal responsibility for all internal controls and have reviewed these controls in the past 90 days. Failure to do so can result in heavy fines of millions of dollars and imprisonment.

Internal Controls:

The SOX act stipulates that public companies need to file a report that demonstrates the existence and efficacy of internal controls pertaining to financial records. Once again, SOX puts the burden of implementing these controls on the CEO and CFO to ensure the integrity and accuracy of financial information.

Data Security Policies:

Organizations that fall under the SOX act must create and implement data security policies that are designed to protect the storage and use of financial information. These policies should be communicated across the organization and enforced consistently to prevent financial inaccuracy or misinformation.

Proof of Compliance:

Companies are required to maintain and provide documentation that proves that all compliance requirements are being met. Also, all controls pertaining to SOX must be continuously monitored, tested, and recertified to measure SOX compliance objectives.

Impact of Internal SOX Controls on ERP Systems

Layered Internal Controls

The consistent implementation of internal controls mandated by SOX means that organizations must ensure adequate controls within all applications, including ERP systems. However, the role-based access controls provided by most ERP vendors are not fine-grained enough to demonstrate internal SOX controls.

To implement and demonstrate controls, organizations need to be able to implement layered access controls, often called defense-in-depth, that go beyond the initial point of access. Security teams must be able to monitor who is accessing what, when, and from where. This requires controls to be implemented at the access, transaction, and data field levels.

Even if you succeed in implementing these controls, SOX demands that these controls be continuously tested and monitored, making control recertification an integral part of your ERP SOX compliance process. And finally, your internal audit teams must be able to pull reports and logs that can undeniably verify the existence and efficiency of these controls.

Segregation of Duties Management

Segregation of Duties (SoD) is another aspect of SOX that affects ERP applications. Detecting and preventing SoD violations is vital to managing risk and fraud. When ERP admins need to manage thousands of roles and authorizations requests, there is a real risk of user over-provisioning and role conflicts that could lead to financial fraud. However, manually tracking each role and the resulting conflicts between roles is practically impossible.

To counter this challenge, automated SoD management solutions can be implemented across your applications. Automated cross-application SoD capabilities help you monitor role conflicts and SoD violations in real-time. They also manage your overall application risk from a single platform.

How Appsian Enables Internal SOX Controls in ERP

The Appsian Security Platform provides organizations with a range of controls and monitoring solutions that enable your security and compliance teams to not only implement internal SOX controls but also demonstrate their effectiveness at multiple levels.

Attribute-Based Access Controls

With Appsian’s ABAC capabilities, organizations can enhance their existing role-based access controls by taking contextual risk into account. For example, when users log into ERP applications, ABAC allows you to implement granular policies based on attributes like time, device, IP address, locations, etc. This information enables you to allow or deny access to sensitive information based on the context of access and significantly reduce data exposure in high-risk scenarios.

Adaptive Internal Controls

SOX requires companies to implement controls on access to and modification of data that affects financial reporting. Appsian enables internal controls at the ERP data field and transaction levels with tools like data masking and step-up multi-factor authentication for sensitive transactions. Coupled with Appsian’s ABAC capabilities, these layered controls can be activated based on contextual risk while allowing users full access when the risk is acceptable.

Automated SoD Management

Manually managing thousands of roles and authorizations while ensuring there are no SoD conflicts is a challenge for most organizations. Appsian automates SoD management by monitoring user activity and role usage in real-time. It pinpoints any current SoD violations of users and roles and prevents potential conflicts by testing roles in advance. Appsian’s cross-application capability also allows you to manage ERP risk with a single platform and implement SOX compliance consistently in all your ERP systems.

Learn how Appsian enables SOX compliance across your ERP applications with cross-application risk management, continuous controls monitoring, and adaptive internal controls. Schedule a demo with our ERP compliance experts.

Put the Appsian Security Platform to the Test

Schedule Your Demonstration and see how the Appsian Security Platform can be tailored to your organization’s unique objectives

How Appsian Enhances SAP GRC with Cross-Application SoD & Risk Management

By Shiv Sujir • December 31, 2021

What is SAP GRC?

SAP Governance, Risk, and Compliance (SAP GRC) is a set of SAP solutions that enable organizations to meet data security and compliance standards. These solutions also provide control mechanisms to manage and mitigate risk. SAP GRC consists of four major components and multiple modules that manage risks, controls, identities, cyberthreats, and international trade across the SAP ecosystem.

What are the Components of SAP GRC?

SAP GRC features four major components that unify enterprise risk and control activities on a single technology platform. Each component has a set of modules that serve a specific function. As a whole, SAP GRC solutions give decision-makers the insights needed to adjust strategies and objectives while enabling them to predict, detect, and respond to business threats and opportunities. The four core components include:

Enterprise Risk and Compliance
Modules: SAP Risk Management, SAP Process Control, SAP Financial Compliance Management, SAP Business Integrity Screening

Cybersecurity, Data Protection, and Privacy
Modules: SAP Enterprise Threat Detection, SAP Privacy Governance, SAP Data Custodian

Identity and Access Governance
Modules: SAP Access Control, SAP Cloud Identity Access Governance, SAP Identity Management, SAP Single Sign-On

International Trade Management
Modules: SAP Watch List Screening, SAP Global Trade Services

Enhancing Your SAP GRC Capabilities with Appsian

While SAP GRC is a good tool to implement GRC across your SAP systems, it has certain noteworthy limitations. Appsian’s GRC solution goes beyond the SAP ecosystem to provide unprecedented visibility of real-time authorization usage and implement fine-grained, adaptive controls across applications. This significantly improves security while reducing fraud, risk, and exposure to sensitive data at an enterprise level. In addition, Appsian can be deployed as a stand-alone solution or combined with your existing SAP GRC solution to enhance security and risk management.

Here are some of the ways Appsian can enhance your GRC capabilities.

Cross Application Connectivity

Most companies utilize multiple ERP platforms for their business operations. Though SAP GRC offers a range of modules and controls, it can be deployed only within other SAP applications. Appsian integrates with several business applications like Salesforce, Workday, Oracle, Microsoft, Infor, or industry-related applications without any third-party connectors. Appsian GRC seamlessly connects all your applications to a centralized system for unified GRC management.

Attribute-Based Access Controls

Many ERP applications, including SAP, offer only role-based access controls. While role-based access works well when the user connects through a secure network like the office, today’s workplace demands a more adaptive approach to access controls. Appsian utilizes contextual attributes like location, device, time, IP address, and more to determine access risk and allows security teams to implement policies based on these attributes. Additionally, unlike role-based authorizations that are granted at access, Appsian’s fine-grained controls go beyond the point of access down to the data field and transaction level to deliver layered security, enhanced compliance, and improved user governance across multiple applications using a single control platform.

Authorization Management

As new users are added, and existing users are granted more roles, it becomes increasingly difficult to track and manage user authorizations, especially when dealing with multiple ERP applications. The result is user overprovisioning that creates greater data exposure, SoD conflicts, and overall risk. Appsian tracks authorization usage to recommend the elimination of unused and underused authorizations and access rights, making the monitored applications safer and simpler.

User Monitoring

While SAP GRC allows you to monitor and manage identities and control who has access to information, it provides little insight into what authorized users are doing within the applications. Appsian enables you to know what your users are doing, what tables they are accessing, what changes are being made, and by whom. It provides a detailed report of user activity data and allows you to set up alerts when sensitive information or tables are accessed.

Identification of Irregularities

The ability to continuously monitor user activity across applications also allows Appsian to track each user to identify and compare authorizations within each department or business unit for any discrepancies. The solution sends a notification to the management team of any suspicious activity that needs further investigation. However, the lack of user monitoring in SAP GRC means that such irregularities go unnoticed.

Impact on Licensing Costs

It is well-known that SAP licenses do not come cheap. Additionally, SAP does not provide a clear view of user roles and licenses. This makes it difficult to understand the cost impact of granting new roles/licenses to users. Appsian’s GRC solution considers licensing costs when recommending the best role to grant users by attaching costs to authorized roles and suggesting a less costly role when available. This allows you to manage your SAP license costs better and avoid overprovisioning.

Appsian’s enhanced approach overcomes the limitations of traditional SAP GRC, enabling you to manage identities, access, authorizations, and risk across multiple ERP platforms. Schedule a demo with our ERP GRC specialists to learn more about our GRC capabilities.

Put the Appsian Security Platform to the Test

Schedule Your Demonstration and see how the Appsian Security Platform can be tailored to your organization’s unique objectives

Remote Access Security: How to Replicate the 9 to 5 Workday

By Esha Panda • December 23, 2021

Over the last two years, organizations had to move employees out of a secure office environment and provide them with access to corporate ERP applications from multiple remote locations — effectively creating an extensive remote and hybrid workforce. A recent report by Gartner predicts that 47% of knowledge workers will work remotely in 2022, compared to pre-pandemic levels of 27%. With this rise in hybrid working and network connections originating from outside the firewall, organizations are understandably prioritizing remote access security.

In this remote/hybrid work landscape, workers and organizations often struggle to replicate that 9 to 5 experience. An experience where employees commute to an office, sit at a desk, and securely access ERP systems behind the office firewall. The reality is that organizations end up facing the challenge of balancing securing ERP systems and critical data with the access demands of the hybrid workforce.

Let’s be clear about something: workers may work 9 to 5, but they have 24/7 access to your ERP applications. And just like you wouldn’t let employees have access to certain areas of a physical office (if it’s a big office space) at all times of the day and night, you shouldn’t grant them remote access to all areas of the ERP system any time they want. 

There isn’t a single technology that will secure remote access. Instead, organizations should leverage a variety of technologies that together provide the necessary remote access security when users are working “9 to 5” from home or other remote locations.

Implement Dynamic Access Controls 

Remote access security begins by giving users access to only the applications, transactions, and data needed to perform their jobs during the “9 to 5” workday. These dynamic access controls consider the different contexts of user access (i.e., location of access, time of request, device used, IP address, and others) to govern who can use specific applications, the types of transactions they can process, and when. For example, if you wouldn’t allow Ted from payroll to enter the office building at 1:00 AM to access employee bank account data when no one is around, why let him do it from home?  

Reauthenticate Users at the Data and Transaction Level

As we continue to follow Ted around his 9 to 5 workday in-office, he uses his security badge to access the accounting area. An area off-limits to most other employees. Essentially, Ted had to reauthenticate his identity before reaching his desk and executing a payroll run. Now that Ted is part of the hybrid workforce, it makes sense that he should reauthenticate his access with dynamic multifactor authentication (MFA) before changing sensitive data, like employee bank accounts, or running critical transactions, like payroll. Enforcing dynamic MFA allows organizations to implement challenges based on contextual attributes. For example, attributes like location, IP address, time, device type, etc. 

Gain Full Control of Data Access Using Dynamic Data Masking 

Controlling what information an employee can see is critical regardless of office location (on-premise or remote). For example, suppose Ted’s manager accesses his employee record to review his information or department settings. In that case, typically, his date of birth and social security number are on display. Data his manager doesn’t need to see to do their 9 to 5 job. Dynamic data masking leverages contextual access controls to ensure that sensitive data is only accessible by the people that need to see it to accomplish their job. Additional controls can ensure full or partial data masking. At the same time, click-to-view and MFA can create a record of data access for use in an audit. Dynamic Data Masking also means a hacker with compromised credentials will be unable to access or view sensitive data fields.   

Increase Visibility through User Activity Monitoring 

Even with remote access security in place, it’s vital that organizations understand who is accessing what, from where, and for what purpose. For example, a hacker compromises Ted’s credentials and starts accessing ERP applications outside of Ted’s regular 9 to 5 activity. With continuous monitoring of user behavior around data access and usage at a granular level, an organization can detect “Ted’s” suspicious activities and quickly apply an appropriate threat response. 

Appsian’s Approach to Remote Access Security  

As more employees take their 9 to 5 workday outside the confines of the corporate firewall and access ERP applications and data from nearly any location, Appsian can help organizations take a dynamic approach to remote access security. 

Contact Appsian today to learn how our context-aware access controls can anchor your remote access security policies and improve ERP data security for your remote teams. 

Put the Appsian Security Platform to the Test

Schedule Your Demonstration and see how the Appsian Security Platform can be tailored to your organization’s unique objectives

Request a Demo

Start your free demo

"Learn how you can reduce risk with rapid threat protection, audit response and access control. All from a single, comprehensive platform"

Trusted by hundreds of leading brands