Security Requirements Engineering is emerging as a branch of Software Engineering, spurred by the realization that security must be dealt with early on during the requirements phase. Methodologies in this field are challenging as they must take into account subtle notions such as trust (or lack thereof), delegation, and permission; they must also model entire organizations and not only systems-to-be. In our previous work we introduced Secure Tropos, a formal framework for modeling and analyzing security requirements. Secure Tropos is founded on three main notions: ownership, trust, and delegation. In this paper we refine Secure Tropos introducing the notions of delegation and trust of execution (at-least delegation and trust) and delegation and trust of permission (at-most delegation and trust). We also propose the use of monitoring as security pattern that can be a design solution to overcome the problem of lack of trust between actors. The paper presents a semantics for these noti...