> For the complete documentation index, see [llms.txt](https://docs.cybaops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybaops.com/settings/connector-and-schedule-screen.md). # Connector and Schedule Screen ### **1. Overview** Within CybaOps, **Connectors** and the **Schedule Screen** work together to manage synchronisation between the platform and third-party security tools. * **Connectors** allow integration with external vendors. * The Schedule Screen controls and monitors how and when data is synchronised. * All synchronisation activity is visible and status-driven. The Schedule Screen is not just for connectors — it also includes other operational schedules such as domain scanning and vulnerability scanning. This structure ensures transparency, reliability, and clear communication when third-party data is delayed or unavailable. ### **2. Licensing & Connector Availability** Connector access depends on the customer’s license tier. #### **CybaLite** * No connectors available. * The Schedule Screen includes: * Domain Scanning schedule only. This tier focuses on core scanning capability without third-party integrations. *** #### **CybaCore** **Available Connector**: * Entra **Schedule Screen includes**: * Domain Scanning * Qualys (internal and external vulnerability scanning) * Entra connector (if configured) This tier introduces integration with Entra while enhancing vulnerability visibility via Qualys. *** #### **CybaEdge** **Available Connectors:** * Entra * Defender * Microsoft Sentinel * SentinelOne * Bitdefender * CrowdStrike * LimaCharlie * Sophos **Schedule Screen includes:** * Domain Scanning * ZAP * Qualys * All configured connectors **CybaEdge** significantly expands third-party integrations and introduces additional scanning capabilities. *** #### **CybaOne** Includes: * All CybaEdge connectors * Flare Schedule Screen includes: * Domain Scanning * ZAP * Qualys * All configured connectors This tier offers the most comprehensive integration coverage. ### **3. Configuring Connectors** Connectors are set up directly within the UI. **Customer Actions**: 1. Navigate to the Connectors section. 2. Click **Connect** next to the desired third-party tool. 3. Enter the relevant credentials or integration details. 4. Save the configuration. Once connected: * The connector appears on the **Schedule Screen**. * Synchronisation begins according to its scheduled execution. There is no hidden automation — visibility always moves to the Schedule Screen. You can find our connector guides [here](/getting-started/onboarding/connectors.md) ### **4. The Schedule Screen** The Schedule Screen is the central control and visibility layer for: * All configured connectors * Domain scanning schedules * Vulnerability scanning schedules (e.g. Qualys) * ZAP scanning (where applicable) It provides: * Real-time status * Synchronisation timestamps * Health visibility * Manual intervention options This ensures customers always understand the operational state of their integrations. ### **5. Schedule Screen Fields Explained** Each row on the Schedule table contains the following fields:
FieldDescription
NameThe name of the third-party tool or scan being scheduled.
TypeThe category or type of tool being synchronised.
StatusA key indicator showing the health and execution state of the schedule.
Last RunThe last time CybaOps successfully synchronised data with the third-party tool.
Next RunThe next scheduled synchronisation time.
These fields provide complete transparency into integration timing and behaviour. ### **6. Schedule Statuses Explained** Understanding schedule statuses is critical for interpreting system health. **New** * A brand-new connection. * Last Run: Never * Next Run: Now Expected lifecycle: * Moves to **Queued** within approximately 5 minutes. * Then transitions to **Stable** once running normally. *** **Stable** The schedule is running as expected and synchronising correctly. This is the desired steady state. *** **Queued** The schedule is due to start within the next 60 seconds. This indicates imminent execution. *** **Late** The schedule should have started but is slightly delayed. * No known error. * Expected to move to Queued shortly. Late does not indicate failure — only a timing delay. *** **Failing** The schedule cannot run successfully. * A status message is provided. * Error messages come directly from the third-party tool. * Common reason: inability to connect to the vendor platform. **Important:** * Internal support is automatically notified. * The team begins remediation immediately. * Customers do not need to report the issue, though they may contact support if concerned. This proactive monitoring ensures reliability without requiring customer intervention. ### **7. Why Schedules Are Important** Schedules are essential for: * Transparent service delivery * Clear communication when issues occur * Visibility into third-party dependency failures * Maintaining trust with customers Because CybaOps relies on third-party vendors for certain data, it is important to clearly communicate when: * Vendor systems are unavailable * Data synchronization is delayed * External errors occur The Schedule Screen provides that transparency. ### **8. Customer Actions in the Schedule Screen** Customers can interact with schedules using the three-dot action menu next to **Next Run**. **Bump** The primary customer action available. **What It Does:** * Forces the schedule to run within the next 15 minutes. * Overrides the normal waiting period. For MDR modules and connectors: * These synchronise every 5 minutes. **What Happens During a Bump?** When bumped: * CybaOps synchronises with the third-party tool. * The latest available data is synchronised. This is particularly useful when: * A vulnerability has been remediated. * A configuration has been changed. * Immediate confirmation is required. ### **9. Special Consideration: Qualys** Qualys behaves differently from most connectors. **Key Behaviour:** * Qualys Cloud Agents scan devices every 4 hours. * CybaOps can synchronise immediately. * However, if Qualys has not completed a scan, there will be no new data to retrieve. *** **Practical Example** 1. A vulnerability is remediated. 2. The next scheduled scan is 24 hours away. 3. The customer bumps the schedule. 4. CybaOps synchronises within 15 minutes. 5. If Qualys has not yet scanned the device, the vulnerability may still appear. **Important Guidance** * Qualys may take up to 4 hours to reflect new data. * Some remediations require device restart. * Best practice: * Restart the device. * Wait a minimum of 4 hours (for the Qualys agent to run a scan). * Bump the schedule. This prevents confusion around delayed vulnerability updates. ### **10. Internal Monitoring & Support** If a schedule enters Failing status: * Internal teams receive automatic notifications. * Investigation begins immediately. * Remediation is handled proactively. **This ensures:** * Minimal disruption * Reduced need for customer escalation * High operational reliability ### **11. Relationship Between Connectors & Schedules** The relationship is straightforward: * Connectors enable integration. * Schedules control synchronisation. * Schedule health reflects connector health. **Without a schedule:** * A connector cannot synchronise data. **Without a connector:** * There is nothing to synchronise. Together, they form the operational backbone of CybaOps’ third-party integration model. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.cybaops.com/settings/connector-and-schedule-screen.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.