×
[searchandfilter taxonomies="search"]

The Keys to Avoiding a Failed PeopleSoft SSO Project

By Scott Lavery • April 19, 2018

In a previous blog ‘Time is Money’ we discussed what lacking a PeopleSoft-integrated SSO is costing your organization.

By now, we all should fully understand what the recurring password recovery cycle is costing organizations in terms of lost end-user productivity and excessive calls to the IT help desk. Organizations can use a single sign-on (SSO), to establish a centralized authentication system that allows IT to manage support costs and efficiently perform password database provisioning. An SSO also greatly reduces user downtime associated with password reset and recovery.

Off-the-shelf SSO solutions DO NOT work with PeopleSoft

There are numerous vendors who promise that the same SSO that you implement across all of your enterprise applications will also work seamlessly in your PeopleSoft environment. Unfortunately, when it comes to implementing that off-the-shelf SSO in PeopleSoft (specifically) those projects are destined for failure. The reason being that off-the-shelf SSO solutions rely on SAML based technology as an identity federation standard – and there’s no native SAML support in PeopleSoft. Unaware of this fact, SSO vendors will assume that PeopleSoft supports SAML (similar to your other applications) and eventually hit a roadblock during implementation/testing. This complication typically results in the recommendation of added customizations and web server(s) in order to save your PeopleSoft environment from being alienated from the rest of your enterprise applications.

The downsides of fitting a square peg in a round hole

Off-the-shelf SSO solutions need to go through extensive customizations in order to have any communication with PeopleSoft. Firstly, organizations need to build extensive frameworks to integrate SAML based identity providers (ADFS, Shibboleth, etc.) with PeopleSoft using a reverse proxy configuration. These custom developments require procuring and setting up additional infrastructure (hardware, web server(s), etc.) – resulting in prolonged project timelines and budget overruns. Secondly, these customizations (once implemented) are fragile, difficult to troubleshoot and require constant intervention – especially during PeopleSoft updates.

PeopleSoft Single Sign-On – a square peg for a square hole

Organizations can save both time and money by opting for an integrated SSO, exclusively designed for PeopleSoft. For years, the demand for a native SSO utilizing SAML identity providers was a hot topic in the Oracle community – fortunately, this solution is now a reality. Being the only native SSO solution for PeopleSoft, PeopleSoft Single Sign-On by GreyHeller allows organizations to support SAML-based authentication technology without any customizations or additional infrastructure. PeopleSoft Single Sign-On eliminates the need for end-users to utilize multiple (weak and easy to remember, but easy to crack) passwords and empowers them to seamlessly transition between PeopleSoft applications using a single, strong login credential. It also empowers IT teams to centralize authentication management and makes it easy for them to provision password databases as employees come and go in the organization.

Once implemented, PeopleSoft Single Sign-On enables your employees to:

  • Authenticate PeopleSoft sessions via the leading identity providers such as: ADFS/Office 365, Shibboleth, or OKTA
  • Access PeopleSoft via deep link navigation (sent by email or other enterprise communication channels)
  • Utilize PeopleSoft links from a 3rd party portal

When it comes to your enterprise applications, opt for the peg that fits rather than hammering the one that doesn’t into a shape that partially fits! To learn more – request a live demo of PeopleSoft Single Sign-On with an Appsian Solutions Expert email us at [email protected].

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

Now Introducing PeopleSoft Security Analytics (Preview Available)

By Scott Lavery • February 5, 2018

GreyHeller is proud to announce the arrival of

PeopleSoft Security Analytics

 

Next-generation software providing actionable insights into how your PeopleSoft data is being accessed – where and by whom.

Enterprise data security professionals understand that identifying potential cyber-crime hinges on one’s ability to spot trends within data. After all, your system isn’t filled with red lasers (think Mission Impossible) that once tripped, sets off a series of blaring alarms. Successful cyber criminals have all the time in the world to formulate their strategy, gather what they need to access your system, and take what they want! Unfortunately, you don’t have all the time in the world to stop them!

GreyHeller’s PeopleSoft Security Analytics software visualizes the data trends that tell the story of how, where, and by whom your data is being accessed:

  • Access volume by IP
  • Geographic location of access
  • Access trends by data sensitivity level
  • Access trends by user privilege level

Data visualization solutions are essential for understanding the granular details that can be the difference between a secure system and a catastrophic data breach. In order to help you be proactive before you’re forced to be reactive – we are providing a sneak peek demonstration at PeopleSoft Security Analytics:

 Wednesday February 14th at 1:00 PM CST (11AM PST.)

Register Today

 

Can’t wait until February 14th? Demonstrations are available with advanced notice. To schedule your demonstration, GO HERE and a solutions representative will be in touch!

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

PeopleSoft and GDPR: 2018’s Elephant in the Room

By Scott Lavery • January 9, 2018

Who does GDPR Affect?

  • Does your organization store or process European Union (EU) consumer data?
  • Do you have employees that are citizens of any EU countries?

If you answered ‘yes’ to either of these questions, you’ve probably heard of the European Union’s General Data Protection Regulation (GDPR). GDPR is a regulatory guideline that protects and empowers the information integrity of European citizens. The introduction of this regulation gives citizens of European Union countries discretion over how their personal data should or shouldn’t be used, processed or shared. In addition, GDPR’s introduction calls for stringent compliance with offenders facing steep financial penalties (Up to €20 million, or 4% of the worldwide annual revenue of the prior financial year, whichever is higher.)

Specific articles under GDPR’s Compliance Guidelines pose challenges to organizations leveraging PeopleSoft:

Article 15

“The data subject shall have the right to obtain from the controller confirmation as to whether or not personal data concerning him or her are being processed, and, where that is the case, access to the personal data and purposes, recipients, time period…”  

Challenge:

  • PeopleSoft consists of hundreds of pages that contain personal data processed within them
  • PeopleSoft does not have the means to track all of the instances that a person’s personal data is accessed – let alone tying it to who accessed it, when, and where. This makes capturing access data for even one page extremely labor intensive.
  • Because any data subject can request an audit, this means that organizations have to be ready to respond to dozens or even hundreds of requests
  • PeopleSoft does not allow for masking rules that provide control over how personal data is processed, whereas Appsian can both control and log all access by the processor to an individual’s personal data.

Article 33

“In the case of a personal data breach, the controller shall without undue delay and, where feasible, not later than 72 hours after having become aware of it, notify the personal data breach to the supervisory authority.”  

Challenge:

  • Identifying a personal data breach and aligning it to the people impacted is a difficult and manual process, often requiring weeks of analysis. Without a monitoring and logging solution like Appsian’s Application Security Platform, it is difficult or (in some cases) impossible to meet this requirement.

Article 35

“The controller shall, prior to the processing, carry out an assessment of the impact of the envisaged processing operations on the protection of personal data.”

Challenge:

  • Without a product like the Application Security Platform, which applies controls, measures usage, and helps identify breaches, the assessment would need to involve every key stakeholder in the organization, analyzing all access by users of the hundreds of pages in PeopleSoft with sensitive data. By centrally capturing and controlling this access, the Application Security Platform rules are sufficient for reporting what is already in place.

Time to Establish your GDPR Compliance Plan:

No matter where your organization resides in the world, if you handle any information for EU citizens, you must take steps to ensure your compliance. As stated above, non-compliance penalties are severe.

The larger the volume of PII, the more complex compliance gets. Since GDPR’s enforcement is set to begin starting this May, organizations must be in motion toward a compliance plan.  In case you are behind or are evaluating your next move – consider these (3) steps:

  • Step one – Establish data whereabouts – Identify data locations across your disparate systems and business entities
  • Step two – Put data governance in place – It is imperative to lay out guidelines and policies for appropriate and authorized data access
  • Step three – Prepare for optimum information security – Data breach response has been thrust into the spotlight and a detailed system of alerting and response objectives is mission critical. A data breach can cost your organization millions of dollars in GDPR fines (before the actual clean-up costs.)

Establishing standards and guidelines around data access is key:

You can start with identifying, managing and tagging safe access locations. To establish compliance without compromising the convenience of mobility, you can identify devices, along with establish multi-factor authentication solutions to ensure PII cannot be easily accessed. These solutions are not native to PeopleSoft.

Enhancing how you monitor and log access is key:

Your PeopleSoft environment automatically captures and logs system access information on a broad level. This enables you to go back and look into the details if a data breach occurs, but while complying with GDPR (where you have to report a breach within 72 hours), that’s not going to be an ideal approach or solution. Since no one is constantly monitoring your security log, if or when you notice the breach it might already be too late. Even with good intentions, you could have run out of time before you were even made aware of a threat.

How Appsian Application Security Platform Can Solve these Challenges:

Appsian’s Application Security Platform enables you to overcome these challenges by employing solutions for multi-factor authentication, location/privilege-based access, enhanced logging, and intrusion response. By layering these solutions within your PeopleSoft applications, you can ensure that the stringent articles of GDPR compliance will not keep you up at night; as these contextually aware solutions are designed to give you maximum influence over what data is accessed, by whom, and how it is used. In addition, incident response solutions ensure that you are on top of any potential threats and ready for any potential compliance audits.

We are here to answer any questions you may have – Get a free security consultation for GDPR compliance 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

Time is Money: What a lack of PeopleSoft Integrated SSO is costing your organization

By Scott Lavery • October 17, 2017

In our blog this past June we discussed the merits of utilizing SAML as a protocol for sharing a person’s identity between systems. More specifically, we addressed how SAML (leveraging ADFS and Shibboleth as identity providers) can be used for controlling access to your systems, providing a single control point for authentication in your organization. These benefits are why GreyHeller developed

SAML Single Signon for PeopleSoft:

  • 1 password vs. multiple passwords (w/ different expirations and controls)
  • Reduction in lost, stolen, or weak passwords
  • Improved adoption of Fluid pages and overall mobility

Now that we’ve addressed the benefits – we will now discuss the consequences of not utilizing SSO

While expensive, embarrassing, and overall damaging to your reputation, security breaches are more likely to capture the headlines. However, there are opportunity costs that (while not as headline-grabbing as a breach) you should be keenly aware of:

1) Over 50% of support calls are generally related to password resets

Every IT person can relate to this. The stopping and starting of your daily objectives due to constant user interruptions, all needing the same thing – a password reset or an unlocking of an account due to too many incorrect login attempts.

2) Loss of productivity PLUS the troubleshooting of end-user authentication issues can take up to 30 minutes 

Now that we know what IT’s biggest time waster is, lets break down that lost time. If your user is locked out of their account, they are useless – merely sitting at their desk waiting to be rescued. This is lost productivity that can be costly if aggregated across the organization throughout the year. The 30 minute time loss includes:

  • Time spent attempting to get into the system
  • Productivity loss on the part of the user waiting for their access
  • The help desk administrator’s time spent troubleshooting the issue

Given that (on average) every user in your organization is requesting (1) password reset each month – this lost productivity can be staggering.

3) Higher Education institutions are the most susceptible to this waste 

According to a 2014 Forrester study of one large US-based university, “the university’s users completed an average of nearly 8,000 password resets per month and that nearly 50% of users requesting a password reset could not complete that action via self-service.” That is 4,000 individually executed password resets each month!

Considering the productivity loss for IT (chasing down password issues) Forrester Research went on to state “the average help desk labor cost for a single password reset is about $70.” Does this sound like an efficient use of valuable budget to you?

Your time and budget are too important to be wasted on password management. If you’re ready to learn more about GreyHeller’s PeopleSoft Single Signon Solution – Request 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

October is National Cyber Security Awareness Month… and it couldn’t have come sooner!

By Scott Lavery • October 1, 2017
In honor of October being National Cyber Security Awareness Month, we ask you to consider this scenario:

How Cyber-Criminals are Stealing Direct Deposit Information

Bob is in a hurry, running from meeting to meeting and one day he receives an email from his organization’s “PeopleSoft Admin” claiming his password is expiring. What does Bob do? Well, given he checks his paystubs every two weeks, he just adjusted his medical benefits, and made a revision to his W-4 – he “confirms” his old password (to create a new one) so he doesn’t run the risk of getting locked out of his account. Bob has now become the latest spear-phishing victim. Sadly, the email from the “PeopleSoft Admin” was actually coming from a cyber-criminal using a targeted phishing email to dupe Bob into surrendering his PeopleSoft credential. Now that our cyber-criminal has Bob’s information, they immediately log into Bob’s payroll account, change his direct deposit destination, and wait until payday. Once payday arrives, they get Bob’s direct deposit, log back in to Bob’s account, change Bob’s direct deposit information back (essentially erasing their tracks), and leave Bob to wonder why his paycheck has not been deposited. Bob has no choice but to call HR so they can begin the painstaking forensic process of unraveling the mystery of Bob’s disappearing paycheck.

Data Breaches on the Rise

According to Verizon’s 2017 Data Breach Investigation Report, “81% of hacking-related breaches leveraged either stolen and/or weak passwords.” Rather than breaking in through the door or windows, the intruders are stealing keys and guessing the passwords of your users – and erasing their tracks as they leave with your data. Organizations are foolish to think that focusing their resources solely on powerful firewalls will keep their data safe. With 81% of hacking-related breaches using valid passwords – the challenge is about protecting your belongings when the robber is already in your house. Phishing and spear phishing tactics often play a significant role in these malicious acts. Users being asked to “reset” or “verify” their passwords with authentic-looking emails have proven to be a successful means for attaining credentials. The level of sophistication of phishing and spear phishing emails is being raised daily, and given the pervasive use of mobile devices for accessing ERP applications, cyber criminals know that mobile users can often be the most vulnerable. In addition, with PeopleSoft users’ continued adoption of Fluid pages (seeking an optimized mobile UI) the problem will only get worse. 2017 has been an especially challenging year for IT security professionals. Consider these findings from Gemalto’s First Half of 2017 Breach Level Index Report:
  • Nearly 2 Billion – Records Breached in First Half of 2017
  • 918 – Number of Breach Incidents in First Half of 2017
  • 164% – % increase of compromised records in first half of 2017, compared to the last half of 2016
The most vulnerable industries? Healthcare (25% of breaches), Financial Services (14% of breaches), and Higher Education (13% of breaches.) The Higher Education industry being so susceptible to breaches may come as a surprise, but it shouldn’t when you consider that the vast majority of users (students) have (according to Gemalto’s report) “[a mix of] varying degrees of technical skills and curiosity.” At GreyHeller, we are constantly speaking to organizations after a destructive security breach as occurred. Evaluating the mess created and seeking solutions to ensure the past doesn’t repeat itself. Which is why, for National Cyber Security Awareness month – we encourage you to ask yourself the question: Is my organization truly prepared if cyber criminals attain valid user credentials? Are my belongings safe if the robber is already in my house? We invite you to participate in the following sessions, developed to demonstrate solutions that combat malicious activity from within your PeopleSoft environment and serve to keep your PeopleSoft applications phish-proof! Thursday October 19th – Demo of GreyHeller’s PeopleSoft Single Sign On solution (SSO via ADFS and Microsoft 365)

Click Here To Register

Tuesday October 26th – Demo of GreyHeller’s Layered Security Platform – ERP Firewall (solutions for data loss prevention, intrusion prevention, and incident response)

Click Here To Register

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

Event Mapping in PeopleTools 8.56

By Chris Heller • September 17, 2017

What it is?

Event Mapping is a new subcomponent of the Related Content Framework. PeopleTools released Event Mapping with version 8.55. What makes it relevant today is enhancements for 8.56.

Imagine this scenario:

A functional user approaches you with changes he or she would like you to make to a PeopleSoft page. These changes include hiding a couple of fields and changing some labels. For the most part, this is a simple request, but you hesitate to accept the request. Why? Because the user just asked you to modify a delivered definition and you know that you will spend the rest of your PeopleSoft life paying for any simple change you make today.

Because there is business value (and you prefer to remain employed), you choose to implement the requested changes. But you ask yourself, how can I make these changes while minimizing upgrade impact? Historically speaking, a good developer, recognizing that these changes are possible through PeopleCode, would create a FUNCLIB or Application Class to hold custom code, and then call that reusable definition from the appropriate location within the delivered event PeopleCode. With the introduction of Event Mapping in PeopleTools 8.55, we now have a new option: we can map an Application Class event handler into a delivered PeopleCode event. This is a configuration that won’t dirty your compare reports. Since your code is no longer merged into Oracle’s code, your changes remain after applying updates.

What is new for 8.56?

PeopleTools 8.56 introduces the following long awaited enhancements to 8.56:

  • You can now configure multiple handlers for the same event,
  • PeopleTools exposed the PageActivate event, which is important for some scenarios to work properly,
  • Event mapping now supports the Component Record Field FieldChange event, and
  • Event mapping works in Component Interfaces (technically arrived in 8.55.09).

How are developers using this new feature?

The most obvious use cases involve changing labels and hiding fields. However, every component customization should be reviewed through the lens of Event Mapping. PS WebSolutions is using Event Mapping with their clients to make the address change effective date display only.

Probably one of the most exciting enhancements to Event Mapping is that it now works with Fluid. Technically, it has been supported on Fluid since its initial release, but demonstrated reliability issues until 8.55.15. What makes Fluid Event Mapping so compelling is that, with Fluid, everything is a component. This includes Homepages, Fluid forms builder, and so on. Logesh Balasubramaniam, from Presence of IT, is using Event Mapping to enhance forms created by the Fluid Forms Builder. Colten Fischer is using Event Mapping to send administrators to a classic homepage from the Fluid homepage. Some GreyHeller customers are using Event Mapping to extend Personal Details to collect additional attributes about employees.

What use cases should I avoid?

Many PeopleCode customizations exist to change business logic. These customizations often require changes to reside somewhere in the middle of an existing event. Event mapping only allows for Pre and Post processing. There are no “inject in the middle” or “replace” options. With that in mind, any PeopleCode change that can’t be categorized as pre or post processing is not a candidate for Event Mapping.

Are there any concerns with Event Mapping?

Yes. One concern is lack of lifecycle management support. When patching or updating a component, there is no indication that an event handler may exist in the event mapping framework. Theoretically speaking, that is the point. Event mapping is supposed to simplify lifecycle management, not create additional tasks. The reality, however, is that any change to a component may impact event mapping PeopleCode. If Oracle removes a field from a page, for example, that field is no longer in the component buffer. Any PeopleCode that references that field will fail at runtime. At this time, Oracle offers no tools to make you aware of this. Nor does it provide any indication that a component has event mapping PeopleCode.

Another concern I have is that code that doesn’t behave as expected. Consider this example:

A user logs a service request because a component is not behaving properly. Based on the timing of the improper behavior, you identify that the errant PeopleCode is in the RowInit event of a level 1 rowset. Armed with that knowledge, you open the RowInit PeopleCode of the component, review the code, and everything looks normal. In fact, there is nothing in that code that would cause the behavior you are seeing in the component. Now what?

If you are like me, you will scratch your head, probably burn a few more hours on it, and then spend even longer digging through a PeopleCode trace, only to discover that some App Class is being invoked even though there is no indication of that App Class in the RowInit event. That App Class is configured into the event through event mapping. Users of dynamic languages are quite familiar with this scenario as the impact is akin to something known as Monkey Patching or Duck Punching. We expect a single source for the truth, but what we discover is there are multiple versions, and it is the last version that wins.

Even with these concerns, do I still use and recommend event mapping? You bet! Event mapping is one of the best features introduced to PeopleTools.

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

Why is Optimizing PeopleSoft for Accessibility so difficult?

By Chris Heller • September 10, 2017

If you’re responsible for Accessibility at your organization, you have a lot of responsibilities:  facilities, training, technology, documentation, note taking, testing, and in the case of higher education – all of the supporting student and employee systems.  And, PeopleSoft is just one of those areas of responsibility – but it’s also something that is always a challenge – and your IT group struggles to meet your requirements.

This blog entry is intended to describe why PeopleSoft is more difficult to change than some of your other systems – as opposed to your website (for example.)

So, what makes PeopleSoft unique?  In a nutshell, it comes down to these 3 things:

  • PeopleSoft has thousands of Complex Use Cases (business functions it supports)
  • PeopleSoft Generates HTML Programmatically
  • PeopleSoft’s development tools don’t have a mechanism for addressing Accessibility Issues or optimizing user experience for assistive technologies

PeopleSoft Use Cases

A standard PeopleSoft environment has between 6,000 and 12,000 pages.  This is because, as an ERP system, there is a lot of data to be captured and managed – spanning all key areas of your HCM and Financial systems.  Institutions of higher education offer additional complexity as PeopleSoft’s use cases cover students enrolling in classes, in addition to the standard use cases found in commercial organizations (ex. employees enrolling in benefits, entering time and expenses, as well as back-office functions to support these processes.)  This creates a high bar for optimizing behavior for all of the assistive technologies available; spanning the wide range of users who routinely access those systems.

PeopleSoft’s Application Architecture

PeopleSoft is what’s called a “definitional development architecture.”  This means that, for the most part, developers use a Graphical User Interface (GUI) to define how the user interface will look instead of writing the code directly.  It has the benefit of streamlining the development process, but also has a significant downside from an accessibility perspective – in that the HTML is generated from these definitions.

What does this mean?  From your perspective, it means that your PeopleSoft development team does not have the ability to change how PeopleSoft generates the HTML.  All of the issues that you may see – such as repeated labels, lack of appropriate ARIA tags, the fact that the HTML is complex and does not follow a semantic structure (relying on CSS) – can not be changed by your PeopleSoft team because is generated by code developed by Oracle in a manner that cannot be modified easily by anybody outside of Oracle.

So, what can I do?

This architecture is why GreyHeller created our UX product (PeopleUX), which intercepts PeopleSoft’s HTML to apply rules to it and give your PeopleSoft team the hooks to change how PeopleSoft generates HTML for given transactions.  The rules address the vast majority of accessibility issues across the 6,000 or more PeopleSoft transactions, while the control allows you to optimize the most complicated use cases in the ways that you would like.

PeopleUX Features

PeopleUX delivers platform-wide consumerization of PeopleSoft (for smartphone, tablet, and desktop), optimizing all PeopleSoft pages without customizations. To take a closer look at how PeopleUX optimizes PeopleSoft to accommodate for a wide variety of disabilities requiring assistive technologies (blindness/low vision, color blindness, limited mobility, and cognitive disabilities) you can view our PeopleUX Features Datasheet HERE. We would also encourage you schedule a customized 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

Adopting Cloud: Fact or Myth – “Hybrid as a Best Practice”

By Scott Lavery • September 6, 2017

Stop me if you’ve heard this one…

Do you want to get the most from your ERP? Then you must move to the cloud. Your bottom line will appreciate it, your users will appreciate it, and your IT security team will appreciate it.” Sounds like a pretty good deal, right?

In our upcoming blog series, we examine some of the most popular cloud adoption myths. By myths, we mean that there is a flipside to every story – and the cloud is no exception.

It’s important to note that we are not “anti-cloud.” Cloud HR functions serve an important purpose, and while there are undoubtedly benefits to moving some functions to the cloud –  it’s important to not get too caught up in the hype.  So, before you undergo a traumatic “rip and replace” of your core ERP and trade it in for that shiny cloud product – we invite you to stop and take a quick breath.

Hybrid as a Best Practice

From Gartner in their 2016 report, “…the extreme of having nothing cloud-based will largely disappear with Hybrid being the most common usage of the cloud.” As organizations determine specific business cases that are best served by a cloud solution, the corporate “no cloud” policy will become increasingly obsolete. This approach is fully supported by GreyHeller and we contend that using specific business cases to guide your cloud migration initiatives is a best practice. With that being said, the business case for a “rip and replace” of your core HR function is rare and can come with many negative implications. This blog series serves to examine just some of those implications and discuss the negative consequences that can occur.

Stay tuned as we release additional blogs in our upcoming “Adopting Cloud: Fact or Myth” blog series, where we address the truths behind:

  • Cloud as a platform for Innovation
  • Improving security via the cloud
  • Offloading operational costs
  • Market trends towards cloud adoption

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

Don’t let the DOJ take your foot off the “accessibility compliance” gas pedal

By Chris Heller • August 22, 2017

We are disheartened by the recent publication of the Trump Administration’s Unified Agenda of Regulatory and Deregulatory Actions which changed the status of its web accessibility rule-making processes related to the Americans with Disabilities Act (ADA) to “inactive.”

What does this mean and why are we – and many of our friends in Higher Education – so disheartened? From the Seyfarth ADA Title III News & Insights Blog:

In the absence of website regulations, the courts are filling the void with a patchwork of decisions that often conflict with one another. The uncertain legal landscape has fueled a surge of lawsuits and demand letters filed and sent on behalf of individuals with disabilities alleging that the websites of thousands of public accommodations are not accessible.

Based on all of this, we believe that institutions should carefully consider their ADA compliance profile for PeopleSoft self-service systems. With the lack of clear regulations, your institution could be at risk.

We fully subscribe to our customer – University of Minnesota’s – position that Accessibility is a diversity issues. Our recent blog – University of Minnesota made PeopleSoft truly accessible. Here’s how.

Lastly, we encourage you to be proactive before you’re forced to be reactive – preview GreyHeller’s solutions for ADA compliance and UX modernization – PeopleMobile/PeopleUX. Contact us to request 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

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