How does grandfathering work with Nexus Firewall?

I have applications in one environment. That environment has the components downloaded and applications built. They were not monitored with Lifecycle.

They are moving to a new environment that has Firewall and Lifecycle. They are existing apps (so grandfathering would help), but building them in the new env for the first time requires the components to be downloaded. Firewall is blocking those downloads, appropriately.

I plan to grandfather the findings in Lifecycle for these apps. But first I think I’ll need to waive the components through Firewall to do so. Is that the case? Or if I can move the binary over and manually upload to Lifecycle in the new env to be grandfathered will Firewall then see the grandfathered components and allow them through without being waived?