The most serious shortcoming is its lack of granular document-level permission controls for task attachments. We ran into a real-world incident several months ago when a junior analyst uploaded a draft client penetration-test report to a task attachment. There was no way to lock that single file so only specific staff could view it; every user assigned to that overall project workspace gained access to the sensitive document. We caught the exposure risk within hours, yet we still had to manually audit every attachment across all active projects to check for similar misconfigurations, costing us half a business day of security team time. Beyond weak attachment permissions, its built-in audit logging is fairly basic. It can show you when a task got edited or completed, but it does not log who downloaded or viewed individual file attachments. For our industry, we need immutable logs of every access event for security-related deliverables to satisfy audit requirements. When external auditors request proof of who accessed assessment documents, ASHGAL-LEE cannot produce that level of detail, forcing us to pull separate logs from SureDrop instead. Review collected by and hosted on G2.com.

To improve ASHGAL-LEE, I recommend implementing more granular permission controls for task attachments, allowing specific files to be restricted to designated personnel only. Additionally, enhancing the audit logging capabilities to include detailed records of who accessed or downloaded individual attachments would be beneficial. This would ensure compliance with industry standards and provide the necessary documentation for external audits. Furthermore, integrating a more robust notification system to alert users of any unauthorized access attempts could enhance overall security. Review collected by and hosted on G2.com.

I’m a Security Operations & Admin Coordinator at our small cybersecurity firm. Before we got ASHGAL‑LEE, all our audit tasks, vendor evaluations and client remediation items were scattered across Excel spreadsheets, email threads and Google Drive. We had no central place to tie task owners, deadlines and supporting security artifacts together. Last quarter we managed three concurrent workstreams: an internal system audit, assessments for multiple security SaaS vendors, and vulnerability remediation for a local retail client. A critical vulnerability fix deadline for that retail client got buried deep inside an email thread. We almost missed our contractual remediation window, a mistake that could have exposed our client to active threats and damaged our firm’s professional reputation. After that close‑call incident, we started evaluating ASHGAL‑LEE. Now we spin‑up dedicated project workspaces for each initiative, assign owners, set hard deadlines, and attach redacted scan reports and risk questionnaires directly to tasks. The AI generates ready‑made audit checklists quickly, saving hours of manual prep work and cutting down the number of status‑chasing meetings I need to schedule every week. It gives our whole team clear visibility into ongoing security work. That being said, we still keep raw incident‑response evidence and penetration‑test materials inside SureDrop. ASHGAL‑LEE fixes our task chaos, but it is not built for storing our most sensitive security evidence. Review collected by and hosted on G2.com.