Going to AWS re:Invent 2024? Meet with us and discuss our latest product release on Discovery and Remediation of standing access. Book a time with us today! 
Attack Surface
An attack surface in permissions management refers to the sum total of all potential vulnerabilities that an unauthorized entity could exploit to gain access to a system or data.
What are adjustable access policies?
Adjustable access policies are designed to dynamically adapt to changing contexts, ensuring that access permissions are always aligned with the current needs and security requirements. This proactive approach eliminates the inefficiencies and risks associated with manual access management.
How Adjustable Access Policies Work
- Context-Aware Automation:
- Access policies automatically adjust based on real-time changes in context, such as:
- Team membership updates.
- Role changes (e.g., promotion or reassignment).
- Project lifecycle stages (e.g., development, testing, production).
- Environmental factors like location, device type, or time of access.
- Example: If an engineer moves from one project team to another, their permissions for the old project are revoked, and the appropriate access for the new project is granted without manual intervention.
- Access policies automatically adjust based on real-time changes in context, such as:
- Preemptive Configuration:
- Policies are designed to anticipate and respond to common scenarios:
- Engineers gaining temporary access during an incident.
- Seasonal adjustments (e.g., higher access needs during a product launch).
- Automatic offboarding access removal for departing employees.
- The system ensures that the right level of access is ready when needed, without delays.
- Policies are designed to anticipate and respond to common scenarios:
- Integration with Workflow and Events:
- Policies can integrate with triggers from CI/CD pipelines, ticketing systems (e.g., Jira, ServiceNow), or monitoring tools (e.g., PagerDuty):
- Example: When an incident is declared in PagerDuty, engineers involved in the response are temporarily granted elevated access to production systems.
- Policies can integrate with triggers from CI/CD pipelines, ticketing systems (e.g., Jira, ServiceNow), or monitoring tools (e.g., PagerDuty):
Benefits of Adjustable Access Policies
- Eliminating Manual Updates:
- IM (Identity Management) teams and others no longer need to manually adjust permissions for every new project, role, or incident. This reduces administrative workload and speeds up response times.
- Reducing Mistakes:
- By automating updates, the risk of human error—like granting excessive permissions or forgetting to revoke old access—is greatly reduced.
- Seamless Engineer Experience:
- Engineers gain access to the tools and systems they need exactly when they need them, without delays or frustrating permission requests.
- Improved Compliance and Audit Readiness:
- Automatic logging and consistent policy application ensure that organizations are always audit-ready, with clear documentation of who had access to what and when.
Real-world Example
Imagine a team working on deploying a feature to production. With Adjustable Access Policies:
- As soon as a deployment ticket is marked as “in progress,” engineers are granted the necessary permissions for production systems.
- Once the deployment is complete, and the ticket status changes to “done,” these permissions are automatically revoked.
- No manual updates, no forgotten access, and complete security coverage.
30-Day Free Trial
Get StartedA
C
G
I
J
L
M
O
P
R
S
T
V
Z