India ITSAR Software Changes NCCS Update Explained

India ITSAR Software Changes NCCS: What Changed

India has introduced an important clarification in its telecom security certification process that directly impacts how manufacturers approach testing. The National Centre for Communication Security in India now allows controlled software changes during ITSAR security testing, providing more flexibility during the evaluation phase. This update reflects a more practical approach to certification in India, acknowledging that issues may arise during testing and need to be addressed without restarting the entire process.

Key changes include:

• Software modifications are allowed during testing

• Issues can be fixed without restarting the full process

• Faster and more efficient certification timelines

What was the rule before?

Previously, the ITSAR testing process in India was more rigid. If any issue or non-compliance was identified during testing, manufacturers were often required to stop the process, make the necessary corrections, and then restart testing from the beginning. This approach frequently led to longer certification timelines, increased costs, and delays in product launches in the Indian market, especially for complex telecom equipment where software adjustments are common during validation.

Previously, if issues were found during testing, manufacturers often needed to:

• Stop the testing process

• Fix the issue

• Restart or repeat testing

  
  

This led to longer timelines and higher costs.

Why it matters

This update makes the testing process more practical.

In simple terms, manufacturers can:

• Fix problems during testing

• Avoid unnecessary delays

• Reduce re-testing costs

What manufacturers should do

Manufacturers undergoing ITSAR testing in India should take a more structured and proactive approach to managing software changes. It is important to work closely with testing laboratories in India to ensure that any modifications are clearly documented, justified, and compliant with NCCS expectations. At the same time, companies should ensure that these changes do not impact critical security features, as significant modifications may still require additional validation or re-testing under India’s regulatory framework.

If your product is undergoing ITSAR testing:

• Work closely with your testing lab

• Document all software changes

• Ensure changes do not affect core security requirements