Ivanti Security Controls 2019.3 (9.4.34544)

von | 15.01.2020

Für welches Programm wurde ein Update veröffentlicht?
Ab sofort steht das Programm Ivanti Security Controls von Ivanti in der Version 9.4.34544 (2019.3) zur Verfügung.
10.01.2020 => Releasedatum Hersteller
15.01.2020 => Releasedatum ProSoft
Sind besondere Hinweise bzgl. der Lizenz zu beachten?
Bei dieser Version handelt es sich um ein Minor Release und somit ist kein neuer Lizenzschlüssel notwendig.
Diese Version kann mit einem Lizenzkey v9.3 verwendet werden
Bug Fixes
Welche Probleme wurden gelöst?
  • Resolved an issue where the “Add delay (days)” option did not work in an agent policy.
  • Resolved an issue where the “Add delay (days)” option did not trigger in a console scheduled task.
  • Resolved an issue where a patch scan initiated via the REST API did not work due to a credential problem.
  • Resolved an issue where the console would fail when running an ITScripts template from the Tools > Run Console ITScripts menu command.
  • Resolved an issue where a patch scan would fail when running against an ESXi host configured to use a proxy.
  • Resolved an issue where upgrading from ISeC 2019.1.1 to ISeC 2019.2 would fail on non-Englishbased operating systems.
  • Resolved an issue where the Application Control engine would fail due to an incorrect file type.
  • Resolved an issue where the console would fail when accessing Protect Cloud due to improperly handling an unsupported media type.
  • Resolved an issue where a SQL database error would occur during an upgrade from Patch for Windows 9.3 to ISeC 2019.2.
  • Resolved an issue where trace logging around hypervisor download and proxy configuration was lacking.
  • Resolved an issue where performing a REST API GET request on a machine group failed due to an issue with the runAsCredential parameter.
  • Resolved an issue where the location of the Next link in the Patches function of the REST API was inconsistent with other functions.
  • Resolved an issue where patch scans would incorrectly time out due to an issue with the Connection timeout parameter.
  • Resolved an issue where enabling User Role Assignments incorrectly prevented the user from generating a report.
  • Resolved an issue where the console failed when attempting to deploy service packs that did not have a valid download source.
  • Resolved an issue where Predictive Patch automatic downloads got stuck in an In Progress state and failed to finish.
  • Resolved an issue where the Help did not properly disclose that an active user session was required in order to use the “If a user is logged on” options.
  • Resolved an issue where the console displayed an incorrect product level ISO name.
  • Resolved an issue where the REST API was missing support for RSA/AES session key encryption when using a session credential.
  • Resolved an issue where, due to a proxy credential error, one of the users at a site could not access the console following an upgrade from Patch for Windows 9.3 to ISeC.
  • Resolved an issue where a SmartFilter configuration was not preserved when upgrading from Patch for Windows 9.3 to ISeC.
  • Resolved an issue where attempting to generate an Executive Summary report for all operating system platforms failed due to a SQL Server 2008 R2 backward compatibility problem.
  • Resolved an issue where the data versions displayed on the home page were not properly updated.
  • Resolved an issue where Linux deployment history was not being updated after a deployment task was run on a Linux 7.x machine.
  • Resolved an issue where database maintenance operations would fail due to excessive amounts of asset scan data.
  • Resolved an issue where performing an agentless scan on a machine group that contains a nested group would report that no machines were found.
  • Resolved an issue where a SQL deadlock would occur when deleting machines at the same time that results were being imported.
  • Resolved an issue where a user with an assigned role that did not include Application Control was presented with an AC trial offer even though the console was already licensed or AC.
  • Resolved an issue where agents were not able to be deployed to non-English Linux machines.
  • Resolved an issue where filtering the Machine OS Listing report failed when filtering by machine group.
  • Resolved an issue where upgrading from 2019.3 EA (Build 9.4.34511) to 2019.3 GA (Build 9.4.34534) failed on non-English operating systems.
Welche erweiterte Funktionen bieten sich?
  • Improved Graphics
    The icons and images in the main console have been updated to use a scalable vector graphics (SVG) format.
    This means the console has proper high DPI support and will scale correctly on machines that have font settings
    greater than 100%.
  • Intelligent Linux Agent Installations
    When installing an agent on a Linux machine, checks will be made to see if the Linux machine is properly
    configured to support all agent functionality. If something is amiss (for example, if the machine’s Red Hat
    subscription is not current), the installation will fail and a message will be displayed informing you of the
  • Application Control Message Settings Enhancements
    The message box enhancements include:

    • Option to include a company logo as a graphic in the message box.
    • Easily resize the message box in the preview, all values of the resize are retained when the preview is closed.
    • Option to include a colored text banner in the message.
    • More descriptive default text in the message body.

    For further details, see ‘Configuration Message Settings’ in Online Help.

  • Rule Collections
    There is now only one type of Rule Collection, in previous versions this was split between Executable Control
    Rule Collections and Privilege Management Rule Collections. For further details, see ‘Rule Collections’ in Online Help.
Neue Funktionen
Welche neue Funktionen stehen zur Verfügung?
  • Linux Listening Agents
    Support is now provided for Linux listening agents. This means that the agents on Linux machines are now able to listen to the console for policy updates and commands.
  • Additional REST API Functionality
    The following functional areas are now available through the REST API:

    • Agents
    • Agent Deployments
    • Agent Tasks
    • Linux Patch Deployment Configurations
    • Linux Patch Group
    • Linux Patch Metadata
    • Linux Patch Scan Configurations
    • Policies
    • Product Level Group

    For complete information on using each of these new functional areas, see the ‘REST API Help’ in Online Help.

  • Application Control Configuration Versioning
    You can now create different versions of a configuration. Each time a modification is made a new version is created which enables the review and auditing of changes. It also means that previous versions of your configuration remain available which you can rollback to if required.

    Specific versions of a configuration can be assigned to an Agent Policy.

    Deletion of specific versions is now also possible.

    For further details, see ‘Manage AC Configurations’ in Online Help.

  • Application Control Configuration Comparison Tool
    The configuration comparison tool has been introduced so you can easily compare two different configurations
    or two different versions of the same configuration. Change tracking can quickly be identified and located.

    For further details, see ‘Configuration Comparison Tool’ in Online Help.

Welche Abkündigungen von Funktionen wurden mitgeteilt?
  • A new set of database views has been created and is organized using the Reporting2 namespace. The
    Reporting2 namespace now includes a view for CVSS scores. The original Reporting namespace will be
    removed in a future release and should only be used by legacy queries. All new queries should be
    created using the Report2.* views. For more information about report views, see the Generating Custom
    Reports section in the ISeC Help
  • Support for SQL Server 2008 and SQL Server 2008 R2 will end in a future release.
Welche zusätzlichen Informationen gibt der Hersteller?


Kunden, die ein Upgrade von Ivanti Security Controls 2019.2 oder früher durchführen, sollten die neue Anforderung der Konsole beachten:

  • Microsoft .NET Framework 4.8 oder höher (war bisher 4.7.2)

Kunden, die von Ivanti Patch for Windows 9.3 Update 1 upgraden, sollten die neue Anforderung der Konsole beachten:

  • Speicher: 16 GB RAM wird jetzt für Hochleistungssysteme empfohlen
  • Speicherplatz: 100GB wird nun für das Patch-Repository empfohlen
  • Microsoft .NET Framework 4.8 oder höher (war bisher 4.6.2 oder höher)
  • Microsoft Visual C++ Redistributable für Visual Studio 2013 (erforderlich für das Scannen von Offline-VMs)
  • Microsoft Visual C++ Neuauflage für Visual Studio 2015-2019

Weitere Hinweise entnehmen Sie bitte den Systemvoraussetzungen Ivanti Security Controls*

Beachten Sie bitte folgende, ergänzenden Hinweise.
Es stehen folgende Downloads zur Verfügung:
Bitte bewerten Sie diesen Beitrag!
[Gesamt: 0 | Durchschnitt: 0]