Technology-Specific Secure Coding: Languages and Frameworks

Wiley extends secure coding into particular technologies and languages, including APIs, web frameworks and mobile systems. Memory problems, race conditions and deserialization illustrate why a general principle needs a context-specific implementation. It suits programmers who want to compare security concerns across stacks and avoid assuming that the same control behaves identically in every framework.

What you will learn

• Compare security concerns across languages and platforms.
• Explore API and framework-specific controls.
• Analyze race conditions, overflows and deserialization issues.

Who this suits

Intermediate learners familiar with programming and secure-coding foundations; this continuation is part two of Wiley’s published sequence.

Before you enroll

Practice in a course lab or an application you are authorized to test, using fictional accounts and sample data. Security tools and framework defaults change, so compare examples with current documentation. A passing exercise or AI-generated suggestion does not establish that an application is secure; explain the threat, the control and how you verified its behavior.

Coursera offers paid enrollment or subscription access. Check the enrollment screen for assessment and certificate terms, trials and any financial-aid options. Provider access terms can change; review them before paying.

Put it into practice

Choose one fictional feature implemented in two technology stacks. Compare the relevant security assumptions and explain a framework-specific setting or control that needs separate verification.

Source and review

This overview is based on the provider's published information, checked on 12 October 2026. It is an editorial assessment, not a claim that we completed the resource. Time filters are approximate study ranges; projects and exercises can take longer.

View the curriculum and current access options at Coursera.

How YellowCourse describes and checks learning resources.