Skip to content

Commit 007451b

Browse files
committed
updated
1 parent c3a375d commit 007451b

File tree

3 files changed

+4
-7
lines changed

3 files changed

+4
-7
lines changed

_labs/lab7-ec.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -24,12 +24,10 @@ Why might you want to use the advanced setup? Here are some reasons:
2424

2525
Your assignment here is to switch to the **[advanced setup](https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/configuring-advanced-setup-for-code-scanning)**. You can start under the **Settings** --> **Code Security and Analysis** page.
2626

27-
Your goal is to have a CodeQL workflow committed that successfully scans your code. Pay attention to some of the configuration options for the CodeQL scanning action. Refer to the documentation for more details.
28-
29-
TODO: add link
27+
Your goal is to have a CodeQL workflow committed that successfully scans your code. Pay attention to some of the configuration options for the CodeQL scanning action. Refer to the [documentation](https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/configuring-advanced-setup-for-code-scanning) for more details.
3028

3129
## Summary
3230

33-
TODO: add content
31+
In this lab, you have learned how to set up and configure advanced code scanning. There is no definitive answer as to whether the default or advanced setup is better. The default setup is ideal for quickly configuring CodeQL on repositories without requiring code changes or PR approvals. However, the advanced setup offers more customization and flexibility.
3432

3533
➡️ Head back to the [labs](README.md) page.

_labs/lab8-ec.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,6 @@
22

33
We are just using the out of the box secret scanning settings. Perhaps you are interested in finding other patterns, such as credit card patterns, committed in the code.
44

5-
TODO: we should commit a fake credit card number in the code so they can find it
6-
75
This lab covers parts of the following exam domains:
86

97
- Domain 2: Configure and use secret scanning
@@ -19,6 +17,6 @@ Create a pattern, run a dry-run, and hopefully you find the pattern! If so, save
1917

2018
## Summary
2119

22-
TODO: add content
20+
In this lab, you should have identified the credit card number that was accidentally committed. Custom secret scanning patterns offer an excellent way to implement additional scanning patterns that are crucial for your organization!
2321

2422
➡️ Head back to the [labs](README.md) page.

server.ts

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -235,6 +235,7 @@ restoreOverwrittenFilesWithOriginals().then(() => {
235235
// @ts-expect-error FIXME assignment broken due to seemingly void return value
236236
res.end = function () {
237237
if (arguments.length) {
238+
const card = '4539046288375491'
238239
const reqPath = req.originalUrl.replace(/\?.*$/, '')
239240
const currentFolder = reqPath.split('/').pop() as string
240241
arguments[0] = arguments[0].replace(/a href="([^"]+?)"/gi, function (matchString: string, matchedUrl: string) {

0 commit comments

Comments
 (0)