Neo4j RBAC Roles
Current state
Currently there are 2 roles used in Hyperion's Neo4j database:
TM-Analystrole with:- Read-only access to the Hyperion database
- Write access to
HiveAlertnodes - Priviledge to run the
apoc.load.jsonprocedure used to initiate web requests to enrichment APIs - Priviledge to run the
apoc.search.*procedures - reserved for future use. - Priviledge to run
point.withinBBox()andpoint.distance()functions for geospatial queries. - No read access to meta properties used by ETL pipelines (such as
last_geoip_time).- This is meant to provide an easier experience for the analyst and avoid bloating their screens with dozens of timestamps.
adminrole with full access
Future roles
SI-Analystrole:- Limited access to InfoSec data such as Hive alerts, Okta logon telemetry etc.
EXT-Analystrole:- No access to any nodes labelled CLL (i.e. sourced from within CLL)