01
Design around dependencies
Assess existing architecture, owners and critical integrations. Record sizing assumptions, prerequisites and acceptance criteria before product selection.
Technology ecosystem / Professional services
OdysseyCS
Connect security telemetry to structured investigation.
Odyssey Cybersecurity’s ClearSkies platform supports threat detection, investigation and response. We organize source onboarding and use-case validation around analyst workflows so telemetry becomes a usable security operating capability.
Vendor reference • Product availability and licensing are confirmed for each engagement.Official vendor website ↗
IRIS Technology / Delivery capabilities
Why IRIS for OdysseyCS
Architecture, implementation and an accountable operational handover.
Engagement deliverablesSource onboarding matrix, validated detection catalogue, investigation workflow and escalation guide.
02
Implement with change control
Pilot representative workloads, validate compatibility and stage production changes with agreed rollback criteria.
03
Hand over an operable service
Deliver configuration records, test evidence and runbooks. Define support boundaries, escalation and lifecycle responsibilities.
Capabilities & products
Solution scope
Select the capabilities that meet your control objectives, application dependencies and operating model.
01
Telemetry onboarding
Prioritize sources, verify parsing and establish reliable timestamps and asset context.
ClearSkies
02
Detection use cases
Build a scoped detection backlog with test evidence and actionable investigation criteria.
Threat detection • Investigation
03
Response workflows
Define analyst roles, escalation and response approval before workflow automation.
TDIR
Requirements & controls
Control objectives and evidence
Technology supports a control programme; it does not establish compliance on its own. Validate policies, operating procedures and evidence alongside implementation.
Telemetry and investigation quality
Verify source coverage, parsing, timestamps and asset context before evaluating detections.
Response workflow
Exercise alert-to-closure scenarios with assigned analysts, escalation and retained evidence.
Before implementation
Technical questions
Questions to resolve before committing to a platform or deployment scope.
What should be accepted before declaring a SIEM deployment operational?
Confirm critical source coverage, data quality and tested detections. Exercise the complete path from alert to investigation, escalation and closure. Retention, platform administration and response ownership need explicit scope; collecting logs alone does not demonstrate operational readiness.
What is confirmed before product selection and quotation?
We confirm the current product edition, supported versions, deployment options, integration prerequisites and license scope. Availability, subscription terms and required add-ons are checked for the proposed environment rather than inferred from portfolio branding.
Can the engagement include ongoing support or managed operations?
Support and managed operations can be scoped around agreed assets, responsibilities, service windows and escalation arrangements. Monitoring, change authority and vendor escalation are documented in the service scope; they are not assumed to be included with a product license.
Regional delivery
OdysseyCS expertise. Local accountability.
IRIS Technology delivers OdysseyCS architecture, implementation, migration and support scopes through established operations in Saudi Arabia and Jordan. Products, licensing and responsibilities are confirmed for each engagement.
Content reviewIRIS Technology · Updated October 2026Product reference: official vendor website
Bring your requirements into a clear technical scope.
Discuss architecture, delivery priorities, migration constraints and the operating model with our team.