> For the complete documentation index, see [llms.txt](https://siff.gitbook.io/siff/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://siff.gitbook.io/siff/getting-started/siff-overview.md).

# SIFF Overview

### What is SIFF <a href="#what-is-siff" id="what-is-siff"></a>

SIFF is a cloud-based platform to search, compare, analyze, and track configuration of your Network and IT infrastructure.

* Troubleshoot and repair problems more quickly and effectively
* Collect and analyze detailed configuration information
* Monitor changes and validate against change requests
* Ensure configuration meets security requirements and assist in security incidents

### Platform Architecture <a href="#platform-architecture" id="platform-architecture"></a>

<figure><img src="/files/FME5d8BUCAWttlXfcIZw" alt=""><figcaption></figcaption></figure>

As a cloud-based platform SIFF is responsible for managing and operating the overall service, however there are a number of software components that must be installed within the customer environment. Specifically at least one SIFF Collector and optionally SIFF Agents.

Refer to Collectors & Agents for more information on installing and configuring these components.

Users interact with the platform through our web-based interface for all administration, configuration, and general use activities.

APIs are available to provide further integration with the SIFF platform.

### Platform Basics <a href="#platform-basics" id="platform-basics"></a>

#### Config Module <a href="#activity-app" id="activity-app"></a>

The Config > Search app provides a way to search for configuration - showing the current known configuration along with information on when it was last validated and full change history.

<figure><img src="/files/YLP04FgAZLdyPY5tv2nr" alt=""><figcaption></figcaption></figure>

The Config > Activity provides a way to watch and search change activity in a timeline format. Searches can be used to filter results based on change fields and also the activity time window.<br>

<figure><img src="/files/UIcF8LnLqSaRuJOXMVF7" alt=""><figcaption></figcaption></figure>

Use the Config > Change is used to track planned changes versus unplanned changes. Either manage change requests within SIFF or via integration with external chanage management systems such as ServiceNow.

<figure><img src="/files/mFzxP7SYUS6nuqzR9B36" alt=""><figcaption></figcaption></figure>

#### Analytics Module <a href="#monitor-app" id="monitor-app"></a>

The Analytics module allows you to define and schedule Reports to process the configuration data and generate CSV or JSON data for useful information. I also includes basic charts that summarizes collected data and usage. The module allows you to query you configs to extract actionable data for your ad-hoc operational queries. For example:

* Extract serial numbers from all of you Juniper devices
* Find all the IP addresses of devices not using a specific NTP server

#### Monitor Module

The Monitor module provides two main functions.

1. Discovering and managing devices to monitor:
   * Devices: Manage devices for monitoring
   * Access Credentials: Manage credentials used for monitoring purposes
   * Discovery: Automatically discover devices to monitor
2. Managing what to monitor:
   * Service Definitions: see below
   * Monitors: Manage active set of Service Definition monitors

Essentially, once devices are known to the platform and appropriate access granted then SIFF can begin monitoring of configuration data. This is based on the current set of active Service Definitions that are provided by SIFF, the community, or created by your organization.

Service Definitions provide a standard way to:

* Determine whether the definition applies to a particular device
* What configuration to retrieve from the device
* What operation data to retrieve from the device

In a new environment our SIFF Certified Service Definitions will already be active and collecting data as soon as there are managed devices to monitor.

#### Policy Module

The Policy module provides a way to monitor for compliance or detect unwanted/not permitted configurations.

In particular the following policies are offered:

1. Examine config: alert on invalid configurations, or alert when out of compliance
2. Compare config - same device: ensure different resources on the same device have matching configuration, for example the startup configuration matches the running configuration on a router
3. Compare config - on different devices: ensure configuration is the same across devices
4. Compare config - to previous config: ensure the configuration hasn't changed

Use the Policy App to manage the policy definitions, policy actions, and the set of active policy monitors.

#### Automation Module

The Automation module allows you to run commands on the devices. It allows you to apply bulk configuration changes across a number of devices in a consistent manner. The Automation module allows you to create Automation Definitons which defines the sequence of commands to execute, process the output of those commands and make conditional logic and/or loops without the need to learn any coding languages.&#x20;

There are many uses of Automation that can help simplify your daily operational tasks, for example:

* Firmware updates / software upgrades
* Pre-Post Checks
* Automated / schedule restarts
* SNMP community, trap host changes

#### Administration Module <a href="#administration-app" id="administration-app"></a>

The Admin module allows the Organization administrators to manage:

* Users: who has access to your environment and their role, along with external directory service integration.
* API Security
* Collectors: used to monitor devices in your environment.
* SSO external authentication
* Sub-Organizations

#### Billing Module <a href="#billing-app" id="billing-app"></a>

The Billing module is used to view billing statements, manage payments, and view usage. This applies only to monthly subscription accounts only.

For more information refer to the Billing documentation.
