This connector analyzes the XML results file produced by PingCastle to generate indicators on the security level of Active Directory (AD) and synchronize vulnerabilities from the report as gaps in Tenacy.
This connector collects several types of information:
AD Indicators: number of users, active users, dormant accounts, machines, accounts with passwords, users with passwords that expire.
AD Security Level Indicators: overall PingCastle score, privileged accounts score, machines and users score.
Vulnerabilities as Gaps in Tenacy: vulnerability name, criticality (according to PingCastle points) and description
Add and configure the connector
To add this connector, go to Catalogue > Connectors > PingCastle > Add connector
After adding the connector, you must configure:
Operator perimeter: the perimeter that operates and dictates the AD hardening rules to which the default indicators will be attached.
Frequency: frequency of XML file imports from PingCastle and periodicity of the associated indicators.
⚠️ When instantiating this connector, the Active Directory Hardening (TE163) measure will automatically be applied to the connector’s operator perimeter, if not already in place.
Once the connector is created, the configuration continues:
Risk points threshold: the threshold above which PingCastle risks will be synchronized as gaps in Tenacy.
Gaps register: Issues identified by PingCastle can be raised as gaps in Tenacy if a gaps register is configured. You can also create your own register by entering its name in the input field. If the register does not exist yet, Tenacy will create it when saving the configuration.
Maximum number of gaps: Only if you wish to limit the creation of gaps to a certain number, this value cannot exceed 100. If the field is left empty, Tenacy will synchronize the 100 (or fewer) most critical vulnerabilities (above the chosen threshold) identified by PingCastle as gaps.
💡 In the XML file, the GenerationDate field allows the indicators to be attached to the correct reporting period, regardless of the import date. For a report generated in November with a monthly frequency, the extracted indicators will be linked to the previous full period: October.
⚠️ If reports are imported out of chronological order, the gaps statuses (open/closed) are not guaranteed, as the import of gaps relies on the connector execution date rather than the date in the XML report.
💡 Additionally, PingCastle expresses its scores in "Risk Level," so a score of 100/100 is a bad score. Tenacy expresses its scores in "Compliance Level," so 100 on PingCastle will correspond to 0 in Tenacy.
Run your first test
Once the connector is properly configured, test the integration by running an initial execution.
Go to ⚙️ > Connectors > Click on the PingCastle connector > Run now > Add your file:
💡 Feel free to contact Tenacy support if you have any questions regarding this.