◆ C#

Monitor audit log activities

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts
See the prompt↓All C# tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskReview the audit logs for the 'Customer Data Platform' from the last 24 hours. Specifically,…+
Review the audit logs for the 'Customer Data Platform' from the last 24 hours. Specifically, look for any unauthorized access attempts, changes to user permissions, or data export activities, and flag anything suspicious for immediate investigation.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I present these audit log findings to the security team, make it easy for them to see…+
Before I present these audit log findings to the security team, make it easy for them to see the critical events. Group all failed login attempts by user, highlight any changes to admin roles, and flag any activity that deviates significantly from normal operational patterns, so they can quickly assess the risk.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI just received an alert about an unusual number of failed login attempts on a dormant admin…+
I just received an alert about an unusual number of failed login attempts on a dormant admin account.
I just received an alert about an unusual number of failed login attempts on a dormant admin account for the 'Billing Service' from an IP address outside our usual range. I'm afraid this could be a sophisticated attack, but I can't tell if it's a brute-force attempt or a targeted effort. What's the immediate diagnosis, and what's the best first step to contain this without causing a panic or alerting a potential attacker?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep getting overwhelmed by the sheer volume of audit log alerts, making it hard to spot…+
I keep getting overwhelmed by the sheer volume of audit log alerts, making it hard to spot actual threats.
I keep getting overwhelmed by the sheer volume of audit log alerts, making it hard to spot actual threats amidst the noise. It feels like I'm constantly chasing false positives instead of focusing on real risks. What habit should I change to more effectively filter and prioritize audit log activities, so I can respond to genuine threats faster and reduce alert fatigue?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from C#'s own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.