Guidance on migrating complex Essbase security filters to Oracle EPM FreeForm

We are currently migrating a Hyperion Essbase application to Oracle EPM FreeForm and would like your guidance on the best approach for migrating complex Essbase security filters.

Our challenge is that many of our existing Essbase filters are not simple member-level grants. They are allow-list filters with Default Access: None and multiple Read rows combining descendants across several dimensions, effectively defining valid data intersections rather than simple hierarchical access.

A representative example is the following Essbase filter from application/database CoReF:
Filter: GR_Asuntos Legales y RegDefault Access: NoneRows: 8
Examples of rows:Read: @IDESCENDANTS ("Negocio ARG"), @IDESCENDANTS ("Total Egresos"), @IDESCENDANTS ("Nodo.A230000"), @IDESCENDANTS ("Nodo.A221000"), @IDESCENDANTS ("Version Budget"), @IDESCENDANTS ("Real AJ"), @IDESCENDANTS ("Version Forecast")Read: @IDESCENDANTS ("Negocio ARG"), @IDESCENDANTS ("Juicios y Contingencias"), @IDESCENDANTS ("Version Budget"), @IDESCENDANTS ("Real AJ"), @IDESCENDANTS ("Version Forecast")Read: @IDESCENDANTS ("Soc_M710"), @IDESCENDANTS ("Vista Resultados"), @IDESCENDANTS ("Version Budget"), @IDESCENDANTS ("Real AJ"), @IDESCENDANTS ("Version Forecast")Read: @IDESCENDANTS ("Ru (VxE)_ASUNTOS LEGALES E INSTITUCIONALES"), @IDESCENDANTS ("Ru (VxE)_RESTO RU_CECO"), "vista x eficiencia rubros", @IDESCENDANTS ("Ru (VxE)_ASUNTOS LEGALES Y REG."), @IDESCENDANTS ("ASUNTOS LEGALES E INSTITUCIONALES (VxE)"), @IDESCENDANTS ("ASUNTOS REGULATORIOS Y WHOLESALE (VxE)"), @IDESCENDANTS ("Version Budget"), @IDESCENDANTS ("Real AJ"), @IDESCENDANTS ("Version Forecast")