Resources
IT Security Glossary
Kerberoasting, TLPT, prompt injection, or NIS2 – IT security is full of technical terms and acronyms. Our IT security glossary explains the most important terms from penetration testing, attack techniques, defense, and regulation – concisely, clearly, and accurately. Each entry also links to the related Rootsektor page.
About this glossary
IT security glossary: technical terms explained clearly
Anyone dealing with penetration tests, threat detection, or new legal obligations quickly runs into technical jargon, acronyms, and the names of laws. This glossary – your compact cybersecurity dictionary – translates them into plain language, from pentest terms such as scope and retest to regulations such as NIS2 and DORA. Each entry explains in a few sentences what a term means and why it matters for the security of your organization.
The entries are sorted alphabetically. For terms rooted in German law or German institutions – such as the BSI, KRITIS, or the German Trade Secrets Act – the German original is given as well, so you can recognize it in German reports, contracts, and regulations. Each term links to a page with a more detailed explanation, and the link at the end of an entry takes you to the matching Rootsektor page – usually the service that addresses the topic in practice.
Terms from A to Z
A
-
Active Directory (AD)
Active Directory is Microsoft’s directory service: in Windows networks, it centrally manages user accounts, groups, computers, and permissions and handles authentication, usually via Kerberos. Because AD holds the keys to the entire network, it is one of attackers’ most important targets: whoever obtains domain admin rights effectively controls the whole environment. Permissions that have grown over the years, outdated protocols, and weak service account passwords often open up attack paths that go unnoticed.
Learn more about Active Directory (AD) Related service: Active Directory Assessment
-
Attack Path
An attack path is the chain of individual steps an attacker takes to get from an initial point of entry to a valuable target – for example, from a compromised workstation via a service account with excessive permissions to domain admin. Often, each individual vulnerability looks harmless on its own; only the combination makes it dangerous. Penetration tests and Active Directory assessments make such paths visible so that you can break them at the most effective point.
Learn more about Attack Path Related service: Active Directory Assessment
-
Attack Surface
The attack surface includes every point where an attacker can strike – from publicly accessible servers, web applications, and interfaces to cloud services and VPN access to employees who can be reached by email or phone. Every new service, every forgotten test environment, and every additional user account expands it. The goal is to know your own attack surface completely, switch off anything unnecessary, and secure the rest in a targeted way.
Learn more about Attack Surface Related service: OSINT Assessment
B
-
Black-Box Testing
In black-box testing, the testing team receives hardly any information up front – often just a company name, a URL, or an IP address range. The team proceeds like an external attacker without insider knowledge and shows realistically what is visible and vulnerable from the outside. The downside: part of the testing time goes into information gathering, and deeper vulnerabilities are more likely to remain undetected than in a gray-box or white-box test.
Learn more about Black-Box Testing Related service: Penetration Testing
-
Blue Team
The blue team is the defending side: it monitors systems, detects attacks, responds to security incidents, and continuously improves protective measures. Depending on the organization, this includes the internal IT security team, a security operations center (SOC), or external service providers. In red teaming exercises, the blue team is the opponent whose detection and response capabilities are put to the test.
Learn more about Blue Team Related service: Red Teaming & APT Simulation
-
Brute-Force Attack
In a brute-force attack, an attacker systematically – and usually automatically – tries combinations until a password, PIN, or key works. Online, the attack targets login pages and services such as VPN or RDP; offline, it targets stolen password hashes, which can be cracked very quickly with powerful hardware. Effective countermeasures include long passwords, multi-factor authentication, rate limiting, and monitoring of failed logins.
Learn more about Brute-Force Attack Related service: Web Applications & Online Shops
-
BSI (German Federal Office for Information Security)
The BSI (Bundesamt für Sicherheit in der Informationstechnik), based in Bonn, is Germany’s federal cybersecurity authority. It publishes standards and recommendations such as the IT-Grundschutz Compendium, warns of current threats, and is the central point of contact for operators of critical infrastructure and for companies covered by NIS2. With its guide “Durchführungskonzept für Penetrationstests” (implementation concept for penetration tests), the BSI has also described a framework for planning and conducting pentests, which we use as a guide.
Learn more about BSI (German Federal Office for Information Security) Related service: Penetration Testing
-
BSI IT-Grundschutz
BSI IT-Grundschutz is a methodology from Germany’s Federal Office for Information Security that organizations use to systematically establish and maintain an appropriate level of security. Its core elements are BSI Standards 200-1 to 200-4 and the IT-Grundschutz Compendium, with modules for typical processes, applications, and systems. Government agencies and public institutions in particular work with it; ISO 27001 certification based on IT-Grundschutz is also possible. The BSI is currently migrating IT-Grundschutz step by step to “Grundschutz++”; the existing IT-Grundschutz remains usable during a transition period of several years.
Learn more about BSI IT-Grundschutz Related service: Public Sector & Education
C
-
Credential Stuffing
In credential stuffing, attackers automatically try combinations of email addresses and passwords stolen in earlier data breaches on other services. The attack works because many people reuse the same password – online shops, customer accounts, and cloud services are particularly affected. Protection comes from multi-factor authentication, bot detection, rate limiting, and monitoring whether your company’s credentials turn up on the dark web.
Learn more about Credential Stuffing Related service: Dark Web Monitoring
-
CSRF (Cross-Site Request Forgery)
With CSRF, an attacker tricks the browser of a logged-in user into unknowingly performing an action in a web application – such as a bank transfer, a password change, or the creation of an administrator account. This is possible because the browser automatically sends session cookies along when a crafted website triggers a request to the application. Countermeasures include anti-CSRF tokens, the SameSite cookie attribute, and re-confirmation of critical actions.
Learn more about CSRF (Cross-Site Request Forgery) Related service: Web Applications & Online Shops
-
CVE (Common Vulnerabilities and Exposures)
CVE is a globally used system that assigns a unique identifier to publicly known vulnerabilities – for example, CVE-2021-44228 for the Log4Shell vulnerability in the Java library Log4j. Thanks to these identifiers, vendors, security teams, and scanners can refer unambiguously to the same vulnerability. The number alone says nothing about severity; a CVSS score is usually provided for that.
Learn more about CVE (Common Vulnerabilities and Exposures) Related service: Vulnerability Assessment
-
CVSS (Common Vulnerability Scoring System)
CVSS is an open standard for rating the severity of a vulnerability on a scale from 0.0 to 10.0. The score takes into account factors such as the attack vector, complexity, required privileges, and the impact on confidentiality, integrity, and availability; version 4.0 has been available since 2023. We rate the findings in our pentest reports using CVSS and also put them into the context of your organization.
Learn more about CVSS (Common Vulnerability Scoring System) Related service: Penetration Testing
-
Cyber Resilience Act (CRA)
The Cyber Resilience Act (Regulation (EU) 2024/2847) sets mandatory cybersecurity requirements for products with digital elements – from connected devices to software placed on the EU market. Manufacturers must build in security from the development stage, handle vulnerabilities throughout the entire support period, and report actively exploited vulnerabilities. The obligations apply in stages; for many manufacturers, regular security testing and a software bill of materials (SBOM) thus become mandatory tasks.
Learn more about Cyber Resilience Act (CRA) Related service: Code Review & Reverse Engineering
D
-
Dark Web (Darknet)
The dark web refers to parts of the internet that can only be accessed with special software such as the Tor Browser and that conceal users’ identities. Besides legitimate uses – such as protecting journalists in authoritarian states – these areas serve as marketplaces for stolen credentials, customer data, malware, and access to compromised corporate networks. If you find out early that your data is being traded there, you can change passwords and prevent attacks before they happen.
Learn more about Dark Web (Darknet) Related service: Dark Web Monitoring
-
DAST (Dynamic Application Security Testing)
DAST tests a running application from the outside by sending deliberately manipulated requests and analyzing the responses – without access to the source code. This uncovers vulnerabilities such as injection flaws, misconfigurations, or missing security headers in real-world operation. Automated DAST tools find typical classes of errors efficiently; logic flaws and complex authorization issues, on the other hand, are only detected by a manual penetration test.
Learn more about DAST (Dynamic Application Security Testing) Related service: Web Applications & Online Shops
-
Data Processing Agreement (DPA, German: AVV)
A data processing agreement – in German, Auftragsverarbeitungsvertrag (AVV) – governs, under Art. 28 GDPR, how a service provider processes personal data on behalf of and on the instructions of a controller, including the subject matter, duration, types of data, technical and organizational measures, and audit rights. A DPA may also be required for security services, for example if the testing team gains access to personal data as part of the engagement. A non-disclosure agreement (NDA) does not replace a DPA but complements it. We clarify with you during scoping whether a security test will touch personal data.
Learn more about Data Processing Agreement (DPA, German: AVV) Related service: Contact
-
DMZ (Demilitarized Zone)
The DMZ is an isolated network segment between the internet and the internal network that hosts systems which must be reachable from the outside – such as web servers, mail gateways, or reverse proxies. Firewalls strictly control which connections are allowed from the internet into the DMZ and from there into the internal network. If a system in the DMZ is compromised, the separation is meant to prevent the attacker from reaching the corporate network directly; an infrastructure pentest shows whether it actually does.
Learn more about DMZ (Demilitarized Zone) Related service: Network & Infrastructure
-
DORA (Digital Operational Resilience Act)
DORA (Regulation (EU) 2022/2554) has applied since January 17, 2025, and harmonizes the requirements for the digital operational resilience of banks, insurers, payment service providers, and other financial entities in the EU. The regulation covers ICT risk management, the reporting of major ICT-related incidents, the management of ICT third-party service providers, and a digital operational resilience testing program. Selected financial entities must also carry out threat-led penetration testing (TLPT) on a regular basis.
Learn more about DORA (Digital Operational Resilience Act) Related service: Financial Services
E
-
EDR / XDR (Endpoint / Extended Detection and Response)
EDR solutions continuously monitor endpoints such as laptops and servers, detect suspicious behavior – such as passwords being read from memory – and can automatically isolate affected systems. XDR extends this approach by also correlating data from the network, email, cloud, and identity services. Whether detection works when it matters can only be verified with realistic attacks of the kind used in red teaming exercises.
Learn more about EDR / XDR (Endpoint / Extended Detection and Response) Related service: Red Teaming & APT Simulation
-
Entra ID (formerly Azure Active Directory)
Microsoft Entra ID is Microsoft’s cloud-based identity and access service and controls sign-in to Microsoft 365, Azure, and many other applications. Until 2023, the service was called Azure Active Directory, but it works fundamentally differently from classic, on-premises Active Directory. Typical risks include missing or inconsistently enforced MFA, gaps in Conditional Access policies, too many global administrators, and app registrations with excessive permissions.
Learn more about Entra ID (formerly Azure Active Directory) Related service: Microsoft 365 & Azure Review
-
EU AI Act
The EU AI Act (Regulation (EU) 2024/1689) is considered the first comprehensive law regulating artificial intelligence and follows a risk-based approach: certain practices are prohibited, and high-risk AI systems are subject to strict requirements. For high-risk systems, it requires, among other things, an appropriate level of accuracy, robustness, and cybersecurity – including protection against attacks such as data poisoning or manipulated inputs. The obligations apply in stages; security testing of AI applications helps meet the requirements in a verifiable way.
Learn more about EU AI Act Related service: AI & LLM Penetration Testing
-
Evil Twin
An evil twin is a fake Wi-Fi access point that mimics the network name (SSID) of a legitimate network – such as the corporate or guest Wi-Fi. When devices connect to the look-alike, the attacker can intercept traffic, harvest passwords via fake login pages, or, with insecurely configured enterprise Wi-Fi, capture credentials for the real network. Protection comes from consistent certificate validation with WPA2-Enterprise and WPA3-Enterprise and from employees who are aware of the risk.
Learn more about Evil Twin Related service: Wireless Penetration Testing
-
Executive Summary
The executive summary is the section of a pentest report written for executives and decision-makers. Without technical jargon, it describes what was tested, how secure the environment is, which risks the organization faces, and which actions take priority. This enables those responsible to make well-founded decisions about budgets and priorities, while the technical part of the report gives the specialist team the details they need for implementation.
Learn more about Executive Summary Related service: Penetration Testing
-
Exploit
An exploit is code – such as a program, a script, or a sequence of commands – that takes advantage of a specific vulnerability, for example to execute arbitrary commands, escalate privileges, or bypass protection mechanisms. Exploits are publicly available for many known vulnerabilities, which significantly lowers the bar for attackers. In penetration tests, we use controlled exploits to prove that a vulnerability can actually be exploited – always within the agreed scope and with consideration for ongoing operations.
Learn more about Exploit Related service: Penetration Testing
F
-
Firmware
Firmware is software permanently embedded in a device that controls its basic functions – from routers and industrial controllers to surveillance cameras. It often contains security-critical weaknesses such as hard-coded passwords, private keys, outdated open-source libraries, or unprotected update mechanisms. In a firmware analysis, the image is extracted, unpacked, and examined using reverse engineering to find such vulnerabilities.
Learn more about Firmware Related service: OT, ICS/SCADA & IoT
G
-
GDPR (General Data Protection Regulation)
The GDPR (Regulation (EU) 2016/679) – known in German as DSGVO – has governed the handling of personal data throughout the EU since May 2018. Art. 32 requires controllers and processors to implement appropriate technical and organizational measures and explicitly mentions a process for regularly testing, assessing, and evaluating their effectiveness. Penetration tests are a recognized means of demonstrating this effectiveness in a traceable way.
Learn more about GDPR (General Data Protection Regulation) Related service: Penetration Testing
-
German Trade Secrets Act (GeschGehG)
The German Trade Secrets Act (Gesetz zum Schutz von Geschäftsgeheimnissen, GeschGehG) has implemented Directive (EU) 2016/943 in German law since 2019. Information is only protected as a trade secret if it is not generally known and therefore has economic value, if there is a legitimate interest in keeping it confidential, and if the owner has taken reasonable confidentiality measures. In addition to technical access restrictions, these measures also include contractual arrangements such as non-disclosure agreements. If confidential company data nevertheless appears on the dark web, automated dark web monitoring reports the finding.
Learn more about German Trade Secrets Act (GeschGehG) Related service: Dark Web Monitoring
-
Gray-Box Testing
Gray-box testing combines the attacker’s outside view with specifically provided knowledge – such as test accounts with different roles, network diagrams, or interface documentation. This makes it possible to simulate realistic scenarios, such as an attacker with stolen credentials or a malicious insider. Because less time goes into pure information gathering, the gray-box approach usually offers the best balance of testing depth and effort.
Learn more about Gray-Box Testing Related service: Penetration Testing
I
-
ICS (Industrial Control Systems)
Industrial control systems monitor and control physical processes in manufacturing, energy supply, water management, and building automation. They include programmable logic controllers (PLCs), distributed control systems (DCS), SCADA systems, and human-machine interfaces (HMI). Many of these components were developed for isolated networks and use protocols without authentication – as connectivity increases, they become attractive targets.
Learn more about ICS (Industrial Control Systems) Related service: OT, ICS/SCADA & IoT
-
IDOR / BOLA (Insecure Direct Object Reference / Broken Object Level Authorization)
With IDOR – called BOLA in the API world – an application does not check whether the logged-in user is actually allowed to access a requested object. If an attacker changes the customer number in a request from 1001 to 1002, for example, they suddenly see someone else’s invoices or profile data. BOLA ranks first in the OWASP API Security Top 10 because the flaw is widespread and easy to exploit. Automated scanners, by contrast, often miss it because they don’t know which data belongs to which account.
Learn more about IDOR / BOLA (Insecure Direct Object Reference / Broken Object Level Authorization) Related service: API Penetration Testing
-
IDS / IPS (Intrusion Detection / Intrusion Prevention System)
An IDS monitors network traffic or system activity for signs of attacks and raises an alarm; an IPS also actively intervenes and blocks suspicious connections. Traditional systems detect attacks based on known signatures; modern solutions add behavioral and anomaly detection to spot new attack patterns as well. What matters is that alerts are analyzed and lead to defined response processes. A red teaming exercise shows whether detection actually notices a realistic attack.
Learn more about IDS / IPS (Intrusion Detection / Intrusion Prevention System) Related service: Red Teaming & APT Simulation
-
IEC 62443
The international IEC 62443 series of standards describes the cybersecurity of industrial automation and control systems and is aimed at operators, integrators, and component manufacturers. Key concepts include dividing systems into zones and communication channels (conduits) and security levels that describe which attackers a system must be protected against. For manufacturers, parts 4-1 and 4-2 define requirements for a secure development process and for the security functions of individual components.
Learn more about IEC 62443 Related service: OT, ICS/SCADA & IoT
-
IoT (Internet of Things)
The Internet of Things comprises connected devices that collect or exchange data or trigger actions – from cameras and access control systems to sensors, building automation, and connected machines. Many IoT devices ship with default passwords, rarely receive updates, and communicate with cloud services without adequate protection. An IoT pentest therefore examines not only the device itself but also its firmware, radio and network interfaces, apps, and the associated cloud connection.
Learn more about IoT (Internet of Things) Related service: OT, ICS/SCADA & IoT
-
ISMS (Information Security Management System)
An ISMS is a systematic framework of policies, processes, responsibilities, and controls that an organization uses to plan, implement, monitor, and continuously improve information security. It is usually based on ISO/IEC 27001 or the BSI’s IT-Grundschutz. An ISMS depends on reliable information about the actual state of security – penetration tests and vulnerability assessments provide it.
Learn more about ISMS (Information Security Management System) Related service: Security Services
-
ISO/IEC 27001
ISO/IEC 27001 is the leading international standard for information security management systems; the current version dates from 2022. Organizations can have their ISMS certified against the standard by accredited bodies, demonstrating audited security management to customers and business partners. Among other things, Annex A contains controls for handling technical vulnerabilities and for security testing in development and acceptance – penetration tests provide reliable evidence for these.
Learn more about ISO/IEC 27001 Related service: Penetration Testing
K
-
Kerberoasting
Kerberoasting is an Active Directory attack technique in which any domain user requests Kerberos service tickets for accounts with a service principal name (SPN). Because these tickets are encrypted with a key derived from the service account’s password, the attacker can crack them offline – without failed login attempts attracting attention. Long, random passwords or group managed service accounts (gMSA), as well as abandoning outdated RC4 encryption, mitigate the risk.
Learn more about Kerberoasting Related service: Active Directory Assessment
-
KRITIS (Critical Infrastructure in Germany)
KRITIS (Kritische Infrastrukturen) refers to organizations and facilities whose failure would lead to significant supply shortages or threats to public safety – for example, in the sectors of energy, water, food, healthcare, finance, transport and traffic, and information technology and telecommunications. Operators of critical facilities must implement state-of-the-art IT security, report significant security incidents, and regularly demonstrate their protective measures to the BSI. With the implementation of the NIS2 Directive, the group of regulated companies has also grown significantly.
Learn more about KRITIS (Critical Infrastructure in Germany) Related service: Energy & Critical Infrastructure
L
-
Lateral Movement
Lateral movement describes how an attacker moves sideways through the network after compromising an initial machine. Using stolen credentials, techniques such as pass-the-hash, or legitimate administration tools, the attacker hops from system to system until reaching valuable data or administrative privileges. Network segmentation, separate administrator accounts, and good network detection make this phase considerably harder.
Learn more about Lateral Movement Related service: Red Teaming & APT Simulation
-
LLM (Large Language Model)
Large language models are AI models trained on huge amounts of text that understand and generate natural language – the foundation of chatbots, assistants, and AI agents. In enterprise applications, LLMs are often connected to internal documents, databases, or tools, which creates new risks: prompt injection, leakage of confidential data, or actions triggered through abuse. The OWASP Top 10 for LLM Applications summarizes the most important of these risks.
Learn more about LLM (Large Language Model) Related service: AI & LLM Penetration Testing
M
-
Malware
Malware is the umbrella term for software developed with malicious intent – such as viruses, worms, Trojans, spyware, keyloggers, or ransomware. It often reaches systems via email attachments, manipulated downloads, exploited vulnerabilities, or infected storage media. After an infection, malware analysis and digital forensics clarify what the malware can do, how it got in, and which systems are affected.
-
Man-in-the-Middle Attack (MitM)
In a man-in-the-middle attack, an attacker secretly inserts themselves into the communication between two parties in order to read or alter data. On the local network, this can be achieved through ARP spoofing or by abusing name resolution protocols such as LLMNR and NBT-NS; on Wi-Fi, through fake access points. Consistent encryption with proper certificate validation, SMB and LDAP signing, and disabling insecure protocols take away the basis for such attacks.
Learn more about Man-in-the-Middle Attack (MitM) Related service: Network & Infrastructure
-
MFA (Multi-Factor Authentication)
With multi-factor authentication, users prove at least two independent factors when signing in: something they know (password), something they have (smartphone, hardware token), or something they are (fingerprint). A stolen password alone is then no longer enough to gain access. However, not all MFA is equal: push approvals can be defeated through “MFA fatigue” and one-time codes can be intercepted via phishing proxies, while phishing-resistant methods such as FIDO2 and passkeys offer significantly more protection.
Learn more about MFA (Multi-Factor Authentication) Related service: Microsoft 365 & Azure Review
N
-
NDA (Non-Disclosure Agreement)
An NDA – also called a confidentiality agreement – obliges one or both contracting parties to keep confidential information they exchange secret and to use it only for a defined purpose. Before a penetration test, it protects sensitive details such as network diagrams, credentials, and test results. At the same time, an NDA can be one of the reasonable confidentiality measures that the German Trade Secrets Act requires for trade secrets to be legally protected. On request, we sign a non-disclosure agreement before scoping.
Learn more about NDA (Non-Disclosure Agreement) Related service: Contact
-
Network Segmentation
Network segmentation divides a network into separate zones – for example for clients, servers, administration, production, guests, and IoT devices – with only explicitly permitted connections between them. If an attacker breaks into one area, effective segmentation prevents them from spreading unhindered. In practice, firewall rules often deviate from the design; a segmentation test shows which connections between zones are actually open.
Learn more about Network Segmentation Related service: Network & Infrastructure
-
NIS2
The NIS2 Directive (EU) 2022/2555 raises the level of cybersecurity in the EU and covers significantly more companies than the previous rules – divided into important and essential entities from 18 sectors. Affected organizations must implement risk management measures, report significant security incidents within fixed deadlines, and also secure their supply chain; management is responsible for implementation. In Germany, the directive is implemented by the amended BSI Act (BSIG).
Learn more about NIS2 Related service: Energy & Critical Infrastructure
O
-
OSINT (Open Source Intelligence)
OSINT refers to collecting and analyzing freely available information – from websites, social networks, job postings, commercial registers, DNS records, certificate transparency logs, or published data leaks. Attackers use OSINT to scout targets, make phishing emails more convincing, and find forgotten systems. An OSINT assessment shows you what picture an attacker can form of your company before taking action.
Learn more about OSINT (Open Source Intelligence) Related service: OSINT Assessment
-
OT (Operational Technology)
Operational technology comprises hardware and software that directly monitors and controls physical processes and equipment – unlike classic office IT, which processes data. In OT, availability and functional safety have top priority; systems often run for decades and cannot simply be patched or restarted. Security testing in OT environments therefore requires special care, coordinated test windows, and often passive methods.
Learn more about OT (Operational Technology) Related service: OT, ICS/SCADA & IoT
P
-
Pass-the-Hash
In a pass-the-hash attack, an attacker uses a stolen NTLM password hash directly to sign in to other systems – without needing to know the plaintext password. The attacker typically extracts the hashes from the memory or the local user database of a compromised computer. The technique is particularly dangerous when the same local administrator password is set on many computers; remedies include Windows LAPS, a tiered model for administrator accounts, and Credential Guard.
Learn more about Pass-the-Hash Related service: Active Directory Assessment
-
Password Spraying
In password spraying, an attacker tries a few commonly used passwords – such as “Summer2026!” – against a very large number of user accounts. Because only a few attempts are made per account, classic account lockouts don’t kick in, and the attack often goes unnoticed. Cloud logins such as Microsoft 365 are hit particularly often; MFA, password policies with banned-password lists, and monitoring of failed logins provide effective protection.
Learn more about Password Spraying Related service: Microsoft 365 & Azure Review
-
Patch Management
Patch management is the structured process of identifying, assessing, testing, and promptly installing security updates for operating systems, applications, firmware, and network devices. Many successful attacks exploit vulnerabilities for which an update had long been available. Effective patch management requires a complete inventory, clear responsibilities, deadlines based on criticality, and regular vulnerability scans that show where updates are missing.
Learn more about Patch Management Related service: Vulnerability Assessment
-
Penetration Test (Pentest)
A penetration test is an authorized, simulated attack on IT systems, applications, or processes in which experts use the methods of real attackers to search for exploitable vulnerabilities. Unlike an automated scan, it manually checks whether vulnerabilities can actually be exploited and combined, and what the consequences would be. The result is a report with verifiably documented findings, a risk assessment, and specific remediation recommendations.
Learn more about Penetration Test (Pentest) Related service: Penetration Testing
-
Pentest Report
The pentest report documents the scope, approach, and results of a penetration test. A good report addresses two audiences: the executive summary puts the results into context for management, while the technical part describes each vulnerability in a reproducible way with evidence, a CVSS rating, and a specific remediation recommendation. At Rootsektor, you also receive a test certificate that you can use to demonstrate the test to customers, partners, insurers, and auditors.
Learn more about Pentest Report Related service: Penetration Testing
-
Phishing
Phishing refers to fraudulent messages, usually sent by email, with which attackers try to get recipients to disclose credentials, open malware, or initiate payments. Targeted variants such as spear phishing use personally tailored content to target individuals, for example in accounting or senior management. Technical filters catch a lot, but not everything – that’s why trained employees and realistic phishing simulations are a key part of the defense.
Learn more about Phishing Related service: Security Awareness & Phishing Simulation
-
PLC (Programmable Logic Controller)
A PLC – in German, speicherprogrammierbare Steuerung (SPS) – is an industrial computer that controls machines and equipment in real time based on a control program. It reads in sensor values, processes them, and switches actuators such as motors, valves, or pumps. Many PLCs can be reprogrammed over the network with no or only weak authentication – an attacker with network access can thus intervene directly in physical processes.
Learn more about PLC (Programmable Logic Controller) Related service: OT, ICS/SCADA & IoT
-
Privilege Escalation
In privilege escalation, an attacker gains higher privileges than they are entitled to – for example, from a regular user account to local administrator or from domain user to domain admin. Causes include unpatched vulnerabilities, incorrectly set file permissions, insecurely configured services, or passwords stored in plaintext. There are two forms: vertical privilege escalation, in which an ordinary account gains administrator functions, for example, and horizontal privilege escalation, in which an attacker accesses the data of other accounts at the same level.
Learn more about Privilege Escalation Related service: Network & Infrastructure
-
Prompt Injection
Prompt injection is an attack technique against applications built on large language models: crafted text overrides the application’s system instructions, causing the model to ignore safeguards, reveal internal information, or trigger unintended actions via connected tools. In the direct variant, the instructions are in the user input; in the indirect variant, they are hidden in content the model processes – such as websites, emails, or documents. The OWASP Top 10 for LLM Applications ranks prompt injection first.
Learn more about Prompt Injection Related service: AI & LLM Penetration Testing
-
Purple Teaming
In purple teaming, attackers (red team) and defenders (blue team) work together openly and closely instead of facing each other as in a covert exercise. The red team executes attack techniques step by step – often along MITRE ATT&CK – while the blue team checks whether and how its systems detect them. This allows gaps in detection and response to be closed immediately and tested again. Rootsektor offers purple teaming as a variant of, or complement to, red teaming.
Learn more about Purple Teaming Related service: Red Teaming & APT Simulation
R
-
Ransomware
Ransomware is malware that encrypts data and systems in order to extort a ransom for decryption. Today, attackers usually also steal data beforehand and threaten to publish it (double extortion). The most effective defenses against ransomware are consistently closing entry points such as unpatched VPN gateways, a segmented infrastructure, separate administrator accounts, and regularly tested offline backups. If an attack has already happened: disconnect affected systems from the network, but don’t switch them off, and get expert help immediately.
Learn more about Ransomware Related service: Ransomware Response
-
RCE (Remote Code Execution)
Remote code execution refers to vulnerabilities that allow an attacker to run their own code on someone else’s system remotely. Causes include insecure deserialization, command or template injection, unchecked file uploads, or memory corruption bugs. Because RCE often allows complete takeover of a server, such flaws are among the most critical findings of a penetration test.
Learn more about RCE (Remote Code Execution) Related service: Web Applications & Online Shops
-
Red Team
A red team simulates a real, targeted attacker and tries over an extended period to achieve a predefined objective – such as access to financial data or production systems. Unlike a classic penetration test, the goal is not to find as many vulnerabilities as possible but to carry out a realistic attack chain across technical, human, and physical vectors. At the same time, the exercise shows whether your organization detects the attack and responds appropriately; in an APT simulation, the approach is modeled on the techniques of professional threat actor groups.
Learn more about Red Team Related service: Red Teaming & APT Simulation
-
Retest
In a retest, the reported vulnerabilities are checked again after remediation to verify that they have been effectively closed. Only the retest confirms that the remediation actually works – often a prerequisite for demonstrating a remediated state to auditors or customers. For Rootsektor penetration tests and security assessments, the retest of remediated vulnerabilities is free of charge.
-
Reverse Engineering
Reverse engineering is the analysis of a finished product to understand its structure and how it works – in IT security, usually software, apps, firmware, or communication protocols without access to the source code. Programs are disassembled or decompiled, and their runtime behavior is observed. This can uncover hidden functions, hard-coded credentials, weak cryptography, or vulnerabilities in proprietary protocols.
Learn more about Reverse Engineering Related service: Code Review & Reverse Engineering
-
Rogue Access Point
A rogue access point is an unauthorized Wi-Fi access point on the corporate network – such as a router connected for convenience or a device hidden by attackers. Because it provides access to the internal network that bypasses the central security architecture, it circumvents firewalls and access controls. Wireless intrusion prevention systems (WIPS), port-based network access control based on IEEE 802.1X, and regular wireless scans help track down such devices.
Learn more about Rogue Access Point Related service: Wireless Penetration Testing
-
Rules of Engagement (RoE)
The rules of engagement set out in binding terms, before a penetration test or red teaming engagement, how testing will be carried out: target systems and exclusions, testing periods, permitted and prohibited techniques, contacts, and escalation paths – for example, who is notified immediately of critical findings. They protect both sides and ensure that the test does not impair ongoing operations in an uncontrolled way. Together with the written engagement, they provide the basis on which a simulated attack is authorized and therefore lawful.
Learn more about Rules of Engagement (RoE) Related service: Red Teaming & APT Simulation
S
-
SAST (Static Application Security Testing)
SAST analyzes an application’s source code, bytecode, or binary code without executing it and looks for insecure patterns such as missing input validation, dangerous function calls, or hard-coded passwords. Because SAST starts during development, errors can be fixed early and with little effort. However, automated tools also produce false positives and miss logic flaws – a manual code review by security experts closes this gap.
Learn more about SAST (Static Application Security Testing) Related service: Code Review & Reverse Engineering
-
SBOM (Software Bill of Materials)
An SBOM is a machine-readable inventory of all components, libraries, and dependencies of a piece of software – including versions and licenses. It shows whether a product is affected by a newly discovered vulnerability in a third-party component, as was the case worldwide with Log4Shell. Common formats are SPDX and CycloneDX; the Cyber Resilience Act makes SBOMs mandatory for many manufacturers.
Learn more about SBOM (Software Bill of Materials) Related service: Code Review & Reverse Engineering
-
SCADA (Supervisory Control and Data Acquisition)
SCADA systems monitor and control geographically distributed industrial processes from a central location – such as power grids, pipelines, waterworks, or wastewater treatment plants. They collect measurements from field devices and controllers, visualize the plant status in control rooms, and send control commands back. Because SCADA systems are increasingly connected to office networks and remote maintenance access, they are a focus of state-sponsored and criminal attackers.
Learn more about SCADA (Supervisory Control and Data Acquisition) Related service: OT, ICS/SCADA & IoT
-
Scope (Test Scope)
The scope defines what is tested in a penetration test – such as which applications, IP ranges, interfaces, sites, or groups of people – and what is explicitly excluded. A clearly defined scope is the basis for a reliable quote, a predictable process, and meaningful results. For penetration tests and security assessments, we clarify the scope in a scoping call and send you a fixed-price quote within 24 hours (on business days).
Learn more about Scope (Test Scope) Related service: Pentest Quote
-
SIEM (Security Information and Event Management)
A SIEM collects log data from servers, network devices, applications, and security solutions centrally, correlates it, and detects suspicious patterns using rules and analytics. This makes it possible to uncover attacks that remain inconspicuous in individual log files – such as a login at an unusual time followed by mass file access. After an incident, the collected data is also a key source for the forensic investigation. As a Rapid7 partner, we advise on Incident Command (formerly InsightIDR), Rapid7’s next-gen SIEM.
Learn more about SIEM (Security Information and Event Management) Related service: Rapid7
-
Smishing
Smishing – a blend of SMS and phishing – refers to fraudulent text messages sent via SMS or messaging apps. Typical examples include supposed parcel notifications, warnings from the bank, or messages in the name of senior management designed to lure recipients into clicking a link or calling back. Because smartphones display links in shortened form and security filters are less likely to catch them there, smishing is particularly effective.
Learn more about Smishing Related service: Security Awareness & Phishing Simulation
-
SOC (Security Operations Center)
A SOC is a team – internal or an external service – that continuously monitors an organization’s IT environment, assesses security events, and responds to incidents. It works with tools such as SIEM, EDR/XDR, and network detection, as well as defined incident handling procedures. How well a SOC actually detects and responds can be measured realistically with red teaming and purple teaming exercises.
Learn more about SOC (Security Operations Center) Related service: Red Teaming & APT Simulation
-
Social Engineering
Social engineering refers to attacks that exploit human traits such as helpfulness, respect for authority, curiosity, or time pressure to obtain information, access, or money. Methods range from phishing emails and calls from supposed service providers to unauthorized entry into the building. Social engineering tests show where processes and awareness work and where they don’t – without exposing individual employees.
Learn more about Social Engineering Related service: Social Engineering & Physical Testing
-
SQL Injection (SQLi)
In SQL injection, an attacker injects their own SQL commands into a database query via input fields, URL parameters, or API requests. Depending on the flaw, the attacker can read, modify, or delete data, bypass logins, and, in the worst case, execute commands on the server. The most effective countermeasure is parameterized queries (prepared statements), complemented by input validation and database accounts with minimal privileges.
Learn more about SQL Injection (SQLi) Related service: Web Applications & Online Shops
-
SSO (Single Sign-On)
With single sign-on, users sign in once to a central identity provider and then gain access to many applications without having to sign in again – technically usually via SAML or OpenID Connect based on OAuth 2.0. This increases convenience and enables central controls such as MFA. At the same time, the identity provider becomes a master key: configuration errors or stolen session tokens can open access to all connected services.
Learn more about SSO (Single Sign-On) Related service: Microsoft 365 & Azure Review
-
SSRF (Server-Side Request Forgery)
With SSRF, an attacker gets a server to send requests to arbitrary destinations on the attacker’s behalf – for example, via a function that loads images or webhooks from a specified URL. This lets the attacker reach internal systems that are not accessible from the outside. In cloud environments, SSRF is particularly dangerous because temporary credentials can, under certain circumstances, be read via an instance’s metadata service.
Learn more about SSRF (Server-Side Request Forgery) Related service: Cloud Penetration Testing
-
Supply Chain Attack
In a supply chain attack, attackers don’t target a company directly but go through a trusted supplier – such as a software vendor, an IT service provider with remote access, or an open-source library. Manipulated updates or compromised packages thus reach many victims at once. Countermeasures include vetting suppliers and components, signed builds, SBOMs, and strictly limiting service provider access.
Learn more about Supply Chain Attack Related service: Code Review & Reverse Engineering
-
System Hardening
System hardening covers all measures that reduce a system’s attack surface: disabling unneeded services and functions, changing default passwords, enforcing secure protocols, restricting privileges to the minimum necessary, and consistently applying security-relevant settings. Guidance is provided, for example, by the CIS Benchmarks, vendor recommendations, or the modules of BSI IT-Grundschutz. A penetration test shows where hardening has gaps in practice.
Learn more about System Hardening Related service: Network & Infrastructure
T
-
Technical and Organizational Measures (TOMs)
Technical and organizational measures (TOMs; German: TOM) are the safeguards that controllers and processors use under Art. 32 GDPR to ensure the security of personal data – such as encryption, access controls, backups, training, and emergency plans. They must be appropriate to the risk and take the state of the art into account. Art. 32 also mentions a process for regularly testing their effectiveness; penetration tests provide reliable evidence for this.
Learn more about Technical and Organizational Measures (TOMs) Related service: Penetration Testing
-
TIBER-EU
TIBER-EU (Threat Intelligence-based Ethical Red Teaming) is a European Central Bank framework for controlled, threat-led red teaming tests in the financial sector. Based on current threat intelligence, external red teams simulate the tactics of real threat actor groups against an institution’s critical functions and production systems. The framework has been aligned with DORA’s requirements for threat-led penetration testing (TLPT); in Germany, it is implemented as TIBER-DE.
Learn more about TIBER-EU Related service: Red Teaming & APT Simulation
-
TISAX (Trusted Information Security Assessment Exchange)
TISAX is an assessment and exchange mechanism for information security that is established in the automotive industry and operated by the ENX Association on behalf of the VDA (German Association of the Automotive Industry). Suppliers and service providers are assessed by approved audit providers based on the VDA ISA catalog and share the results with their customers. In addition to classic information security, prototype protection and data protection can also be part of the assessment, depending on requirements.
Learn more about TISAX (Trusted Information Security Assessment Exchange) Related service: Manufacturing & Industry
-
TLPT (Threat-Led Penetration Testing)
TLPT is a threat-led penetration test that DORA requires for selected financial entities – generally at least every three years. It takes place on production systems that support critical or important functions and follows a strictly regulated process of threat intelligence, a covert red team attack, and a joint review. The competent supervisory authority determines which companies must carry out a TLPT.
Learn more about TLPT (Threat-Led Penetration Testing) Related service: Red Teaming & APT Simulation
V
-
Vishing
Vishing – from voice and phishing – is phishing by phone: attackers pose as IT support, a bank, a government agency, or a manager to obtain credentials, MFA codes, or payments. With spoofed phone numbers and, increasingly, AI-generated voices, such calls seem deceptively genuine. Clear callback processes and regularly trained employees are the most important defense.
Learn more about Vishing Related service: Social Engineering & Physical Testing
-
VPN (Virtual Private Network)
A VPN creates an encrypted tunnel over an insecure network such as the internet – for example, for remote work or to connect sites. VPN gateways are directly reachable from the internet and are therefore a popular entry point: vulnerabilities in VPN appliances have been exploited on a massive scale time and again in recent years. Prompt updates, MFA for all access, and limiting what VPN users can reach on the internal network are therefore essential.
Learn more about VPN (Virtual Private Network) Related service: Network & Infrastructure
-
Vulnerability Scan
A vulnerability scan automatically checks systems for known vulnerabilities, missing updates, and insecure configurations and compares the results against databases such as CVE. Scans are fast, cover large environments, and are suitable for regular checks. However, they only find what is already known, produce false positives, and don’t show whether vulnerabilities can actually be exploited or chained – only a penetration test does that.
Learn more about Vulnerability Scan Related service: Vulnerability Assessment
W
-
WAF (Web Application Firewall)
A web application firewall filters HTTP traffic to web applications and blocks typical attack patterns such as SQL injection or cross-site scripting before they reach the application. It is a useful additional layer of protection but does not replace secure coding: cleverly obfuscated attacks and logic flaws, such as in authorization checks, usually go undetected by a WAF. For penetration tests, we agree with you whether to test with the WAF active or directly against the application.
Learn more about WAF (Web Application Firewall) Related service: Web Applications & Online Shops
-
White-Box Testing
In white-box testing, the testing team receives comprehensive insight: architecture and configuration documentation, accounts with different privileges, and, on request, the source code. This enables the most thorough assessment, because vulnerabilities that are difficult or impossible to find from the outside also become visible. The approach is particularly suitable for critical applications, before go-live, and in combination with a code review.
Learn more about White-Box Testing Related service: Penetration Testing
-
WPA3
WPA3 is the current security standard for Wi-Fi networks and is gradually replacing WPA2. In Personal mode, SAE (Simultaneous Authentication of Equals) replaces the previous pre-shared key authentication, so captured handshakes can no longer be cracked offline with dictionary attacks; in addition, protected management frames are mandatory. In mixed operation with WPA2 (transition mode) or with a faulty configuration, however, attacks remain possible.
Learn more about WPA3 Related service: Wireless Penetration Testing
X
-
XSS (Cross-Site Scripting)
With cross-site scripting, an attacker manages to inject their own JavaScript code into a web page, which is then executed in other people’s browsers. This allows the attacker to hijack sessions, capture input, manipulate content, or perform actions on behalf of the victim. XSS comes in stored, reflected, and DOM-based variants; protection comes from context-sensitive output encoding, secure frameworks, and a Content Security Policy.
Learn more about XSS (Cross-Site Scripting) Related service: Web Applications & Online Shops
Z
-
Zero Trust
Zero trust is a security model based on the principle “never trust, always verify”: no person, device, or network segment is automatically considered trustworthy – not even inside the corporate network. Every access request is checked based on identity, device state, and context and granted only with the minimum necessary privileges. Zero trust is not a single product but an architecture that is introduced step by step, for example through strong authentication, microsegmentation, and continuous monitoring.
Learn more about Zero Trust Related service: Network & Infrastructure
-
Zero-Day
A zero-day vulnerability is a security flaw that is still unknown to the vendor or for which no patch exists yet – defenders have had “zero days” to respond. Exploits for such flaws are particularly valuable and are used for targeted attacks or sold at high prices. Since updates don’t help here, what matters is hardening, segmentation, least privilege, and attack detection that doesn’t rely solely on known signatures. A penetration test shows how far an attacker would get after a successful breach.
Learn more about Zero-Day Related service: Penetration Testing
No term found. Ask us – we’re happy to explain it.
Which of these terms affect your organization?
Knowing the terms is the first step – a penetration test shows which vulnerabilities in your systems can actually be exploited. After scoping, you’ll receive a fixed-price quote within 24 hours (on business days).
Related pages
Can’t find a term?
Missing a technical term or have a specific question about the security of your systems? Write to us using the form or call us at +49 2932 465265-0 – we’re happy to explain.