Successful integrations begin with understanding the data and permissions required from the source system.
Before connecting a security product, teams should identify the environments and accounts that will be included, determine the data that needs to be collected, and establish an appropriate service identity or authentication method.
Access should follow least-privilege principles. A connector should receive only the permissions necessary for the capabilities being used.
Teams should also understand API limits, data retention behavior, network requirements, and any restrictions imposed by the source platform.
After a connector is configured, validation should confirm that expected data is being received and that important relationships—such as assets, findings, vulnerabilities, and incidents—can be resolved correctly.
Specific setup requirements vary by connector. Individual integration documentation should always take precedence over this general preparation guide.