The rapid growth of electric vehicles (EVs) and the corresponding need
for extreme fast charging (XFC) infrastructure have highlighted the
importance of robust cybersecurity measures. The NIST Cybersecurity
Framework Profile for Electric Vehicle Extr...
In the rapidly evolving landscape of cybersecurity, effective governance
is paramount. With the release of NIST Cybersecurity Framework (CSF)
2.0, organizations now have an enhanced toolset to manage and reduce
cybersecurity risks. FortiSOAR, a robus...
FortiSOAR™ is a holistic and enterprise-built security orchestration and
security automation workbench that empowers security operation teams.
FortiSOAR™ increases a team’s effectiveness by increasing efficiency,
allowing for response in near real-ti...
About the Integration:FortiSOAR 6.0 rolled out an enhanced integration
with FortiAnalyzer (FAZ). FAZ users can leverage this integration to
ingest FAZ incidents into FortiSOAR (FSR) and take the investigation
ahead using FSR's extensive connector lib...
Yes, as I said earlier - follow the article there for suggestions on how
this can be done.
https://community.fortinet.com/t5/FortiSOAR-Discussions/Upload-CSV-and-update-FortiSOAR-Records/m-p/219994
Try this - Create an "on-update" playbook listening on the Status
Change. In the playbook, if triggered, you can check if the last status
was "Open". If yes, you can raise a Manual Input pop-up to add in the
reason, and pass it as a comment or use ho...
Hi @MuhammadFaruqi1 - 1. For last shift report - you can create a report
in the format you want, enabling dynamic parameters in the report like
Created Date is In Last X hours, and/or shift details if you need. Now,
in a playbook, use the Reporting C...
Hi - You can, 1. Create a playbook, using ideally, "Get Incidents By
Date Range" action, and filling in right parameters and adding extra
steps, like "Get related alerts for incident" to complete the incident
information pulled in. For all incidents ...