# platform-blueprints
Hey Tsahi, great talk, I have a question that I hope I am verbalizing in the right way: are there any specific security considerations that need to be considered when using a distributed GitOps topology with standalone GitHub's instances in each cluster? How can access control and authentication be effectively managed in this scenario?
Thank you Jordan. In the deck, I’ve demonstrated multiple repositories pointing to a single repository, but of course can point different clusters to different repository. When talking about security, with this approach, each cluster holds the creds to authenticate to the Git repo that it’s synced with. You can encrypt those creds (e.g. sealed secrets, SOPS) and also limit those creds to specific actions on the git source side. Is that what you’ve meant in your question?