Clarge works within your organisation’s security requirements. The setup defines how access is granted, where information stays and how changes are reviewed, from the first account to the final handover.
Your organisation’s requirements guide the setup. Clarge’s own workspace and equipment are used only within the device, connection and information-handling rules agreed for the assignment.
01
Named access. Defined permissions.
Use individual accounts with the permissions needed for the work. Follow your requirements for multifactor authentication and devices, with a named owner for granting and removing access. Production permissions are handled separately.
02
Information stays in agreed places.
Keep code, documents and meeting notes in your approved repositories and channels. Use sanitised or synthetic test data wherever practical, rather than copying production information into development.
03
Approved tools, including AI.
Agree the services permitted for the work and the information each may receive. Client code, credentials and confidential material are not entered into external AI tools without explicit approval and a review of the relevant data-handling terms.
04
Secrets stay out of the code.
Handle credentials through your approved secrets process. Keep them out of source control, tickets, ordinary email and meeting notes. Document who can use them and who is responsible for rotation and revocation.
From first access to final handover.
Before access
Identify the information involved, the contracting parties and the people authorised to access it. Agree confidentiality, approved tools and any personal-data processing arrangements before accounts are connected.
During the work
Follow the agreed review and release process. Raise access or data-handling questions before expanding the work. Review any new tool, account or external integration before it receives client information.
When the work ends
Hand over code and documentation, list active access and agree what must be returned, retained or deleted. The relevant account owners revoke permissions and credentials, with completion recorded in the handover.
If something doesn’t look right.
The working setup includes a security contact, an escalation channel and reporting requirements, so concerns reach the right people.
We raise suspected incidents through that route, record what is known and follow your incident process. Your organisation retains responsibility for notification and recovery decisions.
Support hours, incident response times and any on-call coverage are agreed separately in the engagement terms.
A useful first security conversation.
If you have a supplier checklist, device policy or specific data requirements, bring them to the first conversation. They help us identify what the assignment needs before access is provided.
Keep the first enquiry general. Send credentials and confidential material only through a channel agreed for that purpose.