Start with the systems you rely on
Create an inventory of the applications, websites, devices and infrastructure relevant to the request. Include important connections between systems and explain which workflows depend on them. This makes the scope more concrete than a general request to make everything secure.
Describe the business concern
Explain why you are starting the project. You may be reviewing a new application, preparing an infrastructure change or seeking a clearer understanding of your current environment. State the concern in plain language so the team can connect the proposed work to your priorities.
Set boundaries and authorization
Agree on what is included, what is excluded and who can authorize the work. For any assessment or testing activity, clarify the permitted systems, timing and contact points before work begins. Do not assume that a connected third-party service is automatically part of the authorized scope.
Plan how information will be shared
Decide which information the team needs and how it should be provided. Avoid putting passwords, access tokens or sensitive customer information into a general enquiry form. Arrange appropriate access and information-sharing steps as part of the agreed project process.
Define a useful handover
Discuss the form of the findings or delivery documents, the people who will review them and how follow-up actions will be handled. Establish which team owns each next step. A clear handover connects the engagement to the people who operate the systems afterward.
Use the first enquiry to frame the need
Your initial message can identify the systems involved, your main concern and your contact details. The TCW team can then discuss scope, authorization and delivery terms. An assessment is a defined engagement; it should not be presented as a guarantee that every possible risk has been removed.
Have a related requirement?
Discuss it with TCW →
