<![CDATA[Abstrak Aplikasi E-Raport menyimpan data akademik, identitas siswa, dan aktivitas penilaian yang bernilai sensitif sehingga membutuhkan pengujian keamanan sejak tahap pengembangan. Penelitian ini bertujuan menganalisis celah keamanan pada kode sumber aplikasi E-Raport berbasis Laravel dengan pendekatan OWASP Top 10 dan Static Application Security Testing (SAST), kemudian menyusun langkah mitigasi yang dapat diterapkan langsung oleh pengembang. Metode penelitian menggunakan eksperimen laboratorium dengan alur shift-left security, meliputi pemetaan aset kode, konfigurasi Snyk Security Analyzer dan SonarQube for IDE, pemindaian statis, klasifikasi temuan berdasarkan OWASP dan CWE, refaktorisasi kode, serta validasi ulang. Hasil penelitian menunjukkan tiga kelompok risiko utama, yaitu penggunaan kredensial statis pada model dan pengujian otomatis, kelemahan kriptografi akibat dependensi rentan, serta kurangnya pengendalian konfigurasi keamanan. Mitigasi dilakukan melalui pemindahan rahasia ke environment variable, hashing dinamis, pembaruan dependensi, dan validasi ulang hingga panel pemindai menunjukkan kondisi clean state. Penelitian ini menegaskan bahwa integrasi SAST di IDE efektif sebagai kontrol awal untuk menurunkan risiko keamanan aplikasi pendidikan sebelum kode masuk ke repositori produksi. Kata Kunci: E-Raport, OWASP Top 10, SAST, Laravel, Shift-Left Security Abstract E-Raport applications process academic records, student identities, and assessment activities that require security controls from the earliest development stage. This study analyzes security weaknesses in the source code of a Laravel-based E-Raport application using the OWASP Top 10 perspective and Static Application Security Testing (SAST), then formulates practical mitigation steps for developers. The research applies a laboratory experiment based on the shift-left security workflow, consisting of code asset mapping, configuration of Snyk Security Analyzer and SonarQube for IDE, static scanning, classification of findings using OWASP and CWE, code refactoring, and rescanning for validation. The results reveal three major risk groups: hardcoded credentials in model and automated testing components, cryptographic weaknesses related to vulnerable dependencies, and insufficient security configuration control. Mitigation was performed by moving secrets into environment variables, applying dynamic hashing, upgrading dependencies, and validating the result until the scanner reported a clean state. The study confirms that IDE-integrated SAST is useful as an early control to reduce security risks in educational web applications before code is merged into production repositories. Keywords: E-Raport, OWASP Top 10, SAST, Laravel, Shift-Left Security]]>
Copyrights © 2026
