Home / FAQs / Software project start-up and program selection
QUESTION & ANSWER

Sign Nda Before Sharing Software Requirements

You can. You can sign a two-way confidentiality agreement before you can provide information.

Answer the question.

First, give conclusions that can be used for decision-making

NDA should specify the scope of confidential information, permissible uses, access to persons, protective measures, exceptions, deadlines, return deletions and liability for breach of contract. The information is provided using the minimum necessary principles, production data are not sensitive, source code is used in controlled warehouses, and key is not sent through ordinary documents.

DECISION FACTORS

What conditions need to be identified before judgement is made?

The same question may have different answers under different business, data and project phases. It is suggested that the following conditions be checked and that the common findings on the web be incorporated into their own projects.

Whether the information contains personal information, business secrets or customer contractsWhich roles of the supplier do need to be visitedWhether dissensitization samples are available to complete early assessmentHow to withdraw, return and prove deletion after termination of cooperation
ACTION STEPS

Suggested order of advance

01

First, we'll be clear about the target and the border.

Initial capability communication is done first with open or dissensitized information.

02

Validation Key Dependence

Two-way confidentiality agreements matching the project are reviewed and signed.

03

Development of assessable outcomes

Establish information lists, access accounts, access rights and transmission methods.

04

Make sure you decide the next step with the real results.

The recovery authority is confirmed and returned or deleted after the completion of the phase.

PRACTICAL EXAMPLE

How do you understand it in the actual business?

Example used to illustrate the method of judgement

When signing NDA, the designated engineer is given a read-only warehouse and dissensitization test environment, and provisional access is withdrawn after completion of the diagnosis, and access records are maintained. The examples do not represent the performance of a particular client, and the actual conclusions need to be verified in conjunction with the enterprise’s own business volume, sample, system and liability boundaries.

COMMON RISKS

The easiest pit to step on.

When you sign the NDA, send the production account number and the full amount.

Protocol template does not match data type and partner

Forget to withdraw warehouse and cloud environment privileges after the project is closed

ACCEPTANCE

How should we end up receiving and confirming?

The data processing, safety and cross-border requirements are supplemented by the actual processing of personal data or vital data.

When preparing to communicate with suppliers or internal teams, it is recommended that current processes, representative samples, existing systems, planning time and budget levels be brought. First, the unknown items are clearly marked, and then the decision is made to use diagnostics, PoC, fixed-range projects or ongoing research and development, which is usually more reliable than a direct demand for a price and duration without borders.

Your project conditions are different from the examples above?

Operational objectives, existing systems, sample and planned time could be collated before consultants could make preliminary judgements in relation to actual boundaries.

Associate project consultants