This article provides basic guidance about penetration tests (pentests). Customers are allowed to carry out the pentest and to forward the result to Scheer IMC (via Project Manager, Account Manager, or imc Service Desk). Usually, a pentest result is a document that contains several findings with category LOW , MEDIUM , HIGH .
For documentation purposes, the customer can create a imc Service Desk ticket with ticket type Request. Scheer IMC Support will change the ticket type to the final ticket type Support Request. The ticket stays open until all findings are sorted out / solved. Coordination takes place with the Scheer IMC Security team.
The support agent who is assigned to the ticket will provide an overview of all reported findings and coordinates the feedback from Scheer IMC’s internal departments (mainly Hosting and Product Development).
Feedback Options
|
Category |
What it means |
Next step |
|
|---|---|---|---|
|
|
Software Defect |
LMS software needs a code change. |
Will be scheduled for one of the next patches via a separate software defect ticket. |
|
🖥️ |
Infrastructure change |
Hosting infrastructure needs to be changed. |
Will be scheduled as soon as possible |
|
❌ |
Invalid / won’t fix |
The finding is invalid or will not be fixed by Scheer IMC. |
Scheer IMC will provide reasonable feedback to customer with an explanation why the finding is invalid or will not be fixed by Scheer IMC. |
|
🌐 |
Outside Scheer IMC |
The finding is not related to Scheer IMC software or services. |
Scheer IMC will provide adequate feedback. |
Via Service Desk ticket, the support agent might request further input from customer side in case reported findings are not clear. In addition, it is possible to schedule regular or on demand calls for status updates.
The Service Desk ticket is resolved when Scheer IMC has provided reasonable feedback for all reported findings and all agreed fixes have been delivered.
Additional Information
A Pentest as part of the rollout phase is managed by the project team. In case, fixes need to be delivered after project closure and support handover, the Scheer IMC Project team will forward the necessary tickets to Scheer IMC Support team such that tickets visible to customers can be created in imc Service Desk.
Plan enough time before Go-Live. If the customer does a pentest during the project phase without having this in scope, we cannot avoid an impact on the project timeline.
Example:
If a customer does a pentest one week before Go-Live, it would be unrealistic to expect the findings to be fixed within two days.
Known pentests in projects must be scheduled properly. This also means that not all things have to be fixed before Go-Live. Only confirmed (valid) and “critical” findings (of high risk) that need some action on Scheer IMC side (infrastructure change or software fix) will lbe addressed.