import { useState } from 'react'; import { Link } from 'react-router-dom'; export const Help = () => { const [activeFaq, setActiveFaq] = useState(null); const toggleFaq = (index) => { setActiveFaq(activeFaq === index ? null : index); }; return (

How can we help you?

Search our knowledge base or browse the frequently asked questions below to find the answers you need to secure your infrastructure.

search

Frequently Asked Questions

{/* FAQ 1 */}

You can start a new scan by navigating to the 'New Scan' page from the sidebar. Select your target application, choose the appropriate scan intensity (Quick, Advanced, or Deep), and click 'Start Scan'. The process will begin immediately.

{/* FAQ 2 */}

Quick scans focus on basic security controls, SSL/TLS configurations, and surface-level misconfigurations. Advanced scans run targeted security scripts against common web vulnerabilities like the OWASP Top 10. Deep scans use our complete arsenal of fuzzers and deep-crawling tools for exhaustive analysis.

{/* FAQ 3 */}

Navigate to the 'Reports' section in the sidebar. Find your completed scan in the history list, and click the 'Download PDF' button. You can also view the interactive report directly in the dashboard before downloading.

{/* FAQ 4 */}

SPAs often handle routing dynamically on the client side, which can trick traditional scanners into thinking non-existent pages are real (Soft 404s). LarShield uses advanced baseline fingerprinting to minimize these, but if you notice recurring issues, please contact support.

{/* FAQ 5: How can I manage members in my organization? */}

If you are an Organization Admin, go to the 'Organization' settings. From there, you can invite new members via email, manage their roles (e.g., Executive User, Admin), and revoke access if necessary.

{/* FAQ 6: How is the Security Risk Score calculated? */}

This assessment utilizes an enterprise CVSS-weighted, category-capped vulnerability risk scoring algorithm. The score calculation is fully deterministic, auditable, and reproducible.

{/* Section 1 */}

1. Severity Base Weights & Formula

Deduction per Finding = Severity Base Weight × [0.2 + 0.8 × (CVSS / 10)] × Confidence Multiplier

  • Critical: 25.0 pts (CVSS Scaling Range: 0.20 - 1.00x) - Immediate threat to core business logic or full system compromise.
  • High: 12.0 pts (CVSS Scaling Range: 0.20 - 1.00x) - Direct threat to application confidentiality or integrity.
  • Medium: 4.0 pts (CVSS Scaling Range: 0.20 - 1.00x) - Indirect threat or security control misconfiguration.
  • Low: 1.5 pts (CVSS Scaling Range: 0.20 - 1.00x) - Minor hardening flaw or minimal impact finding.
  • Informational: 0.0 pts (CVSS Scaling Range: 0.00x) - Best practice advisory or design note.
{/* Section 2 */}

2. Category Deduction Caps

To prevent non-exploitable misconfigurations from disproportionately penalizing the overall score, category deduction caps are enforced:

  • Security Headers: 15.0 pts max (Capped)
  • SSL/TLS Configuration: 15.0 pts max (Capped)
  • HTTP Method Tampering: 12.0 pts max (Capped & Root-Cause Deduped)
  • Cookie Security: 10.0 pts max (Capped)
  • DNS Security: 10.0 pts max (Capped)
  • Compliance Framework Signals: 0.0 pts (Unlinked — Reported Separately)
{/* Section 3 */}

3. Graduated Confidence Multipliers & Posture Floor

  • Confirmed / High: 1.00x Multiplier. Floor: 75 / 100 (Grade C) if 0 Critical & 0 Highs (≤ 15 Mediums).
  • Likely: 0.60x Multiplier. Floor: 60 / 100 (Grade D) if 0 Critical & 0 Highs (> 15 Mediums).
  • Medium: 0.50x Multiplier. Floor: 55 / 100 (Grade D) if 0 Criticals (≤ 15 Mediums).
  • Low / Unconfirmed: 0.20x Multiplier. No Floor (Grade F) if 1+ Critical Vulnerability.
{/* Section 4: Worked Calculation Examples */}

4. Worked Calculation Examples

{/* Example 1 Card */}
Example 1: Application with 15 Missing Security Headers (Capped Deduction)

Raw calculation: 15 × [4.0 × (0.2 + 0.8 × 0.53) × 1.0] = 37.4 pts.

Category Cap applied: Security Headers deduction is capped at 15.0 pts max.

Posture Floor rule: No Critical/High findings → Score = 100 - 15 = 85 / 100 (Grade B — Good).

{/* Example 2 Card */}
Example 2: Audit with 1 High, 5 Mediums, and 1 Low Finding

High (No Brute-Force, CVSS 7.5): 12.0 × (0.2 + 0.8 × 0.75) × 1.0 = 9.6 pts.

Mediums (CORS, Cookie, DNS): Sum of capped category deductions = 15.8 pts.

Low (Server Header): 1.5 × (0.2 + 0.8 × 0.31) × 1.0 = 0.7 pts.

Total Deduction = 26.1 pts → Score = 100 - 26.1 = 74 / 100 (Grade C — Fair).

{/* Example 3 Card */}
Example 3: Application with Critical Blind SQL Injection (CVSS 9.8)

Critical (Blind SQLi, CVSS 9.8): 25.0 × (0.2 + 0.8 × 0.98) × 1.0 = 24.6 pts.

High (Auth Bypass, CVSS 8.1): 12.0 × (0.2 + 0.8 × 0.81) × 1.0 = 10.2 pts.

Total Deduction = 34.8 pts → Posture Floor Disabled (Critical Present).

Final Score = 100 - 34.8 = 65 / 100 (Grade D — Poor).

{/* FAQ 7: Privacy Policy & Data Handling */}

We are fully committed to protecting your data and privacy. We align our data collection and handling procedures with global standards, including GDPR, CCPA, and India's DPDP Act.

  • Data Encryption: All vulnerability scan data is encrypted at rest (AES-256) and in transit (TLS 1.3).
  • Audit Logs: To prevent abuse, we retain metadata regarding IP origins, target configurations, and timestamped actions.
  • Third-Party Sharing: We do not sell or share your data with third parties for marketing purposes. Data is only shared with essential infrastructure providers or law enforcement if legally compelled.
Read our full Privacy Policy arrow_forward
); };