Security & Governance
Protecting Your Systems and Information
Technology engagements can require access to important business systems and information. YESA establishes project-specific security, access, development, change, and escalation arrangements appropriate to the agreed scope.
Arrangements agreed for each engagement
Identity & Access
Named accounts, multi-factor authentication, approved roles, and least-privilege access where applicable.
Environment Separation
Appropriate separation of development, test, and production environments.
Controlled Production Access
Customer-approved access, defined activities, and access removal when no longer required.
Secure Development
Documented code, configuration, testing, and change practices appropriate to the engagement.
Incident Escalation
Agreed communication and escalation steps for suspected security or service incidents.
AI Data Boundaries
Defined sources, permissions, evaluation, and human oversight for AI solutions.
Transparency from start to offboarding
- Subcontractor transparency: Cilondis is named as the delivery partner
- Data location and handling agreed in each engagement
- Backup and business-continuity responsibilities defined
- Customer offboarding and access removal at the end of an engagement
- Documents, configurations, and source code handed over appropriately
Certifications
Have specific security requirements?
Tell us about your environment and obligations, and we will walk through how access, data, and changes would be handled.
Discuss Security Requirements