Red Teaming
With red teaming we put all your security measures and your security team to the test. The aim is to simulate real-life scenarios in order to activate the efficiency and effectiveness of your security measures and monitoring, but also the reaction of your employees and your security team, in order to learn and improve.
You and our team define the concrete goals, scope and conditions for the test and design a form of red teaming that suits your needs, with a strong focus on specifically identifying the points most important to you in testing and/or training.
Red Teaming with Simulation of a Threat Actor
With traditional red teaming we define the predominantly relevant threat actors from your risk and threat intelligence analysis and simulate those in one or more red team scenarios. Our basis for a standardised documentation and description of the planned activities is the MITRE ATT&CK framework.
Specialised Red Teaming Engagements
If you have experienced specific security incidents already or you are well prepared for advanced standard scenarios, we will work on new and unknown scenarios in our most specialized red team engagements to push your security team to its limits. Because there is always something new to learn.
Because of their duration and complexity, these specialised assessments are carried out according to the EU TIBER framework, which has been especially developed for complex red team assessments within the banking environment.
365 Red Teaming
If you want to stay up to date throughout the year, we suggest our 365 red teaming service. We monitor your systems 24/7 and either get active when new vulnerabilities become known or train your security measures regularly every year for newly discovered threat actors and scenarios.
Full-Scope Red Teaming
Red team engagements are not limited to IT systems. In full-scope red team engagements we will simulate full industrial espionage attacks involving IT security, physical security and social engineering. This is an ultimate endurance test for all your company's security measures in view of detection possibilities and the applying of fitting counter-reactions in attack situations.
Internal ISMS Audit 2025
As a company, we undergo regular audits of our ISMS (Information Security Management System). These audits are conducted by an external company to obtain an independent opinion on the functioning...
Future-Proofing Talents at the University of Applied Sciences in Hagenberg
As the cybersecurity industry can only remain strong with committed young talents, promoting knowledge is important to us. That is why our team members regularly give speaking engagements or lect...
BCM Exercise 2025
Effective emergency and crisis management helps prepare for worst-case scenarios. That's why, among other things, we regularly conduct simulations as part of our Business Continuity Management (BCM) p...
References & Case Studies
Energy 
The Pitfalls of Cross-Site Request Forgery
Energy
Two web applications were tested for a company in the energy sector. The focus was on attack options for internal and external accounts within the web applications.
Several cross-site request forgery vulnerabilities were identified during the test within the web applications. With CSRF attacks, commands can be executed in the context of the victim if the victim clicks on a manipulated link. This allows a CSRF attack to change an account password on both internal and external registered users. If successful, this would result in the victim's account being completely compromised.
To prevent CSRF attacks, it must be impossible to prepare a valid request to the web application in advance. This is usually ensured with a random value that changes with every call and is validated on the server side with every received request.
Health 
How Forgotten Functionalities Can Endanger Data Security
Health
A company in the healthcare sector wanted to subject its internal backup infrastructure to a security check. The goal of this test was to check the configuration of the services and the servers belonging to the backup infrastructure.
During the check, port 161/tcp was identified on which an SNMP endpoint was running. Additionally, it was possible to use the community string “public” to find out information about account names, the running services as well as the operating system. The identified operating system version was Microsoft Windows CE version 6.0 (Build 0). This embedded version of the Windows operating system was released in 2006 and has been end-of-life since 2022. An increased risk for this system was identified in connection with other open ports and associated vulnerabilities. Since this was concerning a disk management system, successful attacks could provide access to the company's sensitive data.
It was recommended to shut down services that are no longer in use. During penetration tests, we often find that some endpoints that were in use years ago are no longer being used, but still have the same configuration. If these endpoints are still used, for example to send information about the system to a monitoring application, the service must be secured to prevent third parties from reading the information. We also recommended keeping all systems up-to-date in order to neutralize known vulnerabilities via security patches. In this specific case, the accessibility of the services was additionally restricted at the network level to minimize the risk.
IT Service 
Re-Checks in Pentesting: The Key to Finding What You Missed
IT Service
A security recheck was carried out by us for a global corporation with focus on an application that visualizes complex data structures.
A penetration recheck (or retest) verifies that the security vulnerabilities identified during an initial penetration test have been fixed. After the company has made corrections, the testers check the same areas again and determine whether the previously exploited vulnerabilities are now secure. This recheck ensures that the remediation was effective and that new vulnerabilities were not inadvertently introduced. Rechecks are essential for maintaining security posture and compliance as they confirm that the risk level has been reduced. Without rechecks, unresolved vulnerabilities could persist, leaving systems unprotected and negating the goals and investments of the original security review.
After the initial recheck, the parts of the application that had no vulnerabilities in the previous penetration test were also examined. Several Reflected Cross-Site Scripting (XSS) vulnerabilities were identified, which would allow attackers to perform operations in the victim's context if a victim clicked on a manipulated link. In order to prevent injection vulnerabilities, such as XSS, it is recommended to verify any input to the application and to remove the special characters.