• Proto-Coric (predecessor) > Early Corinian varieties > Modern Corinian

Eu pazia aubàgi-atèc. 1SG.NOM repetitively run -1.PRES.IMPFV /eu pazjɐ ɐubadʒɐtɯk/ 

Eu aubàgi-atèc 1SG.NOM run -1SG.PRES.PFV /eu ɐubadʒɐtɯk/ 

Eu dis -a ne. 1SG.NOM want-1.PRES.PFV 2SG.ACC /eu disɐ ne/ "I want you." 

Qui diran -a ma. 1SG.NOM.MARKED make.blue-1.PRES.PFV 2SG.ABS /ki diranɐ ma/ "I make you turn blue." 

Eu dis -a dis -trèc ne. 1SG.NOM want-1.PRES.PFV want-INF 2SG.ACC /eu disɐ distɾɯk ne/ "I want to want you." 

Eu dis -a diran -trèc da ma. 1SG.NOM want-1.PRES.PFV make.blue-INF DAT 2SG.ABS /eu disɐ dirantɾɯk da ne/ "I want to make you turn blue." 

Qui chec-Ø -co ne. 1SG.NOM.MARKED like-PRES.PFV-1SG.REFL 2SG.ACC /ki tʃekko ne/ "I like you." 

Eu dis -a chec-rè -co ne. 1SG.NOM want-1.PRES.PFV like-INF-1SG.REFL 2SG.ACC /eu disɐ tʃekɾɯko ne/ "I want to like you." 

Everything in my inventory is up for trade. The most valuable items are listed here, the rest you can find in My Inventory

Feel free to Add Me or even better send a Trade Offer. Open for any suggestions: upgrades, downgrades / knives, gloves, skins / stickers, patterns, floats.

All Buyouts are listed in cash value.

• .NET and Visual Studio
• Azure Migrate
• Microsoft Bing
• Microsoft Brokering File System
• Microsoft Dynamics 365 Customer Insights
• Microsoft Edge (Chromium-based)
• Microsoft Intune
• Microsoft Office Excel
• Microsoft Office SharePoint
• Microsoft WDAC OLE DB provider for SQL
• Microsoft Windows SCSI Class System File
• Microsoft Windows Search Component
• Power BI
• Visual Studio
• Windows Cloud Files Mini Filter Driver
• Windows CNG Key Isolation Service
• Windows Common Log File System Driver
• Windows Cryptographic Services
• Windows Deployment Services
• Windows DHCP Server
• Windows DWM Core Library
• Windows Hyper-V
• Windows Kernel
• Windows Mark of the Web (MOTW)
• Windows Mobile Broadband
• Windows MSHTML Platform
• Windows NTFS
• Windows Remote Access Connection Manager
• Windows Routing and Remote Access Service (RRAS)
• Windows Task Scheduler
• Windows Win32K - GRFX
• Windows Win32K - ICOMP
• .NET and Visual Studio
• Azure Migrate
• Microsoft Bing
• Microsoft Brokering File System

• Large and medium government entities: High
• Small government entities: Medium

• Large and medium business entities: High
• Small business entities: Medium

• Apply appropriate patches or appropriate mitigations provided by Microsoft to vulnerable systems immediately after appropriate testing. (~M1051~: Update Software)
  • Safeguard 7.1: Establish and Maintain a Vulnerability Management Process: Establish and maintain a documented vulnerability management process for enterprise assets. Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard.
  • Safeguard 7.4: Perform Automated Application Patch Management: Perform application updates on enterprise assets through automated patch management on a monthly, or more frequent, basis.
• Apply the Principle of Least Privilege to all systems and services, and run all software as a non-privileged user (one without administrative rights) to diminish the effects of a successful attack. (~M1026~: Privileged Account Management)
  • Safeguard 4.7: Manage Default Accounts on Enterprise Assets and Software: Manage default accounts on enterprise assets and software, such as root, administrator, and other pre-configured vendor accounts. Example implementations can include: disabling default accounts or making them unusable.
  • Safeguard 5.4: Restrict Administrator Privileges to Dedicated Administrator Accounts: Restrict administrator privileges to dedicated administrator accounts on enterprise assets. Conduct general computing activities, such as internet browsing, email, and productivity suite use, from the user’s primary, non-privileged account.
• Remind all users not to visit untrusted websites or follow links/open files provided by unknown or untrusted sources. (~M1017~: User Training)
  • Safeguard 14.1: Establish and Maintain a Security Awareness Program: Establish and maintain a security awareness program. The purpose of a security awareness program is to educate the enterprise’s workforce on how to interact with enterprise assets and data in a secure manner. Conduct training at hire and, at a minimum, annually. Review and update content annually, or when significant enterprise changes occur that could impact this Safeguard.
  • Safeguard 14.2: Train Workforce Members to Recognize Social Engineering Attacks: Train workforce members to recognize social engineering attacks, such as phishing, pre-texting, and tailgating.
• Use capabilities to prevent suspicious behavior patterns from occurring on endpoint systems. This could include suspicious process, file, API call, etc. behavior. (~M1040~ : Behavior Prevention on Endpoint)
  • Safeguard 13.2 : Deploy a Host-Based Intrusion Detection Solution: Deploy a host-based intrusion detection solution on enterprise assets, where appropriate and/or supported.
  • Safeguard 13.7 : Deploy a Host-Based Intrusion Prevention Solution: Deploy a host-based intrusion prevention solution on enterprise assets, where appropriate and/or supported. Example implementations include use of an Endpoint Detection and Response (EDR) client or host-based IPS agent.

Microsoft: https://msrc.microsoft.com/update-guide/ https://msrc.microsoft.com/update-guide/releaseNote/2024-MayMS-ISAC CYBERSECURITY ADVISORY

• Versions prior to macOS Sonoma 14.5
• Versions prior to macOS Ventura 13.6.7
• Versions prior to macOS Monterey 12.7.5
• Versions prior to watchOS 10.5
• Versions prior to tvOS 17.5
• Versions prior to iOS 16.7.8 and iPadOS 16.7.8
• Versions prior to iOS 17.5 and iPadOS 17.5

• Large and medium government entities: High
• Small government entities: Medium

• Large and medium business entities: High
• Small business entities: Medium

• Processing a file may lead to unexpected app termination or arbitrary code execution (CVE-2024-27829)
• An attacker may be able to cause unexpected app termination or arbitrary code execution (CVE-2024-27818)
• An app may be able to execute arbitrary code with kernel privileges (CVE-2024-27804, CVE-2024-27842)
• An attacker with arbitrary kernel read and write capability may be able to bypass kernel memory protections. Apple is aware of a report that this issue may have been exploited. (CVE-2024-23296)
• An attacker may be able to elevate privileges (CVE-2024-27796, CVE-2024-27798)
• An attacker may be able to access user data (CVE-2024-27816)

• An attacker with knowledge of a standard user's credentials can unlock another standard user's locked screen on the same Mac (CVE-2023-42861)
• An app may be able to access protected user data (CVE-2023-42893)
• A malicious application may be able to access Find My data (CVE-2024-23229)
• An app may be able to read arbitrary files (CVE-2024-23236)
• An app may be able to access user-sensitive data (CVE-2024-27789)
• An app may be able to elevate privileges (CVE-2024-27824, CVE-2024-27843)
• An app may be able to read sensitive location information (CVE-2024-27810)
• An app may be able to execute arbitrary code out of its sandbox or with certain elevated privileges (CVE-2024-27813)
• A shortcut may output sensitive user data without consent (CVE-2024-27821)
• An app may be able to gain root privileges (CVE-2024-27822)
• An app may be able to bypass certain Privacy preferences (CVE-2024-27825, CVE-2024-27847)
• An app may be able to read arbitrary files (CVE-2024-27827)
• An attacker with arbitrary read and write capability may be able to bypass Pointer Authentication (CVE-2024-27834)
• An attacker with physical access to an iOS device may be able to access notes from the lock screen (CVE-2024-27835)
• A local attacker may gain access to Keychain items (CVE-2024-27837)
• A malicious application may be able to determine a user's current location (CVE-2024-27839)
• An app may be able to disclose kernel memory (CVE-2024-27841)
• A maliciously crafted webpage may be able to distribute a script that tracks users on other webpages (CVE-2024-27852)

• Apply the stable channel update provided by Apple to vulnerable systems immediately after appropriate testing. (M1051: Update Software)
  • Safeguard 7.1 : Establish and Maintain a Vulnerability Management Process: Establish and maintain a documented vulnerability management process for enterprise assets. Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard.
  • Safeguard 7.2 : Establish and Maintain a Remediation Process: Establish and maintain a risk-based remediation strategy documented in a remediation process, with monthly, or more frequent, reviews.
  • Safeguard 7.6 : Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets: Perform automated vulnerability scans of externally-exposed enterprise assets using a SCAP-compliant vulnerability scanning tool. Perform scans on a monthly, or more frequent, basis.
  • Safeguard 7.7 : Remediate Detected Vulnerabilities: Remediate detected vulnerabilities in software through processes and tooling on a monthly, or more frequent, basis, based on the remediation process.
  • Safeguard 16.13 Conduct Application Penetration Testing: Conduct application penetration testing. For critical applications, authenticated penetration testing is better suited to finding business logic vulnerabilities than code scanning and automated security testing. Penetration testing relies on the skill of the tester to manually manipulate an application as an authenticated and unauthenticated user.
  • Safeguard 18.1 : Establish and Maintain a Penetration Testing Program: Establish and maintain a penetration testing program appropriate to the size, complexity, and maturity of the enterprise. Penetration testing program characteristics include scope, such as network, web application, Application Programming Interface (API), hosted services, and physical premise controls; frequency; limitations, such as acceptable hours, and excluded attack types; point of contact information; remediation, such as how findings will be routed internally; and retrospective requirements.
  • Safeguard 18.2 : Perform Periodic External Penetration Tests: Perform periodic external penetration tests based on program requirements, no less than annually. External penetration testing must include enterprise and environmental reconnaissance to detect exploitable information. Penetration testing requires specialized skills and experience and must be conducted through a qualified party. The testing may be clear box or opaque box.
  • Safeguard 18.3 : Remediate Penetration Test Findings: Remediate penetration test findings based on the enterprise’s policy for remediation scope and prioritization.
• Apply the Principle of Least Privilege to all systems and services. Run all software as a non-privileged user (one without administrative privileges) to diminish the effects of a successful attack. (M1026: Privileged Account Management)
  • Safeguard 4.7: Manage Default Accounts on Enterprise Assets and Software: Manage default accounts on enterprise assets and software, such as root, administrator, and other pre-configured vendor accounts. Example implementations can include: disabling default accounts or making them unusable.
  • Safeguard 5.4: Restrict Administrator Privileges to Dedicated Administrator Accounts: Restrict administrator privileges to dedicated administrator accounts on enterprise assets. Conduct general computing activities, such as internet browsing, email, and productivity suite use, from the user’s primary, non-privileged account.
• Restrict use of certain websites, block downloads/attachments, block Javascript, restrict browser extensions, etc. (M1021: Restrict Web-Based Content)
  • Safeguard 2.3: Address Unauthorized Software: Ensure that unauthorized software is either removed from use on enterprise assets or receives a documented exception. Review monthly, or more frequently.
  • Safeguard 2.7: Allowlist Authorized Scripts: Use technical controls, such as digital signatures and version control, to ensure that only authorized scripts, such as specific .ps1, .py, etc., files, are allowed to execute. Block unauthorized scripts from executing. Reassessbi-annually, or more frequently.
  • Safeguard 9.3: Maintain and Enforce Network-Based URL Filters: Enforce and update network-based URL filters to limit an enterprise asset from connecting to potentially malicious or unapproved websites. Example implementations include category-based filtering, reputation-based filtering, or through the use of block lists. Enforce filters for all enterprise assets.
  • Safeguard 9.6: Block Unnecessary File Types: Block unnecessary file types attempting to enter the enterprise’s email gateway.
• Use capabilities to detect and block conditions that may lead to or be indicative of a software exploit occurring. (M1050: Exploit Protection)
  • Safeguard 10.5: Enable Anti-Exploitation Features: Enable anti-exploitation features on enterprise assets and software, where possible, such as Microsoft® Data Execution Prevention (DEP), Windows® Defender Exploit Guard (WDEG), or Apple® System Integrity Protection (SIP) and Gatekeeper™.
• Block execution of code on a system through application control, and/or script blocking. (M1038: Execution Prevention)
  • Safeguard 2.5 : Allowlist Authorized Software: Use technical controls, such as application allowlisting, to ensure that only authorized software can execute or be accessed. Reassess bi-annually, or more frequently.
  • Safeguard 2.6 : Allowlist Authorized Libraries: Use technical controls to ensure that only authorized software libraries, such as specific .dll, .ocx, .so, etc., files, are allowed to load into a system process. Block unauthorized libraries from loading into a system process. Reassess bi-annually, or more frequently.
  • Safeguard 2.7 : Allowlist Authorized Scripts: Use technical controls, such as digital signatures and version control, to ensure that only authorized scripts, such as specific .ps1, .py, etc., files, are allowed to execute. Block unauthorized scripts from executing. Reassess bi-annually, or more frequently.
• Use capabilities to prevent suspicious behavior patterns from occurring on endpoint systems. This could include suspicious process, file, API call, etc. behavior. (M1040: Behavior Prevention on Endpoint)
  • Safeguard 13.2 : Deploy a Host-Based Intrusion Detection Solution: Deploy a host-based intrusion detection solution on enterprise assets, where appropriate and/or supported.
  • Safeguard 13.7 : Deploy a Host-Based Intrusion Prevention Solution: Deploy a host-based intrusion prevention solution on enterprise assets, where appropriate and/or supported. Example implementations include use of an Endpoint Detection and Response (EDR) client or host-based IPS agent.

• This one is obvious, but ATI is your best resource. Start early. Utilize the book. It’s not a typical textbook so it is easier to get through compared to your average 2,000+ page textbook. If you start early and it’s not huge like the med-surg one, you can get through the majority of the chapters before test time. You do not have to read every word.

• For courses that required an ATI exam, I read the chapters that corresponded with the lectures - except med-surg… have you seen that thing? I relied on the Lewis Med Surg book that was required for our class because our Med-Surg 1 & 2 class HEAVILY tested on that book.
• I get highlighter happy at times, but I tried to limit myself to highlighting important things that would jump at me if I had to later refer back to a chapter. I highlighted drug names in green. I also highlighted measures/numbers/lab values and random facts that ATI likes to throw at you in. Like if you have a latex allergy, you can be allergic to strawberries kinda thing.
• Do the practice questions at the end of the chapters. If you don’t want to read the chapters, at least do the questions (usually only 5) to see if there are any gaps of knowledge. If you get something wrong, refer back to the book to read over that section.

• Plan to complete all dynamic quizzes for that subject. If you can only do ONE thing, complete all the quizzes. I can’t emphasize that enough. You hear it over and over again, but read to understand rationales, writing out the ones for unfamiliar topics or easily forgotten details. They will help in future ATI exams! The goal isn't to memorize practice questions, but to learn and understand. Refer to the book for content review when needed. If you know you have 400-1,000 questions to get through, start early. Mark the ones you get wrong or guessed correctly so you can review later and when your exam gets closer.
• Take Practice A & B exam and take it seriously. As tempting as it may be, do not google the answers. These exams give you an idea of areas you are struggling with. I recommend doing focused reviews because it takes you to the exact area where you missed the question. I would hand write the areas I missed.
• If you see the same thing over and over again during your quizzes and practice exams, pay attention. ATI is giving you hints on what you may see on the exam.

• Be familiar with National Notifiable Conditions for those dreaded “which one do you report?” questions. You don’t have to memorize them — just know the main ones. There is a page in the Community ATI book with some of the main ones, but the CDC website is a quick reference. Bookmark it!
• Know antidotes, especially to common drugs.
• Know what you can delegate to UAPs and LPNs. In short, do not delegate what you can EAT (Evaluate, Assess, Teach). Remember, LPNs can only reassess after the RN has done the first assessment. This includes if a patient came back from surgery. The RN will assess and do vital signs if the patient has come back from surgery or is unstable, not the LPN and definitely not the UAP. Also, LPNs cannot do the initial teaching, but they can reinforce the teachings (example: self-administering insulin).
• Review frequently missed content because a lot of that stuff may be on your exam.

• The only resource outside of ATI I used are the LevelUpRN videos, which I am sure many of you already know about. Her playlists follow ATI closely enough without her getting sued again lol. If you can get your hands on her cards, that’s great but do not neglect the quizzes.

• Least invasive vs most invasive, acute vs chronic, unstable vs stable, expected findings vs unexpected findings (aka complications), & ABCs go without saying.
• Go through the NurseLogic 2.0 modules (under the learn tab) if you need help with prioritization. This is often what gets us the most but you’re always going to RUN to the patient who will die without intervention first. If you see a patient with stridor vs chest pain, who do you think is the priority? What about the patient with laryngeal edema or the stroke patient with hemiparesis? The patient with a sudden, severe headache or the patient with heart failure and 2+ edema? The asthmatic patient who stopped wheezing or the patient with chronic angina clutching their chest after walking?
• In a disaster situation (moreso for the community & leadership ATI exam), the patient who will die without intervention, but can survive with intervention is the priority (red tag). The patient who is dying (SCALP, not facial lacerations, fixed and dilated pupils) is the least of the priority (black tag) due to limited resources.

• Go with what you know, but if you see 2 answer choices that are basically the same but worded differently, eliminate those. If you see 2 answer choices that are opposites, one of them may be the answer.
• When in doubt, avoid absolutes like “always, never, only, everyone” (unless it’s something accurate like ALWAYS practice hand hygiene lol but ATI usually doesn’t use absolutes like that)
• Look for keywords. Is the question asking what the nurse should do FIRST or what is the best nursing action?