“Live in 7 Days” — SOW Language & Go-Live Prerequisites
Language for Statement of Work terms & conditions, and the prerequisites for a 7-day go-live.
Language for Statement of Work Terms & Conditions
Go-Live Timeline
Any go-live date, timeframe, or estimate referenced in this SOW, is an estimate only, applicable solely where Client has an existing, active deployment of Google Security Operations/Microsoft Sentinel at the time of SOW execution and is further contingent upon Client's timely completion of the onboarding requirements set forth in Section III below ("Onboarding Requirements"). TENEX's ability to meet any estimated go-live date is further dependent on Client providing accurate information, timely access, and required approvals. Delay in Client's completion of the Onboarding Requirements will extend the estimated go-live date on a day-for-day (or reasonable) basis and will not constitute a breach of this SOW by TENEX.
Customer Cooperation
Client will cooperate in good faith and provide timely responses, approvals, access, and personnel availability as reasonably requested by TENEX to support the go-live timeline, including adhering to scheduling and information requests within the timeframes TENEX requests. TENEX's estimated go-live timeline assumes Client's prompt cooperation on this basis; delay attributable to Client's failure to cooperate in a timely manner will extend the estimated go-live date and will not constitute a breach of this SOW by TENEX.
Onboarding Requirements
- Google SecOps or Microsoft Sentinel must be fully deployed and review ready by TENEX at least 7 business days before go-live.
- Google service account and keys generated, configured with proper permissions, and provided to TENEX securely using TENEX approved password access management system at least 7 business days before go-live.
- TENEX platform integration with Google SecOps or Microsoft Sentinel is fully configured and validated at least 6 business days before go-live.
- Customer and tenant setup is completed in the TENEX platform at least 6 business days before go-live.
- Critical log sources including EDR, SEG, Mailflow, CSPM, and Cloud Audit are ingested and normalized properly to allow TENEX detection rules at least 3 business days before go-live.
- Google curated and TENEX detections are loaded covering EDR, SEG, Mailflow, CSPM, and Cloud Audit technologies at least 3 business days before go-live.
- TENEX playbooks are loaded into Google SecOps or Microsoft Sentinel at least 3 business days before go-live.
- Context authored in TENEX platform including VIP assets, standard operating procedures, allowlists, analyst notes, and detection guidance at least 3 business days before go-live.
- Default agents enabled in TENEX platform at least 3 business days before go-live.
- Escalation details have been provided to and verified by the TENEX team at least 1 business day before go-live.
Path to Go-Live, Day by Day
- Day 1Google SecOps or Microsoft Sentinel access is established
- Day 2Verified ingestion and normalization of critical data sources
- Day 3TENEX platform is integrated and verified
- Day 4TENEX content is loaded and enabled in Google SecOps or Microsoft Sentinel
- Day 5Context is curated and agents are enabled in TENEX platform
- Day 6SOC escalation details are validated
- Day 7Go-Live
TENEX SECURITY, INC.
“Live in 7 Days” Disclaimer & SOW Language
Approved Reference Language for Marketing & Legal
This document contains the approved disclaimer language for use anywhere the “Live in 7 Days” promotional tagline appears, along with the corresponding contract language to include in a Statement of Work (SOW) if a client asks that the timeline be referenced in the underlying agreement. For the avoidance of doubt, Legal does not recommend offering to add a reference in the SOW and it should only be done at the explicit request of the client and with approval from Legal. Marketing and sales teams should use the disclaimer text exactly as written, without paraphrasing, and should route any requested edits through Legal.
I. Disclaimers for Marketing Materials
Short Form
USE FOR: ADS, SOCIAL MEDIA, LANDING PAGE BANNERS
Go-live timing assumes the client is an existing Google Security Operations or Microsoft Sentinel customer and prompt completion of required onboarding steps; actual timing may vary. See [Onboarding Requirements]* for details.
*These can be listed via a web link.
Standard Form
USE FOR: PRESENTATIONS, WEBSITE, AND OTHER LONG-FORM MATERIALS
The referenced go-live timeline is an estimate applicable to prospective customers with an existing, active deployment of Google Security Operations or Microsoft Sentinel, and assumes timely completion of all required [Onboarding Requirements]*, as further described in the applicable Statement of Work. Customers using other SIEM platforms, or without an existing deployment of Google Security Operations or Microsoft Sentinel, should expect a longer onboarding and go-live timeline. This timeline is provided for illustrative purposes only and does not constitute a commitment, service level, or warranty of any specific go-live date.
*These can be listed via a web link.
II. Language for Statement of Work Terms & Conditions
Include the following provisions in the Statement of Work whenever a client specifically asks that the “Live in 7 Days” or any related go-live timeline be referenced in the underlying contract. The use of the language below must be approved in advance by Legal.
Go-Live Timeline
Any go-live date, timeframe, or estimate referenced in this SOW, is an estimate only, applicable solely where Client has an existing, active deployment of Google Security Operations/Microsoft Sentinel at the time of SOW execution and is further contingent upon Client’s timely completion of the onboarding requirements set forth in Exhibit [__] (“Onboarding Requirements”). TENEX’s ability to meet any estimated go-live date is further dependent on Client providing accurate information, timely access, and required approvals. Delay in Client’s completion of the Onboarding Requirements will extend the estimated go-live date on a day-for-day (or reasonable) basis and will not constitute a breach of this SOW by TENEX.
Customer Cooperation
Client will cooperate in good faith and provide timely responses, approvals, access, and personnel availability as reasonably requested by TENEX to support the go-live timeline, including adhering to scheduling and information requests within the timeframes TENEX requests. TENEX’s estimated go-live timeline assumes Client’s prompt cooperation on this basis; delay attributable to Client’s failure to cooperate in a timely manner will extend the estimated go-live date and will not constitute a breach of this SOW by TENEX.
III. Prerequisites for 7 Day Go Live
Google SecOps or Microsoft Sentinel Deployed
EDR, SEG, Mailflow, CSPM, Cloud Audit are ingested and normalized properly
Detections are loaded covering EDR, SEG, Mailflow, CSPM, Cloud Audit technologies
Service account and keys generated, configured with proper access, and provided
TENEX integration is configured
Customer and tenant setup in TENEX platform
Escalation details provided and verified
Context authored in TENEX platform
Default agents enabled in TENEX platform


