With service-oriented architecture entering into the mainstream and the fundamental role security service played in Grid computing, it is necessary and commonplace to integrate security service(s) with other Grid services. However, current ad-hoc, handcrafted and proprietary integrating manners greatly hinder the the newly-integrated service?s QoS (Quality of Service) and QoP (Quality of Protection). Efficient and effective security-service integration entails a higher-level abstraction of specific integration scenarios. That?s where this paper takes root. In this paper, we borrow some idea from software engineering and propose several integration patterns of Grid security service. According to the number of the to-be-integrated non-security service(s), we classify all the patterns into 2 kinds: bilateral patterns and multilateral patterns, and propose 6 patterns (binding, on-demand, tailor, composite, contract and migration) and 4 patterns (separated, shared, mediated and enhanced) respectively. For each pattern, we discuss its intent, applicability, participants and consequences.