Project context
Retain supported project, folder, organization, service, and resource identity.
GOOGLE CLOUD CONNECTOR
GCP recommendations remain conditional. If a tenant does not operate GCP, Technolay should not manufacture a missing-connector warning; if it does, the connector supplies current project context.
Illustrative product workflow. No customer compliance data is shown.
Who this is for
Retain supported project, folder, organization, service, and resource identity.
Use supported policies, roles, members, and service-account context.
Capture supported logging, monitoring, and security configuration returned by authorized APIs.
Recommend GCP evidence only when discovery or tenant state indicates the provider is relevant.
How it works
Authorize the account and identify its environment.
Collect the broad reasonable configuration returned by the supported API calls.
Redact secret-like values and retain source, account, environment, and timestamp.
Use relevant facts in control analysis and require human review of the result.
Frequently asked
No. Credentials are encrypted for connection use, and secret-like fields are removed from evidence snapshots.
Yes. Separate connections can represent different accounts and environments.
Not by default. Any supported write capability is separately enabled, narrowly scoped, confirmed, and audited.
Authoritative sources
We cite primary sources and describe Technolay as an independent implementation platform. Source ownership and official interpretation remain with the named publisher.
We will use your frameworks, infrastructure, evidence sources, and operating model—not a generic sales deck.
Book a demo