Which Bloodhound API call should be used to update the schema and import data into Bloodhound?

Hi,

Thank you for this tool.

Which Bloodhound API call should be used to update the schema and import data into Bloodhound? Your instructions does not say. This is needed for the -B parameter.

Is the schema output, BloodHound-customnodes, from MSSQLHound.ps1 still valid so that it can be used as an alternative to above? Using this output it seems that for example :MSSQL_HasLogin is missing which makes for example the query MATCH p = (:Base)-[:MSSQL_HasLogin]->() RETURN p fail. On the other hand MATCH p = (:Base)-[:MSSQL_Login]->() RETURN p, which does exist, also fails. I have imported a regular Bloodhound dump as well as a dump from MSSQLHound. When I search a user account that I know has access to MS SQL I get three results, the regular original AD account node type, the new MSSQL_Login node type and the new MSSQL_DatabaseUser node type. Still the above queries and others fails.

Start by reviewing the -B parameter instructions and the BloodHound import/API behavior, then compare the BloodHound-customnodes output from MSSQLHound.ps1 with the reported MSSQL relationship queries. Done means the supported schema-update and data-import call is identified, the schema format is confirmed, and the relevant query behavior is documented.