Currently the security configuration belongs to cps-rest module.

It causes

• the security configuration became predefined and unavoidable for any custom application assembly using cps-rest
  and other cps jars as imported dependencies
• nf-proxy only assembly will miss security configuration because it does not include the module which holds it,
  then the nf-proxy endpoints exposed will not require any authorization

Issues above can be resolved by moving security configuration to cps-application module.