Join the FortiSOAR Community In Just 3 Simple Steps: Step 1: Sign-up at
Support PortalStep 2: Navigate to FortiSOAR Community Step 3: Click on
Join Group Hub, you are all set Note: If you are already signed into the
support portal, simply navigate to...
What do #FortiSOAR and the #PyramidOfGiza have in common? Well, apart
from being an architectural marvel and the fact that FortiSOAR is going
to SOAR in the heart of Egypt at Cairo (next week), there are some
principles we do share, 1 - Solid Foundat...
Posting a question from an industry peer here about how FortiSOAR helps
in GDPR compliance. Well two ways: 1 - FortiSOAR has a solution pack
(GDPR Framework) that helps users notify a personal data breach to the
supervisory authority as per guideline...
FortiSOAR v7.3.0 is here on a new foundation - The Rocky Linux v8.6 -
The latest and greatest. B-Bye CentOS. With this release, we introduce a
handful of features and a bagful of enhancements, performance boosters,
and loads of security consideration...
Just in case you missed out, last week we rolled out our sizzling update
to the content hub, https://fortisoar.contenthub.fortinet.com/ - an
update that adds enriched user experience, useful content categories
(like demo videos, FortiSOAR kit etc.), ...
@AliMaher , based on limited understanding of your question, I am
guessing you want to write a playbook that would give you Malicious
Indicators, and then you want to Initiate a Block of those. If this is
what you are asking for, then all you need to...
2) Using Message Feature - Every Step in the playbook has a Message
Feature. Anything you put here as static or dynamic text becomes the
comment to alert (or whichever record the playbook is executing). We use
this extensively to put comments as if a...
adding a few more and encouraging community to add the ones they have
established 1) First Step (after Trigger), should always be Set Variable
and named as "Configuration". FortiSOAR team uses this as a convention
to define all the tunables such as v...
Can you elaborate on your use case again? particularly who would trigger
this playbook? (someone by clicking a button, or invoked as
reference/subplaybook from another playbook, or scheduled) ..