Can coverage grow with us?
Yes. We review your coverage, staffing and support needs as your organization grows and the number of alerts or requests changes.
FAQ & AMA
Find answers about L8DT services, technology and ongoing support. This is also where answers from future Ask Me Anything sessions will live.
41 answers across 11 topics.
Try another search or topic, or suggest a question for an upcoming AMA.
Suggest a question →Yes. We review your coverage, staffing and support needs as your organization grows and the number of alerts or requests changes.
The cost depends on what we support, the hours you need covered, the work included, and whether you need shared or dedicated staff. Specialist skills and restrictions on who can access your data also affect the price.
We agree who can access the information, where they can work and which tools they can use before support begins. Each shift follows the access and data-handling rules required by your contracts.
It is one useful signal. A restore test checks whether the agreed data or service can actually be recovered by the intended owner.
We plan the test environment, timing, access and stopping points with you to limit disruption. Switching live services to a recovery system requires a separate plan and your approval.
That depends on how important the service is, how often it changes and any testing commitments in your contracts. We agree a schedule and who will record and review the results.
Monitoring spots problems and sends alerts to the right people. Fixing those problems is a separate responsibility. Your agreement explains which actions we can take, when we need approval and what work is included.
Your agreement sets out what runs automatically, when people review alerts, who responds and how urgent issues are passed on. We confirm staffing and test the handover between shifts before coverage begins.
Yes. Our Stories & scenarios collection includes an illustrative campus monitoring example. It shows how different vendors can fit into one monitoring service, with a delivery plan and estimated costs.
Licenses are customer-direct or separately quoted. Edition, term, geography and eligibility are confirmed for each environment.
Some can, but the platform and its setup must meet the requirements for your information and contracts. We review the service, access restrictions and provider responsibilities before recommending an option.
Yes. We agree which devices, applications and permissions each role needs, test the setup and account-removal steps, and give your team a repeatable checklist.
No. An assessment helps you understand gaps and plan improvements. Meeting a requirement also depends on putting the safeguards into practice and maintaining them. Formal certification, where needed, is a separate process.
Yes. We can start with a specific concern, such as account access, recovery or security logs, and give you a practical plan for the next steps.
We consider the potential harm to your business, the services affected and the effort needed to fix each issue. That helps you decide what deserves attention and budget first.
We work with PCI DSS, CMMC, the ISO/IEC 27000 and ISO 9000 series, NIST CSF, NIST SP 800-171, DFARS cybersecurity requirements and NIST SP 800-53. We help you identify which requirements and versions apply to your organization.
Yes. We can build a plan for your systems, access, day-to-day support and security requirements. Software licenses, eligible cloud services and any restricted 24/7 coverage are priced separately so you can see what is included.
No. Access depends on your approval and the restrictions attached to the information. Only eligible, approved people can handle restricted work. Round-the-clock monitoring does not give every support person access to every system.
A design review defines the certificate service, responsibilities and acceptance checks. Setup, migration and ongoing PKI as a Service can be included in a separate agreed scope. Your proposal states which stages we will deliver.
We test whether the agreed applications and devices reject a certificate after it has been revoked. That includes checking the certificate chain and how those systems receive revocation information.
Often, yes. We first review your current tools and licenses, then check whether they meet your needs and can be supported by the people who will run them.
Yes. We agree which jobs stay with your team and which L8DT takes on, including everyday support and who handles more complex issues.
We can plan 24/7 coverage using teams working across time zones. Your agreement confirms the hours, staffing, response responsibilities and access restrictions before the service starts.
Your quote lists the workstation support and cloud administration included for each person. Servers, network equipment, extra devices, licenses, projects and extended support hours may cost extra.
No. We review what still works, what is no longer supported and what is holding you back. Any recommended purchase comes with a clear reason for the business.
We check what needs to keep working, back up the settings and test changes on a small scale first. We also agree when and how to roll back if something goes wrong.
Yes. Monitoring can be added as a separate service. We agree which devices and services to watch, what should trigger an alert and who will respond.
Yes. We can review your existing environment and agree which applications, infrastructure and operating tasks L8DT will manage. Account ownership, administrator access, cloud billing and the handover process are agreed before work starts.
A migration, new environment or major upgrade is scoped as a project. Ongoing management is priced around the applications or environments covered, their complexity and the support required. Cloud usage, storage and software costs are identified alongside the L8DT service work.
Yes. We can help with supported business devices and carrier accounts you already use, including line changes, inventory, enrollment and ongoing administration. We agree the access and responsibilities with you before making changes.
The work can include a coverage review, router setup, network integration, application checks, failover and return-to-primary testing, plus ongoing monitoring. Equipment and carrier plans are selected for the location, required applications and expected usage.
It can include issuance, renewal, revocation, certificate status publication, monitoring, operating records and recovery for an agreed PKI service or environment. We begin with a review and design, agree the responsibilities and accept the setup before ongoing operations begin.
We agree key custody, protected storage, backup and recovery with you before work begins. The service design names who can approve issuance and who can administer or use each key. It also states how keys and records are handled if the service changes or ends.
We map the authorities, certificates and dependent systems, confirm recovery material, prepare the destination and pilot representative applications and devices. The plan sets migration stages, cutover checks and rollback decisions. Retirement follows agreed acceptance and retention checks.
Yes. Start by identifying cryptographic dependencies, prioritizing important services and long-lived data, and checking vendor support for the versions you use. We can pilot supported options and prepare a staged roadmap that records required upgrades and compatibility limits.
Connection key establishment and certificate or software signatures perform different jobs. Support for one does not establish support for the other. We review the actual products, protocols and versions, then test the relevant dependencies before proposing a migration.
Review, design, setup and migration are scoped as projects. Ongoing operations are scoped per agreed PKI service or environment per month, with certificate volume and the lifecycle work considered. Your proposal states service coverage, fees, licensing, hosting, key protection and each team's responsibilities.
No. Available controls can support age-appropriate choices, but apps, contacts and circumstances change. Technical setup belongs alongside family conversations, regular check-ins and a clear way to ask for help.
We agree the devices, accounts and settings to review, make supported changes with the authorized adults, check representative outcomes and provide a practical handover. The scope and any ongoing support are agreed before work begins.
Headcount does not determine the level. Review the actual solicitation, contract, information handled and system boundary with the responsible contracts and security teams. Confirm the applicable requirements and assessment path using current official guidance.
The agreed work can produce a requirement and boundary register, named responsibilities, prioritized improvements, implementation checks and an evidence handover. Ongoing program support can be scoped separately; preparation does not promise an assessment or certification result.
Ask Me Anything
Questions about IT, security and the decisions behind them are welcome. Answers from future AMA sessions will be added to this FAQ so you can find and share them afterward.
Email your question or topic. Session dates and joining details will be announced in News & AMA.