Colour theme
Book a consultation

Asking suppliers about secure product design

Ask how a supplier builds secure defaults, access controls, updates and vulnerability handling into a product before you adopt it for business use.

An illustration of a shield and padlock against dark grey flowing lines.

Secure by design means addressing security in the product’s design and development. With secure defaults, a product is reasonably safe as installed, so each customer doesn’t have to switch protections on one at a time.

For a buyer, the useful question is what the supplier has built and what your organization must still operate. Ask for evidence that relates to the product and version you’re considering.

Clarify the supplier’s responsibility

The Cyber Centre’s joint design guidance emphasizes manufacturers taking responsibility for customer security through product design and defaults.

Ask how security requirements enter development and how the supplier learns from reported flaws. A pledge or policy statement is a starting point for questions.

Your own organization still has to manage access, configuration and operating procedures.

Check the initial configuration

Ask whether the product arrives with shared default passwords, unnecessary exposed services or broad administrator access.

Review the supported setup flow. Check which controls are included in the proposed licence and which require another product or configuration task.

Test the defaults during a trial. Record any setting you need to loosen and what you’ll do to cover the gap.

Inspect identity and account recovery

Confirm support for named users, role-based permissions and the sign-in methods your business requires. Include supplier and support access.

Test account recovery, and test removing access when someone leaves. A strong login can still be undermined by an uncontrolled reset process.

Ask whether security-relevant actions are logged and whether the business can obtain those records when needed.

Understand updates and vulnerability handling

Request the support lifecycle, update process and route for reporting a flaw. Establish who installs fixes and how urgent notices reach the product owner.

Ask what happens to installed versions when support ends. Include replacement or export needs in the cost review.

A secure-design claim doesn’t mean the product will never have a vulnerability.

Check suitability before acceptance

The Cyber Centre’s updated procurement guidance connects product selection with security questions and risk-based decisions.

Use the business’s data, integration, privacy and recovery requirements as acceptance criteria. A supplier’s compliance with a foreign law, such as GDPR or HIPAA, doesn’t show that the product meets your obligations under Canadian privacy law.

Record the evidence, remaining gaps and the people accepting the operating responsibilities. File that decision with your supplier security review.

Revisit it when the supplier changes ownership, the product gains significant access or support terms change.


Featured Image Credit