OCG with ❤️ - Our Advent Special 2025
Doing good together during the Advent season
For us, the Advent season is a time of togetherness, gratitude and small gestures that can make a big difference. That is why we have created something special this year:
OCG with a heart – our Advent special,
where we do good every Sunday in Advent.
👉 Curious now?
Follow our Advent campaigns on social media and be there live when we share a new good deed every Sunday:
LinkedIn: @oxford-computer-group-gmbh
Instagram: @oxfordcomputergroup
X: @OCGErding
We would be delighted if you would follow us there and join us in bringing good into the world.
We wish you a wonderful and reflective Advent season!
IDABUS Use Cases:
1. secure initial password - more security and control in onboarding
A protected initial password is crucial for a secure start for new employees. IDABUS supports you with clear processes and transparent tracking.
Key points
– No plain text password in emails or password letters
– Time-limited access for the manager
– Overview of all new additions with initial password
– Implementation without additional development effort
– Log of who last saw the password
How it works
The service desk gives the manager access for a few days. The manager receives an email with a link to the user and can find the password in the onboarding area in
Realisation in IDABUS
Tags for initial password, fields for controlling the access time, wizard for displaying the password, report for authorised access, workflow for resetting and triggers for changes.
2. attack on the Active Directory - IDABUS recognises suspicious changes immediately
What is it all about?
If a hacker gains access to the Active Directory, they can cause a great deal of damage with just a few authorisations. It is particularly dangerous if the attacker has already gained
Typical signs of an attack:
- Deactivated or expired AD accounts suddenly become active again.
This is unusual – such accounts normally remain permanently blocked. - Unmanaged admin groups are changed.
Attackers try to gain hidden additional rights in this way.
How IDABUS recognises such attacks:
IDABUS continuously compares the target status from the IAM with the actual status in the AD.
If something does not match, an alarm is triggered immediately.
One example:
- Target in IDABUS: User = deactivated
- Is in AD: Account = activated
→ Mismatch! IDABUS reacts automatically.
What happens in the event of an alarm?
Depending on the configuration, measures can be triggered automatically:
- Notification of the security team
- Starting a workflow
- Creating a ServiceNow ticket
- or automatic defence measures
Technical basis in IDABUS:
- Synchronisation and attribute flow
- XPath logic for ‘active disabled user’
- Trigger: detect active disabled users
- Workflow: notify when active disabled user is detected
Why is this important?
Such automatic detections prevent attackers from reactivating accounts or changing groups unnoticed. IDABUS thus actively protects against silent manipulation of the Active Directory.
