Home

Principles

• mobile first
• notifications-oriented display
• 1-click resolution
• integration with popular tools -> slack, teams, trello (task trackers, chatbots)
• rag dash, routes back to 1-click resolution
• simple reporters notification publishing interface
• host text/html
• extensible resolver from generic abstraction

Components

Reporter

Scripts, Services, or Agents that discover and forward actionable data to the Relay tier.

Recon

A Syntinel-provided Reporter.

Relay Tier

• Formats Reporter data to "Signal"
• Sends Signal message to Subscribers (push notification)
• Record Signal message in Store
• Includes Gateway for Signal Cue Response

Resolver

Receives client response and passes to automation provider.

• Broker: examines config for redirect to proper Resolver
• Resolver: Automation provider, could be “anything, anywhere”

Signal and Cues

• JSON message that contains
  • Cues
    • Options for resolving Signal message
  • UI Abstraction
    • Generic JSON to describe UI
    • Subscriber choice implements for client requirement
  • Default Cue Choice
    • Optional timeout for default Cue

UI Abstraction

• JSON layout for translation to miscellaneous client types
  • Slack
  • Teams
  • HTML
  • Text
  • Support for “any” client architecture

Resolver Abstraction

Resolver Broker examines Signal for selecting proper automation provider

• AWS Native (Lambda), redirects to “anything” under known provider model

Resolver Provider

• Proper automation provider to act on targets based on Cue response

Iterative dev plan

• mvp 1: reporter service, signal file sans UI abstraction, email interface, existing inbound gateway
• mmp 1: reporter service, signal file with UI abstraction, email interface, API Gateway, fixed resolvers
• mvp 2: resolver abstraction, supporting signal config
• mmp 2: UI subscriber implementation, subscriber infra