What's new in the Security Center SDK - Security Center

Security Center SDK Release Notes

Applies to
Security Center
Last updated
Content type
Release notes
English (United States)
Security Center

With each release, new features, enhancements, or resolved issues are added to the product.

The following capabilities are now available in the Security Center SDK:

New .NET Framework requirements

Starting with Security Center 5.8 GA, .NET Framework 4.7.1 is included in Security Center. The minimum Windows 10 version supported is 1607 (Windows 10 Anniversary Update). The Security Center installation will fail with older versions of Windows 10.

For more information, see About upgrading Microsoft .NET Framework for Security Center SDK.

Associate a camera with a zone

Using the SDK, you can now access the list of cameras associated with a zone, add new cameras to the list, and remove cameras from the list.
NOTE: Accessors of the camera list are not exposed in the SDK.

The following attributes were added to support this functionality:

  • ReadOnlyCollection<Guid> Cameras
  • AddCamera(Guid cameraGuid)
  • RemoveCamera(Guid cameraGuid)

Delete ghost camera archives

Using the SDK, you can now delete a ghost camera and the related archives in the same operation.

A new boolean attribute called deleteArchives has been added to ActionManager.DeleteGhostCamera to support this functionality.

Expose Archiver NTP settings

Using the SDK, you can now read and write the NTP server configuration of Archiver roles.

ArchiverRole.NtpConfiguration (of type NtpSettings) was added to support this functionality. NtpSettings exposes the following properties:

  • Server
  • Port
  • PollTimeout

Run standalone applications with FIPS enabled

The Security Center SDK is now Federal Information Processing Standard (FIPS) compatible. Standalone applications that use the SDK must be modified to run with FIPS enabled. The following changes are required:

  • Microsoft .NET Framework 4.8 must be installed.
    NOTE: If your application is compiled against .NET Framework 4.8, no further action is required. The application is automatically FIPS compatible.
  • If your application is compiled against an earlier version of the .NET Framework, an app.config file for the application is required and must include the following entry:
    <AppContextSwitchOverrides value="Switch.System.Security.Cryptography.UseLegacyFipsThrow=false"/>

    At minimum, the app.config file must contain:

    <?xml version="1.0" encoding="utf-8" ?> 
    		<AppContextSwitchOverrides value="Switch.System.Security.Cryptography.UseLegacyFipsThrow=false"/> 

Store macro execution history in activity trail

Macro executions are now logged by the system. The execution history is available in the Audit trails task.

Video analytics: Expose people count properties

To view and change the behavior of a people count module from the SDK, new fields have been exposed in VideoAnalyticsPeopleCountingEvent and VideoAnalyticsPeopleCountingAlarmEvent.

The following attributes were added to support this functionality:

  • EntityNbr
  • RuleName
  • Update
  • Direction
  • Count
  • EntityNbr
  • RuleName
  • Count