Add topic about "Streangthening the security"

[raducoravu]

Description

From the DITA OT meetup discussion, Jarno may do some code changes in the DITA OT to have it avoid reading/writing content from outside the input/output folders but he cannot stop plugins from doing this.

Possible Solution

Maybe we should have a topic in the user's manual about "Streangthening the security".

Maybe tell people that they should properly check and vet all plugins bundled in the DITA OT.
Maybe tell that as the DITA OT reads content and then writes the published output they should take care to properly define the input, temp and output folders so that they do not overwrite other files.
Maybe say that if you are running DITA OT on the server side you should also avoid hogging the CPU by running too many instances at the same time or allowing the same user to post too many jobs, so have some kind of jobs executor and avoid running too many DITA OTs in parallel.
Maybe say that the content processed by the DITA OT should come from reliable people to avoid attacks based on the parsers used to parse the input content.
Maybe say that the best way to isolate the DITA OT so that it never writes or reads content from the outside would be to run it in a container like docker:
https://www.dita-ot.org/dev/topics/using-docker-images#ariaid-title1

@jelovirt if you have any ideas here?