Teminfra
Server, cloud and on-premises operations, infrastructure patching, deployment and recovery within the accepted scope.
Accountable for infrastructure operationsSecurity & data.
Before service starts, we agree on access, change boundaries and how results will be checked. These controls inform the assessment and service agreement. Temika Cyber provides specialist security support under a separate scope. Teminfra carries out the approved operational controls.
Discuss access & scopeThe interactive demo on this site uses example data. Role selection is not a production login, work records stay in your browser, and no commands are sent to servers. How website data is stored
Agreed before
operations begin.
Each control has an owner and verification evidence. Implementation depends on the platform and selected scope.
A staffed team is available 24/7. Response, update and recovery targets are defined in the service agreement.
Access and authority
The service owner names the approvers. Administrators use individual accounts, minimum permissions and MFA where supported. Emergency access, expiry and revocation are defined before service starts.
Evidence to reviewAccess register, designated approvers and review records.
Changes and approvals
Approval covers the plan version, environment, work window and rollback. Changes to the impact or schedule require another review. The operator records execution results.
Evidence to reviewThe approved plan version and post-change verification results.
Operational data and secrets
Define the monitoring data required, storage location, permitted readers and retention period. Passwords, private keys and access tokens use the agreed secrets manager. Tickets contain only the necessary references.
Evidence to reviewData categories, redaction rules and deletion schedules.
Backup and recovery testing
Agree on the data to back up, copy locations and recovery targets. Restore tests run in an isolated environment, then the service owner validates the results. Unresolved findings remain recorded.
Evidence to reviewRestore test evidence, timing, validation results and follow-up actions.
Incidents and escalation
Define reporting channels, impact levels and primary and backup operators. Update schedules and conditions for involving application teams, vendors or Temika Cyber are included in the service agreement.
Evidence to reviewImpact, incident owner, updates and response results.
Handover and service exit
The service owner receives the inventory and outstanding work. Unneeded accounts, tokens and integrations are revoked. Data copies are returned or deleted as agreed, with evidence reviewed together.
Evidence to reviewHandover checklist, access revocation evidence and owner acceptance.
Data access follows
the work required.
These boundaries are proposed during the assessment. Access to one system does not automatically grant access to all company data.
| Data category | Agreed handling |
|---|---|
| Inventory & metrics | Asset identities, status and update times for the operations team and designated client contacts. |
| Tickets & work evidence | Impact, approvals and results. Sensitive data is redacted before it is included in reports. |
| Password & token | Stored in the agreed secrets manager. Work records contain references only. |
| Application content & backups | Copy locations, access permissions and use in testing are agreed specifically with the data owner. |
Assessment references.
References are selected for the systems being assessed. Listing them is not a claim of Teminfra certification or an audit result.
Part of
Temika Group.
Teminfra manages infrastructure operations. Temika Cyber provides specialist security support. TemiDev supports application development.
Meet the teams and their rolesTemiDev
Application development, integrations, code fixes, application dependencies and pipeline logic.
Visit TemiDevTemika Cyber
Specialist security assessments, penetration testing, SOC, DFIR, GRC and security verification within an agreed engagement.
Visit Temika CyberEach company has its own scope. Access, assignments and fees are agreed before handoff. Clients can continue using their own developers or security providers.