Tools / Google SecOps Interview questions
How do SIEM settings and SOAR settings differ in administration?
Google SecOps splits administrative configuration into two separately managed areas, reflecting the platform's underlying SIEM/SOAR division, and understanding which settings live where — and when changes actually take effect — matters for day-to-day platform administration.
| SIEM Settings | SOAR Settings |
| Ingestion, parsing, and detection rule configuration. | Automation, playbooks, and platform permissions. |
| Some settings shared platform-wide, e.g. IdP group mapping. | User group settings for SOAR-specific access. |
| Permissions via IAM apply immediately. | Permission changes take effect at the user's next login. |
This immediate-versus-next-login distinction is a genuinely practical detail administrators need to know: revoking a user's IAM-managed access takes effect right away, but a SOAR-side permission change (managed outside IAM) won't apply to a currently logged-in user's session until they log in again, which matters when urgently trying to restrict someone's SOAR access — a currently active session may retain its prior permissions until that next login occurs.
More Related questions...