Simple scheduling and queueing
npm install @stfsy/api-kitpackage.json to allow applications to enable or disable the tracing feature.
bash
npm i @stfsy/api-kit @discue/open-telemetry-tracing
`
$3
`bash
npm i @stfsy/api-kit @discue/open-telemetry-tracing@npm:@discue/open-telemetry-tracing-noop
`
Middlewares
By default, ten cross-cutting middlewares are configured. These build the foundation for a secure API.
- ✅ accessLog: Logs each incoming request to give insights about usage and response times
- ✅ bodyParser: Parses incoming JSON request bodies into a JavaScript objects
- ✅ contentType: Validates the incoming content type, if the request method implies a state change e.g. POST
- ✅ cors: Adds additional headers to the response to protect from cross-origin resource requests and data exposure
- ✅ defaultVersion: Allows to move clients to a different API version in case of e.g. security incidents
- ✅ htmlEncoder: Encodes HTML embedded in request and response payloads to mitigate XSS attacks
- ✅ normalizeRequest: Ensures request attributes are similar across requests e.g. removes a trailing slash
- ✅ securityHeaders: Adds additional security headers to the response to prevent common attacks and protect users and their data
- ✅ traceContext: Generates a random id per request and makes this id available to all application components
- ✅ upstreamCacheControl: Instructs proxy servers between the client and the API to not cache responses
Tracing
All http-endpoint, most of middleware and util components come with OpenTelemetry Tracing enabled
`txt
Traces give us the big picture of what happens when a request is made to an application. Whether your application is a monolith with a single database or a sophisticated mesh of services, traces are essential to understanding the full “path” a request takes in your application.
`
Traces allow for superior experience when it comes to troubleshooting, debugging, or just learning about an application. The screenshot below shows what the default instrumentation looks like.
!Screenshot of traces collected by Jaeger.
To enable tracing at runtime set the NODE_OPTIONS environment variable and require the file ./tracing/tracing.cjs, which is the entry point for tracing.
- NODE_OPTIONS=--require ./tracing/tracing.cjs
Why
Never has it been easier and cheaper to build and provide services, web applications to customers. Current cloud providers like Microsoft, Google, Amazon,
provide a high abstraction level and consumption-based pricing, which allow even individuals to compete with well-established service providers.
Although, the barrier for entering the market has been lowered, the demand for security has steadily increased. It is clear why: The internet has not only connected businesses and customers, or families and friends, but also hackers, and criminals. Thus, the need for security applications, infrastructure and service is as high as it has ever been.
This API starter kit provides a solid foundation for SaaS, Client/Server and API products. It provides out-of-the-box mitigations for the 10 OWASP risks for APIs:
- API1:2023 - Broken Object Level Authorization APIs tend to expose endpoints that handle object identifiers, creating a wide attack surface of Object Level Access Control issues. Object level authorization checks should be considered in every function that accesses a data source using an ID from the user.
- API2:2023 - Broken Authentication Authentication mechanisms are often implemented incorrectly, allowing attackers to compromise authentication tokens or to exploit implementation flaws to assume other user's identities temporarily or permanently. Compromising a system's ability to identify the client/user, compromises API security overall.
- API3:2023 - Broken Object Property Level Authorization This category combines API3:2019 Excessive Data Exposure and API6:2019 - Mass Assignment, focusing on the root cause: the lack of or improper authorization validation at the object property level. This leads to information exposure or manipulation by unauthorized parties.
- API4:2023 - Unrestricted Resource Consumption Satisfying API requests requires resources such as network bandwidth, CPU, memory, and storage. Other resources such as emails/SMS/phone calls or biometrics validation are made available by service providers via API integrations, and paid for per request. Successful attacks can lead to Denial of Service or an increase of operational costs.
- API5:2023 - Broken Function Level Authorization Complex access control policies with different hierarchies, groups, and roles, and an unclear separation between administrative and regular functions, tend to lead to authorization flaws. By exploiting these issues, attackers can gain access to other users’ resources and/or administrative functions.
- API6:2023 - Unrestricted Access to Sensitive Business Flows APIs vulnerable to this risk expose a business flow - such as buying a ticket, or posting a comment - without compensating for how the functionality could harm the business if used excessively in an automated manner. This doesn't necessarily come from implementation bugs.
- API7:2023 - Server Side Request Forgery Server-Side Request Forgery (SSRF) flaws can occur when an API is fetching a remote resource without validating the user-supplied URI. This enables an attacker to coerce the application to send a crafted request to an unexpected destination, even when protected by a firewall or a VPN.
- API8:2023 - Security Misconfiguration APIs and the systems supporting them typically contain complex configurations, meant to make the APIs more customizable. Software and DevOps engineers can miss these configurations, or don't follow security best practices when it comes to configuration, opening the door for different types of attacks.
- API9:2023 - Improper Inventory Management APIs tend to expose more endpoints than traditional web applications, making proper and updated documentation highly important. A proper inventory of hosts and deployed API versions also are important to mitigate issues such as deprecated API versions and exposed debug endpoints.
- API10:2023 - Unsafe Consumption of APIs Developers tend to trust data received from third-party APIs more than user input, and so tend to adopt weaker security standards. In order to compromise APIs, attackers go after integrated third-party services instead of trying to compromise the target API directly.
Use
$3
To run the API in single instance mode.
`bash
./scripts/run-api.sh
`
To run the API in clustered mode, mimicking a multi-instance mode.
`bash
./scripts/run-api-clustered.sh
`
$3
`bash
./scripts/test-api.sh
`
$3
`bash
./scripts/test-coverage.sh
``