Personal Experience Passing HTB CJCA: What to Know Before the Junior Cybersecurity Analyst Exam
A cybersecurity professional who recently began transitioning careers has published a comprehensive guide based on successfully passing the HTB CJCA certification. The post details what the author wished they had known before attempting the exam, covering preparation, exam structure, note-taking strategies, and examiner feedback.
What CJCA Actually Entails
Although often described as an entry-level certification, CJCA differs significantly from typical training labs or CTF challenges. The exam places candidates in a realistic laboratory environment where they must complete tasks as a working security professional would. There are no multiple-choice questions; instead, participants receive a lab and must solve problems while producing a professional report. The certification evaluates both offensive and defensive skills, requiring candidates to analyze events from a defender’s perspective in addition to performing attacks.
The exam lasts five days. Separate passing scores are required for the red team and blue team portions, meaning strong performance in one area cannot compensate for weakness in the other.
Preparation Steps Taken
The author completed the entire Junior Cybersecurity Analyst learning path in HTB Academy before the exam. Additional practice included solving Easy and Medium difficulty machines across multiple platforms. Prior to the exam, the candidate also began the SOC Analyst Path on LetsDefend to gain familiarity with how attacks appear in logs and how to work with those logs effectively.
Modules on reconnaissance, such as Footprinting and Network Enumeration with Nmap, proved foundational. Process-oriented modules like Introduction to Penetration Testing and Pentest in a Nutshell helped frame the overall workflow. Blue team modules covering Security Monitoring & SIEM Fundamentals, Windows Event Logs & Finding Evil, and Incident Handling Process were identified as particularly valuable.
Exam Experience and Key Advice
The first day was spent understanding the assignment and creating a plan rather than immediately running scanners. Working in short 4-5 hour sessions allowed the candidate to finish within four days while maintaining mental freshness. When stuck on one task, switching between red and blue team activities helped generate new perspectives.
The second phase proved most challenging, requiring analysis of security events, decision-making, and justification of each action. This defensive mindset demanded separate preparation beyond typical offensive skills.
Note-Taking and Reporting Practices
Effective note organization formed half the battle for producing the final report. The author maintained a structured folder system with dedicated files for scope, reconnaissance per host, findings, walkthroughs, credentials, flags, alerts from phase two, and host summaries. Screenshots were captured immediately, and each finding followed a consistent format covering what was discovered, its location, severity, detection method, attacker value, and remediation steps.
Reports were prepared in SysReptor. The author recommends learning the tool before the exam to avoid wasting time during the test. Findings were enriched with MITRE ATT&CK mappings, indicators of compromise, and detection recommendations to address both phases of the exam.
Examiner Feedback and Lessons
The red team portion scored 100 points while the blue team portion passed the threshold. The report received praise for clearly describing the impact of each finding and providing practical recommendations that maintained the tester’s independence. Constructive criticism emphasized signing command outputs, providing sufficient reproduction evidence, documenting hosts with no findings, and explaining vulnerabilities specifically rather than using generic CVE or CWE references.
The author advises future candidates to allocate more preparation time, especially for blue team activities involving event analysis and alert triage. Following the exam, the individual completed the LetsDefend SOC Analyst Path and identified CDSA as the next certification goal.
Related articles
Yandex Black October: How Architectural Flaws and Capacity Mismanagement Turned Data Center Losses Into a 11-Day Fintech Coma
In October 2026 three Yandex data centers in Central Russia were physically destroyed within days, triggering the collapse of Yandex Cloud and multiple core services. Between the first and third site failures engineers had 74 hours to restore quorum and rebalance workloads yet failed to do so because Control Plane components remained tied to the lost zone and spare capacity had been eliminated to cut costs. Core banking and BNPL systems entered Read-Only mode after losing quorum, forcing a complete stop-the-world reconciliation that lasted until 22 October. Backups stored inside the same regional S3 buckets proved unusable, resulting in a seven-day RPO and primary-key collisions after restoration. The incident exposed that Metro-Cluster designs had been incorrectly treated as full Disaster Recovery and that aggressive AP microservice patterns created logical split-brain conditions outside the database layer.
Astra Group Releases Low-Code Astra AI Platform for Building Corporate AI Agents in Closed Environments
Astra Group has launched the Astra AI Platform, a low-code constructor designed for creating corporate AI applications that operate entirely within closed circuits without reliance on foreign clouds. The platform targets small and medium businesses as well as large corporations, enabling rapid deployment of AI secretaries, technical support assistants, and other agents in days rather than months. It forms part of the broader Astra AI ecosystem and includes two main constructors: one for machine learning model training and deployment, and another for LLM-based language assistants, document search, and process automation. Users can assemble scenarios from visual blocks, debug them in real time, or extend functionality with custom Python code when needed. The solution supports RAG-based knowledge bases, integration with external tools such as CRM and ERP systems, and the coordination of multiple agents for distributed task handling. One demonstrated use case involves processing ten pages of engineering drawings and specifications in five minutes to prepare data for downstream systems. The product is already listed in the Russian domestic software registry and available to customers.
Multi-Tenancy Isolation in VictoriaMetrics, VictoriaLogs and Grafana: Building Client Separation in a Shared Stack
Voltir runs a single shared monitoring stack consisting of VictoriaMetrics, VictoriaLogs, Grafana and vmalert for all customers instead of deploying separate instances per tenant. Isolation relies on numeric account IDs enforced at every layer: nginx validates tokens against the platform API before proxying writes, Grafana data sources hard-code tenant accounts, and vmalert rules receive automatic account filters. The team discovered that a single malformed rule or template could break alerting for every tenant because vmalert loads the entire rules directory at once. They also found that Grafana automatically created personal organizations granting Org Admin rights, accumulating hundreds of orphaned organizations and users that consumed disk space and resources. A dedicated cleanup module plus hourly reconciliation now removes rules, organizations, series and users when a tenant is deleted, while isolation tests verify both data and API objects across tenants.
The Real Costs of Using Claude and GPT for Russian Businesses Exposed
Accessing generative AI models like Claude and GPT has become straightforward for Russian companies, yet calculating their true expenses remains complex. Hidden factors such as intermediary commissions, currency conversion rates, taxes, and the often-overlooked costs of model reasoning tokens can double or triple initial estimates. Founder Vitaly Nagay of the Heli service analyzed these financial and organizational risks for Russian firms relying on foreign AI providers. In one example, a support department processing 20,000 monthly queries sees costs rise from $240 to $480 when reasoning tokens are included. Nagay recommends evaluating providers by dividing actual ruble charges by the model's official dollar pricing to reveal hidden markups. Additional concerns involve data control, document compliance, and access history when employees use personal subscriptions. Companies are advised to verify billing details, data storage policies, and issue dedicated API keys with spending limits before procurement.