• Question
Looking to order training but can't get a hold of anyone

Has anyone had trouble getting a hold of their account rep to purchase training? I have been trying since the 13th and customer service say I can only put in a ticket and wait. I did that and I still do not have any contact with the business/academic partner team.

Does anyone know a work around?

Thanks!

Tips: "on controls to mitigate attacks and software vulnerabilities" If You Come Across... Verify For...

1. Cross-Site Scripting (XSS)​

  • If you come across: User input fields (like comments or search bars)
    • Verify for:
      • Reflected XSS: Injecting scripts in the input to see if they are executed in the user's browser.
      • Persistent XSS: Checking if scripts are stored on the server and reflected back to users.
    • Prevention: Implement input validation, output encoding, and Content Security Policy (CSP).

2. Overflow Vulnerabilities​

  • If you come across: User input or data handling that may exceed allocated memory
    • Verify for:
      • Buffer Overflow: Sending oversized inputs to trigger memory corruption.
      • Integer Overflow: Providing inputs that exceed maximum integer values.
      • Heap Overflow: Manipulating dynamic memory allocation to corrupt memory.
      • Stack Overflow: Causing the call stack to exceed its limit.
    • Prevention: Use safe coding practices, input validation, and memory management techniques.

3. Data Poisoning​

  • If you come across: User-modifiable data inputs
    • Verify for: Manipulating data to affect the application's behavior or outcomes.
    • Prevention: Validate inputs and implement strong data integrity checks.

4. Broken Access Control​

  • If you come across: User permissions or roles within the application
    • Verify for: Accessing restricted resources or functions without proper authorization.
    • Prevention: Enforce strict role-based access control (RBAC) and regularly audit access permissions.

5. Cryptographic Failures​

  • If you come across: Data stored or transmitted securely (e.g., passwords, personal data)
    • Verify for: Weak encryption algorithms or improper key management.
    • Prevention: Use strong encryption protocols and ensure proper key storage and lifecycle management.

6. Injection Flaws​

  • If you come across: Input fields that interact with databases or APIs
    • Verify for:
      • SQL Injection: Manipulating SQL queries through input fields.
      • Command Injection: Executing arbitrary commands on the server.
    • Prevention: Use parameterized queries, prepared statements, and input validation.

7. Cross-Site Request Forgery (CSRF)​

  • If you come across: Forms that perform state-changing actions
    • Verify for: Unauthenticated requests being accepted by the application.
    • Prevention: Implement anti-CSRF tokens and validate the origin of requests.

8. Directory Traversal​

  • If you come across: File upload or retrieval functions
    • Verify for: Accessing restricted directories using path traversal techniques.
    • Prevention: Validate and sanitize file paths and restrict access to sensitive directories.

9. Insecure Design​

  • If you come across: Flaws in the application's architecture
    • Verify for: Design weaknesses that expose the application to various attacks.
    • Prevention: Follow secure design principles and perform threat modeling.

10. Security Misconfiguration​

  • If you come across: Default settings in applications or services
    • Verify for: Misconfigured security settings or unused features being enabled.
    • Prevention: Regularly review and harden security configurations, and conduct security audits.

11. End-of-Life or Outdated Components​

  • If you come across: Use of libraries or software that are no longer supported
    • Verify for: Known vulnerabilities associated with outdated components.
    • Prevention: Regularly update and patch software components and replace end-of-life software.

12. Identification and Authentication Failures​

  • If you come across: Login or authentication mechanisms
    • Verify for: Weak password policies, account enumeration, or failure to implement multi-factor authentication.
    • Prevention: Enforce strong password policies and implement multi-factor authentication.

13. Server-Side Request Forgery (SSRF)​

  • If you come across: Applications making backend requests based on user input
    • Verify for: Manipulating requests to access internal services.
    • Prevention: Validate and sanitize user inputs, and restrict server-side requests.

14. Remote Code Execution (RCE)​

  • If you come across: User inputs that are executed by the server
    • Verify for: Ability to execute arbitrary code on the server.
    • Prevention: Validate all inputs and use language features to limit code execution.

15. Privilege Escalation​

  • If you come across: Role or permissions settings
    • Verify for: Users gaining unauthorized access to higher privilege levels.
    • Prevention: Implement the principle of least privilege and regularly review user roles.

16. Local File Inclusion (LFI) / Remote File Inclusion (RFI)​

  • If you come across: File inclusion functionalities
    • Verify for: Ability to include local or remote files that could compromise the application.
    • Prevention: Validate and sanitize file paths and restrict the inclusion of sensitive files.

SHARE WITH US YOUR TIPS

Data Analytics Pathway - certification renewal

Has anyone heard if CompTIA plans to give full or partial credit for CEU renewal by passing a higher-level CompTIA data analytics certification?

Will DataSys+ give full or partial credit for CEUs for Data+?

Will DataX give full or partial credit for CEUs for DataSys+ and/or Data+?

CompTIA Cloud+ Resource List

I've put together a curated list of free and paid resources to help us prepare our students for the CompTIA Cloud+ CV0-004 exam. It includes links to valuable labs, courses, and reading materials. Feel free to check it out and share with your classes!

Attachments

  • CompTIA Cloud.pdf
    244 KB · Views: 84

Difficulty accessing Instructor resources

Hey there, CINners!

I'm running into some trouble accessing the Instructor Resources, for the Test Out Office Pro. I tried accessing them, but it 'refuses to connect'. It doesn't seem to be an internet issue.

Any suggestions or help would be greatly appreciated! Thanks in advance.

Attachments

  • Teaching Aids error.JPG
    Teaching Aids error.JPG
    22.7 KB · Views: 17
  • Teaching Aids 1.JPG
    Teaching Aids 1.JPG
    28.3 KB · Views: 17

Problem with PBQ for CertMaster Learn A+ Core 2?

Hi there

Just out of curiosity, is anyone else getting this error message for the PBQ titled, "Core 2 PBQ: Supporting OS/App Installations Performance-based Question"

I've tried contacting CompTIA Customer Care but received the general "clear your cookies and cache" response. A few of my students have also brought this to my attention so I'm wondering if this is affecting all users.

PBQ Error.jpg
  • Like
Reactions: precious

Addressing the Skills Gap: Bridging Theory and Practice in IT Education

One challenge we face as instructors is bridging the gap between theoretical knowledge and real-world IT skills. For example, students might excel in simulations but struggle with hands-on troubleshooting in real environments. How do you address this skills gap in your courses? I’ve incorporated more real-world scenarios into labs, but I’m curious about other techniques.

ChatGPT Privacy: What You Need to Know Before You Type

ChatGPT’s Footer​

In a recent ChatGPT session, I noticed the footer “Don’t share sensitive info. Chats may be reviewed and used to train our models. Learn more.” Not sure if they recently added it, or if our ChatGPT friends have put that there from the beginning. Regardless, I am writing about sharing sensitive information in AI prompts today. My example is of ChatGPT but I feel this advice applies to all AI interactions.
AI numbers moving through the brain.gif

Why You Should Keep Personal Info Out of ChatGPT, and All AI Engines​

Keep ePHI (electronic protected health information) out of AI prompts.
When using ChatGPT or any AI engine, it’s important to be careful about what information you share. You should avoid putting personal details or health information in your prompts. This helps protect your privacy and keeps sensitive data safe. ChatGPT uses the information you give it to create responses. While the company behind ChatGPT, OpenAI, says they try to keep data private, that is a beautiful plan IMO. Here’s why:

  1. Your conversations might be reviewed by AI trainers to improve the system.
  2. De-identified information could be used for research.
  3. There’s a chance your input could appear in responses to other users.
OpenAI encrypts the data you enter, but they don’t sign special agreements to protect health information (ePHI). This means it’s best to assume anything you type into ChatGPT could potentially be seen by others.

Protecting Your Privacy When Using ChatGPT​

To use AI engines safely:
  • Don’t enter any personal details like names, addresses, or phone numbers.
  • Avoid sharing health information or financial data.
  • Be careful not to include details that could identify you or others.
  • Remember that deleting prompts later isn’t always possible for regular users.
If you’re using ChatGPT for work, especially in healthcare or finance, it’s extra important to follow these guidelines. Your company might have rules about what information can be shared with outside services.

By being careful about what you share, you can enjoy using AI while keeping your personal information secure. It’s always better to be safe than sorry when it comes to protecting private data online.

More​

AI ain’t so tough. See https://cybersafetynet.net/category/ai/ to help understand and use Artificial intelligence.

With CompTIA rebranding CASP+ & ITF, will they also rebrand A+?

With Comptia rebranding the CASP+ exam to the SecurityX exam, (with the feedback being questionable at best, as per Login to view embedded media , Login to view embedded media , and Login to view embedded media ), and ITF being rebranded as Tech+ ( https://www.comptia.org/blog/comptia-tech-vs-comptia-itf-for-it-basics-whats-the-difference), is it time for the CompTIA A+ course to be rebranded CompTIA ITsupport+? or Support+?

I know the A+ has been around for ~30years, and has a history, but the A+ description doesn't really explain what the course does... with the other fundamentals being about Networking and Security, changing the A+ certification to be more descriptive of what the course covers, might make it more recognizable to HR recruiters and IT managers.

Just something to ponder
  • Like
Reactions: precious

Network+ N10-009 - Course Pacing

Hello CIN Team,

Firstly, thank you Stephen and Don for a fantastic TTT series. I really enjoyed it.

I finally got my hands on the instructor resources for this new version of Network+ and I was looking at the pacing guide. I'm interested in the 5 day pacing which is what my academy is delivering courses to. I noticed that the 5 day sheet in the pacing guide has you doing 20 hour per day for 5 days :) I also noted that there were around 160 short labs for the learners to do which aren't part of the pacing. I thought the latest Sec+ (701) planner did a pretty good job of breaking things out into what to do in class and how to pace over 5 days. Does anyone have any recommendation on teaching over 5 days or is there a better planner in the works somewhere ?

Thanks
Rasheed

Filter