Working with your product

CRA: start by qualifying the product with digital elements

Organise facts about digital elements, connectivity and your company role before assembling cybersecurity documentation. Save the basis for qualification and distinguish missing information from an evidenced exclusion or a documented product classification.

Workflow illustration: CRA: start by qualifying the product with digital elements
Illustration of the workflow area.

What you gain

Retain an assessment connected to the product version, assessment date and references supporting answers that may need further specialist review.

When this module helps in daily work

A product gains an application, connectivity or a software function while its old sales description remains unchanged. Qualification begins with recording actual functionality rather than finding a convenient label. Gather an operational description and answers from someone who understands the architecture.

The module provides a starting point for discussion between product, engineering and documentation staff. An unresolved class or exclusion remains a question to investigate. The saved result explains the basis for subsequent work; it is not a technical security test.

What to prepare

  • Digital elements and product connectivity
  • Company role and supply model
  • Classification and exclusion evidence

How the workflow works

  1. Describe the scope

    Select the product and answer questions about digital elements, connections and commercial supply. Do not invent missing technical information. Describe actual connectivity and digital functions of the current version. Establish them with technical staff rather than relying solely on marketing material.

  2. Support qualification

    Identify the product class or leave it unresolved. Retain the required evidence references for documented classifications and scope exclusions. Identify support for the selected class or exclusion. Do not replace unresolved scope with an unsupported not-applicable answer.

  3. Save the result

    Run the assessment and inspect the outcome. History supports another review when functionality, software or the supply model changes. Read the result alongside its inputs. Identify questions requiring a specialist before using the record in subsequent documentation work.

What you retain after the workflow

  • Qualification inputs for a product with digital elements.
  • An outcome based on saved answers and evidence references.
  • Qualification history useful after software or functionality changes.

At the next review, start with the saved version and check whether new information changes earlier findings.

Fictional example

A lamp gains connectivity

The Terra model gains network-based control. Record the updated digital-element and connectivity context, then assess scope instead of assuming that the earlier description remains sufficient for the modified product.

Official sources for further reading

Choose a plan for your workflow

Compare the module scope and available platform plans.

View plans