How it works • Getting-Started • API Inventory • API testing • Add Test • Join Discord community •
Akto is an instant, open source API security platform that takes only 60 secs to get started. Akto is used by security teams to maintain a continuous inventory of APIs, test APIs for vulnerabilities and find runtime issues. Akto offers coverage for all OWASP top 10 and HackerOne Top 10 categories including BOLA, authentication, SSRF, XSS, security configurations, etc. Akto's powerful testing engine runs variety of business logic tests by reading traffic data to understand API traffic pattern leading to reduced false positives. Akto can integrate with multiple traffic sources - burpsuite, AWS, postman, GCP, gateways, etc. Here is our public roadmap for this quarter.
Akto enables security and engineering teams to secure their APIs by doing three things:
Akto.demo.mp4
Step 1: Create inventory
Step 2: Run tests
Run the following commands to install Akto. You'll need to have curl and Docker installed in order to run the container..
- Clone the Akto repo by using this command
git clone https://github.com/akto-api-security/akto.git
- Go to the cloned directory
cd akto
- Run
docker-compose up -d
Please ensure the following for good security practices
-
Open inbound security rule for port 9090 only. And restrict the source CIDR to VPC CIDR or your IP only.
-
Use an EC2 from a private subnet -
a. This way, no one will be able to make an inbound request to your machine.
b. Ensure this private subnet has access to Internet so that outbound calls can succeed!
c. You might have to set up tunneling to access instance via VPN using
ssh -i pemfile ec2-user@vpn-public-instance -L 9090:private-instance:9090
d. In your browser, visit
http://private-instance:9090
-
Use an EC2 from a public subnet - please don't! If you still want to do this, you can skip 2.b and 2.c. Simply access your instance via
http://ip:9090
Akto is really powerful in Cloud deployment if you can provide your application's mirrored traffic (0 performance impact). You would also be able to schedule tests in CI/CD and invite more team members on the dashboard. For that, you should install Akto Enterprise edition available here. Read more about it here
- Install VSCode
- Install VSCode Dev Containers extension
- Windows: Docker Desktop 2.0+ on Windows 10 Pro/Enterprise. Windows 10 Home (2004+) requires Docker Desktop 2.3+ and the WSL 2 back-end.
- macOS: Docker Desktop 2.0+.
- Linux: Docker CE/EE 18.06+ and Docker Compose 1.21+.
Note: If using Docker Desktop, consider changing the memory allocation to 8 GB for better performance
- Open terminal
mkdir ~/akto_code
cd ~/akto_code
git clone https://github.com/akto-api-security/akto
- Open in VScode:
code akto
OpenJDK 8, node(v18.7.0+ link), npm(v8.15.0+), maven (v3.6.3 link), MongoDB (v5.0.3+ link)
mkdir ~/akto_code
cd akto_code
git clone https://github.com/akto-api-security/akto
Open a new terminal tab
cd ~
mkdir ~/akto_mongo_data
<path_to_mongo_folder>/bin/mongod --dbpath ~/akto_mongo_data
Open a new terminal tab
cd ~/akto_code/akto
cd apps/dashboard
npm install
npm run hot
Open a new terminal tab
cd ~/akto_code/akto
export AKTO_MONGO_CONN="mongodb://localhost:27017"
export DASHBOARD_MODE="local_deploy"
mvn clean install
mvn --projects :dashboard --also-make jetty:run -Djetty.port=9090
Open a new terminal tab
cd ~/akto_code/akto
cd apps/testing
export AKTO_MONGO_CONN="mongodb://localhost:27017"
mvn compile; mvn exec:java -Dexec.mainClass="com.akto.testing.Main"
- Open
localhost:9090
in your favourite browser - You will need to signup when logging in for the first time, next time onwards you can login
1. To debug front end, install Vue.js Chrome extension from [here](https://devtools.vuejs.org/guide/installation.html). 2. To debug backend, run the following before running web server - a. Set MAVEN_OPTS variable to enable debugging on your Java process
export MAVEN_OPTS="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8081, -Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.port=9010 -Dcom.sun.management.jmxremote.rmi.port=9010 -Dcom.sun.management.jmxremote.local.only=false -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false"
b. In Visual Studio code, click on any line number to set a breakpoint.
c. Attach the Java debugger from Run and Debug mode. If you are doing this for the first time, click on “Create launch.json file” and then “Add configuration”. Choose “Java: Attach process by ID” and save the file.
d. A list of running Java processes with show up. Select the web server process to attach the debugger
We welcome contributions to this project. Please read our CONTRIBUTING.md for more information on how to get involved.
This project is licensed under the MIT License.