One of the horrible things about SecurityException is just how little information you are given.
For example, let us take a look at:
Yes, that is informative. The real problem is that most security analysis is done at the method level, which means that _something_ in this method caused this problem. Which meant that in order to debug this, I have to change my code to be like this:
Which gives me this:
Just to point out, the first, second, etc are purely artificial method names, meant just to give me some idea about the problem areas for this purpose only.
Then we need to go into the code in the First method and figure out what the problem is there, and so on, and so forth.
Annoying, and I wish that I knew of a better way.