I'm have good resources on both security, domain modelling, and architecture patterns. I've noticed a distinct lack of any suggestion of how and where to integrate security into the systems I build. I imagine the thing that applies the most is Access control, as Authentications and many other security forms would seem to be obviously a layer above the model and is pretty easy to separate and find a place for. Access Control to actions seems more of a grey area. Are there any good resources on this? I prefer well written books, but other resources are also welcome.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or specific expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, see the FAQ for guidance.
The twins of Authentication and Authorization are the key to your initial questions. Access issues are the glue that bring together the three environments that you mentioned.
From there, secure programming techniques are useful to ascertain that your coding of the domain and other layers will stand up to abuse.
It should be somewhat obvious how architecture patterns and the domain layer dovetail with each other. Security is an omnipresent concern that applies across all of the layers.
Any tomes integrating all three aspects are likely to be dated or irrelevant for your focus. When you multiply the three sets of information (security, domains, architecture) against each other, you can see how it would be impossible to write a single book that adequately covered the topics of interest to everyone.
It is quite essential, because security of the system is very high level topic where beginner and intermediate programmers are not interested in. Thus, there is less questions and discussions on the topic.
In my mind, beside authorization and authentication mechanisms, security also should start with Domain design. Thus, it needs to be close to external usages and designed by SOLID principles .
You may also find it interesting to look at IT Security SE discussions.