-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
PAPP-35185: release notes and further documentation
- Loading branch information
1 parent
5fbca98
commit d858ac8
Showing
3 changed files
with
154 additions
and
13 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
[comment]: # " File: README.md" | ||
[comment]: # "Copyright (c) 2025 Splunk Inc." | ||
[comment]: # "" | ||
[comment]: # "Licensed under the Apache License, Version 2.0 (the 'License');" | ||
[comment]: # "you may not use this file except in compliance with the License." | ||
[comment]: # "You may obtain a copy of the License at" | ||
[comment]: # "" | ||
[comment]: # " http://www.apache.org/licenses/LICENSE-2.0" | ||
[comment]: # "" | ||
[comment]: # "Unless required by applicable law or agreed to in writing, software distributed under" | ||
[comment]: # "the License is distributed on an 'AS IS' BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND," | ||
[comment]: # "either express or implied. See the License for the specific language governing permissions" | ||
[comment]: # "and limitations under the License." | ||
[comment]: # "" | ||
|
||
This connector supports both cloud and on-prem delivered FMC. Below are the steps for connecting to both | ||
|
||
## Connecting to a cloud delivered FMC | ||
|
||
1. On Cisco Security Cloud Control navigate to User Management | ||
2. Create a new Api Only User with an Admin role | ||
3. Copy the Api key and enter it in the "Api key for cloud delivered FMC" input box in the SOAR Asset Settings page | ||
4. Specfiy Cloud for the type of FMC you are connecting to | ||
5. Specify your region in the "Region your Cisco Security Cloud Control is deployed in" input box and click Save | ||
|
||
## Connecting to an on-prem delivered FMC | ||
|
||
1. On the SOAR asset setting page select On-prem for the type of FMC you are connecting to | ||
2. Specify the device ip/hostname of your on-prem FMC along with the username and password used ot login to FMC | ||
|
||
**Note** that you can optionally specify a default firepower domain that will be queried. You an overide this domain when running an action. In addition, cloud versions of FMC only support the default domain, to achieve multi tenancy you must use seperate tenants. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1,28 @@ | ||
**Unreleased** | ||
* Initial Cisco Secure Firewall connector with the following actions and features: | ||
* Support for both cloud and on-prem delivered FMC | ||
* test connectivity | ||
* list network objects | ||
* create network object | ||
* update network object | ||
* delete network object | ||
* get network groups | ||
* create network group | ||
* update network group | ||
* delete network group | ||
* get access control policies | ||
* create access control policy | ||
* update access control policy | ||
* delete access control policy | ||
* get access control rules | ||
* create access control rule | ||
* update access control rule | ||
* delete access control rules | ||
* list intrusion policies | ||
* create intrusion policy | ||
* update intrusion policy | ||
* delete intrusion policy | ||
* list devices | ||
* get deployable devices | ||
* deploy devices | ||
* get deployment status |