IoT penetration testing is a complex process that can be divided into 5 phases.
Phase 1: Kickoff
IoT penetration testing begins with a kick-off discussion. In this meeting you and the expert develop clear security concepts, define the objectives, scope and rules of engagement. Open questions can already be clarified in advance. These include:
- Which components are the focus (device/firmware, radio & network, cloud/backend, apps & APIs)?
- Which security objectives are you pursuing?
- Within which framework (black/grey/white box) should the expert examine the systems?
- Should the IoT pentest be carried out on site or remotely?
- Which approvals/test windows apply – and what is out of scope (e.g. productive DoS tests)?
The duration of IoT penetration testing depends largely on these answers! Once the expert has all the important information, they can give you an approximate timeframe. After the kick-off discussion you will have an agreed test plan in your hands. Ideally, you should start IoT penetration testing already at an early stage of development. 
 
Phase 2: Detailed security investigatio
Once the expert has all the necessary information, they carry out a detailed security investigation in phase 2. They uncover vulnerabilities in the system and immediately present you with suitable solutions. In addition, the expert takes into account the respective operating and application environment of the IoT system in order to simulate realistic attack scenarios. This is of course somewhat roughly described – but deliberately so. Unfortunately, the course of such an IoT penetration test cannot be described in detail. Why? Because it depends on the application.
Are they, as a result of an IoT pentest, examining the front end of a web application? Then they will probably attack the application with malicious JavaScript or check the source code for insecure programming patterns to identify security gaps. Phase 2 is a very detailed step of IoT penetration testing. It involves detailed analyses that are individually tailored to your application. This allows the expert to take a close look at your systems.
Phase 3: Report
In the third phase the expert hands you a report on the IoT pentest. There you will find all identified vulnerabilities as well as appropriate countermeasures. In addition to this information, you will also receive a comprehensive overview of the tools used and the methodology applied.
 
Phase 4: Remediation
You now know where the problems lie. In the fourth phase you initiate all steps to remedy the potential attack surfaces. Often the experts of IoT penetration testing also support you in this phase. They give you helpful tips and recommendations to ensure that everything is carried out securely.
Phase 5: Re-testing
After you have remedied all vulnerabilities, a re-test is carried out. Together with the expert, you check whether you have really closed all the gaps found in phase 2. At the same time, in this phase the expert looks to see whether the adjustments could have created new attack vectors. You will then receive a new report, either with the note “remedied” or “not remedied”, as well as clear action steps.
The expert often concludes with a further discussion. There you will receive important advice on how to protect your IoT devices and systems in the future. One thing is certain: the errors found should not occur again! So they will talk to you about the implementation of automated security systems as well as the regular training of your employees.