Security policies allow companies to ensure compliance with data integrity, secrecy, availability and authenticity. Such policies are constantly being updated and scaled to keep up with changes to ongoing operations. When additional policies are added in compliance with guidelines – for example a software update or a DSAG audit, the policy must be compared. To date, this has required checks by hand. Since the Release 5.0 SAST SUITE offers solution, providing automatic identification and adoption of deltas where policies differ.
Identity and Access Management
General Data Protection Regulation (EU GDPR) – Ensure compliance with SAST SUITE
Since the new General Data Protection Regulation (EU GDPR) is fully effective, companies must now face new challenges with respect to protecting personal data.
To meet the guidelines under the GDPR, we can help with two modules of SAST SUITE in particular: SAST HCM Read Access Monitoring and SAST Superuser Management.
Handling Authorizations During an SAP Release Upgrade
After upgrading to a new SAP release, customers often face the challenge of using the SAP transaction SU25 to bring their authorizations up to speed, as well.
In today’s practical tip, Steffen Maltig shows you how to save up to 90% of the resources this normally requires.
You installed an SAP Note and suddenly your organizational levels were gone?
To help you avoid struggling with missing organizational level configurations in your next authorization rollout project, Sascha Heckmann has a practical tip on how to prevent the loss of these configurations in your authorization roles.
Audit or Penetration testing? Find your vulnerabilities before you get hurt!
To answer the question of which Security & Compliance check is right for you, we must first remember that the term “vulnerabilities” can refer to very different levels of your system landscape and thus refer to a number of attack vectors.
This ranges from system-side levels (e.g. operating system and network security) to the underlying database including the current parameterization of your SAP systems down to the authorizations required for operations and applications, including any SoD conflicts.
So, the first question is – how sure are you that you know where your vulnerabilities are? Continue reading
Automated SAP Authorization Management and System Security for 50 countries
Takeda’s twin objectives were to accelerate and simplify its authorization assignment process while deploying a tool that was simultaneously capable of providing vulnerability monitoring for its SAP backend worldwide. Continue reading
General Data Protection Regulation – is your protection in place?
The EU General Data Protection Regulation (EU GDPR) takes effect on May 25, 2018, and hardly a day goes by without some news about it – and that’s the way it should be! As demonstrated by a DSAG member survey of SAP users just a few weeks ago, only just over half of all the companies (53%) have a roadmap. To say nothing of full implementation of the new requirements.
Michael Muellner, Head of Security & Compliance at AKQUINET, discusses helps to make this topic accessible to you by building a bridge from the statutory requirements to steps in operations and concrete tips.
Are your SAP licensing costs really optimized?
Pressure is rising steadily for companies to keep costs down and information technology has not escaped this. In the SAP environment, licensing costs make up a particularly sizeable share of the overall IT costs and they are now being reviewed once again by many companies.
Our tip today will show you how to take the first step to reducing licensing costs yourself.
Do Security Notes Live Up to Their Name?
On every second Tuesday of each month, SAP releases new Security Notes. Many SAP administrators install these patches relatively quickly – but are they putting too much faith in the security they provide?
Very few customers know that security gaps can still be exploited.
You can’t come in here…
Practical tip: How you can easily prevent your SAP users from being inadvertently locked out.
The parameter “icf/reject_expired_passwords” is intended to prevent SAP users from being able to log in via “http” with an expired password. So far so good…