¶ Object hierarchy
Until now, we used simple base objects, like host, vulnerability or patch. But world is more complex. There are a lot of sources for vulnerabilities, hosts, patches and other data. We use object hierarchy to enrich model with more information from different sources.
¶ Example - describe AnsibleHost
See fcpc describe to show more information about describe command
fcpc --describe.object.links=none --describe.format=plantuml describe object/ansiblehost
You can see that objects are inherited. Starting from Core object to AnsibleHost. This helps us to search for specific objects fro different sources.
¶ Simple objects versus hierarchical objects
When searching for data within model, always consider if you want objects from specific source or all objects with same type.
You can use "+" sign as suffix for object to match all subobjects.
- "Host" - matches only bare hosts, not hosts from other sources
- "NmapHost" - matches only hosts created by nmap module
- "Host+" - matches all hosts from all modules
¶ Example
fcpc add nmaphost/abc ip=10.10.10.10 description="Host collected by nmap"
fcpc add ansiblehost/def description="Host collected by Ansible"
fcpc search host
Next - History, Transactions and audit
Previous - Showing impacts of objects
Start - See all steps