LDaaS

Overview

Modern operations are founded on having the right data in the right place at the right time. Data management, pipelining and retention strategies are key to this. Our logging data as a service approach will help you get control of your data, so you control your data, not let it be driven by vendors and tools. It provides centralised, scalable, and secure log collection, normalisation, storage, and analytics capabilities across your IT and security environment. ​

​This approach is applicable for security and operational data. However, for modern organisations 80% of data is shared between security and operational teams. In this service, we can bring together our knowledge of security and operational monitoring together to design, build and operate a data strategy that covers logs, telemetry and metrics across the organisation. 

Who is it for?

• Organisations modernising a legacy data approach​.
• Customers struggling with agent sprawl, data silos, and log non-conformity.
• Enterprises preparing to scale or optimise their data collection strategy​.
• Organisations who want to leverage their data across multiple teams, to build a data first approach.

Typically, Apto approaches an LDaaS project in an iterative fashion with customer collaboration firmly in mind. Most recently, we worked with a financial services provider in there first steps towards a global LDaaS roll out. This scheme of work spanned across 6 phases and ended with a regional LDaaS implementation to be blueprinted and rolled out across the providers other regional operations.

To begin we worked with the provider to identify candidate use cases, data sources, and geographical regions to scope LDaaS in its initial implementation. This meant developing success criteria for LDaaS giving the financial context, and the business value of LDaaS to functional and non-functional requirements. At this point we moved into the 2nd phase, creating a regionally scoped HLD for the LDaaS implementation, working to architect the solution against its success criteria and future development needs.

From here we moved into phase 3, creating a technical LLD for the solutions, detailing a clear and accurate plan for LDaaS deployment. At this point we were ready to move into the pilot LDaaS build, standing up and onboarding the scoped regional data sources. In the firth phase we focused on production rollout support – ensuring the relative customer teams were coached on LDaaS and its operational environment considered.

The sixth phase was a service transition and handover with the technical teams in the defined region, giving the financial services provider autonomy over the LDaaS project. To continually drive LDaaS and ensure it value is derivable we are now working on using this first stage as a base camp for a global LDaaS rollout with the customer.

Key Deliverables

Success Criteria ​

HLD + LLD​

Data Engineering and Tool Strategy ​

Logging & Monitoring Architecture Design Document​

Source-to-Destination Data Flow Map​

Data Normalization and Retention Policies​

Ingestion Pipelines and Parsing Logic​

Dashboards and Alerts for key stakeholder groups ​

Integration validated with key downstream systems​

Knowledge transfer and training​

Outcomes and benefits

1. Cost-efficient ingestion and data strategy with predictability​.
2. Enhanced visibility for security, operations, and compliance teams​.
3. Improved business flexibility and agility by de-coupling data value chain – decouple data ingest from downstream tools, enabling confident decision making around current vendor usage​.
4. Organisational autonomy for tooling decisions and data workflows.