Skip to content

Service

Infrastructure and hardening

Your database is only as secure as the server it runs on.

The problem

Servers installed years ago with generic users, unnecessary services running, no OS patches and the same root password since day one. An audit flags them red; an attacker finds them first. And when the only server fails, there is no plan B.

How we work

  1. 1

    Assessment

    Configuration review against CIS benchmarks and Oracle recommendations: users, permissions, services, network, patches, logs.

  2. 2

    Hardening

    Controlled application of controls: SSH, sudo, firewall, SELinux or the AIX equivalent, auditing, credential rotation, OS patches.

  3. 3

    High availability

    Architecture with real redundancy: Data Guard, RAC, application clusters, load balancers, off-site backups.

  4. 4

    Continuity

    Disaster recovery plan with defined RTO/RPO and periodic failover tests.

Frequently asked questions

Can hardening break the application?

It can, if applied without testing. That is why we start in a non-production environment, document every control and apply it to production in agreed windows with rollback.

Do you still work with IBM AIX?

Yes. Many critical Oracle databases still run on Power/AIX. We administer it and, when it makes sense, plan the move to Linux.

Does it include penetration testing?

We do not perform offensive pentests. We do configuration assessment and hardening, and we can coordinate with your pentest provider to close findings.