Vulnerability Assessment A vulnerability assessment identifies and prioritises weaknesses across an agreed environment. It is broad, repeatable, and particularly effective for maintaining visibility over patching, configuration, exposure, and known vulnerabilities. Penetration testing goes further by attempting to exploit s
What are we assessing? Assessing evidence and information Tribunal decision-making is often document-led, even where hearings are relatively informal. The quality, relevance, and organisation of available information can materially affect the client’s ability to present their position. Assessment does not require that eve
Assessment An assessment is the starting point for clear, proportionate tribunal support. It is a structured review of a dispute, decision, or procedural issue to identify what has happened, what forum may be able to deal with it, what evidence is available, and what practical steps should be considered next.
Vulnerability Management threat. Mahakali Tribunal Services treats vulnerability management as a governance and engineering discipline. Technical findings are translated into prioritised work, ownership is made explicit, and evidence is retained for executive assurance, customer due diligence, regulatory scrutiny, and inter
Security Assessment A security assessment provides a clear, evidence-based view of how well an organisation’s technology, processes, and people are prepared to prevent, detect, and respond to cyber risk. For Mahakali Tribunal Services clients, assessment work is designed to do more than identify technical weaknesses. I
Security Assessments • Privileged access and identity lifecycle analysis; • Review of encryption, key management, and secrets handling; • Network segmentation and remote-access review; • Logging, alerting, and security operations capability review; • Backup, recovery, and ransomware resilience review; and • Review of de
Risk Assessment The assessment does not seek to list every imaginable threat. It focuses on scenarios that are relevant to the organisation’s assets, operating environment, and threat profile. Common cyber threat scenarios include: • Phishing or business email compromise leading to credential theft or fraudulent pa
Web Application Security Assessment Likewise, the assessment provides an informed view based on the agreed scope and the time available; it cannot guarantee the absence of all vulnerabilities. Security changes over time as applications, dependencies, configurations, and threats evolve. A clean assessment result should be understood as
Penetration Testing The exercise is performed under formal written authority. Scope, testing windows, permitted techniques, escalation points, evidence handling, and emergency contacts are agreed before work begins. Penetration Testing Versus Vulnerability Assessment Vulnerability assessments and penetration tests are
Red-Team/Pentest* public-facing risk. Internal Network and Active Directory Testing Internal testing evaluates the consequences of an assumed breach: a compromised workstation, a malicious insider, a contractor account or an attacker who has passed the initial perimeter. Our consultants assess identity architecture,
Threat Modelling • Tampering: altering information, code, configurations, or records; • Repudiation: denying an action where reliable evidence is absent; • Information disclosure: exposing information to an unauthorised party; • Denial of service: preventing legitimate use of the service; and • Elevation of privileg
Threat Intelligence been targeted. A mention on a criminal forum does not necessarily demonstrate a data breach. A threat actor’s self-description is not proof of identity, capability, or access. Our analysts assess source reliability, information credibility, corroboration, timeliness, technical fit, and alternative e
Who reviews it? parameter, role assumptions, and evidence showing how inadequate authorisation was established. For a cloud configuration issue, the platform team may need the relevant account, resource identifier, policy condition, exposure path, and the configuration state observed during testing. Technical owner
What requires a qualified human? Penetration testing is often discussed in terms of tools: scanners, proxies, exploit frameworks, cloud posture platforms, endpoint agents and continuous attack-surface monitoring. These technologies are valuable, but they do not constitute a penetration test on their own. A meaningful penetration te
Cybersecurity • API and system-integration security • Software development lifecycle controls • Code and dependency security practices • Security testing coordination • Logging, audit trails, and configuration-change monitoring • Data classification, retention, and secure disposal requirements Where applications
Environmental enforcement. Vague conditions can create later dispute; excessively burdensome conditions may be vulnerable to challenge if unsupported by evidence or beyond statutory authority. Conversely, conditions that lack measurable limits, monitoring obligations, reporting requirements, or enforcement mechan
What information is required? A well-scoped penetration test begins long before the first scan, exploit attempt, or validation exercise. The quality of the assessment depends on the quality of the information available at the outset: what is being tested, who owns it, what must be protected, and how testing activity should be co
Authorised Penetration Testing Authorised penetration testing provides a clear, evidence-led view of how a determined adversary could compromise systems, data, operations, or trust. It is not a generic vulnerability scan, nor an exercise in accumulating technical findings. It is a controlled security assessment designed to answer
What should the final report contain? • Exposure of sensitive data; • Insufficient segregation between user and production environments; • A high likelihood of exploitation from the internet; or • Several individually moderate weaknesses that can be chained into a significant attack path. Avoid presenting the overall rating as a mathema
How much work is involved? For example: • Blocking one malicious input string does not necessarily correct an injection vulnerability; • Hiding an administrative button does not enforce server-side authorisation; • Updating a library may not remove the vulnerable component from deployed containers; • Restricting one cloud per
Cybersecurity — 1,000 evidence reviewed, and relevant limitations. 2. Prioritised action register — recommendations categorised as immediate, near-term, and planned improvements. 3. Control matrix — a record of the principal controls assessed, their observed status, and the evidence or explanation supporting that status.
Database Security obligations. In a legal or tribunal context, preserving logs and maintaining a defensible chain of custody may be particularly important. Initial actions may include: 1. Confirming and recording the incident indicators; 2. Restricting or isolating affected accounts, hosts, or network paths; 3. Prese
What Constitutes Critical/High/Medium/Low? Severity ratings translate technical findings into business priorities. They answer the essential question behind every penetration-testing observation: how urgently should this issue be addressed, given the realistic harm it could cause? At Mahakali Tribunal Services, Critical, High, Medium, and Lo
Cloud Security protected by strong authentication; • Data protection, covering classification, encryption, retention, recovery, and controlled information sharing; • Application and workload security, from secure design and code review through vulnerability management and runtime monitoring; • Continuous assurance
Extracted from the 11 uploaded Espresso literature volumes. These source materials are educational, not a substitute for verified, jurisdiction-specific professional advice.
