Notice of Archiving

Dear Forseti users,

We are writing to inform you that we plan to archive the Forseti-Security repository.

Over the past few years, GCP Security has introduced a host of new features and capabilities that have addressed many security challenges targeted by Forseti. With low community engagement and limited improvements in the last two years, we have decided to place Forseti Security in archive. Note that other repos such as Forseti Real-Time-Enforcer and Resource-Policy-Evaliation-Library have also been automatically archived in February 2023 following no activities.

We plan to complete the archiving process by the end of June 2023.

What does this mean for you?

The Forseti-Security repository will be read-only, meaning that users will not be able to modify or contribute additional code.

You will however be able to fork or clone the repository and continue to use it however bearing ownership of your instance.

There will be no additional support from Google on Forseti. We are moving the existing support teams to new projects.

We thank you for your active engagement over the last few years.

Notifier

This page describes how Forseti Notifier is used and run.

Notifier can either run as part of the scheduled cron job’s workflow or manually invoked using the Forseti command-line interface (CLI).

When the cron job runs the Notifier, it sends notifications on the latest violations from the previous Scanner run.

Running Notifier

Following are the CLI commands you can use with Notifier:

  forseti notifier --help

  forseti notifier run

  # Send the violations by inventory index id.
  forseti notifier run --inventory_index_id <INVENTORY_INDEX_ID>
  
  # Send the violations by scanner index id.
  forseti notifier run --scanner_index_id <SCANNER_INDEX_ID>