367checks per SAP system
SAP · HANA · Linux · Windowsplus cloud services: SCC, BTP, CPI
EUhosted with data in the EU
DE · EN · PLinterface in three languages
Scope
What exactly is checked.
The full structure of the platform: monitoring areas, security checks and compliance standards.
NexGuard · Monitoring — 367 checks per SAP system
Availability and processesInstances, work processes, RFC reachability, database connection – measured every minute.
Jobs, spool and locksCancelled jobs, backlogs in print queues, lock entries, long-running transactions.
InterfacesStuck queues and failed handovers between systems – before the business notices.
HANA and databaseData and log backups with the age of the last one, disk usage, log volumes, replication, out-of-memory events.
PerformanceCPU, response times, memory and swap – with history from 4 hours to 30 days and thresholds per system.
CertificatesExpiry dates of SSL and SNC certificates – with an alert before they lapse. Public TLS certificates are being shortened step by step to 47 days by 2029.
Beyond SAPLinux servers (104 checks) and Windows (67) as well as SAP cloud services: Cloud Connector, BTP, CPI.
NexShield · Security — six check areas
SAP identityStandard users (SAP*, DDIC) across all clients, password rules, dialog accounts that should not be dialog accounts.
HardeningProfile parameters compared against the baseline, gateway and message server ACLs, transport configuration.
AuthorisationsSAP_ALL and SAP_NEW assignments, critical combinations, RFC destinations with stored passwords of privileged users.
Security audit logWhether it runs at all, what it records – and unusual events, such as series of failed logons from outside.
Vulnerabilities (CVE)Daily comparison of OS packages and kernels against known gaps; ordered by real-world risk (KEV, EPSS), not just by score.
Change recordsWho changed what in the configuration – documented in a form an audit accepts.
Compliance — 14 standards in one catalogue
GermanyKRITIS (BSIG)BSI IT-GrundschutzB3S Medizinische Versorgung§ 391 SGB VDSAG-Prüfleitfaden S/4HANA
European UnionNIS2GDPR – technical measures (TOM)
PolandKSC (uKSC)KNF Rekomendacja DKRI
One piece of evidence counts towards several standards: a control measured once feeds every standard that requires it. For each control the state is visible – proven, open or not measured.
Common questions
What customers want to know before starting.
Our HANA runs on its own server – two agents?No. One agent on the SAP application server reads the HANA over the network.
Does this work with RISE or a hosting provider?With a hoster or in the cloud the agent runs on the application server as usual. Under RISE, SAP operates the OS and database itself – our agent then runs on a server of yours and checks the application layer via RFC: jobs, interfaces, performance, authorisations, security.
What happens when an alert fires?With our service we react within the agreed time. Without it, your team receives the message – by e-mail or Microsoft Teams – with the cause, the affected system and the concrete next step.
Does Nexbase see our data?Only the measurements of your systems, and only if you have engaged us. Business data never leaves your system.
How do we get out again?Uninstall the agent (three commands) and your access is deleted. Export your reports as PDF beforehand.