iKNSA International
Self-assessment10 to 15 minClient areaContact iKNSA

Guidance by trigger

The triggering event determines the order of the analysis.

A questionnaire, an audit, market entry or the maintenance of several engagements each call for distinct decisions and levels of evidence.

Review situations

A client request exists

Security questionnaireContractual annexAnnounced auditFindings received

A decision needs to be prepared

RenewalEU call for tendersEU market entryProduct security

The role determines the mandate

The supplier examines its own capability. The European client defines the supplier decision it needs to reach.

Self-assess my organisation →Assess a supplier →Search the platform →

Choose an engagement

Meet the deadline. Establish capacity. Sustain commitments.

Start from what needs to be obtained now: an answer, an in-depth review, or a capability tracked over time.

View all engagements
01

Reply

A document and a deadline.

QuestionnaireAnnexAuditAll responses →
02

Prepare

Verify and remediate.

EU exposureClient and technical assessmentEvidence and remediationAll preparations →
03

Maintain

Keep the current commitments.

Continuous assuranceClient assurance officeProduct security cellAll recurring services →

Basis for the conclusions

From the client's requirement to a qualified piece of evidence.

The same trail links Promise, Policy, Practice, Platform, finding, remediation and controlled sharing.

Review the 4P method

Trace

Evidence traceabilityAssurance registerTrust roomContinuous verification

Frameworks and sectors

GDPR and international accessHealth data and HDSNIS2 and the supply chainIndustrial confidentialityAll frameworks →

View deliverables

See fictitious examples to understand the structure and depth of the deliverables.

See examples of deliverables →

Terms of engagement

Responsibilities, information and limits established before the engagement.

Confidentiality, independence, reversibility and traceability of responsibilities structure the conduct of the work.

Review the firm's rules

Trust rules

ConfidentialityIndependenceSecurityReversibility

Working with iKNSA

ExpertiseInternational engagementsRequest an engagementContact

European principals

Have an international supplier assessed under explicit mandate and sharing rules.

Assess a supplier →
Your contextContext not defined
Country of the organisation assessedNot provided
What it providesNot provided
Relationship with the EUNot provided
Home / Prepare

Prepare

Evidence and remediation programme

Correct the technical gaps and build the evidence needed to defend them.

In your situation

What the scoping will need to take into account.

Ability to establish

Drive corrections through to their proof of closure.

An action is only considered complete once its owner, its dependencies, its exit criterion and the expected evidence are all made explicit.

Point of convergencePrioritised remediation planGovernance, technical and evidence

Subject of the work

Corrections progress through evidence of closure, not through a declared percentage.

Demonstration example
To be investigatedPrioritise according to client commitmentsPrioritised remediation plan
AssignedCorrect documentation, IAM, platform or operationsControls implemented
In progressAssign actions and dependenciesEvidence file
Expected evidenceVerify closure criteriaScoped verification reports

How it actually unfolds

Organise the review before mobilising the teams.

Working format

Programme driven by a prioritised plan, remediation cycles and evidence reviews through to the agreed closure criteria.

Client-side mobilisation

Owners implement the corrections; iKNSA structures the decisions, verifies the outputs and keeps dependencies visible.

Starting elements

Qualified findings, risks, client commitments, affected architecture, available capacity and starting evidence.

Building the schedule

Pace follows criticality, technical dependencies and client deadlines; progress is measured by demonstrated closure.

Review

Handle each gap with an owner and a verifiable resolution.

01

Prioritise according to client commitments

The plan starts with the gaps that put a client engagement at risk or block an imminent commercial decision.

02

Correct documentation, IAM, platform or operations

Documentary and technical corrections are coordinated to prevent a policy announcing what the platform does not actually deliver.

03

Assign actions and dependencies

Each action retains its dependencies, its decision-making authority and the criterion by which its completion can be verified.

04

Verify closure criteria

The closure review examines the result produced and states the limitations that remain after the correction.

Handover

The evidence that substantiates real progress.

Prioritised remediation plan

The plan gives each gap a priority, an owner, prerequisites and a checkable closure criterion.

Controls implemented

The procedures, configurations or operational changes made are linked to the gap they are intended to correct.

Evidence file

The file brings together the results produced after correction, together with their source, population and remaining limitations.

Scoped verification reports

Each verification specifies what was replayed, on which sample and why the result does — or does not — allow the gap to be closed.

Scoping the engagement

Start from known gaps to build verifiable closures.

The existing gap register, even if incomplete, makes it possible to build the correction batches, dependencies and closure criteria to be verified.

Scope this engagementSee an example deliverable →