Member Avatar for jay84

Hi,

Im a final year student who has to come up with a prject, as a result have come up with two ideas, but im not to sure how to start the project as well as what programs i may require or lanuages.

The 2 choices are: Building a sercure WAP M -Commerce Application, which includes interface design, implementation of the authentication process and research on mobile web services

OR

Profiling Security Threats with Honeypots, project plan is deploy a centralized database to collect the data and design user interface. Then using the user interface to summarize, profiling and report the threats.

  • 3 Contributors
  • 2 Replies
  • 107 Views
  • 17 Hours Discussion Span
  • Latest Post Latest Post by JJ___

Dani AI

Generated

Both options are workable, but pick by matching the project to what you need to demonstrate (skills, novelty, safety) and to what you can reliably build and test in the time you have. is juggling scope; prefers the honeypot route and is unsure. Below are practical trade-offs, concrete tech suggestions, and safety notes to help decide and plan.

If the goal is a modern mobile/web security project: treat it as a secure web app for mobile clients rather than legacy WAP. Build a responsive front end (HTML5/CSS/JS or a simple React/PWA), and a small API backend (Node/Express, Flask or Spring). Use TLS, token-based auth (OAuth2/JWT), input validation, server-side session controls, and automated security testing with tools such as OWASP ZAP. Deliverables: UI prototypes, an authentication module with documented threat model, test logs and a short pen-test summary. See OWASP Mobile Top Ten for current risks: OWASP Mobile Top Ten.

If the aim is attacker profiling and visualization: plan for isolated honeypot sensors (low-interaction to start) and a safe central logging pipeline. Use established honeypot projects (for example, Cowrie) and ship events to a searchable store (ELK stack or PostgreSQL). Build a dashboard that aggregates IPs, attack vectors, timestamps and geolocation, and include filters and automated summaries. Important cautions: keep honeypots fully sandboxed, prevent outbound abuse, anonymize any PII, and get institutional sign-off. Cowrie and ELK are mature building blocks: Cowrie, ELK stack.

Practical next steps: write a short scope (MVP), pick one testable feature to finish in week 1–2, and get supervisor approval—especially for honeypots because of legal/safety issues. Timebox learning (Docker, basic Linux, logging pipeline) and document all assumptions and containment controls in the final report.

Recommended Answers

All 2 Replies

Member Avatar for server_crash

I think I would go with honeypots. That could be an intersting project.

Member Avatar for JJ___

Can't decide either. :confused:

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.