Publishing - out of the of the box the only other target supported for replication is the Static Agent which you can configure to generate static resources which can then be transferred to some other system (the transfer is something custom you have to set up). See this page for info on that. In addition there are several other methods for making content available to other systems:
Once you replicate to Publish other systems can directly access content from publish - either as HTML fragments or JSON for example.
You can also create custom replication agents with customer content builders that would integrate with other systems. This could become very complicated very quickly so I'd lean towards some sort of simply noticiation that new content is available and then let consuming application pull content via REST from publish.
Security management - See the documentation around operations monitoring (https://docs.adobe.com/docs/en/aem/6-2/administer/operations.html). There isn't much out of the box around security monitoring. You can however use something like Splunk or other log aggregaters to pull security metrics out of the logs (by configuring a specific log file that handles specific security related log categories.
AEM doesn't provide any specific functionality around DDOS attacks. Realistically that kind of protection has to happen well above the application layer at the edge of you network. What you can do is reduce the impact of a DDOS attack on an AEM system by following the measures documented in the standard security list (https://docs.adobe.com/docs/en/aem/6-2/administer/security/security-checklist.html).
Malicious file uploads - I don't know of anything out of the of the box. Generally that philosophy around things like cross site scripting is not prevent the upload, but to filter it out on display. Doesn't necessarily work with file uploads however. I have in the past integrated 3rd party products to workflows that handle this issue.
Direct HTML input - yes AEM can support this basically with a custom template that basically has one text field in the page properties that let's you copy and paste in the HTML of the page. It's not really best practice - it can lead to all sorts of bad things but you can definitely make it work.
Publishing - out of the of the box the only other target supported for replication is the Static Agent which you can configure to generate static resources which can then be transferred to some other system (the transfer is something custom you have to set up). See this page for info on that. In addition there are several other methods for making content available to other systems:
Once you replicate to Publish other systems can directly access content from publish - either as HTML fragments or JSON for example.
You can also create custom replication agents with customer content builders that would integrate with other systems. This could become very complicated very quickly so I'd lean towards some sort of simply noticiation that new content is available and then let consuming application pull content via REST from publish.
Security management - See the documentation around operations monitoring (https://docs.adobe.com/docs/en/aem/6-2/administer/operations.html). There isn't much out of the box around security monitoring. You can however use something like Splunk or other log aggregaters to pull security metrics out of the logs (by configuring a specific log file that handles specific security related log categories.
AEM doesn't provide any specific functionality around DDOS attacks. Realistically that kind of protection has to happen well above the application layer at the edge of you network. What you can do is reduce the impact of a DDOS attack on an AEM system by following the measures documented in the standard security list (https://docs.adobe.com/docs/en/aem/6-2/administer/security/security-checklist.html).
Malicious file uploads - I don't know of anything out of the of the box. Generally that philosophy around things like cross site scripting is not prevent the upload, but to filter it out on display. Doesn't necessarily work with file uploads however. I have in the past integrated 3rd party products to workflows that handle this issue.
Direct HTML input - yes AEM can support this basically with a custom template that basically has one text field in the page properties that let's you copy and paste in the HTML of the page. It's not really best practice - it can lead to all sorts of bad things but you can definitely make it work.
