Start with the buyer, product and data

A buyer may ask a supplier to complete a security questionnaire, follow a policy, provide an audit report or use a named assessment scheme. These requests often come from a contract or procurement process. Ask the buyer for the exact requirement, the systems in scope, the evidence it accepts and the deadline.

A product sold across a border can also have legal requirements. Those depend on the product, the market, the role of the exporter and the information the business handles. There is no universal cyber security certificate that every Indian exporter must hold before shipping goods.

Data protection rules can also matter. For example, the European General Data Protection Regulation may apply to a company outside the European Economic Area when it targets people there, monitors their behaviour or processes personal data for an organisation in the region. Exporting a physical product alone does not settle that question.

Automotive customers may request TISAX

An automotive customer may ask a supplier to complete a TISAX assessment based on the VDA Information Security Assessment catalogue. The request depends on the customer relationship and the information handled. Confirm the required assessment objectives and level with the customer before you start.

TISAX results are shared through the ENX process. A general penetration test or ISO certificate does not automatically replace a TISAX assessment when a buyer specifically requires TISAX.

EU and US rules apply to defined cases

The EU Cyber Resilience Act concerns products with digital elements placed on the EU market. It does not make every textile, bicycle part or machine component subject to the same product rules. A manufacturer of connected equipment or software should check whether the product is in scope and what role it has in placing it on the market.

NIS2 covers defined sectors and entities, subject to scope and size rules. A supplier outside the EU is not automatically covered only because it sells to an EU customer, though the customer may include supplier security terms in its contracts. In US Department of Defense contracts, CMMC requirements apply to systems that handle specified Federal Contract Information or Controlled Unclassified Information, including relevant subcontractor systems.

Build evidence that matches the request

Keep an asset list, access review, update records, backup test results, incident contacts and supplier list. Limit access to buyer data and use a clear process for reporting security events. Ask whether a buyer needs a specific certificate or whether evidence of controls is enough.

Do not pay for a certification or assessment until the buyer confirms the scope and accepted scheme. CYPEE can help assess websites, applications, servers and networks, then help you plan technical fixes for the systems in scope.