It is historically known that extensive phases of rework affect directly both costs and quality of already developed applications. In regard to requirements, systems security figure among those which are left behind, generating undesired steps of reformulation. This article is a short presentation on design patterns and non functional security requirements; it relates both and shows that an initial use of certain patterns, in early development phases, might reduce the impacts of relegating the systems security requirement implementation to a second plan.