IPAM 1.0.3
  • 28 Mar 2023
  • 2 Minutes to read
  • Dark
    Light
  • PDF

IPAM 1.0.3

  • Dark
    Light
  • PDF

Article Summary

tags: Python | Enrichment | IPAM | OpenWISP | Subnet | Internal IP


Description

Integration with OpenWISP IPAM supports CDC users by providing enrichments for internal IPs via REST API. This enables CDC users to make informed decisions regarding incident response.

OpenWISP IPAM is the IP address space administration module of OpenWISP.

CyberProof provides CLI commands to cater to different user actions, such as:
• Create IP, enrich IP, update IP, delete IP
• Create subnet, create subnet through CSV
• Enrich host, enrich subnet
• Create organization, delete organization, get organization list

CyberProof has also provided a custom input adaptive card form for IP, subnet, organization operations - so that a CDC user can perform these actions on IPAM to get the required information in the CDC. Custom adaptive cards are extensively used to display the enriched information in the CDC.

Integration Type:Enrichment
Information read:IP, Subnet, Organization details
API Supported:Rest APIs
Input:Details required to Create, Enrich, Update, Delete IP or Subnet or Organization
Output:Details enriched information about IP, Subnet, Organization provided in Input

Customer Configuration

No specific configuration required at the customer end.


CDC Command Lines

* **create_ip_cli**
Create IP address

OptionTypeDescriptionRequired
ipstringIP address ipv4 or ipv6True
subnetstringsubnet where IP needsTrue
internet_facingbooleaninternet facing.False
host_namestringIP address name.False
descriptionstringIP address description.False
critical_assetstringcritical asset can be in range 1-5.False

* **create_subnet_cli**
Create subnet address.

OptionTypeDescriptionRequired
subnetstringtext file to upload for adding subnetTrue
subnet_namestringname of the subnetTrue
descriptionstringdescription of the subnetFalse

* **import_subnet_cli**
This CLI of the CDC is used to upload a file from the CDC to the IPAM client server. Note the following: 1. At least one of use case config or rule config file name needs to be mentioned. 2. Input files for this CLI should be mandatorily in ".csv" format only. 3. Input 'overwrite' must be a boolean value (true/false). 4. While running the CLI, enter the Incident ID or Channel ID or Alert ID (in CDC version < 2.2).

OptionTypeDescriptionRequired
subnet_filestringsubnet import file nameFalse

* **ip_operation_form_cli**
Populates form to handle IP operation.

OptionTypeDescriptionRequired

* **subnet_operation_form_cli**
Populates form to handle subnet operation.

OptionTypeDescriptionRequired

* **update_ip_cli**
Update IP address.

OptionTypeDescriptionRequired
ipstringip address.True
host_namestringIP address name.False
descriptionstringIP address description.False
internet_facingbooleaninternet facing.False
critical_assetstringCritical asset can be in range 1-5.False

* **update_subnet_cli**
Update subnet address.

OptionTypeDescriptionRequired
subnetstringtext file to upload for adding subnetTrue
subnet_namestringname of the subnetTrue
descriptionstringdescription of the subnetFalse

Workflows

* **get_file_content_subworkflow**
This workflow is used to get the content of the yaml file attached to a CDC incident, alert, or channel.

* **post_create_organization**
Post create-organization in the CDC, by the ID of the incident/message/channel.

* **post_delete_ip**
Post delete-ip in the CDC, by the ID of the incident/message/channel.

* **post_delete_organization**
Post delete-organization in the CDC, by the ID of the incident/message/channel.

* **post_delete_subnet**
Post delete-subnet in the CDC, by the ID of the incident/message/channel.

* **post_enrich_host**
Post enrich-host in the CDC, by the ID of the incident/message/channel.

* **post_enrich_ip**
Post enrich-ip in the CDC, by the ID of the incident/message/channel.


Rules

No rules


Sensors

No sensors


Triggers

No triggers


Known Issues

No known issues


Was this article helpful?