We got this new book in my library, the patterns are similar to Core J2EE patterns with more emphasis on implementing security. The best practices and reality checks for designing security is very appealing. Free chapter and samples are available at coresecuritypatterns.com and securityfocus.com.
Does this book provide hints about what, when and how to secure different aspects of a system. For example with JMS one approach might be to encrypt data being sent via JMS or another alternative solution might be to run the JMS over SSL. Both approaches I feel are valid but the per message encryption approach might be a bit of overkill.
There is an excellent opportunity to ask the authors of the book anything you like: they're our guests in the Security forum this week, and are answering questions about the book and (Java) security in general.
Yeah, it looks like the saloon email sent out earlier today advertising this weeks book contest was accidentally pointing people to the wrong forum. I've sent an email to the head honcho's here in the saloon, and hopefully they'll send out a correction email later, and maybe a kind moderator could move the incorrectly positioned posts to the security forum please?
Do you give some concrete example on the implementation of JAAS into the Servlet ? (for relying on a specific profiles repository) is there something on the declarative security : put some meta data (JSR 175) into the code for tagging an intern (private) method of the servlet and delegate security control to the container
Originally posted by Noel M OConnor: Does this book provide hints about what, when and how to secure different aspects of a system. For example with JMS one approach might be to encrypt data being sent via JMS or another alternative solution might be to run the JMS over SSL. Both approaches I feel are valid but the per message encryption approach might be a bit of overkill.
Thanks for bringing this up.
The book discusses about all possible JMS Security options such as "Securing JMS Channel including message and transport", "JMS Provider Authentication", "Enabling JMS Destination Access Control". You need to be cautious about using these options...as all these options are not dictated by the JMS Specifications and it is more vendor specific.