Ivanti Patch Management Ivanti Patch Management

Import Ivanti Patch Management data into OverView via CSV or JSON export

This document describes how to configure the Ivanti Patch Management connector, allowing OverView to import patch management and endpoint compliance data.

Objective

The Ivanti Patch Management connector imports the following information:

  • Patch status per machine (installed, missing, pending)
  • Inventory of deployed patches
  • Compliance with patch management policies

Prerequisites

  • Access to Ivanti Patch Management with export rights.
  • Ability to generate a CSV or JSON export of the patch inventory.

Import modes

This connector works with file imports. OverView accepts the following formats:

  • CSV: tabular export from the Ivanti console
  • JSON: structured export from Ivanti

Procedure

Export data from Ivanti Patch Management

  1. Log in to the Ivanti Patch Management (or Ivanti Security Controls) console.
  2. Go to the Machines or Patch Status view.
  3. Select the machines and patches to export.
  4. Use the Export or Report function to generate a CSV or JSON file.
  5. Download the generated file.

Import into OverView

  1. In OverView, go to Data Sources Settings > Sources.
  2. Select Ivanti Patch Management and click Configure.
  3. Choose CSV Import or JSON Import mode.
  4. Upload your export file (50 MB maximum).
  5. Configure column mapping if needed.
  6. Click Save Configuration.

!!! tip "Automation" To keep data up to date, schedule regular exports from Ivanti and import them periodically into OverView.

Uploading files through DropPoint

Files for the Ivanti Patch Management connector are stored in a dedicated S3 bucket named ivanti_patch_management. Drop your CSV (or JSON) files at the root of s3://ivanti_patch_management/: OverView automatically detects new files and imports them on the next synchronization.

Where do the files go?

Bucket : s3://ivanti_patch_management/

Example : s3://ivanti_patch_management/export.csv

Several ways to send your files

You can populate your bucket in several ways:

  • OverView web interface — import your files, configure the mapping, then click “Replace” to refresh the data without redoing the mapping.
  • AWS CLI — for a one-off or scripted upload.
  • S3 SDK (boto3, etc.) — to fully automate recurring imports.

Using the AWS CLI

# Upload a file to the ivanti_patch_management bucket
aws s3 cp export.csv s3://ivanti_patch_management/export.csv --profile ovs_your_org

# Or sync a whole local folder
aws s3 sync ./exports/ s3://ivanti_patch_management/ --profile ovs_your_org

Automating the import via S3

import boto3

s3 = boto3.client(
    "s3",
    endpoint_url="https://s3.oversoc.com",
    region_name="fr-par",
    aws_access_key_id="YOUR_ACCESS_KEY",
    aws_secret_access_key="YOUR_SECRET_KEY",
)

# Push the export into the ivanti_patch_management bucket
s3.upload_file("export.csv", "ivanti_patch_management", "export.csv")

Pair this script with a scheduled task (cron on Linux, Task Scheduler on Windows) to push your exports automatically at a regular interval. Each upload triggers a new import on the OverView side.

Prerequisite: generate your S3 credentials and configure your client (endpoint, profile) as described in the OverView DropPoint guide. The profile and endpoint used here are explained there.

← PreviousManageEngine Endpoint CentralNext →Microsoft SCCM (MECM)