Contact person: Finite Automaton Intrusion Prototype

Phone:Show

Email:Show

Location: Auroville, India

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"I need a working prototype that demonstrates how a finite automaton can monitor incoming HTTP traffic and raise a flag after three consecutive GET requests (S0 → S1 → S2 → S3). Any non-GET request must reset the automaton back to S0, exactly as specified.

The build should include a simple banking public login page that every visitor uses. A small “Admin” toggle in one corner must redirect to a separate portal that only I can access. From that dashboard I must be able to:
• view real-time and historical login events,
• see every moment the automaton hits S3 (attack detected) together with timestamp and IP,
• reset the main consumer login flow with a single click.
and so can check the account is in login or off

Technical preferences and priorities
• First milestone: deliver the finite automaton logic, fully testable through Postman (or any comparable REST client) so I can watch the state changes.
• Backend language and web framework are flexible, but store all events in a MySQL database.
• Front-end can be good as well—just enough HTML/CSS/JS to log in, flip to Admin, and show tables or charts of activity.
• Clean API endpoints for login, state transition logging, and admin queries.

Acceptance checks
1. Posting three consecutive GET requests through Postman must surface an “attack” entry in the admin view.
2. Any non-GET request immediately returns the automaton to S0.
3. Unauthorized users who try the admin URL are redirected to the public login page.
4. All records persist in MySQL and survive server restarts.

Once the automaton logic is solid we can iterate on UI polish, additional analytics, or containerization, but the above items form the initial scope.
mainly :first analyze my problem statement A finite automaton can track user request patterns to detect three consecutive GET requests. It uses states like S0 → S1 → S2 → S3, each transition triggered by a GET request, resetting on other inputs. Reaching state S3 indicates a potential misuse or abnormal pattern. Such automata help in intrusion detection and rate-limiting mechanisms. and in this i have an criteria i have a thing that need to use formal language automata and computer network and front end ,backend and database connection and postman or flash anything to triggeration i need it like prototype and i need one common page for all user to logging in and at corner admin toggle should be there i need to be redirected if i clicked there but the admin portal can be only accessed by me in that i can see the login history attacks reached and from where and reset option of the main portal login of common consumer" (client-provided description)