We should provide a repository that stores known, good Rule Sets. These Rule Sets can then be pulled from the repository and installed in any APEX-SERT instance. This mechanism can also be used to provide updates based on new releases of APEX.
This can be done via ORDS web services and hosted in the OCI Free tier. We should require users to at least provide an email and provide them with a unique key. This can be used for anonymous metrics, as well as the ability to terminate a user who is making too many requests. We can also send out notifications when new updates are pushed so users of APEX-SERT can pull and install them.
Rules should also have a VERSION column that is specific to the rule, not version of APEX. This will allow for rule "patches" to be created & delivered, in the case of a bug with the rule.
We should provide a repository that stores known, good Rule Sets. These Rule Sets can then be pulled from the repository and installed in any APEX-SERT instance. This mechanism can also be used to provide updates based on new releases of APEX.
This can be done via ORDS web services and hosted in the OCI Free tier. We should require users to at least provide an email and provide them with a unique key. This can be used for anonymous metrics, as well as the ability to terminate a user who is making too many requests. We can also send out notifications when new updates are pushed so users of APEX-SERT can pull and install them.