Qualification PIT DIP Simulator Guidance


documents.jpg

Qualification Pre-Integration Testing (PIT) Data Integration Platform (DIP) Simulator Guidance

Code Bodies provided guidance for participants about using locally-hosted versions of the DIP Simulator versus the Programme-hosted DIP Simulator.

The security parameters were complex and where a locally-hosted version was not set up correctly, it introduced risk that a participant may not have been aligned to the security requirements of the DIP itself, therefore invalidating any test results.

The Programme-hosted DIP Simulator’s security parameters were correctly configured for testing which meant that participants using the Programme-hosted version could be confident that their security requirements were aligned.

The Programme and Code Bodies recommended that the Programme-hosted DIP Simulator was used for Functional and Migration Testing wherever possible.​

Participants could use a locally-hosted version, provided that they could demonstrate their alignment to DIP security configurations. However, there was a risk that the security configuration might have been incorrect and could impact DIP onboarding or have created errors during Qualification Testing.​

Programme participants should have provided confidence that the DIP security configuration was appropriately implemented and issues were not encountered in the full integration for the PIT Phase. The key security parameters that formed part of this provision were use of API Keys, mTLS implementation and evidence of message signing.

For example, in the ‘Test Run’ feature, where screenshots were used for PIT evidence as per the guidance document, there was an indicator called ‘Signature Provider’ which showed as valid or not to indicate whether Message Signing was turned on. Participants could screenshot their settings to show that these parameters were turned on/implemented.

If you have any questions about the DIP Simulator, please email ITHelp@mhhsprogramme.co.uk