Skip to content
SYS-01Cybersecurity

Cyber Shield Portal

Pulsar Security · via C3S Software

Backend work on Pulsar Security's cybersecurity platform: restructuring core business modules with Domain-Driven Design, making report generation reliable with AWS SQS, running background work on AWS Lambda, and adding real-time tracking for long-running scans and reports.

  • Backend engineering
  • Domain-Driven Design
  • Queue-based reliability
  • Serverless background work
Illustration · not a screenshot of client software. Illustration of a domain-monitoring dashboard: a list of monitored domains with status tags, a scan radar, and progress tracking for long-running scans and reports.
Client
Pulsar Security
Engaged via
C3S Software
Role
Software Engineer
Engagement
C3S Software · Nov 2022 – Present
Stack
  • Java
  • Spring Boot
  • AWS
  • CDK
  • DDD
Public site
cybershieldportal.com

Context

Cyber Shield Portal is a cybersecurity product for Pulsar Security, built at C3S Software. The work covered features that protect and manage more than 5,000 customer domains.

Three capabilities sit at the centre of that work: bulk domain management, dark-web monitoring and vulnerability reporting.

Domain model

The customer, domain, agreement and MSP modules were restructured using Domain-Driven Design.

The purpose was to simplify complex business logic and to make future expansion of the platform simpler.

Cyber Shield · restructured with Domain-Driven Design

  • M1

    Customer

    Module

  • M2

    Domain

    Module

  • M3

    Agreement

    Module

  • M4

    MSP

    Module

Dwg SYS-01/A

Restructured modules

Scale NTS

Status Conceptual

The four modules restructured with Domain-Driven Design. Only the module boundaries are drawn; the relationships between them are not part of the public record.

Reporting reliability

Report reliability was improved with AWS SQS. Report work gained automatic retries, and a safe recovery path for reports that became stuck or failed.

Conceptual report reliability pathReport request, then AWS SQS report queue, then report generation, then completed report. Retry loops from generation back to the queue; stuck or failed reports go to safe recovery; real-time tracking runs back to the portal.RETRYTRACKINGSTUCK OR FAILEDCYBER SHIELDreport requestAWS SQSreport queueREPORT GEN.long-running workREPORTcompletedSAFE RECOVERYfor affected reports

Dwg SYS-01/B

Report reliability path

Scale NTS

Status Conceptual

Conceptual view of the reporting work: report jobs pass through AWS SQS, failures are retried automatically, reports that become stuck or fail take a safe recovery path, and long-running work is tracked in real time. Queue topology and service boundaries are not specified.

Background processing

AWS Lambda runs work that belongs in the background: file uploads, security scans and external integrations.

  1. aBackground file uploads
  2. bSecurity scans
  3. cExternal integrations

Tracking long-running work

Scans and reports are long-running operations. Real-time tracking was added for both, so their progress is visible while they run.

The same work improved report generation speed by approximately 40%.