forked from demisto/content
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Private upload mode docs #11 (demisto#28838)
* Updated Docs * added RNs * updated X-Force .pack-ignore
- Loading branch information
Showing
21 changed files
with
79 additions
and
20 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
6 changes: 6 additions & 0 deletions
6
Packs/SlashNextPhishingIncidentResponse/ReleaseNotes/1_3_6.md
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,6 @@ | ||
|
||
#### Integrations | ||
|
||
##### SlashNext Phishing Incident Response | ||
|
||
Documentation and metadata improvements. |
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
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,3 @@ | ||
Use the Spycloud API to collect the breach information from watchlists or based on domain information | ||
Use the Spycloud API to collect the breach information from watchlists or based on domain information | ||
|
||
Notice: Submitting indicators using the **spycloud-domain-data** command of this integration might make the indicator data publicly available. See the vendor’s documentation for more details. |
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,6 @@ | ||
|
||
#### Integrations | ||
|
||
##### SpyCloud | ||
|
||
Documentation and metadata improvements. |
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
1 change: 1 addition & 0 deletions
1
Packs/ThreatMiner/Integrations/ThreatMiner/ThreatMiner_description.md
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 @@ | ||
Notice: Submitting indicators using the **domain** command of this integration might make the indicator data publicly available. See the vendor’s documentation for more details. |
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,6 @@ | ||
|
||
#### Integrations | ||
|
||
##### ThreatMiner | ||
|
||
Documentation and metadata improvements. |
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
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,6 @@ | ||
|
||
#### Integrations | ||
|
||
##### URLhaus | ||
|
||
Documentation and metadata improvements. |
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 |
---|---|---|
|
@@ -5,4 +5,7 @@ ignore=BA108,BA109 | |
ignore=IM111 | ||
|
||
[file:XFE_image.png] | ||
ignore=IM111 | ||
ignore=IM111 | ||
|
||
[known_words] | ||
X-Force |
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
31 changes: 18 additions & 13 deletions
31
Packs/XForceExchange/Integrations/XFE_v2/XFE_v2_description.md
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,13 +1,18 @@ | ||
# Configure API Credentials | ||
|
||
To configure the credentials of IBM X-Force Exchange, you should generate an API key and API password. | ||
In order to generate those keys, you must have an IBM X-Force Exchange Account. | ||
Then, follow the steps below: | ||
|
||
1. Log in to the IBM X-Force Exchange website. | ||
2. Click on the profile icon, and go to Settings. | ||
3. Go to API Access tab, and generate an API key. | ||
4. Copy your API key and API password, and enter it inside the API key and password fields. | ||
|
||
**Note**: retain the API password for your records. You cannot request the API password again. | ||
Also, provide a meaningful name for the API key. | ||
# Configure API Credentials | ||
|
||
To configure the credentials of IBM X-Force Exchange, you should generate an API key and API password. | ||
In order to generate those keys, you must have an IBM X-Force Exchange Account. | ||
Then, follow the steps below: | ||
|
||
1. Log in to the IBM X-Force Exchange website. | ||
2. Click on the profile icon, and go to Settings. | ||
3. Go to API Access tab, and generate an API key. | ||
4. Copy your API key and API password, and enter it inside the API key and password fields. | ||
|
||
**Note**: retain the API password for your records. You cannot request the API password again. | ||
Also, provide a meaningful name for the API key. | ||
|
||
Notice: Submitting indicators using the following commands of this integration might make the indicator data publicly available. | ||
- ***url*** | ||
- ***domain*** | ||
See the vendor’s documentation for more details. |
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,6 @@ | ||
|
||
#### Integrations | ||
|
||
##### IBM X-Force Exchange v2 | ||
|
||
Documentation and metadata improvements. |
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